Supported Platforms
Related Documentation
baydata
Syntax
baydata <–b n> (-clear | -data “data-definition”)
Release Information
Command supported by Junos OS Release 9.1 and later.
Description
(JCS management module CLI) Display, configure, or remove informational data (blade bay data) associated with Routing Engine blades.
 | Note: When a blade restarts, the status should change from “BSMP” to “Supported”. The "Supported" status indicates that the blade has been restarted since the last baydata change for that blade, and it should have the proper baydata configuration information. However, if the management module (MM) is reset, all blades will show a "BSMP" status, because the MM does not know if the blades have current baydata information after a restart. As individual blades are restarted, their status should change to "Supported". |
Options
-b n—(Optional) Specify a specific Routing Engine. Replace n with the Routing Engine slot number (1 through 12). If a Routing Engine is not specified, the command applies to all Routing Engines in the JCS chassis.
–clear—Remove the blade bay data definition.
-data “data-definition”—Set the blade bay data. Blade bay data is an ASCII text string with the following format: Vn-JCSn-SDn-PSDn-REPn-REBn-PRDplatform-type. Enclose the text string in double quotation marks (” “).
- Vn—Version number of the blade bay data. Replace n with a version number. The accepted value is 01.
- JCSn—JCS identifier. Replace n with the ID number of the JCS. The range of values is 01 through 04.
- SDn—RSD identifier. Replace n with the ID number of the RSD. The range of values is 01 through 03.
- PSDn—PSD identifier. Replace n with the ID number of the PSD. The range is 01 through 31.
- REPn—Slot number of the primary Routing Engine in a primary, backup Routing Engine pair. Replace n with the slot number of the Routing Engine. The range is 01 through 12.
- REBn—Slot number of the backup Routing Engine in a primary, backup Routing Engine pair. Replace n with the slot number of the Routing Engine. The range is 01 through 12.
- PRDplatform-type—Routing platform type. Replace platform-type with one of the following values: T1600, T640, T320, or SCE (standalone control element).
Required Privilege Level
supervisor
Related Documentation
List of Sample Output
baydata (Display)baydata (Configure a Routing Engine)
baydata (Clear a Routing Engine)
baydata (Clear All Routing Engines)
Output Fields
Table 1 lists the output fields for the baydata command. Output fields are listed in the approximate order in which they appear.
Table 1: baydata Output Fields
Field Name | Field Description |
|---|---|
Bay | Slot number of the Routing Engine (blade). |
Status | Status of the Routing Engine. |
Definition | Blade bay data (if any) assigned to the Routing Engine. |
Sample Output
baydata (Display)
system> baydataBay Status Definition 1 Unsupported 2 No blade present 3 Supported V01–JCS01–SD01–PSD01–REP03–REB04–PRDT640 4 Supported V01–JCS01–SD01–PSD01–REP03–REB04–PRDT640 5 Supported V01–JCS01–SD01–PSD01–REP05–REB06–PRDT640 6 Supported V01–JCS01–SD01–PSD01–REP05–REB06–PRDT640 7 No blade present 8 No blade present 9 No blade present 10 No blade present 11 No blade present 12 No blade present
baydata (Configure a Routing Engine)
system> baydata —b 05 —data “V01–JCS01–SD01–PSD01–REP05–REB06–PRDT1600”OK
baydata (Clear a Routing Engine)
system> baydata –b 06 —clear OK
baydata (Clear All Routing Engines)
system> baydata —clear OK
