With Routing Engines located in a separate chassis, the JCS 1200 platform provides a greatly expanded and highly-scalable control plane without sacrificing any forwarding slots in the T-series routing platform. Up to eight PSDs can be configured on a single, interconnected platform, obviating the need to deploy multiple physical routers.
The Root System Domain (RSD) is the JUNOS software running on the pair of redundant Routing Engines in the T-series router and the switch fabric connection to the JCS 1200 platform. The configuration on these Routing Engines assigns FPCs in the T-series chassis and Routing Engines in the JCS chassis to a particular PSD. Once a PSD is configured, you initially access and configure it by way of the console port on the assigned master Routing Engine in the JCS chassis. A PSD functions exactly as a physical router, running a separate configuration file, administering its own domain, and requiring unique authentication in order to access it.
To create a PSD using the RSD configuration, include the following statements at the [edit chassis] hierarchy level:
- system-domains {
- root-domain-id root-domain-id;
-
- protected-system-domains psdn {
- oontrol-slot-numbers [ slot-numbers ];
- control-system-id control-system-id;
- description description;
- fpcs [ slot-numbers ];
- }
- }
The JCS 1200 has a management module command-line interface (CLI) that is used to configure Routing Engine parameters in conjunction with the parameters set through the JUNOS CLI configuration on the RSD. The management module is also used to configure general JCS platform parameters and user access.
The Routing Engines on the JCS chassis connect to the T-series routing platform through the JCS switch module (or through a redundant pair of switch modules). Each JCS switch module is preconfigured with defaults. However, a script is available to configure the following items on the switch module:
- NTP—The JCS switch module does not have a real-time clock. You must configure NTP so that the system clock on the JCS switch module has the correct time. The script sets the IP address for the NTP server, enables the NTP server, and sets the time zone for the switch module.
- SNMP traps—The script also configures SNMP trap information for the switch module. This includes setting the SNMP community name and type and specifying alert recipients.
 |
Note: The JCS switch module configuration is not replicated across redundant switch modules. You must run the configuration script on both JCS switch modules. |
In addition, a default configuration file is available to recover a JCS switch configuration. A description of how to use the JCS switch script and restore the default configuration is provided in a README file.
The README file, switch script, and default configuration file are available through the Juniper Networks Knowledge Base at http://kb.juniper.net/KB11673.
|
Note: In JUNOS Release 9.1, Ethernet IQ2 PICs, services PICs, and monitoring PICs are not supported for use with the JCS 1200 platform. |
|
Note: In JUNOS Release 9.1, no MIBs have been added to support FPC-to-PSD mapping or to indicate whether a T-series router is part of an RSD or is a standalone router. |