Example: Configuring the JCS1200 Platform as a Route Reflector

Requirements

This configuration example requires the following hardware and software components:

• Junos OS Release 9.5 or later
• One JCS1200 platform with Routing Engines in slots 1, 2, 3, and 4
• One T640 router with FPCs in slots 0, 1, and 2

Overview and Topology

Figure 1: Example: Route Reflection

Figure 1 shows a T640 router (T-route) and four Routing Engines (RR, R1, R2, and R3) on the JCS1200 chassis (bcg) configured for route reflection.

Each router is configured as a separate PSD. Each PSD has an associated Routing Engine assigned on the JCS chassis and an associated FPC assigned on the T640 router. Table 1 provides the chassis parameters required for the JCS1200 platform and for the T640 router for each PSD.

Configuration

The configuration of route reflection is described in the following sections:

• JCS1200 Configuration
• RSD Configuration
• PSD15 Configuration (Route Reflector)
• PSD11 Configuration (Router 1)
• PSD12 Configuration (Router 2)
• PSD13 Configuration (Router 3)

JCS1200 Configuration

Step-by-Step Procedure

1. Log in to the JCS management module CLI.
2. Configure the Routing Engine that is part of PSD15. This Routing Engine is located in slot 1 of the JCS chassis and acts as the route reflector.

   To configure the Routing Engine in slot 1, issue the following command:

   system> baydata -b 01 -data “V01–JCS1–SD2–PSD15–REP01–REB00–PRDSCE”

   The baydata command specifies the target as a bay blade (-b), identifies the Routing Engine (blade) in slot 01, and specifies the following parameters:

   • V01—Product version, which is 01.
   • JCS1—JCS platform identifier, which is 1.
   • SD2—RSD identifier, which is 2.
   • PSD15—PSD identifier, which is 15.
   • REP01—Slot in which the primary Routing Engine resides, which is 01.
   • REB00—Slot in which the backup Routing Engine resides. 00 indicates that there is no backup Routing Engine.
   • PRDSCE—Juniper Networks router product. There is a special product type for the route reflector: Standalone Control Element (SCE).
3. Configure the Routing Engine that is part of PSD11 This Routing Engine is located in slot 2 of the JCS chassis and acts as standalone router (not a route reflector).

   To configure the Routing Engine in slot 2, issue the following command:

   system> baydata -b 02 -data “V01–JCS1–SD1–PSD11–REP02–REB00–PRDT640”

   The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 02, and specifies the following parameters:

   • V01—Product version, which is 01.
   • JCS1—JCS platform identifier, which is 1.
   • SD1—RSD identifier, which is 1. This router is in SD1, the route reflector is in SD2.
   • PSD11—PSD identifier, which is 11.
   • REP02—Slot in which the primary Routing Engine resides, which is 02.
   • REB00–Slot in which the backup Routing Engine resides. 00 indicates that there is no backup Routing Engine.
   • PRDT640—Juniper Networks router product, which is the T640 router.
4. Configure the Routing Engine that is part of PSD12. This Routing Engine is located in slot 3 of the JCS chassis and acts as standalone router (not a route reflector).

   To configure the Routing Engine in slot 3, issue the following command:

   system> baydata -b 03 -data “V01–JCS1–SD1–PSD12–REP03–REB00–PRDT640”

   The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 03, and specifies the following parameters:

   • V01—Product version, which is 01.
   • JCS1—JCS platform identifier, which is 1.
   • SD1—RSD identifier, which is 1. This router is in SD1, the route reflector is in SD2.
   • PSD12—PSD identifier, which is 12.
   • REP03—Slot in which the primary Routing Engine resides, which is 03.
   • REB00–Slot in which the backup Routing Engine resides. 00 indicates that there is no backup Routing Engine.
   • PRDT640—Juniper Networks router product, which is the T640 router.
