You have been asked to install and configure a new switch in a customer network. Use the console access to the existing and new switches to configure and verify correct device configuration.
To comply with the configuration of other switches, we need to get VTP configuration of Sw1 or Sw2. On Sw1 use the “show vtp status” command:
From this output we learn on Sw1:
+ VTP is running version 3
+ VTP Domain is “CCNP”
+ Sw1 is the VTP Primary Server (we will explain about Primary Server later. Now just understand it is in VTP Server mode)
So on the New_Switch, the VTP Domain must match. New_Switch should run VTP version 3 if if can (but it is not a must as VTP version 2 is compatible with VTP version 3). The New_Switch is connecting to hosts so it is in Access Layer so it should be configured as a VTP Client (although Transparent mode is acceptable) so there are only two suitable choices D & E.
From the exhibit, the New_Switch is connecting to a host in VLAN 100 so its E0/0 interface should be in VLAN 100 -> only D is correct.
On Sw1 & Sw2 we can check with the “show interfaces trunk” command:
Sw1 & Sw2 are connected through E2/3 & E2/3 so we can see the native Vlan on these trunks are 99. We should check both Sw1 & Sw2 to see if the Native Vlan on both sides match.
In VTP version 3, there are two additional fields under the output of “show vtp status” command. They are:
+ “Primary ID”: The MAC address of the Primary Server
+ “Primary Description”: The hostname of the Primary Server
The Primary Server is used on VTP version 3 to avoid the bad behavior in version 2. In VTP version 2, a VTP client (or Server) can be taken out of the network. When it comes back, it can overwrite a VTP Server if its Revision number is higher. This problem no longer exists in VTP version 3 because there is only one VTP Primary Server at a time. Only a VTP Primary Server can create new VLAN.
After creating new VLAN, the VTP Primary Server will advertise its VLAN database to other VTP clients/servers so in fact answer A is not correct. In this question you just need to check if Sw1 or Sw2 is the VTP Primary Server then we can create both VLAN 500 & 600 on it. Then it will advertise these VLANs to other switches.
From the output we see Sw1 is the Primary Server so we should configure VLAN 500 & 600 only on this switch.
Note: To make a switch a Primary Server, issue the “vtp primary vlan” under privilege exec mode. For example:
|Sw1#vtp primary vlan|
To configure private VLAN we have to change VTP (even version 3) to Transparent mode. In fact, to disable VTP pruning on Sw4 (in Client mode) we also have to change to VTP Transparent mode so answer C can be understood as “change SW4 to Transparent mode” so it is the best choice.
Note: Unlike VTP version 1 and 2 in which VTP pruning is enabled on VTP Server only, VTP version 3 requires VTP pruning must be enabled on all the switches in the VTP domain so we can also disable VTP pruning on each switch separately. Here is the link for your reference: http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_55_se/configuration/guide/3750xscg/swvtp.html
“With VTP versions 1 and 2, when you enable pruning on the VTP server, it is enabled for the entire VTP domain. In VTP version 3, you must manually enable pruning on each switch in the domain.”