Sunday, December 31, 2017

Cisco CCNP:300-115 - 1.4 Configure and verify trunking: 1.4.a VTPv1, VTPv2, VTPv3, VTP pruning

Recently I needed to renew my Cisco CCNPs, that is both CCNP Routing and Switching as well as CCNP Security. While working with Cisco products (well now they own SourceFire, so exclude these) is not within my daily duties, I still thought it was important for me to maintain these two credentials. As a result, I've put together my notes below focusing on the key points I used to study. I believe that someone else may find them useful.

      - Pruning
            - Increases network bandwidth by restricting flooded traffic to specific trunks
            - Without pruning a switch flood broadcast, multicast and unknown unicast traffic across all trunk links within the VTP domain
            - VTP pruning is disabled by default
            - Pruning list only applies to trunk ports
            - Each trunk port has its own eligibility list
            - Only VLANs in the pruning-eligible list can be pruned
            - By default VLANs 2-1001 are eligible to be pruned
            - VTP pruning is supported in all versions of VTP
            - Enabling VTP pruning on a VTP server enables pruning for the entire management domain
            - Making VLANs pruning-eligible or pruning-ineligible affects pruning of those VLANs on that trunk only
            - VLANs 1 and 1002-1005 are pruning-ineligible.
            - Traffic from VLANs 1 and 1002-1005 cannot be pruned
            - Extended range VLANs (1006-4094) are also pruning-ineligible
            - Not designed to be used in VTP "Transparent" mode
            - All switches in a VTP domain must have the same VTP domain name but does not need the same VTP version
            - VTPv2 switches can operate in the same domain as a VTPv1 enable switch
            - Switches which are capable of running VTPv2 but are running VTPv1 and receives a VTPv3 advertisements, will automatically move to VTPv2
            - When a VTPv3 switch is connected to a switch running VTPv1, the VTPv1 swich moves to VTPv2 and the VTPv3 switch sends a scale down version of the Vtp packets so that the VTPv2 swich can update its database
            - Switches running VTPv3 cannot be moved to VTPv2 or VTPv1 if using extended VLANs
            - When VTPv2 is enaled on a switch in the VTP domain, all other switches within that domain enables VTPv2
            - Two VTP versions 3 regions can only communicate in transparent mode over VTPv1 or v2
            - VTP version 3 device does not accept configuration information from a VTP version 2 or version 1 device
            - VTPv1 and VTPv2 does not support Private VLAN. If Private VLANs are configured, the switch must be in transparent mode
            - VTPv3 supports Private VLAN
            - Domain names cannot be removed but can be changed


No comments:

Post a Comment