5. Configure the Routing Engine that is part of PSD13. This Routing Engine is located in slot 4 of the JCS chassis and acts as standalone router (not a route reflector).

   To configure the Routing Engine in slot 4, issue the following command:

   system> baydata -b 04 -data “V01–JCS1–SD1–PSD13–REP04–REB00–PRDT640”

   The baydata command specifies the target as a bay blade (-b), identifies the blade (Routing Engine) in slot 04, and specifies the following parameters:

   • V01—Product version, which is 01.
   • JCS1—JCS platform identifier, which is 1.
   • SD1—RSD identifier, which is 1. This router is in SD1, the route reflector is in SD2.
   • PSD13—PSD identifier, which is 13.
   • REP04—Slot in which the primary Routing Engine resides, which is 04.
   • REB00–Slot in which the backup Routing Engine resides. 00 indicates that there is no backup Routing Engine.
   • PRDT640—Juniper Networks router product, which is the T640 router.

Results

Display the results of the configuration:

Bay  Status            Definition
1    Supported         V01-JCS1-SD2-PSD15-REP01-REB00-PRDSCE
2    Supported         V01-JCS1-SD1-PSD11-REP02-REB00-PRDT640
3    Supported         V01-JCS1-SD1-PSD12-REP03-REB00-PRDT640
4    Supported         V01-JCS1-SD1-PSD13-REP04-REB00-PRDT640
5    No blade present
6    No blade present
7    No blade present
8    No blade present
9    No blade present
10   No blade present
11   No blade present
12   No blade present

RSD Configuration

Step-by-Step Procedure

1. Log in to the T640 router.
2. At the [edit chassis system-domains] hierarchy level of the Junos OS CLI, include the root-domain-id 1 statement to identify the RSD associated with Router 1, 2, and 3.
3. At the [edit chassis system-domains] hierarchy level, include the protected-system-domains psd11 statement to create PSD11.
4. At the [edit chassis system-domains protected-system-domains psd11] hierarchy level:
   1. Include the description “bcgcpu2 SWLab R1” statement to describe the PSD.
   2. Include the fpcs 1 statement to assign the FPC in slot 1 to PSD11.
   3. Include the control-system-id 1 statement to identify the JCS1200 platform.
   4. Include the control-slot-numbers 2 statement to assign the Routing Engine in slot 2 in the JCS chassis to PSD11.
5. At the [edit chassis system-domains] hierarchy level, include the protected-system-domains psd12 statement to create PSD12.
6. At the [edit chassis system-domains protected-system-domains psd12] hierarchy level:
   1. Include the description “bcgcpu3 SWLab R2” statement to describe the PSD.
   2. Include the fpcs 2 statement to assign the FPC in slot 2 to PSD12.
   3. Include the control-system-id 1 statement to identify the JCS1200 platform.
   4. Include the control-slot-numbers 3 statement to assign the Routing Engine in slot 3 in the JCS chassis to PSD12.
7. At the [edit chassis system-domains] hierarchy level, include the protected-system-domains psd13 statement to create PSD13.
8. At the [edit chassis system-domains protected-system-domains psd13] hierarchy level:
   1. Include the description “bcgcpu4 SWLab R3” statement to describe the PSD.
   2. Include the fpcs 0 statement to assign the FPC in slot 0 to PSD13.
   3. Include the control-system-id 1 statement to identify the JCS1200 platform.
   4. Include the control-slot-numbers 4 statement to assign the Routing Engine in slot 4 in the JCS chassis to PSD13.

Results

Display the results of the configuration:

The RSD configuration on the T640 router does not include a root-domain-id 2 statement for domain 2 (the route reflector domain) or any protected-system-domains PSD15 statements for the route reflector PSD. This is because the route reflector is self-contained within the JCS chassis and does not require configuration on the T640 router.

PSD15 Configuration (Route Reflector)

Step-by-Step Procedure

