CWM Feature Limitations

Only 15-minute collection buckets are supported for PNNI statistics.

Peak statistics are not supported for PNNI statistics.

If the PXM45 release is less than 4.0(0.0) PNNI historical statistics can not be enabled.

The BPX-SES does not support PNNI statistics collection.

The CWM does not support statistical alarms for lines on PXM45-based MGX nodes.

The following statistics for SRM and SRM/E T3 lines can be enabled on the switch, but are not supported by SCM: 28 dsx3LCVCurrent, 29 dsx3LESCurrent, 30 dsx3LSESCurrent,

31 dsx3PCVCurrent, 32 dsx3PESCurrent, 33 dsx3PSESCurrent, and 34 dsx3CCVCurrent.

HP OpenView is supported on the SSM. The SSM processes generate CWM traps.

At least one CWM must be running, with the nodes synced up, for the SSM to work properly. The SSM uses the CWM server to get traps while enabling statistics for cell bus service modules on the MGX 8850 and PNNI statistics on the BPX.

The WANDEST server must be up and running on the CWM. The SSM gets the node, node_info, card, network, rsc_part, and bis_object tables from the CWM by using WANDEST.

If the statsmaster SSM or CWM is down or unreachable in an SCM gateway setup, the statsmaster must be changed on the switch to another CWM or SCM that is up. The statsmaster is needed for SCM statistics enabling or disabling.

In an SCM Gateway setup with statistics collection in process, the old statistics data is not moved to the new primary CWM or SSM machine after switchover.

The SSM does not receive traps on Node/Card deletion, so statistics collection must be stopped and disabled before deleting a node or card from the network. Also the SSM does not receive traps on node or card Add messages, so the WANDEST upload must be received before the node or card can be seen in the SCM GUI on the SSM.

In the SSM, statistics collection must be stopped and restarted after changing the node name or changing the node FTP password.

Statistics data is stored on in statsdb database.

Statistics parsing is only supported for the statsdb database on the SSM and the CWM. Statistics parsing is not supported for the stratacom database on the SSM and the CWM.

Stop statistics collection before upgrading a node image.

CWM-to-CWM Communication Limitations

This section describes CWM-to-CWM communication limitations:

The secondary CWMs have to wait for the primary CWM to finish syncing up with the network. Trap 28075 (svDatabaseInSync) is sent when the primary CWM has finished syncing up with the network.

All the CWMs managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWMs should not all point to the same gateway node, but the gateway nodes they point to should be on the same network.

If an IP address is entered as gateway in the network.conf file and the DNS entry is missing for the gateway node IP address, the Auto-Route network is not discovered.

 

Release Notes for the Cisco WAN Manager, Release 15.3.00 P1

30

OL-11190-01, Rev. C0

Page 30
Image 30
Cisco Systems 15.3.00P1 manual CWM-to-CWM Communication Limitations

15.3.00P1 specifications

Cisco Systems 15.3.00P1 is a pivotal release in the evolution of Cisco's IOS (Internetwork Operating System). This version introduces a range of features and enhancements aimed at improving network reliability, security, and performance. Built to support various networking scenarios, 15.3.00P1 serves as a robust platform for enterprises and service providers alike.

One of the standout features of 15.3.00P1 is its enhanced support for IPv6, which is increasingly vital as the internet continues to evolve. This version includes improved routing protocols and mechanisms that allow seamless integration and transition between IPv4 and IPv6. This dual-stack support ensures that network operators can manage their resources efficiently while preparing for the future.

Quality of Service (QoS) enhancements in Cisco IOS 15.3.00P1 help prioritize critical traffic flows, enabling organizations to allocate bandwidth according to application needs. This is particularly beneficial in environments where latency-sensitive applications, such as VoIP and video conferencing, are prevalent. The precise control over traffic helps reduce congestion and ensures a smooth user experience.

Security features have been significantly bolstered in this release. It includes advanced threat detection capabilities and improved access control lists (ACLs), allowing for more granular security policies. The enhanced security framework helps protect network devices from a variety of threats, ensuring that data integrity and confidentiality are maintained.

Another critical improvement in this version is its enhanced multicast routing capabilities. This is particularly essential for organizations utilizing video or other bandwidth-intensive applications that require efficient data delivery to multiple endpoints. The use of protocols such as Protocol Independent Multicast (PIM) facilitates efficient routing and reduces bandwidth consumption.

Cisco 15.3.00P1 also features better support for various hardware platforms, ensuring compatibility and optimal performance across Cisco routers and switches. The architecture enhancements allow for improved system resource management, reducing operational overhead while maximizing performance.

In addition to these features, the release incorporates several bug fixes and performance optimizations, addressing issues in previous versions. This attention to detail not only enhances system stability but also contributes to a more streamlined user experience.

Overall, Cisco Systems 15.3.00P1 represents a significant step forward in network operating systems, with its array of security, performance, and management enhancements making it an ideal choice for modern networking environments. Organizations deploying this version can expect improved operational efficiency and a more secure networking experience.