- play_arrow Overview
- play_arrow MPC-specific
- play_arrow Fabric Management
- play_arrow Power Management
- play_arrow Environment Monitoring
- play_arrow Managing Errors and Alarms
- play_arrow Network Services Mode
- play_arrow Packet Scheduling Mode
- play_arrow Configuration Statements and Operational Commands
Configuring OSS Mapping
Configuring OSS Mapping to Represent a T4000 Chassis as a T1600 or a T640 Chassis
You can configure the operations support systems (OSS) mapping feature to represent a T4000 chassis as a T1600 chassis or a T640 chassis. This topic includes the following tasks:
- Configuring T4000 Chassis as a T1600 Chassis
- Configuring T4000 Chassis as a T640 Chassis
- Disabling the OSS Mapping Feature
Configuring T4000 Chassis as a T1600 Chassis
To configure a T4000 chassis as a T1600 chassis:
Configuring T4000 Chassis as a T640 Chassis
To configure a T4000 chassis as a T640 chassis:
By default, the OSS mapping feature is disabled.
Disabling the OSS Mapping Feature
To disable the OSS mapping feature:
The
set chassis oss-map model-name t640 | t1600command 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 t640command or theset chassis oss-map model-name t1600command if the OSS is compatible with either the T640 chassis or the T1600 chassis, respectively.
Example: Configuring a T4000 Chassis to Represent a T640 Chassis
This example shows how to configure OSS mapping feature to represent a T4000 chassis as a T640 chassis. You can extend this concept to configure a T4000 chassis to represent as a T1600 chassis as well.
Requirements
This example uses the following hardware and software components:
One T4000 router
Junos OS Release 12.3R3, 13.1R2, 13.2R1, or later
Overview
Operations support systems (OSS) is used by service providers to maintain their networks. When a new router is added or removed from the network, the OSS must be updated to reflect the changes. This process is tedious and time-consuming.
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 tedious process of qualifying it for the customer’s network. The OSS mapping feature helps avoid this scenario.
Using the OSS mapping feature, you can map a T4000 chassis to
a T1600 chassis or to a T640 chassis with the set chassis oss-map
model-name t640|t1600 configuration command. This configuration
command overrides the chassis model name, so that the OSS recognizes
the chassis as a known chassis and proceeds without any requalification.
The
set chassis oss-map model-name t640 | t1600command 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 t640command or theset chassis oss-map model-name t1600command, if the OSS is compatible with either the T640 chassis or the T1600 chassis, respectively.
Configuring the T4000 Chassis to Represent a T640 Chassis
Procedure
Step-by-Step Procedure
To configure the T4000 chassis to represent a T640 chassis by using the OSS mapping feature:
In configuration mode, go to the
[edit chassis]hierarchy level.content_copy zoom_out_map[edit] user@T4000# edit chassis
Configure the OSS mapping feature to map the T4000 chassis to a T640 chassis.
content_copy zoom_out_map[edit chassis] user@T4000# set oss-map model-name t640
Verification
Verifying the OSS Mapping Feature
Purpose
To verify that the OSS mapping feature is working on a T4000 router.
Action
Run the show chassis operational command and verify that the configured known chassis name is displayed when the T4000 chassis is mapped to a T640 chassis.
Run the
show chassis hardwareoperational command:show chassis hardware
content_copy zoom_out_mapuser@T4000> show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis JN11B3892AHA T640 Midplane REV 01 710-027486 RC9848 T-series Backplane FPM GBUS REV 13 710-002901 BBAG5143 T640 FPM Board FPM Display REV 04 710-021387 BBAL2705 T1600 FPM Display CIP REV 06 710-002895 BBAL3705 T-series CIP PEM 1 REV 03 740-036442 VJ00054 Power Entry Module 6x60 SCG 0 REV 18 710-003423 BBAJ0727 T640 Sonet Clock Gen. SCG 1 REV 18 710-003423 BBAE3887 T640 Sonet Clock Gen. Routing Engine 0 REV 06 740-026941 P737F-002705 RE-DUO-1800 Routing Engine 1 REV 06 740-026941 P737F-002675 RE-DUO-1800 CB 0 REV 09 710-022597 EF7371 LCC Control Board ....
Run the
show chassis hardware detailoperational command:show chassis hardware detail
content_copy zoom_out_mapuser@T4000> show chassis hardware detail Hardware inventory: Item Version Part number Serial number Description Chassis JN11B3892AHA T640 Midplane REV 01 710-027486 RC9848 T-series Backplane FPM GBUS REV 13 710-002901 BBAG5143 T640 FPM Board FPM Display REV 04 710-021387 BBAL2705 T1600 FPM Display CIP REV 06 710-002895 BBAL3705 T-series CIP PEM 1 REV 03 740-036442 VJ00054 Power Entry Module 6x60 SCG 0 REV 18 710-003423 BBAJ0727 T640 Sonet Clock Gen. SCG 1 REV 18 710-003423 BBAE3887 T640 Sonet Clock Gen. Routing Engine 0 REV 06 740-026941 P737F-002705 RE-DUO-1800 ad0 3823 MB SMART CF 201101050335CCFACCFA Compact Flash ad1 62720 MB SMART Lite SATA Drive 2011021700D8789F789F Disk 1 Routing Engine 1 REV 06 740-026941 P737F-002675 RE-DUO-1800 ad0 3823 MB SMART CF 201011150208AF59AF59 Compact Flash ad1 62720 MB SMART Lite SATA Drive 2010122700A160026002 Disk 1 CB 0 REV 09 710-022597 EF7371 LCC Control Board ....
Run the
show chassis hardware extensiveoperational command:show chassis hardware extensive
content_copy zoom_out_mapuser@T4000> show chassis hardware extensive Hardware inventory: Item Version Part number Serial number Description Chassis JN11B3892AHA T640 Jedec Code: 0x7fb0 EEPROM Version: 0x02 S/N: JN11B3892AHA Assembly ID: 0x0507 Assembly Version: 00.00 Date: 00-00-0000 Assembly Flags: 0x00 ....
Verifying the OSS Mapping Feature on SNMP MIBs
Purpose
To verify that the SNMP MIBs are updated with the configured known chassis name.
Action
Run the show snmp mib operational commands
and verify that the configured known chassis name is displayed in
SNMP MIBs when the T4000 chassis is mapped to a T640 chassis:
Run the
show snmp mib walk systemoperational command:show snmp mib walk system
content_copy zoom_out_mapuser@T4000> show snmp mib walk system sysDescr.0 = Juniper Networks, Inc. t640 internet router, kernel JUNOS 12.3-...Juniper Networks, Inc. sysObjectID.0 = jnxProductNameT640 ...
Run the
show snmp mib walk jnxBoxAnatomyoperational command:show snmp mib walk jnxBoxAnatomy
content_copy zoom_out_mapuser@T4000> show snmp mib walk jnxBoxAnatomy jnxBoxClass.0 = jnxProductLineT640.0 jnxBoxDescr.0 = Juniper t640 Internet Backbone Router jnxBoxSerialNo.0 = JN11B3892AHA jnxBoxRevision.0 ....
Meaning
On configuring the OSS mapping feature, the OSS maps the T4000 chassis to a T640 chassis, thereby preventing requalification of the new chassis.
