Cisco,Certification,Introducti computer Cisco Certification: An Introduction To Multilayer Switchin
Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc ----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a
Sure, you have to know all about SVIs and multilayer switching to earn your CCNP, but you also need to know about them because theyre so commonplace in todays networks! Why? We can use an SVI to allow inter-VLAN communication on a multilayer switch, eliminating the need for a separate router to get involved.In this example, we have Host_1 in VLAN 11 and Host_3 in VLAN 33. Before we begin configuring, we'll send pings between the two hosts. (Well use Cisco routers for the hosts in this lab, which is why the ping output may look familiar!)HOST_1#ping 30.1.1.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 30.1.1.1, timeout is 2 seconds:.....Success rate is 0 percent (0/5)HOST_3#ping 20.1.1.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 20.1.1.1, timeout is 2 seconds:.....Success rate is 0 percent (0/5)As we expect, theres no IP connectivity between the hosts. Assuming the appropriate switch ports are already placed in VLAN 11 and VLAN 33, well now create two switched virtual interfaces on this multilayer switch. One will represent VLAN 33, and the other will represent VLAN 11.SW1(config)#int vlan1101:30:04: %LINK-3-UPDOWN: Interface Vlan11, changed state to up01:30:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan11, changed state to upSW1(config-if)#ip address 20.1.1.11 255.255.255.0SW1(config-if)#int vlan3301:30:11: %LINK-3-UPDOWN: Interface Vlan33, changed state to up01:30:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan33, changed state to upSW1(config-if)#ip address 30.1.1.11 255.255.255.0At this point, weve still got a problem when we look at the routing table.SW1# show ip routeDefault gateway is not setHost Gateway Last Use Total Uses InterfaceICMP redirect cache is emptyThe problem is that we dont have a routing table, because IP routing is off by default on a multilayer switch. Lets turn IP routing on and then check the routing table.SW1(config)#ip routingSW1(config)#^ZSW1#show ip routeGateway of last resort is not set20.0.0.0/24 is subnetted, 1 subnetsC 20.1.1.0 is directly connected, Vlan1130.0.0.0/24 is subnetted, 1 subnetsC 30.1.1.0 is directly connected, Vlan33Now were in good shape! The hosts need to have their default gateway set to the appropriate SVI IP address; here, Host_1 should have its gateway set to 20.1.1.11, and Host_3 to 30.1.1.11. After doing so, inter-VLAN communication is now in place, as shown by the ping output below.HOST_1#ping 30.1.1.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 30.1.1.1, timeout is 2 seconds: !!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 msHOST_3#ping 20.1.1.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 20.1.1.1, timeout is 2 seconds: !!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 msIn a future Cisco certification tutorial, well take a look at configuring a multilayer switch port as a routed port, and assign an IP address to that port. See you then!
Cisco,Certification,Introducti