Configuring The Routing Engine (Blade) Name - Juniper JUNOS OS 10.4 - PROTECTED SYSTEM DOMAIN Configuration Manual

JUNOS 10.4 Protected System Domain Configuration Guide
Related
Documentation

Configuring the Routing Engine (Blade) Name

Related
Documentation
52
To enter the blade bay data:
Log in to the JCS management module.
1.
Use the command to configure the blade bay data. For example:
baydata
2.
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.
3.
Configuring an RSD and Creating PSDs on page 84
baydata on page 56
JCS configuration should include a name for each Routing Engine (blade) included with
the JCS1200 platform. This name is used to identify each Routing Engine in CLI command
output and so on.
To configure the blade name information:
Log in to the JCS management module.
1.
Use the env command to specify the blade you want to configure. For example:
2.
system> env -T blade[1]
Use the command to configure the blade name. For example:
3. config
system:blade[1]> config -name BLADE01
In this example, the blade name is
Engine on the network, and it appears in monitoring command output.
env on page 62
config on page 60
BLADE01 . This name identifies the JCS Routing
Copyright © 2010, Juniper Networks, Inc.