Cisco MGX 8850 PXM45 Release Notes page 38

Limitations, Restrictions, and Notes
•
•
•
•
•
•
Preferred Route
•
•
•
•
•
•
•
•
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
38
The slave end of a single-ended SPVC is not be visible to CWM.
If single-ended SPVCs are originated from switches, they can only be configured via CLI and not
from CWM in the current release.
Single-end provisioning will not be supported for DAX connections, because no value addition is
seen for interoperability.
SPVC statistics are not available for the slave endpoint of a single-ended SPVC because this
endpoint is non-persistent.
When the persistent slave endpoint of an existing SPVC connection is deleted and the master
endpoint is allowed to remain, the connection may get established as a single-ended spvc
connection. In this case, CWM will show the connection as Incomplete.
Override of SVC connections on a VPI due to an incoming SPVP request for that VPI is not
supported. The following override options are alone supported:
spvcoverridesvc
–
spvcoverridesvp
–
– spvpoverridesvp.
Upgrading a preferred routing configured connection from any Release 3.0.x will be nongraceful.
In a future release, the configuration of the preferred route identifier information for each
connection will be supported on the Service Module cards instead of on the PXM controller. During
the upgrade, the preferred route identifier information for each connection will be lost and the
preferred route identifier needs to be reprovisioned on the Service Module cards. Also, the preferred
route table at the PXM controller will be lost. Connections that have already been routed with
preferred routing will remain, and there will be no alarms for these connections.
The preferred routes can be specified only within a PNNI single peer group meaning all the nodes
in the preferred route lie within the same peer group.
All the nodes in the network should be running Release 3.0.00 software to use the preferred route
feature.
All the links specified in the preferred route should be PNNI links.
If a node in the PNNI network changes its PNNI node ID, the old entry in the persistent topology
database in all the nodes in the network need to be deleted. If any of the preferred routes in any nodes
in the network contains the changed node as one of the hops, the preferred route(s) must be modified
using the new table index (in the persistent topology database) allocated for the changed node.
If a node in the PNNI network is deleted via configuration commands from the persistent topology
database, if any of the preferred routes configured at that node (where the delete command is
executed) contains the deleted node as one of the hops, the preferred route(s) must be
deleted/modified manually.
If a node in the PNNI network is removed via physical decommissioning, and if any nodes in the
network had some preferred routes that contain the removed node as one of the hops, the preferred
route(s) must be deleted/modified manually.
Due to differences in physical port numbering, non-Cisco nodes can only be the terminating nodes
in a preferred route.
OL-2914-01 Rev D0, July 3, 2003