Downloads |
 Feedback
|
Table Of Contents
Release Notes for Cisco WAN Manager 15.0.00
New Features and Enhancements in CWM Release 15
Features Introduced in CWM Release 15.0.00
Features Not Supported and Known Feature Limitations in 15.0.00
Connection Manager Limitations
Issues with the CWM 15 Statistics Collection Manager
Limitations for CWM to CWM Communication
CWM 15 Server Installation or Upgrade to CWM 15
Node Numbering for Release 9.4 IGX Feeder Nodes
ChassisView Operation After Card and Line Switchovers
Equipment Management Configuration Notes
Network Monitor Server Configuration File (NMServer.conf)
Creating and Configuring a CWM Auto-Restart Shell Script
Using the vi Editor to Create Your Auto-Restart Shell Script
SNMP Service Agent Release Notes
Trap Limitation with PXM1-based MGX Nodes
Known Anomalies in CWM 15 Software
Anomalies Resolved in the Baseline, but not Included in CWM 15.0.00 Software
Obtaining Technical Assistance
Release Notes for Cisco WAN Manager 15.0.00
These release notes are part OL-4151-01 Rev. F0, December 10, 2004
Cisco WAN Manager Release 15.0.00 software supports the following Cisco products as of 04/14/04:
•
Cisco MGX 8850 PXM45-based products running software releases 3.0.23 through 3.0.25, 4.0.00 through 4.0.15, or 5.0.00.
•
•
•
•
•
•
•
Table of Contents
Required Patches 7Recommended Patches 8CWM-specific Enhancements 21WANDEST 2.5-Specific Enhancements 21Overview
This document contains the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
System Requirements
The following are additional notes for CWM platform requirements:
•
•
•
•
•
CWM Server
•
•
Java Client
Standalone Statistics Manager
•
•
•
•
•
•
Five statistics are collected from each connection segment endpoints and 15-minute file collection interval.
This system requirement should be added to the CWM Server requirements if the Parser Function is enabled.
4 Million endpoints with 5 statistics per endpoint requires 80 GB disk space per 24 hour period. You'll need at least 3 x 36 GB of disk space.
Solaris Patch Requirements
After installing the Solaris 8 operating system, you must install the following patch cluster:
•
(previously was 108528-13)
After you have installed the 108528-27or higher cluster, install the following additional patches if they were not already installed as part of the cluster:
Required Patches
You can display which patches are already installed in the CWM workstation by entering the Solaris showrev -p command.
Patches can be obtained from SunService (if the user has a SunSpectrum contract) or from the SunSolve Recommended and Security Patches web site.
Patches are available to Sun Microsystems customers over the Web at
www.sunsolve.sun.COM/pub-cgi/show.pl?target=homeUse the search facility on the SunSolve site to search for these patches, entering only the six-digit patch ID number (do not include the two-digit patch version number). The version number can be later than the one referenced below.
•
•
•
•
•
•
•
•
•
•
Recommended Patches
•
•
•
•
•
•
You can get these patches from Sun Microsystems SunSolve online patch page at the following URL:
http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access
Note
CWM Software Packaging
Following is the list of CDs for the CWM 15.0.00 release:
When you order the CWM package, you receive the following 2 disks:
•
–
–
–
•
–
–
–
–
The Service Agent software is provided on a separate CD. This CD is ordered separately from the CWM Release 15 Client/Server package CD set.
•
–
The Standalone Statistics Collection Manager software is also on a separate CD. This CD is ordered separately.
•
–
–
The Standalone Statistics Collection Manager software also includes the RTM Proxy for SCM Application on a separate CD. This CD is included only when you have ordered the Standalone Statistics Collection Manager software.
•
–
Note
The WANDEST Release 2.5 software is provided on two separate CDs. Each CD is ordered separately.
•
–
•
–
HP OpenView Requirements
The CWM 15 release works with HP OpenView Release 6.2 or 6.3 for Solaris 8.
Note
For HP OpenView installation requirements and procedures, please refer to "HP OpenView Network Node Manager Products, Installation Guide" (part # J1136-90000 from HP).
HP OpenView 6.2 or 6.3 is not bundled with CWM CDs. You must order HP OpenView separately. HP OpenView is used for viewing the Event Log. It is not required for any other CWM procedures.
INFORMIX Requirements
The CWM 15 release uses Informix release 9.21.UC7XH for database operations. The INFORMIX software is bundled with CWM software on disk 1 of the CWM CD package. The INFORMIX program is automatically installed during CWM installation.
Supported Hardware
This section provides information about the hardware supported by the CWM 15 release.
Existing Hardware
Table 5 lists the existing hardware supported prior to CWM 15.0.00.
New Hardware
Table 6 lists the new hardware supported in CWM Release 15.
Certified Releases
The following releases were tested with CWM release 15:
•
–
–
–
•
–
–
–
•
–
–
•
–
–
–
•
–
•
–
–
–
•
–
–
–
•
–
–
•
–
–
–
•
–
•
–
–
•
–
–
New Features and Enhancements in CWM Release 15
Features Introduced in CWM Release 15.0.00
This section describes the new features introduced in Cisco WAN Manager Release 15.0.00.
•
–
–
The Voice Switch Service Module (VXSM) is the carrier class, high density, service module for the MGX88xx voice gateway. CWM is the system for setting up AAL2 connection between voice gateways using VXSM for Voice Trunking solutions. This enables the use of packet network for carrying voice traffic and eliminates the need for point-to-point TDM circuit.
Both VXSM with 4 port OC3/STM1 and VXSM with 48 ports of T1/E1 are supported by this CWM release. These modules can be used on the Cisco MGX 8880 PXM45-based voice gateway with AXSMB and VISM-PR.
CWM 15 supports configuration of the lines, ports and channels on these VXSM cards via the GUI and the SNMP Service Agent.
CWM 15 also provides the ability to provision and diagnose ATM connections between VXSM modules or between VXSM and VISM-PR. Image download, TRAP monitoring for the equipment, 1:1 protection switching, and the ATM connections are handled as in other service modules.
The Statistics Collection Manager collects bulk statistics files from VXSM for ATM connection statistics, SONET/SDH line and path statistics, Megaco gateway and termination statistics, and SCTP and LAPD statistics. Realtime statistics counters for CID level statistics can be queried from the CWM 15 GUI using the Diagnostics Center application.
•
–
CWM 15 supports the AXSM-16-155-XG service module, which addresses the need for enhanced traffic management capabilities over a higher OC-3c/STM-1 port density.
The AXSM-16-155-XG service module supports ABR with VS/VD and per-VC/VP shaping on 128K connections and provides a full 2.4 Gbps of usable bandwidth per card. These enhancements help lower the cost of OC-3c/STM-1 ports.
–
CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.
With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.
CWM based provisioning using the SNMP MIB is also supported.
–
CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.
The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.
CWM based provisioning using the SNMP MIB is also supported.
•
–
CWM 15 supports the AXSM-16-155-XG service module, which addresses the need for enhanced traffic management capabilities over a higher OC-3c/STM-1 port density.
The AXSM-16-155-XG service module supports ABR with VS/VD and per-VC/VP shaping on 128K connections and provides a full 2.4 Gbps of usable bandwidth per card. These enhancements help lower the cost of OC-3c/STM-1 port.for customers in need of the enhanced traffic management capabilities.
–
CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.
With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.
CWM based provisioning using the SNMP MIB is also supported.
–
CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.
The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.
CWM based provisioning using the SNMP MIB is also supported.
•
–
CWM 15 supports management of the SRME/B. The SRME/B adds T3/E3 interfaces to the current SRM-E which only supports OC-3 and STM-1 Electrical interfaces. This new SRME/B now supports T3/E3, OC-3 and STM-1 Electrical interfaces with the same front card. Bulk distribution to all 24 slots is now possible for the 8230/8250/8850 PXM1-based platforms.
–
This feature allows all PXM1-based nodes to use SNTP or Simple Network Time Protocol to synchronize clocks within an internetwork of PXM1-based nodes. SNTP provides a comprehensive mechanism to access national time sources and adjust each nodes's clock to that time source. CWM support for SNTP on PXM1-based nodes is the same mechanism as supported by CWM on the MGX 8800 PXM45-based switches in prior releases.
•
–
CWM 15 supports soft rerouting. In previous releases during the grooming process the connection was derouted and rerouted when the connection was on a PNNI routed path. Even when the better/desired route was unavailable the connection was derouted and rerouted using PNNI. The soft reroute feature enables you to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until a connection has been established on a new path. Thus soft route brings higher connection availability. QoS is preserved/improved by soft reroute for the rerouting connection.
With this capability the data loss due to grooming of connections is reduced as the new path is established before breaking the older path of a connection. This increases connection availability.
CWM based provisioning using the SNMP MIB is also supported.
–
CWM 15 supports scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow you to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.
The enhancements to route optimization allow you to administer route optimization of connections from the CWM network management workstation. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.
CWM based provisioning using the SNMP MIB is also supported.
•
The VISM 3.2 features listed below apply to the PXM45-based MGX 8850 and MGX 8880 nodes, the PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5 and the PXM1-based MGX 8850, MGX 8250, and MGX 8230 nodes running Release 1.3.
–
CWM 15 supports the new compression technique (lossless compression CODEC) in the DSP (for VISM-PR Release 3.2), which enables Wireless Service Providers to reduce the number of leased lines needed to backhaul traffic from a cell site (BTS) to the central office (BSC).
–
CWM 15 supports the detection of a small subset of commonly used Call Progress tones now that VISM-PR reports these tones to the Call Agent as RFC2833 specified events.
–
CWM 15 supports the 3 way conference capability. The three-way calling service allows an end user already engaged in a two-party call to add a third party to the conversation.
•
CWM 15 supports IMA auto restart configuration using the Equipment Manager and service agent. The auto-restart functionality to be configured and displayed through Configuration Center. You can also view the auto-restart attribute using inspector view. IMA auto restart applies to the PXM45-based MGX 8850 nodes with the AXSME-32T1E1 running Release 5 and the PXM1E-based MGX 8850 and MGX 8830 nodes with the PXM1E-16T1E1 running Release 5.
•
CWM 15 supports the Preferred Route Indicator feature for PXM45-based MGX 8850 nodes and/or PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5. For more information about configuring and managing preferred routes, refer either to the online help or to the appropriate section in the Cisco WAN Manager User's Guide, Release 15 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/devices.htm#wp1134735
•
CWM 15 allows you to configure the criteria for dropping cells on AUSM cards. Depending upon the configuration Frame Based Discard or CLP threshold can be used for determining the criteria for dropping cells.
•
CWM 15 allows you to execute delay tests between given OAM segment endpoints on PXM45-based MGX 8850 nodes and/or PXM1E-based MGX 8850 and MGX 8830 nodes running Release 5.using the SNMP Service Agent.
•
CWM 15 now supports the configuration of VPI = 0 for AXSM port resource partitions. For more information about configuring and managing VPI = 0 for AXSM port resource partitions, refer either to the online help or to the appropriate section in the Cisco WAN Manager User's Guide, Release 15 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/index.html
CWM-specific Enhancements
•
CWM 15 introduces a new Graphical User Interface. For an overview of the look and feel of this new interface, refer to the Cisco WAN Manager User's Guide, Release 15 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/ug/index.html
Here's a list of the changes you'll see:
The following applications are new in CWM 15:
–
–
–
–
–
–
–
The following CWM 12 and earlier applications have been replaced in CWM 15:
–
–
–
–
–
•
•
•
•
•
•
•
XPVC connection data no longer requires the manual XPVC grooming tool during upgrade to CWM 15. XPVC connections are now discovered from the network by CWM 15.
•
•
WANDEST 2.5-Specific Enhancements
•
Prior to Release 2.5, every table within the stratacom database was accessed by WANDEST, regardless of whether you used the table or not. Now you can select the tables you need. Refer to the WANDEST Installation and Reference, Release 2.5 for more information on setting up this feature.
Features Not Supported and Known Feature Limitations in 15.0.00
The following features are not supported in CWM 15.0.00:
CID level traps are not sent to CWM to prevent potential trap flooding.
CID level statistics are not available in bulk statistics file format from the VXSM modules.
XPVC support on the FRSM T3E3 in PXM45-based switches has not been tested
Bulk statistics for VISM are not supported
The CONDITIONAL_PRIMARY flag in the CWMGateway.conf file is not supported.
When managing VISM service modules that are running 3.2.10, CWM only supports the 3.2 features
The following features introduced in VISM 3.1 are not accessible from CWM:
•
•
•
The CWM database is not populated with the MPG configuration data. Instead, the Service Agent accesses the configuration directly from the switch.
The following cards are not supported by CWM 15.0.00:
•
•
•
Limitations
1.
2.
3.
Correct the problem by first freeing up some disk space in /usr/users, then restarting the orbix processes and CWM using the following procedure:
Step 1
Step 2
Step 3
Step 4
4.
Exception raised while calling activateLease on pseudoServer.IT_ATLI_IOP:CONNECTION_CREATION_TIMEOUTThe error message is printed when server tries to contact the client, but is not able to. The call is initiated by the GUI client for activating the lease plugin on the client to detect server crash.
The problem is with the client machine DNS setup. The client machine cannot be pinged from the server.
The DNS is setup so that the client can communicate with the server, but when server tries to contact client machine it fails.
The resolution is to make sure the client machine is pingable from the CWM workstation.
Possible reasons for the server not being able to ping the client are:
–
–
5.
Avoid this problem by waiting 2-3 minutes after starting core in the Primary SSM before starting core in the Secondary SSM in Gateway.
6.
shmat: [22]: operating system error18:45:49 shmat: [22]: operating system error18:45:57 Error writing '/tmp/shmem.1fd4555c.0' errno = 418:45:57 mt.c, line 10260, thread 7148, proc id 1008, errors occurred during mt_notifyvp.When this error occurs, statsparser is not able to do any database related operation.
The error can be resolved temporarily by changing the /etc/system configuration as follows:
forceload: sys/shmsysforceload: sys/semsysset shmsys:shminfo_shmmax=1073741824set semsys:seminfo_semaem=16384set semsys:seminfo_semmap=5000set semsys:seminfo_semmni=8192set semsys:seminfo_semmns=8192set semsys:seminfo_semmnu=8192set semsys:seminfo_semume=256set semsys:seminfo_semvmx=50000set shmsys:shminfo_shmmin=256set shmsys:shminfo_shmmni=32000set shmsys:shminfo_shmseg=256set semsys:seminfo_semmsl=100The long-term solution is to increase the amount of memory to support 2 million connections consistently.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
If you register the SNMP Manager with a non-default bit-mask because you do not want certain groups (Example: FFFFFFFFF10701555), then you do not get trap 25302 and 25303, even though you have registered for that group.
If you deselect a currently undefined group like group 28, which is a bitmask of FFFFFFFFEFFFFFFF, you can then add traps 25302 and 25303 by editing the trap_filter.conf file and adding the following lines to GROUP 20 # Network Connectivity Status Change Traps:
–
–
21.
22.
–
–
–
–
A whole card resync takes several minutes to complete.
23.
In this situation, Cisco recommends you either remove and add the feeder while CWM is down, or, after adding the feeder, restart CWM.
24.
The attribute values in the internal frame can be updated by using the Refresh button of that internal frame.
25.
26.
27.
28.
29.
30.
31.
32.
33.
For example, when SmartLogging is enabled, an SNMP failure which triggers a Level 2 log message will cause a dump of log messages at all levels immediately prior to and following this event. The SmartLogging feature may have performance impact, due to excessive log messages. It should be disabled in normal operation and enabled only when needed for special investigation.
Connection Manager Limitations
When the connection modify dialog box is already open, another user can delete the connection using the CMGUI delete option.
The Connection Manager 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), CWM will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection.
RPM on PXM1-based MGX 8850/8230/8250 provisioning is done using telnet since 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.
HP OpenView Limitations
All event messages are displayed in the HPOV 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 CWM 15. Use the Network Monitor map instead.
Issues with the CWM 15 Statistics Collection Manager
In order to collect connection statistics, statistics should be enabled on individual connections. If the user only enables connections stats on SCM but does not set the stats enabled flag to true on the connection, the stats will not be collected, for that connection. Since there is no mechanism or warning to the user to have this enabled on the connections, CWM will not give appropriate error message.
When enabling statistics by selecting multiple nodes at a time in the SCM, enabling statistics on all the nodes will only work if all of the nodes have the same card types or 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. There is no such limitation for AXSM-E.
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 following statistics for SRM and SRM/E T3 lines.can be enabled on the switch, but are not supported by SCM:
•
•
•
•
•
•
•
HP OpenView is supported on StandAlone Statistics Manager (SSM). SSM processes generate CWM traps.
Stats Parsing is only supported for the "statsdb" database on the SSM machine. Stats Parsing is not supported for the "stratacom" database on the SSM machine.
At least one CWM must be up and running, with the nodes synced up, for SSM to work normally. SSM uses the CWM server workstation to get traps while enabling statistics for cellbus-based service modules on MGX 8850 and PNNI statistics on BPX.
The WANDEST server must be up and running on the CWM server workstation. SSM gets the node, node_info, card, network, rsc_part, bis_object tables from the CWM server workstation using WANDEST.
If the statsmaster SSM/CWM is down or unreachable in a SCM Gateway setup, the statsmaster must be changed on the switch to a machine that is up. The statsmaster is needed for SCM statistics enabling/disabling.
In an SCM Gateway setup with statistics collection going on, after switchover the old statistics data is not moved to the new Primary CWM/SSM machine.
SSM does not receive traps on Node/Card Deletion, so statistics collection must be stopped and disabled before deleting a node/card on the network. Also SSM does not receive traps on Node/Card Add messages, so the WANDEST upload must be received before the node/card can be seen in SCM GUI on SSM.
In SSM, statistics collection must be stopped and restarted after changing the node name or changing the node FTP password.
Limitations for CWM to CWM Communication
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 CWM workstations managing the same network must have seed nodes or gateway nodes that have IP addresses within the same network. All the CWM workstations should not all point to the same gateway node, but the gateway nodes they point to should be on the same network. The exception is that when using the Preferred Route feature, all the CWM workstations must all point to the same gateway node
The Configurator can be started on either the Primary CWM or the Secondary CWMs, but Add, Modify, or Delete operations using the Configurator can only be performed on the Primary CWM.
All the CWM to CWM Communication limitations listed above also apply to SCM Gateway.
Network Monitor Limitations
In a single routing node PNNI network, the node is managed using the IP address specified in the network.conf file.
In the case of a PXM45-based or PXM1E-based MGX network, the PXM45-based or PXM1E-based MGX nodes are managed using the primary IP address. The primary IP address is specified using Option 8 in the cnfndparms CLI. Configure the trap IP with the primary IP. PXM1-based MGX nodes connected to PXM45-based MGX nodes are managed through the atm0 IP. If the atm0 is not set, then the LAN IP is used to manage the PXM1-based MGX nodes. Configure the trap IP accordingly.
CWM 15 Notes and Cautions
Due to the nature of asynchronous behavior of ILOG client and server interaction, CWM client requests may be sent before the CWM server is ready. In this case, the following error message will be displayed on the workstation screen:
Ilb Error: Synchronous request to <unidentified actor failed by timeout>.
Note
Parameters displayed by the Network Monitor or Configuration Center that are not applicable to an element i.e.: a line or a trunk often contain the value -1. Treat this as the same as Not Applicable.
CWM 15 Server Installation or Upgrade to CWM 15
Note
The most current upgrade and installation information is found in the CWM Installation Guide, Release 15 (OL-4550-01). A PDF copy of this document is on the CWM 15 Documentation CD.
Important Configuration Notes
This section provides important information about configuration.
Naming Managed Nodes
Each node name of all the nodes managed by CWM must be unique.
Core File Management
Core files used to be created without unique names, and overwritten. Now core files are stored in the /usr/users/svplus/corefilesdir/ directory. Each is given a unique name in the format:
<process name>.<pid>.core.dump
Cisco Info Center Version
The Cisco Info Center (CIC) version supported by CWM 15 is 3.6 patch 1 (for MGX), or 3.6 patch 2 (for CWM). The file bundle included with this release is theCIC36Pipp000CWM15 bundle for CIC 3.6.x.
C-Note/CWM Configuration
The C-Note version supported by CWM 15 is 3.
The CWM core must be started and core processes should be up before the Orbix cmldomain services for C-Note are started.
Add the IP address of the C-Note workstation to the /opt/ssng/config/CMLLogin/SnmpPublisher.xml file by entering the following command:
vi /opt/ssng/config/CMLLogin/SnmpPublisher.xmlThe line you add should look like this:
<ipAddress>172.28.140.218</ipAddress>You need to substitute the actual IP address of your C-Note workstation for the sample 172.28.140.218 address listed above).
Node Numbering for Release 9.4 IGX Feeder Nodes
When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number, this node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing the CLI command "rnmnd <x>" where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use the CLI command "dspnds +n". Failing to do so, the CWM Databroker may have an incorrectly formed hybrid connection database, and the CWM GUI may show the connection as incomplete.
Security Profiles
The security profile and user profile are stored in the database as user_info and sec_profile tables. All CWM systems in the same domain will have the same data in the user_info and sec_profile table by means of CWM to CWM communication.
The user_info and sec_profile tables will not get dropped when the coldstart command is executed during a cold start. These tables can only be dropped by executing the coldstart command with the "-F" option.
The Security Manager GUI can be started from the Network Monitor main window in the primary CWM system.
The CWM user to be added to the database has to be a valid UNIX user, when a user logs in to CWM desktop, user authentication against UNIX gets performed. The CWM user's password needs to match the one defined in the UNIX system.
CWM Database
After performing the creation of a new database by executing the coldstart script, if CWM is restarted (stop core and start core) before it is synchronized with the network, it will result in a database inconsistency. In this case, rerun the coldstart script to avoid database inconsistencies.
Note
When a Gateway node is upgraded or rebuilt, before CWM has synchronized up with the network, CWM must be cold-started (create CWM database and restart CWM). This is required to ensure CWM database consistency.
The user supplied network name can be up to 10 characters in length and should be alphanumeric characters only (no periods).
The asi_line table is populated with the 1-based port number and not the 0-based port number for IGX ports.
Occasionally, a triggered resync (the automated running of the restoreallcnf command) may result in the CWM connection data being inconsistent with that on the switch. In this case, run a manual node resync to ensure that there are no inconsistencies between CWM connection data and the connection data on the switch.
RPM Management Limitations
RPM-PR is not supported on MGX PXM1-based nodes managed by Chassis View in CWM 15. The applicable trap is missing so CWM cannot monitor the back card.
For both the RPM and RPM-PR card types hardware and firmware revisions are not populated in the database.
For the RPM-PR card type the front card description displays "RPM" instead of "RPM-PR".
The RPM back card support feature is disabled by default. Customers interested in obtaining the RPM back card information should enable this feature by editing the emd.conf file before starting the CWM core. If this feature is enabled, the back card information is polled from the switch only during a coldstart or a manual resync. After the coldstart or manual resync completes, any changes to the back card configuration or status will not be updated until you execute another coldstart or manual resync.
CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. There is no functionality difference.
ChassisView Operation After Card and Line Switchovers
When two cards are in a redundancy relationship, the primary card (i.e. the logical slot) is used to display the ports and lines for all provisioning and troubleshooting activities, even if the primary slot becomes a standby. The secondary slot does not show any ports and lines under it even after it becomes active. Provisioning is only allowed on the working line of an APS pair, irrespective of whether that line is currently active or not. However, both the working and protection lines are monitored.
In ChassisView, the ports on the card only display if they are available. Ports do not display on the secondary slot, even after it becomes active. The backcard appears as blank, not with greyed out ports as in previous releases that used CiscoView for equipment management.
Equipment Management Configuration Notes
In the emd.conf file, the following two parameters will need to be customized depending on network.
The OORequest parameter defines the number of configuration files per node that can be requested at one time. You can request a maximum of 32 configuration files concurrently per node. The range is 1 through 32, and the default is 32.
The OOStart parameter defines the number of OOEMC child processes. The range is 1 through 25, and the default is 6.
All the PNNI nodes managed by CWM (PXM45 and PXM1E- based 8950, 8850, and 8830 nodes and BPX nodes with SES shelves) are distributed among OOEMC processes.
The number of nodes managed by a single process is computed by dividing the total number of PNNI nodes in the network by the number of processes is defined by OOStart. Let us name this computed number of nodes managed by a single process the MANAGED_NODE_COUNT.
Then, MANAGED_NODE_COUNT * OORequest must be less than or equal to 200.
This can be achieved by either increasing the OOStart or reducing the OORequest. The normal range of OOStart is 5-20.
If the OOStart parameter value is increased beyond 10 then the number of DMD processes has to be increased or a shared memory overflow will occur.
Network Monitor Server Configuration File (NMServer.conf)
There are two parameters (HELLO_EVENT_INTERVALand EVENT_REDELIVERY_COUNT) in the NMServer.conf configuration file.that are tied to the NMSERVER_DISCONNECT_TIMEOUT parameter in the CMSCClient.conf client configuration file.
The NMSERVER_DISCONNECT_TIMEOUT parameter value needs to be set to the same as the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value. the range for HELLO_EVENT_INTERVAL is 0 through 60, the default is 60. The range for EVENT_REDELIVERY_COUNT is 0 through 3. The default is 3. The default for the NMSERVER_DISCONNECT_TIMEOUT parameter is 60 times 3 or 180.
If you change any of these parameters they must be adjusted so the HELLO_EVENT_INTERVAL value times the EVENT_REDELIVERY_COUNT value continues to equal the NMSERVER_DISCONNECT_TIMEOUT parameter value.
The Network Monitor Server configuration file (NMServer.conf) also contains the PERIODIC_RESYNC_INTERVAL parameter. This parameter defines the interval in hours between periodic resyncs. The range is 2 through 24, and the default is 8. You can also disable the periodic resync feature by setting the PERIODIC_RESYNC_INTERVAL parameter to 0.
Creating and Configuring a CWM Auto-Restart Shell Script
This section describes how to create a shell script that automatically starts the CWM core after a reboot. To create this shell script you need to use a text editor to create a new file containing the commands that you want the script to execute.
Using the vi Editor to Create Your Auto-Restart Shell Script
Follow the steps below to create a script that uses shell commands to automatically restart the CWM core after the workstation has been rebooted.
Step 1
$ suStep 2
# cd /etc/rc3.dStep 3
# vi /etc/rc3.d/S99init_svSince this script does not currently exist, the vi editor will open on a blank line, waiting for you to enter the script commands.
Step 4
******************************************************************#!/bin/sh# Check if Informix configuration is going onwhile [ ! -z "`ps -ef | grep S98init_db | grep -v grep`"]doecho "Informix initialization in progress...." >> /usr/users/svplus/log/.start_stopCWM.logsleep 5done# Start Orbix E2A ... as svplusecho "Starting Orbix E2A ..." >>/usr/users/svplus/log/.start_stopCWM.logsu - svplus -c /usr/users/svplus/scripts/startorbix2000 >> /usr/users/svplus/log/.start_stopCWM.logsleep 5# Running Guard process ... as svplusecho "Running Guard process" >>/usr/users/svplus/log/.start_stopCWM.logsu - svplus -c /usr/users/svplus/scripts/Install/RunGuard &# Start CWM core process ... as svplussu - svplus -c /usr/users/svplus/scripts/start_SV+ &******************************************************************
Note
Step 5
# chmod 755 S99init_sv
Note
For more information on configuring this feature, refer to the /etc/init.d/README file.
SNMP Service Agent Release Notes
Trap Limitation with PXM1-based MGX Nodes
The type of traps collected by CWM from connection addition and modification on Cisco MGX PXM1-based nodes running release 1.3.00 and onwards can be configured using the following new CLI commands:
•
•
Use these commands to select either DEFAULT: the same legacy traps plus trap 50601 to be sent, or ENABLE: only trap 50601 to be sent for every connection addition or modification.
If the dspchantrapenbl CLI command is set to DEFAULT, you can use the cnfchantrapenbl ENABLE CLI command to change to only collecting trap 50601 while CWM 15 is running.
However, if you are currently only collecting trap 50601 (the dspchantrapenbl CLI command is set to ENABLE), and you decide to configure the node to send legacy traps for every connection addition or modification by executing the cnfchantrapenbl DEFAULT CLI command, all CWM workstations monitoring the node must be in shutdown state before you execute the command.
Caveats
This section lists known and resolved anomalies in the Cisco WAN Manager 15 software and other associated software.
Known Anomalies in CWM 15 Software
This section lists known anomalies in CWM Release 15 software as of 04/14/04
.
Anomalies Resolved in the Baseline, but not Included in CWM 15.0.00 Software
This section lists the anomalies resolved in the baseline, but not included in CWM Release 15.0.00 software as of 04/14/04
.
Related Documentation
The following technical documents comprise the CWM 15 documentation set:
•
•
•
•
•
•
PDF copies of the first five items in the CWM 15 documentation set are provided on the CWM 15 Documentation CD along with a copy of Adobe Acrobat and Netscape Communicator 4.76 for use in reading the files.
Use the included gzip utility to decompress the .gz files. The command is gzip -d.
These release notes are not available on the CWM 15 Documentation CD. They are available on-line at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/rnote.htm
Obtaining Documentation
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0402R)
