Supported Platforms
Configuring Member IDs for a Virtual Chassis
After you commit the preprovisioned configuration on the master router, you must assign the preprovisioned member IDs to both MX Series routers in the Virtual Chassis by using the request virtual-chassis member-id set command. Assigning the member ID causes the router to reboot in preparation for forming the Virtual Chassis.
 | Note: If you issue the request virtual-chassis member-id set command without first installing an MX Virtual Chassis Redundancy Feature Pack license on both member routers, the software displays a warning message that you are operating without a valid Virtual Chassis software license. |
To configure the member ID and reboot each MX Series router in Virtual Chassis mode:
- Set the member ID on the router configured as member 0.user@hostA> request virtual-chassis member-id set member 0
This command will enable virtual-chassis mode and reboot the system.
Continue? [yes,no] yes
- Set the member ID on the router configured as member 1.user@hostB> request virtual-chassis member-id set member 1
This command will enable virtual-chassis mode and reboot the system.
Continue? [yes,no] yes
- (Optional) Verify the member ID configuration for member 0.
For example:
{master:member0-re0}user@hostA> show virtual-chassis statusPreprovisioned Virtual Chassis Virtual Chassis ID: 4f2b.1aa0.de08
Mastership Neighbor List
Member ID Status Serial No Model priority Role ID Interface 0 (FPC 0- 11) Prsnt JN10C7135AFC mx240 129 Master* - (Optional) Verify the member ID configuration for member 1.
For example:
Amnesiac (ttyd0) login: user Password:
...{master:member1-re0}Virtual Chassis ID: ef98.2c6c.f7f7 Mastership Neighbor List
Member ID Status Serial No Model priority Role ID Interface 1 (FPC 12- 23) Prsnt JN115D117AFB mx480 128 Master*Note: At this point in the configuration procedure, all line cards are offline, and the routers are each designated with the Master role because they are not yet interconnected as a fully formed Virtual Chassis. In addition, member 1 remains in Amnesiac state (has no defined configuration) until the Virtual Chassis forms and the configuration is committed.
