Cisco Cisco Prime Provisioning 6.3 發佈版本通知
5
Cisco Prime Provisioning 6.3 Release Notes
OL-27133-01
New Features and Enhancements in Prime Provisioning 6.3
Ethernet A and Z end VLAN Tagging
Prime Provisioning now support the ability to edit the Inner VLAN ranges or outer VLAN ranges flag
when creating the service request. The VLAN ranges are allowed to be controllable only at the policy
level. In particular, this enables the creation of a pseudowire where on one access port you have an outer
VLAN range, and on the other you have an inner VLAN range. It was not possible in the past because
both ports were controlled by one policy.
when creating the service request. The VLAN ranges are allowed to be controllable only at the policy
level. In particular, this enables the creation of a pseudowire where on one access port you have an outer
VLAN range, and on the other you have an inner VLAN range. It was not possible in the past because
both ports were controlled by one policy.
MPLS Transport Profile New Features
See the
for further information about MPLS-TP. This section
includes:
•
•
•
MPLS-TP Topology Integration with Prime Network
Prime Provisioning will retrieve the MPLS-TP topology from Prime Network. This change enables
discovery on IOS-XR devices and removes the requirement to run CDP in your network to discover the
physical topology.
discovery on IOS-XR devices and removes the requirement to run CDP in your network to discover the
physical topology.
This includes MPLS-TP enabled nodes and links. Prime Network is now a prerequisite for provisioning
of MPLS-TP tunnels with Prime Provisioning. For more information about this feature, see
of MPLS-TP tunnels with Prime Provisioning. For more information about this feature, see
Note
The ability to discover MPLS-TP topology directly from previous discovery in the network
without using Prime Network is still present but is deprecated. This would be removed going
forward and Prime Network will be a prerequisite for MPLS-TP provisioning.
without using Prime Network is still present but is deprecated. This would be removed going
forward and Prime Network will be a prerequisite for MPLS-TP provisioning.
MPLS-TP Topology Change
Prime Provisioning supports management of changes in the MPLS-TP topology. After making topology
changes in the network, including node and/or link insertion and/or removal, you can re-synchronize
Prime Provisioning with Prime Network in order to learn about the topology changes. The
re-synchronization can be targeted towards, e.g., only the newly inserted node. Any MPLS-TP tunnel
Service Requests that are impacted by the topology change will automatically recalculate the tunnel path
(for working and/or protect path) and the Service Request will enter the Requested state so that the
operator can review and deploy the modified tunnel. Discovery updates the affected Service Request
(SR) history report with state transition, affected LSP (working path), and new path calculated by
discovery.
changes in the network, including node and/or link insertion and/or removal, you can re-synchronize
Prime Provisioning with Prime Network in order to learn about the topology changes. The
re-synchronization can be targeted towards, e.g., only the newly inserted node. Any MPLS-TP tunnel
Service Requests that are impacted by the topology change will automatically recalculate the tunnel path
(for working and/or protect path) and the Service Request will enter the Requested state so that the
operator can review and deploy the modified tunnel. Discovery updates the affected Service Request
(SR) history report with state transition, affected LSP (working path), and new path calculated by
discovery.
MPLS-TP on ASR 9000 (with IOS XR)
Prime Provisioning now supports provisioning of MPLS-TP tunnels on ASR 9000 series devices with
IOS XR 4.2 and 4.2.1. The ASR 9000 devices can be MPLS TP endpoint and midpoint.
IOS XR 4.2 and 4.2.1. The ASR 9000 devices can be MPLS TP endpoint and midpoint.