Qodex.ai

updateOrgVirtualChassisMember

PUT https://{{host}}/api/v1/orgs/:org_id/devices/:device_id/vc

op values:

  • add: add members to the virtual chassis
  • remove: remove members from the virtual chassis
  • preprovision: switch virtual chassis to preprovision mode
  • renumber: change virtual chassis member numbering

Add new members

For models (e.g. EX4300 and up) having dedicated VC ports, it is easier to add new member switches into a VC by just connecting cables with the dedicated VC ports. Cloud will detect the new members and update the inventory.

For EX2300 VC, adding new members requires to follow the procedures below:

  1. Powering on the new member switches and ensuring cables are not connected to any VC ports.

  2. Claim or adopt all new member switches under the VC’s organization Inventory

  3. Assign all new member switches to the same Site as the VC

  4. Invoke vc command to add switches to the VC.

  5. Connect the cables to the VC ports for these switches

  6. After a while, the Org’s Inventory shows this new switches has been added into the VC.

Removing member switch

To remove a member switch from the VC, following the procedures below:

  1. Ensuring the VC is connected to the cloud first

  2. Unplug the cable from the VC port of the switch

  3. Waiting for the VC state (vc_state) of this switch is changed to not-present

  4. Invoke update_vc with remove to remove this switch from the VC

  5. The Org’s Inventory shows the switch is removed.

Please notice that member ID 0 (fpc0) cannot be removed. When a VC has two switches left, unpluging the cable may result in the situation that fpc0 becomes a line card (LC). When this situation is happened, please re-plug in the cable, wait for both switches becoming present (show virtual-chassis) and then removing the cable again.

Perprovision VC members

By specifying “preprovision” op, you can convert the current VC to pre-provisioned mode, update VC members as well as specify vcports when adding new members for device models without dedicated vc ports. Use [renumber] for fpc0 replacement which involves deviceid change.

Note: 1. vc_ports is used for adding new members and not needed if * the device model has dedicated vc ports, or * no new member is added 2. New VC members to be added should exist in the same Site as the VC

[Update Device’s VC config] can achieve similar purpose by directly modifying current virtualchassis config. However, it cannot fulfill requests to enabling vcports on new members that are yet to belong to current VC.

Renumber VC members

When a member switch doesn’t work properly and needed to be replaced, the renumber API could be used. The following two types of renumber are supported:

  1. Replace a non-fpc0 member switch
  2. Replace fpc0. When fpc0 is relaced, PAPI device config and JUNOS config will be both updated.

For renumber to work, the following procedures are needed: 1. Ensuring the VC is connected to the cloud and the state of the member switch to be replaced must be non present. 2. Adding the new member switch to the VC 3. Waiting for the VC state (vc_state) of this VC to be updated to API server 4. Invoke vc with renumber to replace the new member switch from fpc X to

Request Body

{"op"=>"add", "members"=>[{"mac"=>"aff827549235", "member"=>0, "vc_ports"=>["xe-0/1/1"]}, {"mac"=>"aff827549235", "member"=>2, "vc_ports"=>["xe-0/1/1"]}, {"mac"=>"8396cd00777c", "vc_ports"=>["xe-0/1/0"], "vc_role"=>"linecard"}, {"mac"=>"8396cd00888c", "vc_ports"=>["xe-0/1/0"], "vc_role"=>"linecard"}]}