subject: Cisco CCNA Certification Examination Tutorial: Configuring And Troubleshooting VTP [print this page] Cisco CCNA Certification Examination Tutorial: Configuring And Troubleshooting VTP
Not only is your CCNA exam going to have questions on VLAN trunking protocol, almost any network that has more than one VLAN is going to have VTP running. Whether or not you're planning on passing the CCNA exam or just brushing up in your networking expertise, this VTP tutorial will help you study the fundamentals of this important protocol.
VTP permits switches to advertise VLAN information between different members of the identical VTP domain. VTP permits a consistent view of the switched network across all switches. When a VLAN is created on one swap in a VTP server, all other VTP units within the domain are notified of that VLAN's existence. VTP servers will know about each VLAN, even VLANs that haven't any members on that switch.
Switches run VTP in one in every of three modes. In server mode, VLANs might be created, modified, and deleted on a VTP server. When these actions are taken, the adjustments are marketed to all switches in the VTP domain. VTP Servers maintain VLAN configuration info upon reboot.
In client mode, the switch cannot modify, create, or delete VLANs. VTP shoppers can not retain VLAN configuration data upon reboot; they should obtain this info from a VTP server.
In real-world networks, that is usually executed to centralize the creation and deletion of VLANs. An interesting aspect impact of the server/consumer methodology is that if a VLAN is only to have ports on the VTP shopper swap, the VLAN should still first be created on the VTP server. The VTP consumer will learn about the VLAN from the VTP server, and ports can then be positioned into that VLAN.
The third VTP mode is transparent mode. VTP switches on this mode ignore VTP messages. They do forward the VTP ads received from different switches. VLANs might be created, deleted, and modified on a clear server, however these modifications are usually not advertised to the other switches in the VTP domain.
For switches running VTP to efficiently alternate VLAN information, three things have to happen. I've listed them for you within the order that you're going to see them in the real world.
The VTP domain title must match. This is case-sensitive. "CISCO" and "cisco" are different domains.
To distribute details about a newly-created VLAN, the switch upon which that VLAN is created must be in Server mode.
Studying VTP isn't simply a good suggestion for passing your CCNA exams, it is a talent you will need to should be efficient in configuring and troubleshooting VLANs. I wish you the best in each of these pursuits!
The commonest technique of configuring ISDN is with dialer maps, but dial data will also be configured on a logical interface. To move the CCNA examination, you could know tips on how to configure and troubleshoot both dialer maps and dialer profiles.
Dialer Profiles enable different dialing info to be configured onto logical interfaces. The logical interfaces might have different dialing destinations, totally different remote router names, etc., but they'll be using the same bodily interface.
Dialer strings are used on dialer profiles. Notice that every logical interface has a different IP deal with, a special distant router to dial, and a special dialer string, but they will be using the same bodily interface to dial out. The instructions dialer pool and dialer pool-member are used to link the logical and physical interfaces. The number following every command should match for the logical interface to accurately bind to the physical interface.
R1(config)interface dialer0
R1(config-if)ip tackle 172.16.1.1 255.255.255.0
R1(config-if)encapsulation ppp
R1(config-if)dialer remote-name Remote0
R1(config-if)dialer pool 1
< places logical interface into dialer pool >
R1(config-if)dialer string 5551212
< quantity dialed to contact router Remote0 >
R1(config-if)dialer-group 1
< links logical interface to dialer-record 1 >
R1(config)interface dialer1
R1(config-if)ip deal with 172.16.1.2 255.255.255.0
R1(config-if)encapsulation ppp
R1(config-if)dialer remote-identify Remote1
R1(config-if)dialer pool 1
R1(config-if)dialer string 5551234
R1(config-if)dialer-group 1
R1(config)interface bri0
R1(config-if)no ip tackle
< With dialer profiles, IP addresses are assigned to logical interfaces. >
R1(config-if)encapsulation ppp
< The encapsulation sort is place on both the logical and bodily interfaces.>
R1(config-if)dialer pool-member 1
< The number related to this command ought to match the quantity configured with the dialer pool number on the logical dialer interfaces. >
R1(config-if)isdn spid1 0835866101
R1(config-if)isdn spid2 0835866301
When configuring dialer profiles, the encapsulation sort needs to be positioned on each the physical BRI interface and the logical dialer interfaces. The SPIDs are configured on the physical interface as well.
Configuring dialer profiles generally is a little difficult at first, and the best way to grasp this skill is to get actual hands-on follow in your individual CCNA / CCNP residence lab or a rack rental service. Either method, arms-on is the perfect practice. Best of luck in your CCNA research
