ccnp3v30 lab correction

8/11/2019 CCNP3V30 Lab Correction

http://slidepdf.com/reader/full/ccnp3v30-lab-correction 1/16

* If you see anything that is not working as Cisco has described in the lab, please drop

me an email and let me know where this the problem, and I will add it to this document.

Lab 1.6.2 Catalyst 2950T and 3550 Configuration and IOS Files

4 - 9 CCNP 3: Multilayer Switching v 3.0 - Lab 1.6.2

If all the optional parameters in the commands are entered, a prompt will confirm the copyoperation.Switch1#copy nvram:startup-config tftp://10.1.1.10/Switch1-switch-confgWrite file Switch1-switch-confg on host 10.1.1.10? [confirm]!!!!!664 bytes copied in 3.264 secs (221 bytes/sec)

Attention:

• A simple “copy start tftp” will worj here.

• Use the same syntax for the rest of this lab.

Lab 2.9.1 Catalyst 2950T and 3550 Series Static VLANS 9 - 10 CCNP 3: Multilayer Switching v 3.0 - Lab 2.9.1

The VLAN information is saved in a flash file called vlan.dat. This file needs to be deleted toremove the VLAN information. This is done with the delete flash:vlan.dat or deletevlan.dat

command.Switch#delete flash:vlan.datDelete filename [vlan.dat]?Delete flash:vlan.dat? [confirm]Switch#

Attention:

This is a very important step here. Please pay attention. On the question of

Delete filename [vlan.dat]? HIT THE RETUEN KEY HERE.

All you have to do here is hit the return key. If you type in anything other than just hit a return key here, you will erase the flash file. If you erase the flash file, it

will take us about one hour to re-install the flash back to the switch. If you are

not certain what to do here, please ask your instructor for the demonstration.

Lab 2.9.2 Catalyst 2950T and 3550 Series VTP Domain and VLANTrunking 4 - 16 CCNP 3: Multilayer Switching v 3.0 - Lab 2.9.2

VLAN information is not propagated until a VTP Domain Name is specified and learned throughtrunked ports. The default settings for interfaces on the 2950T-24-EI and 3550-24-EMI switchesare to automatically trunk when cabled appropriately. Therefore, VTP automatically propagatesthe corp VTP Domain Name to both ALSwitchA1 and ALSwitchA2.



Issue a show vtp status command on ALSwitchA1 and ALSwitchA2 to verify that the VTP

Domain Name is corp, the VTP mode is Server, and the Configuration Revision is zero as shownin the following ALSwitchA1 sample output.

Attention:1. The VTP information will not be automatically propagated to Catalyst

2900XL switches. Therefore, you need to manually setup vtp domain andsetup vtp client on the Catalyst 2900XL

Or

2. Setup up automatic trunking on Catalyst 2900XL switches. Then, the

trunking information should be propagated automatically.


ALSwitchA1#show interfaces trunkPort Mode Encapsulation Status Native vlanFa0/1 desirable 802.1q trunking 1

Port Vlans allowed on trunkFa0/1 1-4094

Port Vlans allowed and active in management domainFa0/1 1

Port Vlans in spanning tree forwarding state and not prunedFa0/1

Attention:

Your output from the Catalyst 2900XL may look slightly different from the

output shown above.


The VTP Domain Name corp does not need to be entered since it is already propagated fromDLSwtichA.

Attention:

This may not happen automatically in Catalyst 2900XL switch. You may berequired to configure it manually.




ALSwitchA1(config)#interface FastEthernet 0/1ALSwitchA1(config-if)#switchport mode trunkALSwitchA1(config-if)#switchport trunk native vlan 1ALSwitchA1(config-if)#interface range FastEthernet 0/5 – 8ALSwitchA1(config-if-range)#switchport access vlan 10ALSwitchA1(config-if-range)#interface range FastEthernet 0/9 – 10ALSwitchA1(config-if-range)#switchport access vlan 20ALSwitchA1(config-if-range)#̂ z

ALSwitchA2#configure terminalALSwitchA2(config)#interface FastEthernet 0/1ALSwitchA2(config-if)#switchport mode trunkALSwitchA2(config-if)#switchport trunk native vlan 1ALSwitchA2(config-if)#interface range FastEthernet 0/5 – 8ALSwitchA2(config-if-range)#switchport access vlan 10ALSwitchA2(config-if-range)#interface range FastEthernet 0/9 – 10ALSwitchA2(config-if-range)#switchport access vlan 20ALSwitchA2(config-if-range)#^z

Attention:

The range command will not work on Catalyst 2900XM switch.

