The Best Questions on CCNA and CCNP

Part 1:

For this part of the lab you will reconfigure the Catalyst 520 switches such that they will enable a minimum of 2 VLANS that cannot see each other, except as follows. Once the VLANs are established you can see that machines on one VLAN cannot see the other. Can you route between them? How would you do that?

You can’t setup AN ether channel between a layer3 device and a layer a pair of device, so as to form this setup work simply take away the ether channel configuration and connect one cable to your switch and piece this interface as trunk and piece dot1q on the router on the physical interface rather the logical interface moreover Isolated VLANs Ports within an isolated VLAN cannot communicate directly with each other at the Layer 2 level.

An isolated port may be a host port that belongs to associate degree isolated secondary VLAN. This port has complete isolation from alternative ports at intervals identical non-public VLAN domain, except that it will communicate with associated promiscuous ports. Non-public VLANs block all traffic to isolated ports except traffic from promiscuous ports. Traffic received from an isolated port is forwarded solely to promiscuous ports. You’ll be able to have quite one isolated port in a very nominal isolated VLAN. Each port is totally isolated from all alternative ports within the isolated VLAN. The second issue is visibility. The desktop device in our example will realize any connected device just by causation one or additional arp broadcasts. A D-switch permits most visibility as a result of it cannot verify whether or not a requesting device is permitted to check or contact the target device. Further, all devices exist on constant network segment.


Part 2:

  • In Packet tracer you will design a campus VLAN with five switches and 25 machines total.

The switches will be configured to initially achieve 3 VLANs (1, 25, and 246).


Switch#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)#vlan 1

Switch(config)#vlan 25

Switch(config)#vlan 246




Switch#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.


Switch(config)#interface FastEthernet0/1




%SYS-5-CONFIG_I: Configured from console by console


Switch#vtvconf t

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)#vtp domain Cisco1

Changing VTP domain name from NULL to Cisco1

Switch(config)#vtp mode SERVER

Device mode already VTP SERVER.

Switch(config)#vtp domain Cisco1

Changing VTP domain name from NULL to Cisco1

Switch(config)#int fa0/1

Switch(config-if)#switchport trunk allowed

% Incomplete command.

Switch(config-if)#switchport trunk allowed vlan 1-1000


  • Next place switch 2 into transparent mode and add Vlan 1000 for 2 devices and place the switch in transparent mode.


Switch#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#vlan 1000


Switch#config t

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)#vtp domain Cisco1

Changing VTP domain name from NULL to Cisco1

Switch(config)#vtp mode transparent

Setting device to VTP TRANSPARENT mode.

What happens if you change vlan 1 on switch 1 to vlan 2? Who sees the messages?

No change occurs and message is seen switch 1
Next change switch 2 back to a client mode and in domain Cisco1. What happens to that switch now? Do updates occur?

Switch#config t

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)#vtp mode client

Setting device to VTP CLIENT mode.

Part 3:


VLAN Trunk Protocol (VTP) diminishes organization in an exchanged system. When you design another VLAN on one VTP server, the VLAN is conveyed through all switches in the area. This diminishes the need to design the same VLAN all over the place. VTP is a Cisco-restrictive convention that is accessible on the greater part of the Cisco Catalyst arrangement items.
VTP exists to guarantee that VLANs exist on the nearby VLAN database of switches in a trunked way. Notwithstanding verifying the VLANs exist, VTP can further synchronize name settings and can be utilized to prune VLANs from trunk interfaces that are bound for switches that don’t have any ports dynamic in that specific VLAN.

