• Downloads
• Configuration Roadmap    

• Related Topics
• Configuring JCS Management Module Settings
• Configuring the JCS Switch Module
• Configuring the Routing Engine Parameters (Blade Bay Data)
• Configuring the Routing Engine (Blade) Name
• Configuring an RSD and Creating PSDs
• Configuring a PSD with a Single Routing Engine
• Configuring a PSD with Redundant Routing Engines
• Configuring Shared Interfaces on the RSD
• Configuring Shared Interfaces on a PSD

Configuration Roadmap

Step One: Configure the JCS1200 Platform

To configure the JCS1200 platform, log in to the JCS management module command-line interface (CLI) and:

1. Configure basic system parameters:
   • Restore the default configuration on the JCS management module.
   • Configure the JCS management module Ethernet management interface.
   • Configure the JCS switch module Ethernet management interface.
   • Create user accounts.
   • Configure the NTP server.
   • Configure the time zone.
   • Configure the system name and contact information.
   • Configure Secure Shell (SSH) access.
   • Configure Simple Network Management Protocol (SNMP) traps.
   • Configure the JCS switch module.
2. Configure the Routing Engines (blades) on the JCS1200 platform:
   • Configure Routing Engine (blade) bay data to assign a single Routing Engine (or redundant pair) to a Root System Domain (RSD) and to a unique Protected System Domain (PSD).
   • Configure Routing Engine (blade) names.

Step Two: Configure the T Series Router

Log in to the master Routing Engine on the T Series router to configure it as a Root System Domain (RSD) and to create Protected System Domains (PSDs) under the RSD. Through the JUNOS Software CLI or through the J-Web user interface:

1. Assign an ID number to the RSD.

   This ID number must match the ID number set through the JCS management module baydata command.

2. Configure a PSD and assign it an ID number.
3. Provide a description of the PSD.
4. Assign one or more FPCs to the PSD.

   Note: Any FPC that is not assigned to a PSD belongs to the RSD. For information about how to configure shared interfaces on a SONET PIC in an unassigned FPC, see Step Four: Configure Shared Interfaces (Optional).

5. Assign an ID number to the JCS1200 platform.

   The ID number must match the ID number set through the JCS management module baydata command.

6. Assign a Routing Engine (or redundant pair) on the JCS1200 platform to the PSD.

   Routing Engine assignments must match the assignments configured through the JCS management module baydata command.

7. Repeat Step Step 2 through Step Step 6 for each PSD to be configured under the RSD.
8. Repeat this entire procedure for each RSD.

Step Three: Configure Basic System Properties on a New PSD

To configure a PSD, connect to the console port on the Routing Engine on the JCS1200 platform for the PSD you want to configure and, using the JUNOS Software CLI, include the following information:

• Hostname
• Domain name
• Ethernet management IP addresses
• IP address of a backup router
• IP address of one or more DNS name servers on your network
• Password for the root account

Step Four: Configure Shared Interfaces (Optional)

Optionally, configure shared interfaces. Shared interfaces are configured on both the Root System Domain (RSD) and the Protected System Domain (PSD).

On the RSD

On the Root System Domain (RSD):

1. Configure the physical interface.
2. For SONET interfaces, configure Frame Relay encapsulation. For Ethernet interfaces, configure virtual LAN (VLAN) tagging.
3. Configure logical interfaces under the physical interface.
4. For each logical interface:
   1. Provide an identifier. For a SONET logical interface, configure a data-link connection identifier (DLCI). For an Ethernet logical interface, configure a virtual LAN (VLAN) identifier.
   2. Specify the Protected System Domain (PSD) that owns the shared interface.

On the PSD

On the Protected System Domain (PSD):

1. Configure the physical interface (as specified in the RSD configuration).
2. For a SONET interface, configure Frame Relay encapsulation on the physical interface to match the RSD configuration. For an Ethernet interface, configure VLAN tagging to match the RSD configuration.
3. For a SONET physical interface, configure the maximum transmission unit (MTU) size to match the RSD configuration. (If the RSD has no MTU size specified, do not include an MTU size on the PSD.)
4. Identify the physical interface as a shared interface.
5. Configure the logical interfaces that belong to the PSD (as specified in the RSD configuration).
6. On each logical interface:
   1. Configure the same DLCI (for SONET) or VLAN ID (for Ethernet) that has been specified in the RSD configuration
   2. Specify the logical tunnel interface that is peered with the logical SONET or Ethernet interface.

      The logical unit number of the tunnel interface must be the same as the one that is configured on the SONET or Ethernet interface.

   3. Configure the protocol family and IP address of the logical SONET or Ethernet interface.
7. Configure the physical tunnel interface.
8. Configure the logical tunnel interfaces under the physical interface.
9. For each logical tunnel interface, specify its peer logical SONET or Ethernet interface.

   The logical unit number must be the same as the one that is configured on the logical tunnel interface.