Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
18Activity
0 of .
Results for:
No results containing your search query
P. 1
ESwitching Final Exam - CCNA Exploration LAN Switching and Wireless

ESwitching Final Exam - CCNA Exploration LAN Switching and Wireless

Ratings: (0)|Views: 681|Likes:
Published by nguyenvantruongitc

More info:

Published by: nguyenvantruongitc on Dec 28, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

02/23/2011

pdf

text

original

 
 ESwitching Final Exam - CCNA Exploration LAN Switching and Wireless (Version 4.0)By: Owey1Why is it important that the network administrator consider the spanning-tree network diameter when choosing therootbridge?The network diameter limitation is 9.
BPDUs may be discarded because of expiring timers.
The cabling distance between the switches is 100 meters.The network diameter must be set to the number of meters of the cable between the root bridge and its farthestconnected switch.2Refer to the exhibit. A network administrator configures HyperTerminal with the parameters shown but is unable to connectto a switch via the console port. The administrator is using a tested rollover cable attached to the only COM port on thecomputer, and the connections have been verified. What is the likely problem?The cable is connected to the wrong port.The wrong connection speed is selected.The cable is the wrong type.
The flow control setting is not correct.
The stop bits should be set to zero.
 
 3Refer to the exhibit. Switch SW2 was tested in a lab environment and then inserted into a production network withoutreloading its configuration. After the trunk link between SW1 and SW2 was brought up, all users lost connectivity to thenetwork. What could be the source of the problem?All the VLANs were pruned from the trunk port between SW1 and SW2.SW1 and SW2 cannot be both set as VTP servers in the same VTP domain.
VTP configuration revision number of SW2 was higher than the configuration revision number of SW1.
The additional VLANs from SW2 created more VLANs than the VLAN database of SW1 could contain.4
 
 Refer to the exhibit. R1 is configured for traditional inter-VLAN routing. R1 can ping computer 3 but cannot ping computer 1.What is a possible cause for this failure?
S1 port Fa0/11 is in the wrong VLAN.
R1 does not have an active routing protocol.The IP address of computer 1 is in the wrong logical network.Router interface Fa0/0 has the wrong trunk encapsulation type configured.5Refer to the exhibit. The hosts connected to switch SW1 are not able to communicate with the hosts in the same VLANsconnected to switch SW2. What should be done to fix the problem?Configure VLANs with different VLAN IDs on switch SW2.
Reconfigure the trunk port on switch SW2 with static trunk configuration
.Introduce a Layer 3 device or a switch with Layer 3 capability in the topology.Apply IP addresses that are in the same subnet to the interfaces used to connect SW1 and SW2.

Activity (18)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
mcfaruh liked this
dr34m5 liked this
jeroberts01 liked this
amani_olivier liked this
max350035 liked this
Pain1990 liked this
siven123 liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->