Lab 2.9.4 Catalyst 2950 and 3550 Series Intra-VLAN Security 3 - 5 CCNP 3: Multilayer Switching v 3.0 - Lab 2.9.4

Although it is not absolutely necessary, reset ALSwitchA1 and ALSwitchA2 to the VTP client

mode by issuing the following commands:

Attention:

It may require to manually setup in Catalyst 2900XL switch.

Lab 2.9.4 Catalyst 2950 and 3550 Series Intra-VLAN Security 3 - 5 CCNP 3: Multilayer Switching v 3.0 - Lab 2.9.4

Step 3

Issue the following to deny ICMP ping access from Workstation A to the server that has an ACLin DLSwitchA:DLSwitchA#configure terminalDLSwitchA(config)#access-list 101 deny icmp host 10.1.2.10 host 10.1.2.30 echoDLSwitchA(config)#access-list 101 permit ip any anyDLSwitchA(config)#interface FastEthernet 0/5DLSwitchA(config-if)#ip access-group 101 inDLSwitchA(config-if))#^z

Attention:



Please pay attention on the source and destination and match it with in or out

direction. You should be able to figure out the problem in this configuration.

Lab 3.10.2 Use Network Inspector to Observe STP Behavior 3 - 12 CCNP 3: Multilayer Switching v 3.0 - Lab 3.10.2

DLSwitch1(config-if)#switchport mode trunkDLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config)#interface FastEthernet 0/3DLSwitch1(config-if)#switchport mode trunkDLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config)#interface FastEthernet 0/7DLSwitch1(config-if)#switchport mode trunkDLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config-if)#^Z

Attention:

You need to enter the encapsulation command before the mode command..

DLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config-if)#switchport mode trunkDLSwitch1(config)#interface FastEthernet 0/3DLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config-if)#switchport mode trunkDLSwitch1(config)#interface FastEthernet 0/7DLSwitch1(config-if)#switchport trunk encapsulation dot1qDLSwitch1(config-if)#switchport mode trunkDLSwitch1(config-if)#^Z

Lab 3.10.3 Advanced PVST+ Configuration6 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 3.10.3

Step 4

PVST+ is automatically enabled on 802.1Q trunks. No user configuration is required. Theexternal spanning-tree behavior on access ports and Inter-Switch Link (ISL) trunks is notaffected by PVST+. Cisco IOS supports a maximum of 128 spanning-tree instances.

Attention:

It is require to manually setup trunking protocol in Catalyst 2900XL switch.

Lab 3.10.4 Implementing MST


ALSwitch2(config-mst)#name region1

ALSwitch2(config-mst)#revision 1

ALSwitch2(config-mst)#exit

ALSwitch2(config)#spanning-tree mode mst



ALSwitch1(config)#spanning-tree mst configuration

ALSwitch1(config-mst)#instance 1 vlan 1-50

ALSwitch1(config-mst)#name region1

ALSwitch1(config-mst)#revision 1

ALSwitch1(config-mst)#exit

ALSwitch1(config)#spanning-tree mode mst

Attention:

The command “ALSwitch1(config)#spanning-tree mst configuration” will notwork on Catalyst 2900XL switch. MOVE ON TO THE REST OF THE LAB.

Lab 3.10.5 Configuring Fast EtherChannel 3 - 7 CCNP 3: Multilayer Switching v 3.0 - Lab 3.10.5

ALSwitch1(config)#interface range fastethernet 0/5 - 8ALSwitch1(config-if-range)#switchport access vlan 10ALSwitch1(config-if-range)#exit

ALSwitch1(config)#interface range fastethernet 0/9 - 12ALSwitch1(config-if-range)#switchport access vlan 20ALSwitch1(config-if-range)#exit

And ………………………

Attention:



Configure ALSwitch1 to combine ports 0/1 and 0/2 into one logical channel.ALSwitch1(config)#interface range fastethernet 0/1 – 2ALSwitch1(config-if-range)#channel-group 1 mode desirableALSwitch1(config-if-range)#̂ Z

Configure the ALSwitch2 to combine ports 0/1 and 0/2 into one logical channel.ALSwitch2(config)#interface range fastethernet 0/1 – 2ALSwitch2(config-if-range)#channel-group 1 mode desirableALSwitch2(config-if-range)#̂ Z

And ………………………

Attention:1. The range command will not work on Catalyst 2900XM switch.

2. use the command “port group 1” instead..


Verify the port aggregation protocol (PAgP) operation.



