Cisco Systems 15.3.00P1 manual Feature Limitations

CWM Feature Limitations

•These VISM 3.1 features introduced cannot be accessed from the CWM: TGCP, Dynamic Payload, and T.38 Fax Relay.

•The CWM database is not populated with the MPG configuration data. Instead, the Service Agent accesses the configuration directly from the switch.

•These cards are not supported by CWM 15.3.00 P1: the BME card and the FRSM12, URM, ARM, FRM, BTM, ALM and CVM service modules. To take advantage of the GUI enhancements, you must upgrade to the newer service modules supported in releases after CWM 12.0.

•These are the Current Route feature limitations:

–P2MP calls and SVC/SVP connections are not supported.

–Only master-ended (not slave-ended) connections have current route information.

–The configuration upload file contains only a snapshot of the current route information at the time the switch receives a CWM configuration upload request.

–If a node becomes congested, both of the connTrace messages that the command line interface (CLI) and the Current Route feature send are dropped. The CWM does not distinguish between the messages. This situation is also true for a connTrace ACK message received on a congested node.

–When a node ID is changed, follow this procedure on each network node to flush out all existing current route information and start collecting new information. Disable and re-enable the current route feature by using the cnfndcurrte command. After disabling the feature, wait for at least 9 seconds (the timeout period for a conntrace message) before re-enabling the feature to avoid processing stale conn-trace messages.

–Because the path information for a connection traversing more than 20 nodes is not stored in the current route path table, the connection does not have current route information.

•While the CWM is running, if the remote display is stopped without properly shutting down the CWM desktop, reopening it remotely may not succeed.

Feature Limitations

The following are known CWM feature limitations:

•For a few of the latest Solaris patches and the Sun Fire E6900 server, the Informix engine may generate a shared memory error as shown in this example:

"oninit: Fatal error in shared memory creation <machine name>"

When this error occurs, the Informix engine fails to come up and is not able to perform database related operations.The error can be resolved by changing values in the /etc/system and /usr/users/informix94/etc/onconfig files. The following shows the change to the /etc/system file:

forceload: sys/shmsys

forceload: sys/semsys

set shmsys:shminfo_shmmax=268435456 set semsys:seminfo_semaem=16384 set semsys:seminfo_semmap=64

set semsys:seminfo_semmni=4096 set semsys:seminfo_semmns=4096 set semsys:seminfo_semmnu=4096 set semsys:seminfo_semume=64 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmin=100 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=100

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