Filter
Top Products
25
Release Notes for the Cisco WAN Manager, Release 15.3.00 P1
OL-11190-01, Rev. C0
CWM Feature Limitations
set semsys:seminfo_semmsl=100
set rlim_fd_max=1024
After you have made the above changes, edit and configure the “SHMBASE” value in
/usr/users/informix94/etc/onconfig as follows and reboot the machine:
SHMBASE 0x0A000000L
• Because of a VISM image issue, the CWM cannot update fax_jitt_mode and fax_jitt_initdelay in
the vism_card table for a Fax jitter configuration change. This problem will be fixed in the next
VISM release.
• Even though the VXSM T3 card is compatible with the MGX 8880 and 8850 PXM45 platform
releases, the CWM software does not discover it.
• Cisco does not recommend pointing multiple CWMs at the same gateway node.
• When /usr/users becomes completely full, the orbix processes cannot write to the disk and continue
operations. To correct the problem, free up disk space in /usr/users and then restart the orbix
processes and the CWM as follows: Stop the core and exit out of the CWM prompt, run the
stoporbix2000 script, type CWM (you should see “Starting Orbix...” in the
~svplus/log/.startStopOrbix.log file), and start the core.
• When the SSM is installed with the SCM Gateway configuration, the SCM GUI does not open when
the primary SSM and secondary SSM are started simultaneously (or within a time gap of 30 seconds
to 1 minute). Avoid this problem by waiting 2 to 3 minutes after starting core in the primary SSM
before starting core in the secondary SSM in the SCM Gateway configuration.
• When a shortage of shared memory exists on the workstation, the Informix engine may generate an
operating system error, as shown in this example:
shmat: [22]: operating system error
18:45:49 shmat: [22]: operating system error
18:45:57 Error writing '/tmp/shmem.1fd4555c.0' errno = 4
18:45:57 mt.c, line 10260, thread 7148, proc id 1008, errors occurred during
mt_notifyvp.
When this error occurs, the statsparser is not able to perform database-related operations. The error
can be resolved temporarily by changing the /etc/system configuration as follows:
forceload: sys/shmsys
forceload: sys/semsys
set shmsys:shminfo_shmmax=1073741824
set semsys:seminfo_semaem=16384
set semsys:seminfo_semmap=5000
set semsys:seminfo_semmni=8192
set semsys:seminfo_semmns=8192
set semsys:seminfo_semmnu=8192
set semsys:seminfo_semume=256
set semsys:seminfo_semvmx=50000
set shmsys:shminfo_shmmin=256
set shmsys:shminfo_shmmni=32000
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmsl=100
The long-term solution is to increase the amount of memory to support 2 million
connections consistently.
• When using in-band management, only 50-KB connections are supported on the BPX-SES. To
manage 100-KB connections on the BPX-SES, set up the CWM for out-of-band management.