The PAgP facilitates the automatic creation of EtherChannels by exchanging packets betweenEthernet interfaces. By using PAgP, the switch learns the identity of partners capable ofsupporting PAgP and learns the capabilities of each interface. It then dynamically groups similarlyconfigured interfaces into a single logical link, channel, or aggregate port. These interfaces aregrouped based on hardware, administrative, and port parameter constraints. For example, PAgPgroups the interfaces with the same speed, duplex, native VLAN, VLAN range, trunking status,and trunking type. After grouping the links into an EtherChannel, PAgP adds the group to thespanning tree as a single switch port.

Use the show pagp neighbor command on DLSwitch to verify PagP operation.

Attention:

Skip this part. The PAgP function does not work on Catalyst 2900XL switch.


Verify the default behavior by transferring a TFTP file from Host A to Host C.1. Observe the lights on the DLswitch. Which links were used?

________________________________________________________________

Attention:

If you are having difficulty of setting up the TFTP file transfer. Use the command

Ping –l “size” –t “ip_address” command instead. .

Lab 3.10.7 Port Level Tuning to Control STP Behavior

Attention Since there is no Gigabit Ethernet setup on the switch, please use the topology

diagram from 3.10.6 and change all the port assignment accordantly.



Lab 3.10.7 Port Level Tuning to Control STP Behavior 4 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 3.10.7

Configure DLSwitch2 as a VTP client as shown below.DLSwitch2#vlan databaseDLSwitch2(vlan)#vtp clientDLSwitch2(vlan)#exit

Step 5Configure ALSwitch1 and ALSwitch2 as VTP clients and assign ports to the respective VLANs ineach switch as shown below. The interface range command can be used to configure

several

interfaces at the same time.ALSwitch1#vlan databaseALSwitch1(vlan)#vtp clientALSwitch1(vlan)#exitALSwitch1#config terminalALSwitch1(config)#interface range fastethernet 0/5 - 8ALSwitch1(config-if-range)#switchport access vlan 10ALSwitch1(config-if-range)#interface range fastethernet 0/9 - 12ALSwitch1(config-if-range)#switchport access vlan 20ALSwitch1(config-if-range)#̂ ZALSwitch2#vlan databaseALSwitch2(vlan)#vtp clientALSwitch2(vlan)#exitALSwitch2#config terminalALSwitch2(config)#interface range fastethernet 0/5 - 8

ALSwitch2(config-if-range)#switchport access vlan 10ALSwitch2(config-if-range)#interface range fastethernet 0/9 - 12ALSwitch2(config-if-range)#switchport access vlan 20ALSwitch2(config-if-range)#̂ Z

Attention

The command “vtp domain CORP” needs to be added to DLSwitch2,ALSwitch1, and ALSwitch2.




Step 8Observe what happens when the status of an uplink changes.

Remove the uplink cable between ALSwitch1 and DLSwitch1 while monitoring the backup linkport. Observe if the light on the switch is indicating a yellow blocked port or use the show

spanningtree command.

Attention

The light may not change to yellow as it indicated in the lab. You need to connect

the console cable and observe the behavior and state change on the console

display using “show spanning-tree” command.


Step 9Use the global configuration mode to enable the BPDU guard feature on ALSwitch1.ALSwitch1(config)#spanning-tree portfast bpduguard

Attention

The command “spanning-tree portfast bpduguard ” may not work in Catalyst

2900XL switch.

Lab 3.10.7 Port Level Tuning to Control STP Behavior 6 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 3.10.7Step 11Disconnect one of the connectors between ALSwitch1 and DLSwitch1. Observe the line status onthe switches. A unidirectional link has just been created.

Attention

The light may not change to yellow as it indicated in the lab.


UDLD is a Layer 2 protocol that enables devices connected through fiber-optic or twisted-pairEthernet cables to monitor the physical configuration of the cables and detect a unidirectional link.



All connected devices must support UDLD for the protocol to identify and disable unidirectionallinks.

When UDLD detects a unidirectional link, it shuts down the affected port and sends out an alert.Unidirectional links can cause a variety of problems such as spanning-tree topology loops. Nowreconnect the transmit or receive cable to the switch.Enable UDLD with the global configuration command udld enable on the DLSwitch1,

DLSwitch2,and ALSwitch1.Note: This command only affects fiber-optic interfaces. Use the udld interface configurationcommand to enable UDLD on other interface types.ALSwitch1(config)#udld enableDLSwitch1(config)#udld enableDLSwitch2(config)#udld enable

Attention

Since we don’t have fiber optic cables, these commands will not work.

Lab 4.3.1 Inter-VLAN Routing with an External Router 3 - 5 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.1