1. At the [edit interfaces] hierarchy level, include the fxp0 statement to configure the internal Ethernet interface.
2. At the [edit interfaces fxp0] hierarchy level, include the unit 1 statement to configure the logical interface.
3. At the [edit interfaces fxp0 unit 1] hierarchy level, include the family inet address 10.12.100.18/30 statement to configure the IP version 4 (IPv4) suite protocol family.
4. At the [edit interfaces] hierarchy level, include the fxp1 statement to configure the internal Ethernet interface.
5. At the [edit interfaces fxp1] hierarchy level, include the unit 1 statement to configure the logical interface.
6. At the [edit interfaces fxp1 unit 1] hierarchy level, include the family inet address 10.12.100.14/30 statement to configure the IPv4 suite protocol family.

Results

Display the results of the configuration:

PSD11 Configuration (Router 1)

Step-by-Step Procedure

1. At the [edit interfaces] hierarchy level, include the ge-1/1/0 statement to configure the Gigabit Ethernet interface.
2. At the [edit interfaces ge-1/1/0] hierarchy level, include the unit 0 statement to configure the logical interface.
3. At the [edit interfaces ge-1/1/0 unit 0] hierarchy level, include the family inet address 10.12.100.10/30 statement to configure the IPv4 suite protocol family.
4. At the [edit interfaces] hierarchy level, include the ge-1/1/1 statement to configure the internal Ethernet interface.
5. At the [edit interfaces ge-1/1/1] hierarchy level, include the unit 0 statement to configure the logical interface.
6. At the [edit interfaces ge-1/1/1 unit 0] hierarchy level, include the family inet address 10.12.100.6/30 statement to configure the IPv4 suite protocol family.

Results

Display the results of the configuration:

PSD12 Configuration (Router 2)

Step-by-Step Procedure

1. At the [edit interfaces] hierarchy level, include the ge-2/0/1 statement to configure the Gigabit Ethernet interface.
2. At the [edit interfaces ge-2/0/1] hierarchy level, include the unit 0 statement to configure the logical interface.
3. At the [edit interfaces ge-2/0/1 unit 0] hierarchy level, include the family inet address 10.12.100.13/30 statement to configure the IPv4 suite protocol family.
4. At the [edit interfaces] hierarchy level, include the ge-2/0/2 statement to configure the internal Ethernet interface.
5. At the [edit interfaces ge-2/0/2] hierarchy level, include the unit 0 statement to configure the logical interface.
6. At the [edit interfaces ge-2/0/2 unit 0] hierarchy level, include the family inet address 10.12.100.5/30 statement to configure the IPv4 suite protocol family.
7. At the [edit interfaces] hierarchy level, include the ge-2/0/3 statement to configure the internal Ethernet interface.
8. At the [edit interfaces ge-2/0/3] hierarchy level, include the unit 0 statement to configure the logical interface.
9. At the [edit interfaces ge-2/0/3 unit 0] hierarchy level, include the family inet address 10.12.100.1/30 statement to configure the IPv4 suite protocol family.

Results

Display the results of the configuration:

PSD13 Configuration (Router 3)

Step-by-Step Procedure

1. At the [edit interfaces] hierarchy level, include the ge-0/1/7 statement to configure the Gigabit Ethernet interface.
2. At the [edit interfaces ge-0/1/7] hierarchy level, include the unit 0 statement to configure the logical interface.
3. At the [edit interfaces ge-0/1/7 unit 0] hierarchy level, include the family inet address 10.12.100.2/30 statement to configure the IPv4 suite protocol family.
4. At the [edit interfaces] hierarchy level, include the ge-0/2/3 statement to configure the internal Ethernet interface.
5. At the [edit interfaces ge-0/2/3] hierarchy level, include the unit 0 statement to configure the logical interface.
6. At the [edit interfaces ge-0/2/3 unit 0] hierarchy level, include the family inet address 10.12.100.9/30 statement to configure the IPv4 suite protocol family.
7. At the [edit interfaces] hierarchy level, include the ge-0/1/0 statement to configure the internal Ethernet interface.
8. At the [edit interfaces ge-0/1/0] hierarchy level, include the unit 0 statement to configure the logical interface.
9. At the [edit interfaces ge-0/1/0 unit 0] hierarchy level, include the family inet address 10.12.100.17/30 statement to configure the IPv4 suite protocol family.

Results

Display the results of the configuration: