Lab Switch Report

8/3/2019 Lab Switch Report

http://slidepdf.com/reader/full/lab-switch-report 1/7

Multi-Layer Switching, Routed and SVI Interfaces

Daniel Morgan

28th October, 2011

Mr. Pete Marino

Net 272 Lab 7



This lab covered several main topics involved in multilayer switching and a small portion of

routing protocols. The main focus used port manipulations and creating routed and SVI interfaces on

several layer 3 switches. This was all meshed together with inter-VLAN routing in the Distribution

switches which provided redundancy between the Core and the Access layer. This lab required at least4 multilayer switches, one router and 3 layer 2 switches along with 6 workstations. All connections ran

through Ethernet cables. All Layer 3 interfaces utilized EIGRP as the dynamic routing protocol with the

router working as an ISP whose loopback provided the final gateway. Full connectivity between theVLAN's 1,100,200,300 finalized the lab along with monitoring of routing, modified interfaces, and

traffic flow.

As far as the initial configuration went, it was pretty similar to previous ones. Although this wasa larger topology the setup remained relatively similar. Starting with connecting the devices with cross-

over cables between like devices and straight through for those leading to the workstations and router.

Al packets were encapsulated with Ethernet protocols. To improve efficiency the Core routers used an

aggregated EtherChannel connection with 2 links bundled leading to the Router from Core 2. This labconsisted of 3 working VLAN's: Engineering (100), Marketing(200), and Finance(300). The links

between the Access layer and Distribution layer were all truncated via 802.1q. The first Figure displays

a full visual diagram of the topology, included are the IP addressing required for connectivity of all ports.

Figure 7-1



The next Figure lays in detail the configuration commands required from scratch to

connectivity of inter-VLAN's.

Figure 7-2(SHOW RUN of DS1/DS2)**VTP Conf.DS1(config)#vtp mode client

DS1(config)#vtp domain ciscoChanging VTP domain name from lab to ciscoDS1(config)#vtp pass ciscoSetting device VLAN database password to cisco

**Sho runinterface FastEthernet0/1no switchportip address 172.1.0.45 255.255.255.252!interface FastEthernet0/2no switchportip address 172.1.0.41 255.255.255.252!interface FastEthernet0/13

switchport trunk encapsulation dot1qswitchport mode trunk!interface FastEthernet0/14!interface FastEthernet0/15switchport trunk encapsulation dot1qswitchport mode trunk!interface FastEthernet0/16!interface FastEthernet0/17switchport trunk encapsulation dot1qswitchport mode trunk!

interface Vlan1ip address 172.1.0.3 255.255.255.240!interface Vlan100ip address 172.1.0.17 255.255.255.248!interface Vlan200ip address 172.1.0.25 255.255.255.248!interface Vlan300ip address 172.1.0.33 255.255.255.248

***DS2_3560_5(config)#ip routingDS1(config)#ip routing

( ACCESS LAYER COMMANDS)ACC2_2960_2(config)#interface vlan 1ACC2_2960_2(config-if)#ip address 172.1.0.6 255.255.255.240

ACC2_2960_2(config)#ip default-gateway 172.1.0.3

interface FastEthernet0/1switchport access vlan 100switchport mode accessspanning-tree portfast!



interface FastEthernet0/2switchport access vlan 300switchport mode accessspanning-tree portfastACC2_2960_2(config)#do sho int trunk

Port Mode Encapsulation Status Native vlanFa0/15 on 802.1q trunking 1Fa0/16 on 802.1q trunking 1

Port Vlans allowed on trunkFa0/15 1,100,200,300

(CORE SWITCHES)Core1_3560_6(config)#do show runinterface Port-channel2no switchportip address 172.1.0.57 255.255.255.252interface FastEthernet0/1no switchportno ip addresschannel-group 2 mode active!interface FastEthernet0/2