The native VLAN cannot be configured on a subinterface for Cisco IOS releases that are earlierthan 12.1(3)T. The native VLAN ip address will need to be configured on the physical interface.Other VLAN traffic will be configured on subinterfaces. Cisco IOS releases 12.1(3)T and later willsupport native VLAN configuration on a subinterface with the encapsulation

encapsulation vlan_id native command. This technique will be used in the lab

configuration.

VLAN 1 interface

CORP(config)#interface fastethernet 0/0.1CORP(config-subif)#description Management VLAN 1CORP(config-subif)#encapsulation dot1q 1 nativeCORP(config-subif)#ip address 172.16.1.1 255.255.255.0

Attention

Please use the “shoe version” command to check the version of the currentversion of the IOS running on the router. If the version of the IOS that is prior

then 12.1.(3)T, the vlan 1 and native vlan has to be configured on the physical

interface.

Router(config)#interface fa 0/0

Router(config-if)#description Management VLAN 1 Router(config-if)#ip address 172.16.1.1 255.255.255.0

Lab 4.3.1 Inter-VLAN Routing with an External Router 4 - 5 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.1

Set the interface connected to the router to trunk with the router. The router is already set to trunk



Attention:

Use fastethernet interface instead of Gigabit Trunk..

Lab 4.3.2 Inter-VLAN Routing with the Internal Route Processor5 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.2

Verify the VLAN configuration with the show vlan command.

DLSwitch#vlan database

Attention The command should be (It is alswitch not dlswitch.)

ALSwitch#show vlan

Lab 4.3.2 Inter-VLAN Routing with the Internal Route Processor5 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.2



The 2950 switches do not need the encapsulation configured. These switches default to 802.1Q.Some IOS versions do not include any other options. Console into ALSwitch switch and configuretrunking.

Attention The trunking encapsulation for 2900XL is ISL. Therefore, you need tomanually change it to 802.1q

ALSwitch(config)#interface fastethernet 0/1

ALSwitch(config-if)#switchport trunk encapsulation dot1q ALSwitch(config-if)#switchport mode trunk

Lab 4.3.3 Routing Between an External Router and an InternalRoute Processor1 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.3

Attention:

Use fastethernet interface instead of Gigabit Trunk..

Lab 4.3.3 Routing Between an External Router and an InternalRoute Processor5 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.3

The 2950 switches do not need the encapsulation configured. These switches default to 802.1Q.In some IOS versions there are no other options. Console into ALSwitch and configure trunking.



ALSwitch(config)#interface gigabitethernet 0/1

ALSwitch(config-if)#switchport mode trunk

Switch(config-if)#exit

AL

Attention The trunking encapsulation for 2900XL is ISL. Therefore, you need to

manually change it to 802.1q

ALSwitch(config)#interface fastethernet 0/1

ALSwitch(config-if)#switchport trunk encapsulation dot1q ALSwitch(config-if)#switchport mode trunk

Lab 4.3.3 Routing Between an External Router and an Internal RouteProcessor6 - 8 CCNP 3: Multilayer Switching v 3.0 - Lab 4.3.3

Move the ports into the appropriate VLANs.

ALSwitch(config)#interface range fastethernet 0/5-8

ALSwitch(config-if-range)#switchport access vlan 10ALSwitch(config-if-range)#exit

ALSwitch(config)#interface range fastethernet 0/9-12

ALSwitch(config-if-range)#switchport access vlan 20

ALSwitch(config-if-range)#exit

Attention:


Lab 6.5.1 Hot Standby Router Protocol


Step 1

Cable the lab as shown in the diagram.

If the routers are connected to Ethernet switches, it could take a few seconds for theswitch to reach Spanning-Tree Protocol (STP) forwarding state. To maximize the benefitsof HSRP, change the connected switch ports to spanning-tree PortFast. If the router isconnected to a hub or switch with PortFast configured, the interface should come upalmost immediately.

Attention:

In order for this run successfully, the step 1 must be followed. You must turn on port-fast on all the ports that are connected to PCs and Routers on a switch or usethe hubs for connections.

Lab 6.5.1 Hot Standby Router Protocol




Plug the cable back into interface FastEthernet 0/1 on the East router. Try the ping againand enter the show standby command on both the East and West routers. Notice that theWest router is still the Active router while the East router is now the Standby router.

Step 12

Make the East router the active HSRP router by setting the standby priority to 150. TheEast router has the higher priority and will win the election because the default standbypriority is 100.

Attention:

Ignore the sentence of the Notice session. It is the other way around.

