Cisco Cisco Prime Optical 9.6 Referencia técnica
2
Cisco Prime Optical 9.6 ML Provisioning Methodology
OL-27085-01
Introduction
•
•
Introduction
Cisco Prime Optical (formerly Cisco Transport Manager) is a carrier-class, multitechnology
management system that integrates the end-to-end management of traditional transport networks and
new carrier packet transport networks. It can help maintain the integrity of existing services, plus deliver
interactive, content-based services and high-bandwidth applications.
management system that integrates the end-to-end management of traditional transport networks and
new carrier packet transport networks. It can help maintain the integrity of existing services, plus deliver
interactive, content-based services and high-bandwidth applications.
Cisco Prime Optical manages the entire Cisco optical portfolio, including:
•
Metro core
•
Metro dense wavelength-division multiplexing (DWDM)
•
Metro edge and access products
•
New Carrier Packet Transport (CPT) System products
Prime Optical also serves as a foundation for integration into a larger overall Operations Support System
(OSS) environment by providing northbound gateway interfaces to higher-layer management systems.
(OSS) environment by providing northbound gateway interfaces to higher-layer management systems.
Prime Optical supports data service provisioning over ML-series cards. Data service provisioning
consists of provisioning the Layer 2 topology using optical circuits, and then provisioning the Layer 2
service on top of the Layer 2 topology.
consists of provisioning the Layer 2 topology using optical circuits, and then provisioning the Layer 2
service on top of the Layer 2 topology.
Alarm notification and performance monitoring features on data cards (ML-series cards) are
SNMP-based. To allow Prime Optical to support alarm and event notification and performance
monitoring on data cards, the SNMP trap forwarding mechanism must be set up on each node of the data
card.
SNMP-based. To allow Prime Optical to support alarm and event notification and performance
monitoring on data cards, the SNMP trap forwarding mechanism must be set up on each node of the data
card.
This document provides the set of Cisco IOS commands issued by Prime Optical during Layer 2
topology and Layer 2 service provisioning, including provisioning of interface ports for ML data cards.
The syntax used for the commands must be respected for services provisioned directly using Cisco IOS
so that Prime Optical recognizes the provisioned services.
topology and Layer 2 service provisioning, including provisioning of interface ports for ML data cards.
The syntax used for the commands must be respected for services provisioned directly using Cisco IOS
so that Prime Optical recognizes the provisioned services.
SNMPv1 and SNMPv2 Trap Destination Setup
For the cards to have full Prime Optical support, the SNMP trap destination must be set up for each node
where there is a data card inserted:
where there is a data card inserted:
•
The NE containing the ML-series card must have a valid SNMP community string. If the SNMP
community string is not valid, a resynchronization failure occurs and is logged in the Audit Log.
community string is not valid, a resynchronization failure occurs and is logged in the Audit Log.
•
The Cisco IOS startup-config file must contain the snmp-server enable traps command to receive
traps from ML-series cards. See
traps from ML-series cards. See
for more information.
•
You must force resynchronization on the NE by marking it as Out of Service (OOS), and then back
In Service (IS) when you change the trap destination in either Cisco Transport Controller (CTC) or
Prime Optical. This operation forces the registration of ML-series cards for traps.
In Service (IS) when you change the trap destination in either Cisco Transport Controller (CTC) or
Prime Optical. This operation forces the registration of ML-series cards for traps.
•
You must set up the trap destination based on the SNMP version (SNMPv1 or SNMPv2) and the
gateway NE/end NE (GNE/ENE) configuration of the node. Set the trap destination in the
NE Explorer window (see
gateway NE/end NE (GNE/ENE) configuration of the node. Set the trap destination in the
NE Explorer window (see
).