no switchportno ip addresschannel-group 2 mode active!interface FastEthernet0/3no switchportip address 172.1.0.50 255.255.255.252!interface FastEthernet0/4no switchportip address 172.1.0.42 255.255.255.252!interface Vlan1ip address 172.1.0.1 255.255.255.240

Although many of these commands entered into the switches were CCNA level or learned in

previous CCNP labs, they added a twist of challenge since they were performed on layer 3 systemswhich required certain commands to ensure operation like the “Ip routing” command that tells the

switch to perform layer 3 functions. The 3560 switches assume they are full switches until this

command “wakes them up”. Inter-VLAN routing using Switch Virtual Interfaces has far exceeded theuse of using “Router on a stick” implementations for its hardware-based speeds. Instead of requiring an

an actual interface to be used and trunk lines like a router it only requires specific VLAN's enabled with

IP addresses corresponding to them. Although there are many benefits using L3 devices such asincreased packet flow/bandwidth the main disadvantage is providing funds for an expensive device.

After the SVI's were created to manage the Acces switches and their corresponding VLAN's thelinks between the Distribution and Core Switches needed to be address and the Router. The solution tointegrate both the switches and routers to have routes between one another was using Cisco's routing

protocol EIGRP. Although its beyond the scope of this lab to explain EIGRP this link provided will

allow for further research:

