Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX] Converting a Virtual Chassis Member Role from Linecard to Backup

0

0

Article ID: KB21115 KB Last Updated: 05 Jun 2011Version: 1.0
Summary:

This article assists you with converting a Virtual Chassis’s Role from Linecard to Back-Up. This document will help the user who prefers to make a Linecard of a Virtual Chassis to a Backup role.

This article is part of the EX Resolution Guide: KB21064 - Verifying health of Virtual Chassis and troubleshoot if the members are not all present.


Symptoms:

  • How do I change my Linecard to a Backup?
  • I want to make my Linecard as a Back-up Role.
  • A different member is preferred to be backup.

For example, in the 'show virtual-chassis' output below, FPC 0 - (BR0208233776) is preferred to act as Backup.

root@EX4200-VC# run show virtual-chassis    

Virtual Chassis ID: 6eb0.0094.e64b
                                          Mastership            Neighbor List  
Member ID   Status   Serial No    	Model          priority   Role     ID  Interface
0 (FPC 0)   Prsnt    BR0208233776 	ex4200-24f     128        Linecard  1  vcp-0      
1 (FPC 1)   Prsnt    BR0209456997 	ex4200-24f     128        Master*   2  vcp-0      
                                                                            0  vcp-1      
2 (FPC 2)   Prsnt    BR0208233803 	ex4200-24f     128        Backup    1  vcp-1      

Member ID for next new member: 3 (FPC 3)


Solution:

Reduce the mastership-priority of the existing Backup to be lower that the expected Backup.

In the example above, reduce the mastership-priority of Member FPC 2 to be lower than the 'expected' Backup Member FPC 0 with the following command:
root@EX4100-VC# set virtual-chassis member 2 mastership-priority 127
After changing the mastership-priority, a commit synchronize needs to be executed. 
root@EX4100-VC# commit synchronize
Refer to KB12879 on understanding commit synchronize.

The end result will be as follows:

root@EX4200-VC# run show virtual-chassis    

Virtual Chassis ID: 6eb0.0094.e64b
                    Mastership            Neighbor List  
Member ID   Status      Serial No    	Model        priority   Role        ID  Interface
0 (FPC 0)   Prsnt       BR0208233776 	ex4200-24f   128        Backup       1  vcp-0      
1 (FPC 1)   Prsnt       BR0209456997 	ex4200-24f   128        Master*      2  vcp-0      
                                                                             0  vcp-1      
2 (FPC 2)   Prsnt       BR0208233803 	ex4200-24f   127        Linecard     1  vcp-1      

Member ID for next new member: 3 (FPC 3)



Related links in the Technical Documentation:

Troubleshooting Mastership Priority

Understanding How the Master in an EX4200 or EX4500 Virtual Chassis Is Elected



Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search