PSD Administration View

Access Privileges

Each PSD is independent of all other PSDs and requires login authentication. When you initially configure a PSD, you set its root authentication parameters. Authentication is enforced when a user attempts to log in to a PSD directly or from the RSD.

System Information

The PSD administrator can display information about the Routing Engines, FPCs, and PICs that are assigned to the PSD. The administrator can also display information about shared T Series hardware, such as SIBs, the SPMB, PEMs, and fans. When a show command is issued on a PSD, a field heading such as psd1-re0: precedes the set of information that pertains only to the PSD, whereas a field heading such as rsd-re0: precedes the set of information that pertains to the shared hardware.

System log messages originating from an FPC that is assigned to a PSD are logged locally at the RSD and forwarded to the PSD. If a system log message originates from a hardware resource that is shared between and RSD and PSDs, the message is logged locally at the RSD and is forwarded to all PSDs associated with the RSD. Again, you can determine the origin of a system message by labels such as psd1-re0: and rsd-re0:.

Management Tasks

The PSD administrator controls and manages Routing Engines and FPCs assigned to that PSD. For example, the PSD administrator can issue request, clear, and test commands for the FPCs and PICs that are part of the PSD. The PSD administrator has view-only access to shared T Series hardware, such as SIBs, the SPMB, PEMs, and fans.

Note: A switchover between Routing Engines on the JCS1200 platform that are assigned to a PSD does not affect the RSD or other PSDs. However, when the master Routing Engine in a PSD reboots or goes offline, the FPCs assigned to that particular PSD will reboot or go offline.