Lab 6.5.1 Hot Standby Router Protocol5 - 7 CCNP 3: Multilayer Switching v 3.0 - Lab 6.5.1

Step 13

From the workstation, perform a tracert to the Web router. The tracert command willtrace the path of a packet, similar to the Cisco IOS traceroute command. The resultsshould be similar to the following output.

C:\>tracert 10.1.1.4

Tracing route to 10.1.1.4 over a maximum of 30 hops1 <10 ms 10 ms <10 ms 10.2.2.1

2 <10 ms <10 ms <10 ms 10.1.1.4

Trace complete.

From the workstation, ping the Web router with a –t option. The –t option providescontinuous pings. Disconnect the cable from interface FastEthernet 0/0 on the Westrouter. Observe the output of the ping.

Attention:C:\>tracert 10.1.1.4

Tracing route to 10.1.1.4 over a maximum of 30 hops1 <10 ms 10 ms <10 ms 10.1.2.32 <10 ms <10 ms <10 ms 10.1.1.4

Trace complete.

There is no host with ip address 10.2.2.1.

AND

From the workstation, ping the Web router with a –t option. The –t option providescontinuous pings. Disconnect the cable from interface FastEthernet 0/0 on the EAST router. Observe the output of the ping.



The ESAT router is the active router. It is the one should be demoted.


Step 13When the direct connection to the Web router is broken, West must use the FastEthernet0/1 interface through East to pass packets to the Web.

There is another way to view the problem. Even if a ping is successful, there could stillbe issues with a connection. For example, the hops that the packet must traverse arehidden from the ping output. With the cable still disconnected from interface FastEthernet0/0 on the West router, issue the tracert command to the Web router.

Attention:The WEST should be EAST and EAST should be WEST.


Step 13

From the workstation, perform a tracert to the Web router. The tracert command willtrace the path of a packet, similar to the Cisco IOS traceroute command. The resultsshould be similar to the following output.

C:\>tracert 10.1.1.4

Tracing route to 10.1.1.4 over a maximum of 30 hops1 <10 ms 10 ms <10 ms 10.2.2.1

2 <10 ms <10 ms <10 ms 10.1.2.33 <10 ms <10 ms <10 ms 10.1.1.4

Trace complete.

West could not pass the packet to the Web router on the FastEthernet 0/1 interface.Therefore, the packet had to be sent to East on 10.1.2.3. The packet was successfullydelivered from East interface FastEthernet 0/0 to the Web router.

………..

Reconnect the cable between the Web router and the West router.

Attention:C:\>tracert 10.1.1.4

Tracing route to 10.1.1.4 over a maximum of 30 hops

1 <10 ms 10 ms <10 ms 10.1.2.32 <10 ms <10 ms <10 ms 10.1.2.22 <10 ms <10 ms <10 ms 10.1.1.4

Trace complete.



There is no host with ip address 10.2.2.1.

The cable that needs to be reconnected is the one between east and the switch, but

not the one between WEB and west.

The WEST should be EAST and EAST should be WEST.

EVERYTHING AFTER THIS POINT ON, EAST SHOULD BE WEST AND WEST SHOULD BE EAST.

Lab 6.5.2 Multigroup Hot Standby Router Protocol3 - 4 CCNP 3: Multilayer Switching v 3.0 - Lab 6.5.2

Remove the original standby configuration before implementing MHSRP.

West(config)#interface fastethernet 0/1

West(config-if)#no standby ip 10.1.2.1

East(config)#interface fastethernet 0/1East(config-if)# no standby ip 10.1.2.1

East(config)#interface fastethernet 0/1

East(config-if)#standby 1 ip 10.1.2.1

East(config-if)#standby 1 preempt

East(config-if)#standby 1 track fastethernet 0/0

East(config-if)#standby 2 ip 10.1.2.254

East(config-if)#standby 2 preempt

East(config-if)#standby 2 priority 95

East(config-if)#standby 2 track fastethernet 0/0

West(config)#interface fastethernet 0/1

West(config-if)#standby 1 ip 10.1.2.1

West(config-if)#standby 1 preempt

West(config-if)#standby 1 track fastethernet 0/0

West(config-if)#standby 1 priority 95

West(config-if)#standby 2 ip 10.1.2.254

West(config-if)#standby 2 preempt

West(config-if)#standby 2 track serial 0

West(config-if)#standby 2 track fastethernet 0/0

Attention:Delete the command “West(config-if)#standby 2 track serial 0”. There is no serial 0 on the

topology.

ccnp3v30 lab correction

Documents