Description

This article discusses the steps that must be performed on a standalone switch before converting it into a satellite device in a Junos Fusion Provider Edge, processes for adding satellite devices to a Junos Fusion Provider Edge using auto conversion method.

Symptoms

Auto Conversion Method - If SD device has become faulty and requires a replacement, you may need to perform the replacement activity. In case of adding a new device as an SD, you may follow the same article to achieve the same.

Solution

Please follow the below steps:

 

Step 1. Log in to the device using the console port.

 

Zeroize the device:

 

user@satellite-device> request system zeroize

 

Step 2. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:

 

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port port-number

 

For example, to convert all four built-in 40-Gbps QSFP+ interfaces on an EX4300-24P switch into network ports:

 

user@satellite-device>request virtual-chassis vc-port delete pic-slot 1 port 0

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 1

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 2

user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 3

 

Adding Satellite Devices to the Junos Fusion Provider Edge using auto-conversion Method

 

To auto convert a switch into a satellite device:

 

Step 1. Cable a link between the aggregation device and the satellite device, if desired. Log in to the aggregation device.

 

Step 2. Configure the cascade ports. See Configuring the Cascade Ports on the Aggregation Device.

 

For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

 

[edit]

user@aggregation-device# set interfaces xe-0/0/1 cascade-port

 

Step 3. Associate an FPC slot ID with each satellite device. There are multiple methods of assigning FPC slot IDs

 

To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:

[edit]

user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports xe-0/0/1


Step 4. To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:

 

[edit]

user@aggregation-device# set chassis satellite-management fpc 101 serial-number ABCDEFGHIJKL


Step 5. To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:

[edit]

user@aggregation-device# set chassis satellite-management fpc 101 system-id 12:34:56:AB:CD:EF


Step 6. (Recommended) Configure an alias name for the satellite device:

[edit]

user@aggregation-device# set chassis satellite-management fpc slot-id alias alias-name


Step 7. where slot-id is the FPC slot ID of the satellite device defined in the previous step, and alias-name is the alias.

For example, to configure the satellite device numbered 101 as qfx5100-48s-1:
 

[edit]

user@aggregation-device# set chassis satellite-management fpc 101 alias qfx5100-48s-1

 

Step 8. To add the satellite device using FPC slot ID 101 to an existing software group named group1, or create a software upgrade group named group1 and add the satellite device using FPC slot 101 to the software upgrade group:

 

[edit]

user@aggregation-device# set chassis satellite-management upgrade-group group1 satellite 101

 

Step 9. If you are creating a new software upgrade group in this step, you also need to associate the group with a satellite software image. You can skip this final step if the software upgrade group has already been created and a satellite software package association exists.

 

Step 10. The configuration with the satellite software upgrade group must be committed before a satellite software image is associated with a satellite software upgrade group:

[edit]

user@aggregation-device# commit synchronize


Step 11. After committing the configuration, associate a satellite software image named satellite-1.0R1.1-signed.tgz to the upgrade group named group1:

user@aggregation-device> request system software add /var/tmp/satellite-1.0R1.1-signed.tgz upgrade-group group1


Step 12. Enable automatic satellite conversion:

[edit]
user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite slot-id

For example, to automatically convert FPC 101 into a satellite device:

[edit]
user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite 101

 

Step 13. Commit the configuration:

 

[edit]

user@aggregation-device# commit

If you want to commit the configuration to both Routing Engines:


Optional:

[edit]

user@aggregation-device# commit synchronize

 

The satellite software upgrade on the satellite device begins after this final step is completed, or after you cable the satellite device to a cascade port using automatic satellite conversion if you have not already cabled the satellite device to the aggregation device.

After the satellite software update, the switch operates as a satellite device in the Junos Fusion.

 

Modification History

2023-12-23 : Article Created