Viewing a Graphical Image of the Optical Interface Components
The Chassis View provides a pictorial representation of the optical interface, optical channel data unit (ODU), optical channel transport unit (ODU) of an MX Series and PTX Series router, and the modules or components that are installed in it, such as the line cards, interfaces, and other hardware elements.
The purpose of this view is to try and provide a comprehensive monitoring view of the health and status of deployed devices across the network. In this view all the managed devices are shown with their appropriate status and health based on the services and device settings applied. This view helps the operator to know the health and status across the network, it provides with the operator to quickly see the macro level information, which allows the operator to further analyze the information provided and quickly navigate to individual devices and take any further corrective measure required. It provides a cohesive tool for the operator to quickly see the micro-level information and take any further remediation action required.
To view a graphical image of the optical interfaces, OTUs, and ODUs of MX Series and PTX Series routers, and its associated components:
You can mouse over the different parts of the graphical image of the device , such as the interfaces, line cards, and slots. When you mouse over the different modules, their corresponding details are displayed as tooltips. On clicking the device components, the corresponding description for the selected component is displayed by default in the Component Info pane and the Equipment tab.
Manufacturer—Name of the company that built and shipped the device.
Part number—Part number of the chassis component.
Serial number—Serial number of the chassis component. The serial number of the backplane is also the serial number of the router or switch chassis. Use this serial number when you need to contact Juniper Networks Customer Support about the router or switch chassis.
When you select any physical interface configured on the DPCs or PICs or MICs provisioned, the following fields are displayed for the corresponding component for each interface. The interface is surrounded by a colored box to show the Operational Status.
The Component Info pane and the Active Alarms monitor are displayed in the lower portion of the page.
The Active Alarms monitor shows any active alarm that has not yet been cleared. You can view the alarm name, the unique identifier assigned to the alarm, the person to which the alarm is assigned for corrective action, and the severity of the alarm. Click the Launch Alarm Mgmt icon (right upward-slanting arrow enclosed in a square) to navigate to the Fault mode and view the four standard alarm monitors available in Fault mode.
Active Alarms for the respective components are displayed when the component is clicked in the image of the chassis displayed. The components for which the alarms are displayed are Flexible Port Concentrator (FPC), Dense Port Concentrator (DPC), Physical Interface Card (PIC), Modular Interface Card (MIC), Routing Engine, Control Boards, fan trays, Switch Interface Board (SIB), and power supply module (PSM).
The following fields are displayed in the Active Alarms pane:
Table Column |
Description |
---|---|
Severity |
The severity of the alarm. Severity levels are:
|
Name |
The alarm name. |
Source |
The IP address of the device or network element that generated the alarm. The SNMP agent is located at the source IP. In most cases, the source IP is the IP address of the switch or controller. |
Last Updated |
The date and time that the information for the alarm was last modified. |
The following fields are displayed in the Component Info pane:
Field |
Description |
---|---|
Host Name |
Hostname of the device |
Physical Interface Name |
Name of the physical interface |
IP Address |
IP address configured on the interface |
Encapsulation |
Encapsulation configured on the logical interface |
Hardware Address |
MAC address configured on the interface |
Operation Status |
Operational status of the physical interface: Up, Down. |
Admin Status |
Administrative state of the interface: Enabled or Disabled. If the interface is disabled, it can provide network connectivity, but it cannot provide power to connected devices. |
Link Level Type |
Encapsulation type configured on the interface |
Link Type |
Data transmission type |
Speed |
Speed at which the interface is running |
MTU |
Maximum transmission unit size on the physical interface |
Loopback |
Specifies whether the loopback status is enabled or disabled. If loopback is enabled, the type of loopback—Local or Remote—is displayed. |
Description |
Configured textual description of the interface |
A redundant Ethernet interface is a pseudointerface that includes at minimum one physical interface from each node of the cluster. A redundant Ethernet interface must contain, at minimum, a pair of Fast Ethernet interfaces or a pair of Gigabit Ethernet interfaces that are referred to as child interfaces of the redundant Ethernet interface (the redundant parent). If two or more child interfaces from each node are assigned to the redundant Ethernet interface, a redundant Ethernet interface link aggregation group must be formed.
A pseudowire subscriber logical interface terminates an MPLS pseudowire tunnel from an access node to the MX Series router that hosts subscriber management, and enables you to perform subscriber management services at the interface. Subscriber management supports the creation of subscriber interfaces over point-to-point MPLS pseudowires. The pseudowire subscriber interface capability enables service providers to extend an MPLS domain from the access-aggregation network to the service edge, where subscriber management is performed. Service providers can take advantage of MPLS capabilities such as failover, rerouting, and uniform MPLS label provisioning, while using a single pseudowire to service a large number of DHCP and PPPoE subscribers in the service network.
The pseudowire is a tunnel that is either an MPLS-based Layer 2 VPN or Layer 2 circuit. The pseudowire tunnel transports Ethernet encapsulated traffic from an access node (for example, a DSLAM or other aggregation device) to the MX Series router that hosts the subscriber management services. The termination of the pseudowire tunnel on the MX Series router is similar to a physical Ethernet termination, and is the point at which subscriber management functions are performed. A service provider can configure multiple pseudowires on a per-DSLAM basis and then provision support for a large number of subscribers on a specific pseudowire. Figure 1 shows an MPLS network that provides subscriber management support.
The following table describes the fields displayed in the Pseudo Interfaces pane.
Field |
Description |
---|---|
Pseudo Interface Name |
Name of the pseudowire subscriber logical interface. |
Type |
Signaling type for the pseudowire interface. You can use either Layer 2 circuit signaling or Layer 2 VPN signaling. The two signaling types are mutually exclusive for a given pseudowire. |
Operation Status |
Operational status of the physical interface: Up, Down. |
Admin Status |
Administrative state of the interface: Enabled or Disabled. If the interface is disabled, it can provide network connectivity, but it cannot provide power to connected devices. |
The logical interfaces configured on each interface are also shown along with the physical interface description in tabular format. The following table describes the details displayed for logical interfaces.
Field |
Description |
---|---|
Device Name |
The device configuration name. |
Interface Name |
Standard information about the interface, in the format type-/fpc/pic/port/logical interface, where type is the media type that identifies the network device; for example, ge-0/0/6.135. |
IP Address |
The IP address for the logical interface. |
Encapsulation |
The encapsulation type used on the logical interface. |
Vlan |
The VLAN ID for the logical interface. |
Description |
An optional description configured for the interface. It can be any text string of 512 or fewer characters. Any longer string is truncated. If there is no information, the column entry is blank. |
From the Chassis View window, click the Details icon (arrow enclosed in a square) at the top-right corner of the window to open the Chassis View Details page that lists the configured devices and their parameters in the form of a table.
The following fields are displayed on the right pane, depending on the component or element of the chassis you selected from the chassis image displayed.
Field |
Description |
---|---|
Module |
Name of the SDG and the platform type, such as MX240 or MX480. Click the plus sign (+) to expand the tree to display the components of the device, such as chassis, PIC, CPU, and PIC parameters. Information about the chassis, midplane, craft interface (FPM), power midplane (PMP), Power Supply Modules (PSMs), Power Distribution Modules (PDMs), Routing Engines, Control Boards (CBs) and Switch Processor Mezzanine Boards (SPMBs), Switch Fabric Boards (SFBs), Flexible PIC Concentrators (FPCs), PICs, adapter cards (ADCs) and fan trays is displayed. |
Model Number |
Model number of the FRU hardware component. |
Model |
Model of the FRU component. |
Part Number |
Part number of the chassis component. |
Serial Number |
Serial number of the chassis component. The serial number of the backplane is also the serial number of the router chassis. Use this serial number when you need to contact Juniper Networks Customer Support about the router or switch chassis. |
Description |
Brief description of the hardware item:
|
Click the Apply Configlet button (pencil icon displayed beside the button) and use the links shown on the components in Chassis View to select the context and apply configlets.