TechLibrary

Table of Contents

Guide That Contains This Content

[+] Expand All

[-] Collapse All

Understanding Operations Support Systems Mapping on T4000 Router

The operations support systems mapping feature is supported on the T4000 chassis. This feature prevents requalifying of an existing router on the customer’s operations support system when a T1600 chassis or a T640 chassis is upgraded to a T4000 chassis.

The following sections explain this feature in detail:

Operations Support System Overview

Operations support systems (OSS) is a networking system or software that is used by telecommunication providers and Internet service providers in conjunction with, and to operate, Juniper Networks products. The OSS is used to identify and qualify any existing or new Juniper product that is added to the network. To distinguish the different routers, the OSS uses the Chassis field, which is displayed in the output of the show chassis hardware operational command.

When a T1600 chassis or a T640 chassis is upgraded to a T4000 chassis, the OSS identifies the new chassis as a new networking element and follows a time-consuming process of qualifying it for the service provider network. The OSS mapping feature helps avoid this scenario.

Using the OSS mapping feature, you can map T4000 chassis to a T1600 chassis or a T640 chassis with the set chassis oss-map model-name t640 | t1600 configuration command. This configuration command overrides the chassis model name (as is seen in the output of the show chassis hardware and the show chassis oss-map operational mode commands), so that the OSS recognizes the chassis as a known chassis and proceeds without any requalification.

Note:

The set chassis oss-map model-name t640 | t1600 command is applicable only on T4000 routers. You must explicitly set this command when a T1600 chassis or a T640 chassis is upgraded to a T4000 chassis.
You can execute the set chassis oss-map model-name t640 command or the set chassis oss-map model-name t1600 command if the OSS is compatible with either the T640 chassis or the T1600 chassis, respectively.

Methods to View the Updated Chassis Name

After you execute the set chassis oss-map model-name t640 | t1600 configuration command, you can view the updated chassis name through one of the following ways:

Operational commands—The show chassis hardware, show chassis hardware detail, and show chassis hardware extensive operational commands display the configured known chassis name.
SNMP MIBs—The show snmp mib walk system and show snmp mib walk jnxBoxAnatomy operational commands display the configured known chassis and object ID.

Supported Platforms

Table 1: Routers Supporting OSS Mapping

Supported Platforms	Junos OS Release
T4000	12.3R3
T4000	13.1R2
T4000	13.2R1

Points to Remember

The following points illustrate the functionality on the T4000 chassis that undergoes a change or remains unchanged as a result of OSS mapping:

Chassis functionality and behavior remain unchanged.
No change in field-replaceable unit (FRU) details or model numbers. However, note that new FRUs must be qualified through the normal process.
The chassis personality is identified only by SIB type.
No changes in system log messages.
No change to other MIBs or traps other than system, jnxboxanatomy, and object ID.
No change in Common Language Equipment Identifier (CLEI) details.
OSS mapping works even after GRES or unified ISSU is performed. The backup Routing Engine is updated with the latest information after the commit synchronize command is executed.