Technical Documentation
Configuring the Routing Engine Parameters (Blade Bay Data)
To pass system configuration information to the Routing Engines on the JCS, you must configure the blade bay data. Blade bay data is stored as a 60-byte text string that contains information about how the Routing Engines on the JCS1200 platform are mapped to PSDs and to the RSD. The blade bay mapping information is passed from the JCS management module to the appropriate Routing Engine, so that it is available when the Junos OS boots.
You enter a blade bay data string for each primary and standby Routing Engine on the JCS chassis.
Blade bay data is entered as a text string with the following format. See Table 1 for details.
n is a number. platform-type is the routing platform type (T1600, T640, or T320).
Table 1: Format Requirements for Blade Bay Data
Item | Description |
|---|---|
V | Version number of the blade bay data. The accepted value is 01. |
JCS | JCS identifier. The range of values is 01 through 04. The value for this parameter must match the value set by the control-system-id statement configured through the Junos OS CLI. |
SD | RSD identifier. The range of values is 01 through 03. The value for this parameter must match the value set by the root-domain-id statement configured in the Junos OS CLI. |
PSD | PSD identifier. Each identifier must be unique. The value range is 01-31. The value for this parameter must match the value set by the protected-system-domains statement configured through the Junos OS CLI. |
REP | Slot identifier of the primary Routing Engine. The value range is 01 through 12. In the absence of any Junos OS CLI configuration that affects mastership, the Routing Engine in the slot indicated by REP will boot as the master, and the Routing Engine in slot REB will boot as the backup. The value for this parameter must match the value set by the control-slot-numbers statement configured through the Junos OS CLI. |
REB | Slot identifier of the backup Routing Engine. Typically, the value range is 01 through 12. Use 00 if no backup Routing Engine is installed. In the absence of any Junos OS CLI configuration that affects mastership, the Routing Engine in the slot indicated REB will boot as the backup. |
PRD | Routing platform type. The accepted values are T1600, T640, T320, or SCE (standalone control element). |
To enter the blade bay data:
- Log in to the JCS management module.
- Use the baydata command to configure the blade bay data. For example:
baydata -b 1 -data “V01–JCS01–SD01–PSD01–REP01–REB02–PRDT640”baydata -b 2 -data “V01–JCS01–SD01–PSD01–REP01–REB02–PRDT640”The bay data slots are Routing Engine slots 1 through 12 on the JCS chassis. In this example, the blade bay data is configured for the Routing Engine in slot 1 and the Routing Engine in slot 2. Blade 1 is the primary Routing Engine of PSD 1. Blade 2 is the backup Routing Engine of PSD 1. PSD 1 is connected to RSD 1, and RSD 1 is a T640 router.
- Repeat this procedure for each Routing Engine on the JCS1200 platform.
