Cisco MGX 8850 PXM45 Release Notes page 37

•
SNTP
•
Priority Routing
•
•
•
•
•
•
SPVC Interop
•
•
•
•
•
•
•
OL-2914-01 Rev D0, July 3, 2003
Path and connection trace feature in Release 3.0.00 and higher is not compatible with the path and
connection trace available with previous releases.
The CWM MIB is not supported in Release 3.0.00 and higher.
Prioritized reroute of SPVCs is not guaranteed, if the SPVCs originate on a signaling port. We might
see SPVCs getting routed out-of-order. In-order routing of SPVCs is guaranteed on nonsignaling
ports.
The MGX-RPM-PR-256/512 does not support configuration of routing priority. All RPM mastered
SPVCs will be assigned a routing priority of 8 by the PXM.
The addcon command on VISM does not have support for specifying the routing priority. All the
SPVCs added from VISM are assigned a priority of 8. The routing priority can be changed using the
cnfpncon command.
Changing the routing priority for DAX connections will not change the priority of the associated
pn-cons (SVCs). This is because the SPVCs will not be derouted and rerouted if just the endpoint
parameters are changed, and routing priority is an endpoint parameter. Also, because DAX
connections are never derouted, even when the UNI port goes down and the rrtcon command is not
supported for DAX connections, the routing priority change will never get reflected. The only way
for this to get reflected is to use the dncon and upcon commands. Because DAX connections are
never derouted, the effect of this limitation is voided.
Priority routing operates in a best effort manner. This is because of the following reasons:
Two in-order RELEASEs can still arrive out-of-order at the Master node, if they take two
–
different paths.
Under congestion scenarios we can expect RELEASEs to be transmitted out-of-order. This is
–
because we do not want to hold up the release of other calls if we are not able to send
RELEASEs on one of the interfaces, as it is congested. The calls that we are unable to release
could be higher priority calls.
Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can happen if we have
attempted several times to route higher priority SPVCs, but failed. To prevent starvation of lower
priority SPVCs, we will start to route lower priority SPVCs and we will get to the higher priority
SPVCs at a later point in time.
NNI SPVC Addendum Version 1.0 is not supported.
PNNI 1.0 Addendum (Soft PVC MIB) is not supported.
Terminating single-ended SPVCs on AUSMs, CESMs, or FRSMs is not supported.
Origination of single-ended spvcs (with -slavepersflag) from AUSMs, FRSMs, CESMs, VISMs and
RPMs is not supported.
CC (Continuity Check) is not be available at the slave end of a single-ended SPVC.
Reporting AIS detection to CWM is not be available at the slave end of a single-ended SPVC.
The tstdelay command is not be available at the slave end of a single-ended SPVC on a switch.
Release Notes for Cisco MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830, Software Release 3.0.10
Limitations, Restrictions, and Notes
37