In this configuration example, the JCS 1200 platform is connected to multiple T-series routing platforms. The configuration is described in the following sections:
This configuration example requires the following hardware and software components:
This example configures the JCS 1200 platform and three connected T-series routing platforms. For this example, you need to configure a Root System Domain (RSD) for each connected T-series routing platform. Within each RSD, create Protected System Domains (PSDs) and assign Flexible PIC Controllers (FPCs) and Routing Engines to each PSD.
First, configure the Routing Engines on the JCS 1200 platform using the management module CLI. Then, configure each T-series routing platform using the JUNOS CLI.
To configure the parameters required for the Routing Engines in the JCS chassis:
Table 20: JCS Chassis Routing Engine Assignments
|
RSD ID |
PSD ID |
Primary Routing Engine |
Backup Routing Engine |
Routing Platform |
|---|---|---|---|---|
|
1 |
1 2 |
01 03 |
02 04 |
T320 |
|
2 |
3 4 |
05 07 |
06 08 |
T640 |
|
3 |
5 6 |
09 11 |
10 12 |
T1600 |
system> baydata —b 01 —data
“V01–JCS01–SD01–PSD01–REP01–REB02–PRDT320”
system> baydata —b 02 —data
“V01–JCS01–SD01–PSD01–REP01–REB02–PRDT320”
system> baydata —b 03 —data
“V01–JCS01–SD01–PSD02–REP03–REB04–PRDT320”
system> baydata —b 04 —data
“V01–JCS01–SD01–PSD02–REP03–REB04–PRDT320”
system> baydata —b 05 —data
“V01–JCS01–SD02–PSD03–REP05–REB06–PRDT640”
system> baydata —b 06 —data
“V01–JCS01–SD02–PSD03–REP05–REB06–PRDT640”
system> baydata —b 07 —data
“V01–JCS01–SD02–PSD04–REP07–REB08–PRDT640”
system> baydata —b 08 —data
“V01–JCS01–SD02–PSD04–REP07–REB08–PRDT640”
system> baydata —b 09 —data
“V01–JCS01–SD03–PSD05–REP09–REB10–PRDT1600”
system> baydata —b 10 —data
“V01–JCS01–SD03–PSD05–REP09–REB10–PRDT1600”
system> baydata —b 11 —data
“V01–JCS01–SD03–PSD06–REP11–REB12–PRDT1600”
system> baydata —b 12 —data
“V01–JCS01–SD03–PSD06–REP11–REB12–PRDT1600”
Display the results of the configuration:
system> baydata
Bay Status Definition 1 Supported V01–JCS01–SD01–PSD01–REP01–REB02–PRDT320 2 Supported V01–JCS01–SD01–PSD01–REP01–REB02–PRDT320 3 Supported V01–JCS01–SD01–PSD02–REP03–REB04–PRDT320 4 Supported V01–JCS01–SD01–PSD02–REP03–REB04–PRDT320 5 Supported V01–JCS01–SD02–PSD03–REP05–REB06–PRDT640 6 Supported V01–JCS01–SD02–PSD03–REP05–REB06–PRDT640 7 Supported V01–JCS01–SD02–PSD04–REP07–REB08–PRDT640 8 Supported V01–JCS01–SD02–PSD04–REP07–REB08–PRDT640 9 Supported V01–JCS01–SD03–PSD05–REP09–REB10–PRDT1600 10 Supported V01–JCS01–SD03–PSD05–REP09–REB10–PRDT1600 11 Supported V01–JCS01–SD03–PSD06–REP11–REB12–PRDT1600 12 Supported V01–JCS01–SD03–PSD06–REP11–REB12–PRDT1600
To configure the RSD and create the PSDs on the T320 router:
Table 21: T320 Router Configuration
|
PSD |
FPCs |
Redundant Routing Engine Slots |
|---|---|---|
|
1 |
0, 1, 2, and 3 |
1 and 2 |
|
2 |
4, 5, 6, and 7 |
3 and 4 |
Display the results of the configuration:
- system-domains {
- root-domain-id 1;
-
- protected-system-domains {
-
- psd1 {
- description “psd for customer1”;
- fpcs [ 0 1 2 3];
- control-system-id 1;
- control-slot-numbers [ 1 2 ];
- }
-
- psd2 {
- description “psd for customer2”;
- fpcs [ 4 5 6 7];
- control-system-id 1;
- control-slot-numbers [ 3 4 ];
- }
- }
- }
To configure the RSD and create the PSDs on the T640 routing node:
Table 22: T640 Router Configuration
|
PSD |
FPCs |
Redundant Routing Engine Slots |
|---|---|---|
|
3 |
0, 1, 2, and 3 |
5 and 6 |
|
4 |
4, 5, 6, and 7 |
7 and 8 |
Display the configuration results:
- system-domains {
- root-domain-id 2;
-
- protected-system-domains {
-
- psd3 {
- description “psd for customer3”;
- fpcs [ 0 1 2 3];
- control-system-id 1;
- control-slot-numbers [ 5 6 ];
- }
-
- psd4 {
- description “psd for customer4”;
- fpcs [ 4 5 6 7];
- control-system-id 1;
- control-slot-numbers [ 7 8 ];
- }
- }
- }
To configure the RSD and create the PSDs on the T1600 routing node:
Table 23: T1600 Router Configuration
|
PSD |
FPCs |
Redundant Routing Engine Slots |
|---|---|---|
|
5 |
0, 1, 2, and 3 |
9 and 10 |
|
6 |
4, 5, 6, and 7 |
11 and 12 |
Display the configuration results:
- system-domains {
- root-domain-id 3;
-
- protected-system-domains {
-
- psd5 {
- description “psd for customer5”;
- fpcs [ 0 1 2 3];
- control-system-id 1;
- control-slot-numbers [ 9 10 ];
- }
-
- psd6 {
- description “psd for customer6”;
- fpcs [ 4 5 6 7];
- control-system-id 1;
- control-slot-numbers [ 11 12 ];
- }
- }
- }
Verify that the PSDs configured under each RSD are online.
Issue the show chassis psd command:
RSD1user@rsd1> show chassis psd
PSD Description State Uptime 1 psd for customer1 Online 1 hour, 12 minutes, 15 seconds 2 psd for customer2 Online 1 hour, 12 minutes, 15 secondsRSD2
user@rsd2> show chassis psd
PSD Description State Uptime 3 psd for customer3 Online 1 hour, 12 minutes, 15 seconds 4 psd for customer4 Online 1 hour, 12 minutes, 15 secondsRSD3
user@rsd3> show chassis psd
PSD Description State Uptime 5 psd for customer5 Online 1 hour, 12 minutes, 15 seconds 6 psd for customer6 Online 1 hour, 12 minutes, 15 seconds
RSD1 owns PSD1 and PSD2. RSD2 owns PSD3 and PSD4. RSD3 owns PSD4 and PSD5. All PSDs are online.
Verify that each PSD is assigned the correct FPCs on the T-series routing platform.
For each PSD, issue the show chassis fpc command. For example:
user@psd1> show chassis fpc
rsd-re0:
--------------------------------------------------------------------------
Temp CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt DRAM (MB) Heap Buffer
0 Online 34 3 1 256 12 50
1 Online 52 4 0 2048 3 24
2 Online 34 3 1 256 12 50
3 Online 52 4 0 2048 3 24
In this example, PSD1 owns the FPCs in slots 0, 1, 2, and 3 on the T-series routing platform.
Verify that each PSD owns the correct Routing Engines on the JCS chassis.
On each PSD, issue the show chassis routing-engine command. For example:
user@psd2> show chassis routing-engine
Routing Engine status:
Slot 0:
Physical Slot 3
Current state Master
Election priority Master (default)
DRAM 3328 MB
Memory utilization 11 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-JCS1200-1x2330
Serial ID SNBLBCD001
Start time 2008-09-03 13:49:00 PDT
Uptime 27 days, 2 hours, 50 minutes, 9 seconds
Last reboot reason 0x49:power cycle/failure power-button hard power off thermal shutdown
Routing Engine status:
Slot 1:
Physical Slot 4
Current state Backup
Election priority Backup (default)
DRAM 3328 MB
Memory utilization 10 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-JCS1200-1x2330
Serial ID SNBLBCD002
Start time 2008-09-24 17:04:01 PDT
Uptime 5 days, 23 hours, 35 minutes, 18 seconds
Last reboot reason 0x49:power cycle/failure power-button hard power off thermal shutdown
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
In this example, PSD2 owns the Routing Engines in slots 3 and 4 on the JCS chassis as indicated by the values in the Physical Slot fields. The Routing Engine in slot 3 is the master, whereas the Routing Engine in slot 4 is the backup.