(http://en.wikipedia.org/wiki/Enhanced_Interior_Gateway_Routing_Protocol)When configuring the 3560 switches for routing they assume they switchports and must be

reconfigured to route. When entering the interfaces the command “no switchport” is required,

followed by the IP address and possibly “no shut”. After the Distribution and Core switches were



configured for routing the 2 links between the Core switches needed an Layer 3 EtherChannel initiated.

The process is relatively similar to setting up a layer 2 EtherChannel yet requires an Ip address on

either side of the switches to act as the Aggregated Interface. This next Figure show's an example of

the process.

Figure 7-3 (Example Router)

Router# configure terminal Router(config)# interface port-channel 1 Router(config-if)# ip address 172.32.52.10 255.255.255.0 Router(config-if)# end

Router# configure terminal Router(config)# interface range fastethernet 5/6 -7 Router(config-if)# channel-group 2 mode desirable Router(config-if)# end

Core1_3560_6#show etherchannel sumFlags: D - down P - in port-channel

Group Port-channel Protocol Ports------+-------------+-----------+-----------------------------------------------2 Po2(RU) LACP Fa0/1(P) Fa0/2(P)

This lab required EIGRP setup with the discretion for the teams to assign autonomous system

numbers along with the IP addressing that was already created early on. Figure 7-4 displays the

commands written to achieve this as well as full access to every port in the network.

Figure 7-4 (EIGRP)

(Setup)Core1_3560_6#router eigrp 1network 172.1.0.0 0.0.0.15network 172.1.0.40 0.0.0.3network 172.1.0.48 0.0.0.3network 172.1.0.56 0.0.0.3auto-summary

(Convergence)172.1.0.0/16 is variably subnetted, 9 subnets, 3 masksD 172.1.0.44/30 [90/30720] via 172.1.0.41, 00:04:15, FastEthernet0/4C 172.1.0.40/30 is directly connected, FastEthernet0/4D 172.1.0.32/29 [90/28416] via 172.1.0.49, 00:04:15, FastEthernet0/3

[90/28416] via 172.1.0.41, 00:04:15, FastEthernet0/4C 172.1.0.56/30 is directly connected, Port-channel2D 172.1.0.52/30 [90/30720] via 172.1.0.49, 00:04:15, FastEthernet0/3C 172.1.0.48/30 is directly connected, FastEthernet0/3D 172.1.0.0/28 [90/28416] via 172.1.0.49, 00:04:16, FastEthernet0/3

[90/28416] via 172.1.0.41, 00:04:16, FastEthernet0/4D 172.1.0.24/29 [90/28416] via 172.1.0.49, 00:04:16, FastEthernet0/3

[90/28416] via 172.1.0.41, 00:04:16, FastEthernet0/4D 172.1.0.16/29 [90/28416] via 172.1.0.49, 00:04:16, FastEthernet0/3

[90/28416] via 172.1.0.41, 00:04:16, FastEthernet0/4

Core1_3560_6#ping 172.1.0.41(Pings)Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.1.0.41, timeout is 2 seconds:!!!!!



Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 msCore1_3560_6#ping 172.1.0.49

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.1.0.49, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 msCore1_3560_6#ping 172.1.0.58

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.1.0.58, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msCore1_3560_6#

Lastly after the multilayer network was finished with configurations it was time to monitor the

operations of spanning-tree and EIGRP neighbor relationships. The Distribution switches would show

their SVI interfaces and their routed interfaces performing required tasks. When looking at several

parts of this lab topology it would appear from an untrained eye that its very redundant in the event of link failures yet there is one key link that holds the gateway to the external networks. Although this

network is highly reliable for local connections there is only one link leaving Core 2 that reaches the

“ ISP”

router. In the event that a bulldozer disrupts this line all access is lost. Figure 7-5 displays themonitoring commands used at various parts of the network. In conclusion there is a lack or redundancyor lack of HSRP integreated.

Figure 7-5

(Spanning-tree)ACC2_2960_2#sho spanning-tree activeVLAN0001Spanning tree enabled protocol ieeeRoot ID Priority 32769

Port 15 (FastEthernet0/15)

VLAN0100Spanning tree enabled protocol ieeeRoot ID Priority 32868

Address 0018.ba12.4f00Port 15 (FastEthernet0/15)

DS1#sh span

VLAN0001Spanning tree enabled protocol ieeeRoot ID Priority 32769

Address 0018.ba12.4f00 This bridge is the rootVLAN0100Spanning tree enabled protocol ieeeRoot ID Priority 32868

Address 0018.ba12.4f00

This bridge is the root

(SVI & Routed Int.)DS1# sh int vlan100Vlan100 is up, line protocol is upHardware is EtherSVI, address is 0018.ba12.4f41 (bia 0018.ba12.4f41) <-Notice the SVI HW Internet address is 172.1.0.17/29



DS2_3560_5#show ip int f0/1FastEthernet0/1 is up, line protocol is upInternet address is 172.1.0.49/30Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is disabledMulticast reserved groups joined: 224.0.0.10 <--Shows this is using EIGRP routing

(EIGRP Neighbor, Top)Core1_3560_6#show ip eigrp neIP-EIGRP neighbors for process 1H Address Interface Hold Uptime SRTT RTO Q Seq Type

(sec) (ms) Cnt Num0 172.1.0.41 Fa0/4 12 00:06:57 17 200 0 481 172.1.0.49 Fa0/3 14 00:09:32 552 3312 0 68

Core1_3560_6#show ip eigrp intIP-EIGRP interfaces for process 1

Xmit Queue Mean Pacing Time Multicast PendingInterface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes

Fa0/4 1 0/0 17 0/1 50 0Fa0/3 1 0/0 552 0/1 2756 0Po2 0 0/0 0 0/1 0 0Vl1 0 0/0 0 0/1 0 0

Core1_3560_6#show ip eigrp topIP-EIGRP Topology Table for AS(1)/ID(172.1.0.57)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,r - reply Status, s - sia Status

P 172.1.0.44/30, 2 successors, FD is 30720via 172.1.0.58 (30720/28160), Port-channel2via 172.1.0.41 (30720/28160), FastEthernet0/4via 172.1.0.49 (30976/28416), FastEthernet0/3

P 172.1.0.40/30, 1 successors, FD is 28160

via Connected, FastEthernet0/4P 172.1.0.32/29, 2 successors, FD is 28416

via 172.1.0.49 (28416/2816), FastEthernet0/3via 172.1.0.41 (28416/2816), FastEthernet0/4

P 172.1.0.60/30, 1 successors, FD is 30720via 172.1.0.58 (30720/28160), Port-channel2

Lab Switch Report

Documents

Transcript of Lab Switch Report