Virtual Chassis Case Study
This section combines the information we’ve covered thus far in the form of a practical VC deployment case study based on the book’s topology. Here are the design requirements:
Rename Switch 3,
Vodka, toVodkila, to reflect the impending merger of the two previously standalone switch names.Note
There is an old saying that mixing beer and whiskey is risky; this is sage advice and we can only hope that no ill effects result from the vodka-tequila combination that is soon to be born!
Assign 172.16.69.34/24 to the OoB interface; ensure that incoming Telnet and console connections to any switch members are redirected to the current VC master.
Switch 3 and Switch 4 share a closet; the third member is located in a remote closet.
Ensure that Switch 3 and Switch 4 can function as the master RE in a non-revertive manner.
Ensure that the third VC member functions as an LC whenever either or both Switch 3 and Switch 4 are operational.
Assign Switch 3 and Switch 4, and the new VC member IDs 0, 1, and 2, respectively.
Ensure that no additional switches can join the VC without management intervention.
The design must have no single point of VC failure, and the loss of any VC trunk should not prevent ongoing communications.
You may need the following information to complete your task:
All three VC member switches have a 4×1 GE uplink module installed.
The EX4200 serial numbers are:
Switch 3 = BM0208269780
Switch 4 = BM0208269767
Third VC member = BM0208269780
Figure 4-16 shows the before ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access