Of course VTP is in server mode, which is an operational mode that empowers you to oversee VLANs on the nearby switch’s database and utilize the data as a part of the database to synchronize with different switches. To arrange VTP for operation, you must determine a name. After you empower trunking, this name proliferates to switches that have not been designed with a name. In the event that you decide to design names on your switches, then again, recall that VTP names are case-delicate and must match precisely. Switches that have diverse VTP names won’t trade VLAN data.
As a matter of course Cisco switches are in VTP server mode. For a VTP server, you can make, erase, or change a VLAN in the nearby VLAN database. After you roll out this improvement, the VLAN database changes are spread out to all different switches in server or customer mode in the VTP space. A server will likewise acknowledge changes to the VLAN database from different switches in the area. You can likewise run the VTP in customer mode. Switches in customer mode can’t make, alter, or erase VLANs in the nearby VLAN database. Rather, they depend on different switches in the space to overhaul them about new VLANs. Customers will synchronize their databases, however they won’t spare the VLAN data and will detached this data on the off chance that they are fueled off. Customers will likewise publicize data about their database and forward VTP data to different switches. VTP straightforward mode meets expectations much like server mode in that you can make, erase, or alter VLANs in the nearby VLAN database. The distinction is that these progressions are not spread to different switches. Also, the nearby VLAN database does not acknowledge changes from different switches. VTP straightforward mode switches forward or hand-off data between other server or customer switches. A VTP straightforward mode switch does not oblige a VTP area name.
Whenever a change happens in the VLAN database, the VTP server additions its design amendment number and afterward promotes the new update all through the VTP space by means of VTP promotions.

VTP works in one of three modes: server, straightforward, or customer.

Server: The default mode. When you roll out an improvement to the VLAN design on a VTP server, the change is spread to all switches in the VTP area. VTP messages are transmitted out of all the trunk associations. In Server mode we can make, change, and erase VLANs.

Client: can’t roll out improvements to the VLAN design when in this mode; be that as it may, a VTP customer can send any VLANs right now recorded in its database to other VTP switches. VTP customer likewise advances VTP promotions (however can’t make VTP notices).

Transparent: When you roll out an improvement to the VLAN arrangement in this mode, the change influences just the neighborhood switch and does not spread to different switches in the VTP area. VTP straightforward mode does forward VTP promotions that it gets inside the space.

VTP Pruning makes more effective utilization of trunk transfer speed by sending telecast and obscure unicast outlines on a VLAN just if the switch on the less than desirable end of the trunk has ports in that VLAN.
1.) How did the ability trunk VLANs make this design more efficient?

Trunk links give VLAN identification for frames traveling between switches. The standard style makes the network simple to scale, understand, and troubleshoot by promoting settled traffic patterns. Trunks carry traffic from all VLANs to and from the switch by default however may be designed to hold solely fixed VLAN traffic.
2.) How would the assignment of data link addressed VLANs make the design more flexible?

VLANs allow to make several LANs on identical network device or on several interconnected network devices on identical layer two domain. VLANs are created to separate totally different traffic into different virtual LANs. This will increase the protection as traffic from totally different customers or services is separated on different VLANs, Offers additional flexibility in style and makes it easier to separate the traffic into separate traffic classis by as an example marking traffic on totally different VLANs with different quality of service marking so that they are in higher priority in alternative elements of the network.
3.) Discuss the use of VTP in a large network with many switches that requires that type of security?

In a giant network, the network administrator should create a judgment out in some purpose, once the NVRAM storage that’s necessary is wasteful as a result of it’s duplicated on each switch. At now, the network administrator should opt for a number of well-equipped switches and keep them as VTP servers. Everything else that participates in VTP are often become a consumer. The quantity of VTP servers ought to be chosen so as to supply the degree of redundancy that’s desired within the network. VLAN trunking for giant networks with several interconnected switches are often an awfully troublesome task. VLAN Trunk Protocol (VTP) could be a protocol created by Cisco to form and manage VLANs for an outsized network with several interconnected switches and to take care of consistency throughout the network. In alternative words, switches use VLAN trunking protocol (VTP) to speak among themselves regarding VLAN configuration.



4.) Please show screen shots of your design (each step of the way)

5.) Please reset your switches so that all ports are on VLAN one.


clear config {mod | rmon | all | snmp | acl {nvram}


Please enter your comment!
Please enter your name here