Cisco Systems 15.3.00P1 Configuration Center Limitations, HP OpenView Limitations, SSM Issues

CWM Feature Limitations

Configuration Center Limitations

When the connection modify dialog box is already open, another user can delete the connection using the CMGUI delete option.

The Connection Management section of the Configuration Center GUI for preferred route displays all available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic.

While adding connections originating and terminating on the same feeder nodes (MGX8220 only), the CWM treats these connections as three segment connections and adds three segments (two on the same feeder node, one on the routing node) to realize this connection. This is because the ASC cannot route traffic. If you want to pass traffic between two cards in an MGX 8220 chassis, regardless of how connectivity is added, the actual physical connectivity that has to be built is a connection from each endpoint to the ASC and then a looping segment on a BPX.

The RPM card on the PXM1-based MGX 8850/8230/8250 platform is provisioned using Telnet because the RPM does not support SNMP SETs. This should be transparent in daily operation. For more details, please refer to the specific RPM switch CLI release notes.

Occasionally, when the databroker is busy deleting SPVC connections on a PXM1E-based node, this error message appears: “can not delete connections. Failed to communicate with databroker.” The error message can be ignored because the connections are correctly deleted on the switch.

HP OpenView Limitations

All event messages are displayed in the HP OpenView Event Browser window. There is a limit of 2000 pending messages on the Event Browser. If there are more than 2000 messages to be processed and displayed by the Event Browser, it may exit.

The WAN network icon in the network node manager is no longer automatically created when running the CWM. Use the Network Monitor map instead.

SSM Issues

Note these SSM issues:

•To collect connection statistics, statistics need to be enabled on the individual connections by setting the stats enable flag to true on each connection. If the user enables connections statistics only on SCM but does not set the stats-enabled flag to true on the connection, the statistics are not collected for that connection. Because no mechanism or warning to the user exists to have this enabled on the connections, the CWM does not display an appropriate error message.

•When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes only succeeds when either all of the nodes have the same card types or all of the nodes only contain cards of the same family.

•Occasionally, when high connection counts are enabled on the SES, and statistics collection is enabled, the SES node is not getting synced up. The workaround is to disable statistics collection in the SES. Refer to CSCdw32076 for more information.

•The statistics collection manager retrieves SPVC connection statistics data from BPX-SES nodes, however, only 15-minute collection buckets are supported on the SES.

•The same limitation of only 15 minute collection buckets applies for MGX 8850 PXM45-based nodes with AXSM. No such limitation exists for AXSM-E.

	Release Notes for the Cisco WAN Manager, Release 15.3.00 P1
OL-11190-01, Rev. C0		29