-
User Guide for the Cisco Mobile Wireless Transport Manager 6.1.1
-
Table of Contents
-
Preface
-
Overview
-
Configuring Security
-
Setting Up Your Server
-
Getting Started
-
Basic Operations
-
Understanding Basic Object Functions
-
Managing Views
-
Understanding Detailed Object Functions
-
Managing Alarms and Events
-
Viewing Network Topology
-
Accessing Data from the Web Interface
-
Viewing Administrative Information from the Web Interface
-
Managing Reports
-
Editing an ITP Route Table File
-
Editing an ITP Global Title Translation Table
-
Editing ITP MLR Address Table Files
-
Client Object Map Reference
-
Command Reference
-
FAQs
-
Troubleshooting the MWTM and the Network
-
Status Definitions
-
MIB Reference
-
Trap Reference
-
Configuring MWTM to Run with Various Networking Options
-
MWTM Ports
-
Glossary
-
Index
-
FeedbackTable Of Contents
FAQs
This appendix contains:
General FAQs
These categories of frequently asked questions are general questions about the Cisco Mobile Wireless Transport Manager (MWTM):
Installation Questions
This section addresses the following installation questions:
•
How do I install the MWTM client?
•
How do I install the MWTM client?
You can install the MWTM client either from the DVD distributed with the MWTM, or by using a web browser to download the MWTM client from an MWTM server. See the Installation Guide for the Cisco Mobile Wireless Transport Manager 6.1.1 for full details.
After a failed uninstall of the Windows client, I am prompted to uninstall again, but the procedure does not work. Why?
If for some reason the Windows MWTM client uninstall procedure fails before the client is completely uninstalled, the MWTM prompts you to uninstall the client again. However, this might not be possible using the standard Add/Remove Programs icon in the Windows Control Panel, or from the Windows Start menu.
If you cannot uninstall the MWTM client using the standard procedure, use this procedure:
Step 1
Step 2
Why do I see strange character strings when I install the MWTM?
Some UNIX systems use the LANG variable to indicate the locale. The setting of the LANG environment variable can cause syntax errors in the MWTM setup scripts, which can result in messages that contain strange character strings such as ?y?d@O. To correct this problem, unset the LANG environment variable in the workstation from which you are installing the MWTM, using one of these commands:
•
•
Then install the MWTM again.
Server Questions
This section addresses the following server questions:
•
•
•
•
•
What workstation and network devices do I need to run the MWTM?
The MWTM comprises two distinct pieces of functionality.
•
•
Note
For further hardware and software requirements, see the "Preparing to Install the MWTM" chapter of the Installation Guide for the Cisco Mobile Wireless Transport Manager 6.1.1.
Why can't my remote workstation access the MWTM on my local workstation?
Keep in mind that performance is always better if you access the MWTM by installing the MWTM client on the remote workstation.
However, if you want to enable a remote Solaris/Linux workstation to access the MWTM on a local workstation, enter the xhost + remote_workstation UNIX command on your local workstation, where remote_workstation is the remote device you are enabling to access your local workstation.
To enable a remote Windows workstation to access the MWTM on a local workstation, you can use an X-Window system emulator such as eXceed or Reflection X, but be aware that there might be display problems. For example, the window borders might disappear, or the keyboard focus might be missing.
The X Performance Enhancer (AntiAliasing Off) check box in the Preferences window specifies whether antialiasing is turned on in the topology map. Antialiasing, which is turned on by default, improves the appearance of the icons and connections in the map.
You can improve the performance of the MWTM client on a remote workstation by turning off antialiasing in the topology map. For more information, see Turning Off Antialiasing, page 10-24.
I moved the server on which I had installed the MWTM and now I can't start the MWTM client or server. Why?
If you change the IP address of the server on which you installed the MWTM, or if you move the server to a new network, you must reboot the server to prevent MWTM connection problems.
To reboot the server, use this procedure:
Step 1
Step 2
cd /opt/CSCOsgm/bin./mwtm rebootIf you change the server's Solaris/Linux hostname, you must reset the default hostname on the MWTM server and client, using this procedure:
Step 3
Step 4
cd /opt/CSCOsgm/bin./mwtm evilstopThe MWTM stops all MWTM servers on the local host.
Step 5
./mwtm servername hostnamewhere hostname is the new default hostname. Ensure that the new name is valid and is defined in your /etc/hosts file.
The MWTM resets the default hostname for the MWTM server and client and automatically restarts the MWTM server.
Step 6
Why did I receive a "cannot connect to server" message?
When you launch the MWTM client, the GTT Editor, Address Table Editor, or the Event Editor, or when you connect to a new server (whether manually or automatically as the result of a server failure), you might receive this message:
This client is not allowed to connect to the server or the server is listening on a port the client does not know about or cannot reach. Click the help button for a more detailed explanation.If you receive this message, one of these situations has occurred:
•
To resolve this problem, contact the MWTM administrator and ask to have your client's IP address added to the ipaccess.conf file (see Limiting MWTM Client Access to the MWTM Server (Server Only), page 2-27).
•
To resolve this problem in Solaris/Linux, use the mwtm servername command to reset the MWTM server's default hostname to an IP address that your client can access and restart the server (see mwtm servername, page B-60).
To resolve this problem in Windows, choose Start > Programs > Cisco MWTM Client > Modify Default MWTM Server Name, then you can enter the mwtm servername command.
Note
•
To resolve this problem, set up the firewall correctly (see Firewall Communication, page H-5).
Will the MWTM server processes restart automatically after a system reboot?
Yes. When you install the MWTM server, the MWTM modifies your system startup scripts to ensure that the MWTM server processes start up again after a system reboot. To accomplish this, the MWTM adds these lines to your system startup scripts:
/etc/init.d/sgm/etc/rc0.d/K99sgm/etc/rc1.d/K99sgm/etc/rc2.d/K99sgm/etc/rc3.d/K99sgm/etc/rc3.d/S99sgmThese lines ensure that the MWTM shutdown and startup scripts run in the correct order for each system initiation state.
Note that for Linux only, these lines are modified as well:
/etc/rc5.d/S99sgm/etc/rc6.d/K99sgmWhy doesn't my MWTM server start after installing SSL?
If you have not installed the SSL key and certificate, the MWTM server will not start. For exact details on this process, see Enabling SSL Support on the MWTM Server, page 2-20.
GUI Questions
This section addresses the following GUI questions:
•
Some of my MWTM windows are showing up with small, unusable text entry fields. How can I correct this?
Depending on your system, as well as other factors, the MWTM windows can sometimes display so small that text is illegible, and columns and text entry fields are very narrow and unusable. If this happens, resize the window and widen the individual columns until the information is again legible and the columns and text entry fields are usable.
To make a column wider or narrower, click the column divider in the heading and move the divider to the right or left while holding down the right mouse button.
Sometimes my MWTM display seems to lock up. Why?
In the MWTM, events might cause message popups to remain in the background of your display, preventing you from interacting with other windows. If you suspect that your display has locked up, perform these tasks:
•
•
Browser Questions
This section addresses the following browser questions:
•
Sometimes when browsing the MWTM web interface, a popup appears with this message: Unresponsive Script. Why does this happen and how can I prevent it from reoccurring?
This problem occurs when using the Firefox browser version 1.5. It is not an MWTM bug. You can prevent the popup from occurring with this workaround:
Step 1
Step 2
You should now see a setting appear in the window below the filter bar. The setting's name should match what you entered previously (dom.max_script_run_time) and most likely shows a default value of 5.
Step 3
If changing this setting still causes the Unresponsive Script popup to appear, repeat these steps but increase the number that you enter in this step.
The MWTM web pages appear empty (without content). Why does this happen and how can I prevent it from reoccurring?
Your Internet Explorer browser settings in the MWTM client are disabling active scripting. To modify this, in Internet Explorer, change the browser settings as follows:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
What is the difference between the Java and Web client?
The following table compares MWTM features for Java and Web Client:
Topology Questions
This section addresses the following topology questions:
•
•
How does "zoom in on an area" work in a topology map?
With this feature, you can zoom in on a chosen area of the topology map in the topology window. To do so, click the Zoom in on an area button, or choose Topology Tools > Zoom > Area from the MWTM main menu, then click in the topology map and drag a rectangle around the area you want to zoom in on. The MWTM expands the chosen area to fill the topology map.
Can I add my own icons to the topology map?
No. To ensure that icons on the topology map can be resized cleanly, they are drawn as special vector-based images. Raster images, such as GIF files, do not resize cleanly.
Events and Alarms Questions
This section addresses the following events and alarms questions:
•
•
•
•
•
If I select the Clear Event Icon menu option, does that delete the event from the MWTM database?
No. When you select the Clear Event Icon menu option for an object, the MWTM does not delete the actual event from its database. The MWTM only deletes the event icon (an orange triangle) from its displays for the object, and only for the MWTM client on which you are currently working.
Can I add my own sounds to the Event Sound Filter?
Yes. You can add sound files to an MWTM client. The MWTM clients can play these sound file formats: AIFC, AIFF, AU, SND, and WAV.
Note
The MWTM client sound files are stored in the MWTM client's sounds directory:
•
•
•
If for some reason the MWTM cannot play a specified sound file, the MWTM plays a default beep. For example, the MWTM cannot play a sound file if one of these conditions exists:
•
•
•
•
Why are the age of my alarms always 0 minutes?
If the server clock is ahead of the client clock, the value will be 0 until the client clock catches up to the server clock. To get accurate values, use a time service such as Network Time Protocol (NTP) or similar, which keeps server and client clocks in sync.
Why are objects in the Physical folder ignored?
Interfaces that are not configured for ITP, IPRAN, mSEF, or management connections could be set as administratively up on the node; however, since these interfaces are not connected and/or not configured, they appear to be operationally down, even though this status does not affect the behavior of the network (for example, unconnected E1 ports on cards in an ONS chassis). To make sure that these interfaces do not contribute to the overall status of the parent node, the Physical folder status is ignored.
Objects that appear in the Physical folder but also outside of the Physical folder are not ignored, and their status does contribute to the status of the parent node.
If you want to monitor the status of objects that are ignored in the Physical folder:
Step 1
Step 2
How do I enable CPU usage threshold alarms?
MWTM does not currently poll the device for CPU threshold alarms. MWTM recognizes the cpmCPURisingThreshold and cpmCPUFallingThreshold traps defined in the CISCO-PROCESS-MIB and creates events for them in the Event History table. You can modify the MWTM event configuration to raise and clear an alarm when these traps are received. Using the Event Editor, enable the raise alarm check box of both the CPURisingThreshold and CPUFallingThreshold events. Select File -> Deploy to make your changes active.
To enable the cpmCPURisingThreshold and cpmCPUFallingThreshold traps on the device, execute the following commands. It is recommended that the rising and falling intervals be 900 seconds or greater to ensure that the traps convey reliable information.
snmp-server enable traps cpu thresholdprocess cpu threshold type <total|process|interrupt> rising <rising threshold> interval <rising interval> falling <falling threshold> interval <falling interval>If needed, also consult the IOS command reference for your platform.
Polling Questions
This section addresses the following polling questions:
•
•
How often does the MWTM poll nodes?
By default, the MWTM polls the nodes in the network every 15 minutes. However, you can initiate a poll for one or more nodes at any time by selecting the nodes in the Discovery tab in the Discovery dialog box and pressing Poll.
You can also change the default poll interval for one or more nodes in the SNMP Configuration dialog box. You must be logged in as the root user or as a superuser to access this dialog box.
Finally, the Node Details window polls the visible node and its adjacent node every 15 seconds, but you can change that poll interval, too.
How do I change the default status polling interval?
The MWTM polls the MWR node for status information (for example, interface up or down) every 15 minutes. The size of this poll depends on the number and type of interfaces that are enabled on the MWR.
To change the default polling interval of 15 minutes, open the SNMP Configuration dialog box by selecting Network > SNMP Configuration from the MWTM main window. You can use this dialog box to change the default polling interval to any number of minutes from 5 to 1440.
Note
MIB Questions
What are the names of the MIBs used by the MWTM?
You can find the complete list of MIBs that the MWTM configures and queries in Appendix F, "MIB Reference."
You can obtain the latest versions of these MIBs from one of these locations:
•
•
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
•
Miscellaneous Questions
This section addresses the following miscellaneous questions:
•
•
•
•
•
•
•
•
Does the MWTM require any other NMS applications?
The MWTM is functionally a standalone product and does not require any other products. However, you can integrate the MWTM with other products to provide added value.
For example, you can integrate the MWTM with CiscoWorks, which provides access to the full suite of CiscoWorks products, including the Device Center, the CiscoView Element Manager, Resource Manager Essentials (RME), the Internetwork Performance Monitor (IPM), and the Access Control List Manager. See Integrating the MWTM with CiscoWorks, page 5-35 for more information.
You can also forward the MWTM events to other hosts, in the form of SNMP traps. This enables the MWTM to integrate with high-level event- and alarm-monitoring systems such as the Cisco Info Center (CIC) and Macrames's Netcool suite of products. These systems can provide a single high-level view of all alarm monitoring in your network, making it easier to detect and resolve problems (see Forwarding Events as Traps to Other Hosts, page 9-37).
Can I run the MWTM on my Windows PC?
You can run the MWTM client on Windows XP Professional on your PC. However, the MWTM server must run on a Solaris/Linux system.
What is a superuser?
A superuser is an MWTM user who has been enabled to perform most of the MWTM functions that otherwise require the user to be logged in as the root user.
For a complete description of the functions that a superuser can and cannot perform, as well as instructions for enabling a superuser, see Specifying a Super User (Server Only), page 2-17.
Does the MWTM Java RMI use TCP or UDP?
The two-way RMI communication in the MWTM that occurs between Java-based GUI clients and Java-based server processes uses TCP sockets.
What does a status of Deleted, Uninhibited, or NoShutdown mean?
A status of Deleted, Uninhibited, or NoShutdown indicates a possible problem with the MWTM. If you see one of these status settings, contact Cisco TAC or your Cisco Account Team.
Why don't the contents of the syslog tab match the log files of my syslog server?
The MWTM client shows current syslog information available from a node, which reflects what content the node has stored in its internal memory. It is possible to configure your node to send its syslog messages to a host that stores these messages in files (usually under /var/adm). The MWTM does not access these persisted log messages, even if the host on which your MWTM server is running is logging syslog messages from your node. To access these persisted log messages, use CiscoWorks, or other software with syslog viewing capabilities.
When I start my MWTM client, I get a login window. However, I did not specify a user password during installation. How do I fix this?
When you install the MWTM and if you select all the default settings, user security is enabled (default option) which causes the MWTM login window to appear when you start the MWTM client. However, if you did not provide a user password during the installation, you must disable user security before you can log into the MWTM client or add user passwords to the MWTM.
To disable user security:
Step 1
Step 2
/opt/CSCOsgm/bin/mwtm useraccess disableOutput similar to the following appears:
[root@mwtm-server bin]# /opt/CSCOsgm/bin/mwtm useraccess disableUser Based Access Protection is Disabled.MWTM server must be restarted for changes to take effect.Use the following command to restart the server:mwtm restartClear browser cache and restart browser after changing MWTM Security!![root@mwtm-server bin]#Step 3
To enable user security:
Step 1
Step 2
/opt/CSCOsgm/bin/mwtm useraccess enableStep 3
/opt/CSCOsgm/bin/mwtm adduser <username>Output similar to the following appears:
[root@mwtm-server bin]# /opt/CSCOsgm/bin/mwtm useraccess enableUser Based Access Protection is Enabled.Use the "mwtm adduser" command to add users.Log in with usernames and passwords for access to MWTM Features.MWTM server must be restarted for changes to take effect.Use the following command to restart the server:mwtm restartClear browser cache and restart browser after changing MWTM Security!![root@mwtm-server bin]# /opt/CSCOsgm/bin/mwtm adduser newuserAdding user newuserNew password:Re-enter new password:Adding password for user newuserShould user be forced to change this password at the next login? [n] nAccess Level===========================1 - Basic User2 - Power User3 - Network Operator4 - Network Administrator5 - System AdministratorEnter access level for user newuser: 5User newuser added with level 5 access.User Based Access Protection is Enabled.Clear browser cache and restart browser after changing MWTM Security.[root@mwtm-server bin]#Step 4
I'm field testing MWTM in my lab and I see confusing results when discovering new network configurations. What's going on?
The MWTM keeps information about older objects in its database even after they have been deleted. This is considered a logically deleted state. MWTM retains this information to try and maintain any user customized data associated with an object (for instance, a customized name) in case the object is rediscovered at some point in the future. Logically deleted data is physically deleted after seven days if it is not reused by then. You can use the mwtm purgedb command to immediately remove this logically deleted data from the MWTM database.
Unfortunately, this benefit might have a side effect. In certain cases, rediscovery of a deleted object may cause the MWTM to use obsolete information in the database, rather than the new information. Ultimately, some configuration changes are not detected, and the viewable data from the client application is incorrect.
There are 2 alternatives to address this behavior in a lab environment:
1.
2.
Why can't I discover primary and standby devices at the same time?
In MWTM, nodes are identified by their management IP address, from which MWTM initiates SNMP polling of a device. In various redundancy scenarios, different devices respond to requests on the same IP address. When this happens, MWTM is unable to differentiate between the multiple devices and considers them the same device.
For example, if two routers share the same physical link via a Y-cable where only one of the devices can use the IP address at a time (even though there are actually two devices), MWTM discovers and displays a single device only.
If a redundancy mechanism is instantiated where two devices share the same virtual IP address but only one device responds to any given request, MWTM discovers and displays a single device only.
How do I increase the swap size in Solaris?
To create a new swap file on Solaris:
Step 1
For example, to create a 1GB swap file, enter the following command:
/usr/sbin/mkfile 1024m /opt/swapfilewhere /opt/swapfile is the name of the file to be used as swap space. Units for the size can be kilobytes (k), blocks (b), or megabytes (m). Choose carefully the disk location to create the swap file. Choose a disk partition with plenty of free disk space.
Step 2
/usr/sbin/swap -a /opt/swapfileStep 3
/usr/sbin/swap -lStep 4
/opt/swapfile - - swap - no -How do I increase the swap size in Linux?
To create a new swap file on Linux:
Step 1
For example, to create a 1GB swap file, enter the following command:
/bin/dd if=/dev/zero of=/opt/swapfile bs=1M count=1024where /opt/swapfile is the name of the file to be used as swap space. This specifies a blocksize of 1Mb and 1024 of them for 1Gb total. Choose carefully the disk location to create the swap file. Choose a disk partition with plenty of free disk space.
Step 2
/sbin/mkswap /opt/swapfile/sbin/swapon /opt/swapfileStep 3
/sbin/swapon -sStep 4
/opt/swapfile swap swap defaults 0 0
ITP Specific FAQs
This section addresses frequently asked questions related to ITP operations:
•
•
•
•
•
•
•
•
Can ITPs send traps to the MWTM and to another process on the same node?
Yes. You can configure your ITPs to send SNMP traps to more than one process on a single node. Each process receives traps on a different port number. However, to do so, you must configure a different community string for each process.
For example, your ITP configurations could include these lines:
snmp-server host 1.2.3.4 public udp-port 162snmp-server host 1.2.3.4 otherCommunity udp-port 44750where:
•
•
You would then configure the MWTM to receive traps on port number 44740. For information about how to configure the MWTM port number, see Enabling SNMP Traps, page 3-7.
Why did the MWTM not discover all of my ITP nodes?
After you discover the network, examine the Discovered Nodes table to verify that the MWTM discovered all of the nodes in the network. If you suspect that the MWTM did not discover all of the nodes, verify these conditions:
•
•
•
•
•
•
How can the Received for some of my links be 105%?
For serial and HSL links on Cisco 7507 and 7513 series routers, in the Received and Send real-time data charts for links and linksets, the visible data can vary by up to 5% from the actual —the MWTM might even display data above 100%. This variance results from the synchronization of Layer 2 counters between the Versatile Interface Processor (VIP) CPU and the Route Switch Processor (RSP) CPU on 7500 series routers. This variance does not occur for links on Cisco 2600, 7200, or 7300 series routers.
What does the asterisk (*) mean next to an SLC number?
In the MWTM, each link is identified by its signaling link code ID (SLC). An asterisk indicates that a link is not configured, or that a poll could not get data for the link.
The placement of the asterisk, to the left or right of the SLC, indicates whether the missing link is associated with the chosen linkset or with its adjacent linkset. For example, SLC (*)3 means that no link is associated with the chosen linkset for SLC 3, and SLC 3(*) means that no link is associated with the adjacent linkset for SLC 3.
When I try to deploy routes, GTT files, or address table files from the MWTM, why does TFTP fail or time out?
There are three primary causes for TFTP failure or timeout errors:
•
•
•
Why don't my linkset and link totals match?
When you run the mwtm export command for a link or linkset, you might notice the output totals do not match the totals in the MWTM client. This discrepancy occurs because the mwtm export command counts each side of the linkset or link as a individual linkset or link, whereas the MWTM client (assuming it knows both sides) counts both sides as one linkset or link pair. Therefore, the mwtm export command might have more linksets and links than the MWTM client shows.
How do I enable accounting collection in the MWTM?
Enabling accounting collection in the MWTM is described next. First, you must enable accounting on each ITP node using IOS commands. Then you can enable accounting in the MWTM.
Note
To enable accounting globally for all linksets on an ITP node:
Step 1
Step 2
node name(config)#cs7 accounting global-gttnode name(config)#cs7 accounting global-mtp3node name(config)#cs7 accounting global-unrouteable
Note
To enable accounting per linkset on an ITP node:
Step 1
Step 2
node name(config)#cs7 instance number linkset namenode name(config)#accountingnode name(config)#gtt-accountingnode name(config)#unrouteable-accounting
Note
The MWTM accounting reports are disabled by default. Enable them:
Step 1
node name#/opt/CSCOsgm/bin/sgm statreps acctnode name#/opt/CSCOsgm/bin/sgm statreps gttData is collected daily, and is not affected by polling interval preferences in the Java or web clients.
Note
Step 2
node name#crontab -lThe list should include statreps acct and statreps gtt.
How do I generate custom ITP reports quarter hourly instead of hourly or daily?
You can manually generate custom reports using the MWTM command line interface (CLI).
Note
These commands apply to generating custom reports:
•
•
•
•
•
•
The quiet option disables output to the console.
The output of these commands is placed in this directory:
/opt/CSCOsgm/reports/custom
Note
Use the UNIX cron facility to schedule the CLI commands to be run every quarter hour:
Step 1
Step 2
crontab -eStep 3
a.
54 * * * * /opt/CSCOsgm/bin/sgmCron.sh xuastats56 * * * * /opt/CSCOsgm/bin/sgmCron.sh linkstatsb.
00,15,30,45 * * * * /opt/CSCOsgm/bin/mwtm linkstats quiet00,15,30,45 * * * * /opt/CSCOsgm/bin/mwtm xuastats quietYou can find these reports in this directory:
/opt/CSCOsgm/reports/customThere will be 15 minute timestamps on each report file.
Step 4
Note
Why do I have limited functionality on certain tabs?
You might notice limited functionality on the following ITP tabs:
•
•
•
These tabs are available on certain nodes, and also require specific IOS images:
IP-RAN Specific FAQs
This section addresses frequently asked questions related to IP-RAN operations:
•
•
•
•
•
•
What is the difference between in-band and out-of-band management?
Nodes located at the cell site are usually accessible only over the same path used to transport voice traffic. Collecting management information over this path is called in-band management and has an impact on backhaul. The MWTM can reduce the amount and frequency of collecting management information when information is collected in-band.
Nodes located at the aggregation site are managed using different paths than those used by voice traffic. Collecting management information in this configuration is called out-of-band management and has no impact on backhaul.
The following table compares MWTM features for in-band and out-of-band management:
Historical reports
Not available1
Generated
Trap polling
Traps do not trigger polling
Traps do trigger polling
Regular polling2
Performed
Performed
Real-time polling
Available3
Performed
1 However, you can always collect historical reports from the aggregation node site (that is, the RAN SVC module in the ONS). The receiving traffic on the RAN SVC shorthaul and backhaul matches transmitting traffic from the MWR shorthaul and backhaul.
2 Polls are performed every 15 minutes. To change this rate, see the SNMP and Credentials Dialog Box (for details, see SNMP Settings Table, page 3-16).
3 To perform real-time polling in-band, you must configure it in the Preferences window (for details, see Startup/Exit Settings, page 5-3).
•
conf tipran-mib location cellSiteipran-mib snmp-access inBand•
conf tipran-mib location cellSiteipran-mib snmp-access outOfBand•
conf tipran-mib location aggSiteipran-mib snmp-access outOfBandThis example shows the range of options that are available for the ipran-mib command:
ems1941ka#conf tEnter configuration commands, one per line. End with CNTL/Z.ems1941ka(config)#ipran-mib ?backhaul-notify-interval Interval for backhaullocation Location of devicesnmp-access Specify type snmp connectivitythreshold-acceptable Acceptable thresholdthreshold-overloaded Overloaded thresholdthreshold-warning Warning thresholdems1941ka(config)#ipran-mib location ?aggSite Located at BSC or RNC sitecellSite Located at BTS or Node B siteundefined Undefined locationems1941ka(config)#ipran-mib snmp-access ?inBand In Band SNMP connectivityoutOfBand Out of Band SNMP connectivityundefined Undefined connectivityHow does the MWTM server communicate to the IP-RAN node at the remote cell site?
The MWTM server must communicate to the cell-site node using IP routing. If the cell-site node is reachable only through the backhaul interface, add a static route on the MWTM server to point to the cell-site node. Use the IP address of the local (aggregation site) IP-RAN node as the next-hop address.
These examples of static routing for Solaris and Linux platforms are based on the diagram in Figure C-1.
Figure C-1 Example of Static Routing
To create a static route on a Solaris MWTM server, use this procedure:
Step 1
Step 2
/usr/sbin/route add host 10.1.1.1 20.1.1.1To create a static route on a Linux MWTM server, use this procedure:
Step 1
Step 2
route add -host 10.1.1.1 gw 20.1.1.1When viewing capacity planning information in the RAN Backhaul report, the peak timestamps are sometimes outside the chosen range. For example, 2005-12-01 appears in the report window, but I see Nov 30, 2005 11:58:37 PM in the Peak Timestamp information. Why is the peak timestamp outside the chosen range?
Summaries do not end on fifteen-minute boundaries such as 12:00:00, 12:15:00, 12:30:00, because the node processes system time from its own start time, not from the current hour and minute. Therefore, when the timestamps are normalized to the MWTM server time, the end timestamp might appear as 12:03:15, 12:18:15, or 12:33:15.
When you run a capacity planning report, the MWTM retrieves records for the fifteen-minute period that has an end timestamp in the start and stop range that you specify. Using the previous timestamps as examples, if a user runs a report for the 12:00-to-13:00 time range, the 12:03:15 record is retrieved. That record is a fifteen-minute summary of the period between 11:48:16 and 12:03:15. If the Peak Timestamp for this record occurred at 11:55:44, the user would observe this value in the capacity planning report.
A user might observe Peak Timestamps that occur up to fifteen minutes before the start timestamp specified in the capacity planning report query. This is the expected behavior.
Does the MWTM support the use of Hot Standby Router Protocol (HSRP) for a pair of redundant nodes?
The MWTM supports HSRP for the Cisco Mobile Wireless Router (MWR) 1941-DC-A operating in an active-standby configuration. The MWTM supports these scenarios:
•
•
•
Note
Because the IOS configurations are not synchronized between MWR nodes, make sure the IOS configs are identical (except HSRP settings) on both nodes.How do I sync up the time/date display on my IP-RAN performance and error data with the time/date on the MWR?
For the performance and error data to match the time/date on the MWRs, all equipment (Cisco and MWTM server) must be configured with the same Network Time Protocol (NTP) server.
To configure NTP on the Cisco node:
Step 1
Step 2
Step 3
ntp server <ip-address-of-ntp-server>Step 4
Step 5
To configure NTP on a Solaris-based MWTM server:
Step 1
Step 2
server <ip-address-of-ntp-server>Step 3
/etc/init.d/ntpd restartStep 4
If the date is still incorrect, follow these instructions:
a.
/etc/init.d/ntpd stopb.
/usr/sbin/ntpdate <ip-address-of-ntp-server>c.
/etc/init.d/ntp start
Note
To configure NTP on a Linux-based server:
Step 1
Step 2
server <ip-address-of-ntp-server>Step 3
/etc/init.d/ntpd restartStep 4
If the date is still incorrect, follow these instructions:
a.
/etc/init.d/ntpd stopb.
/usr/sbin/ntpdate <ip-address-of-ntp-server>c.
/etc/init.d/ntp start
Note
Why are my MWR nodes yellow when I discover them?
When the MWTM discovers or polls a node, a list of all interfaces and their corresponding status are reported back to the MWTM server. If the MWTM determines that one or more interfaces are operationally down, the MWR node is marked with a yellow status symbol unless the interface has an administrative status of Down (coming from the IOS shutdown directive). To determine the status of an interface, the MWTM uses the following logic matrix:
Status
StatusUp
Up
Up
Not ignored
Up
Down
Down
Not ignored
Down
Down
Down
Ignored
Down
Up
Down
Ignored
Note
Why does my backhaul graph show greater than 100% for transmit traffic?
When the backhaul for transmit traffic exceeds 100%, the likely cause is oversubscription of the shorthaul links that constitute the backhaul. The backhaul is the amount of traffic that the system attempted to send, not the amount that was actually sent. If it is greater than 100%, you should see queue drops or other errors during the same time period. A backhaul of greater than 100% is possible for a heavily loaded link with some occasional oversubscription.
How to create SAToP and CESoPSN Interfaces?
There is no separate interface type for SAToP. For TDM over PWE3, MWTM supports provisioning of both SAToP and CESoPSN by selecting the TDM group as unframed vs framed with time slots where as, the user is choosing between SAToP vs CESoPSN.
The SAToP and CESoPSN Interfaces can be created as follows:
Step 1
Step 2
Step 3
Step 4
Step 5
The provisioning screen is displayed.
Step 6
Step 7
The Basic panel is displayed.
Step 8
Step 9
Step 10
Begin time slot and End time slot text fields are disabled if you select the Unframed check box and the text fields are enabled if you deselect Unframed check box.
The remaining text fields displayed in the Basic panel are optional.
Step 11
The Feature panel is displayed.
Step 12
Step 13
The Summary panel is displayed.
Step 14
mSEF Internet Specific FAQs
This section addresses frequently asked questions related to mSEF operations:
•
What is SAMI card? What are SAMI processors? What is single IP architecture versus IP address for individual processors? For each architecture, how they are shown in MWTM? How is the Cisco 7600 chassis shown in MWTM?
The Cisco SAMI, is a high-performance Cisco software application module that occupies one slot in the Cisco 7600 series router platform. With a network processor and six PowerPCs (PPCs), the Cisco SAMI offers a parallel architecture for Cisco software applications such as the Cisco Content Services
Gateway - 2nd Generation (CSG2), the Cisco Gateway GPRS Support Node (GGSN), the Cisco Mobile Wireless Home Agent (HA), the Cisco Broadband Wireless Gateway (BWG), and the Cisco IP Transfer Point (ITP).In early releases of the mSEF technologies, each of the six PPCs ran an individual, separately addressable IOS image. As such, in MWTM a single SAMI card appeared as six separate Node objects. In later releases, the individual PPCs are combined into one IOS image and as such a single SAMI card appears as a single Node object. In ITP, the SAMI card serves as a line processor and does not appear as a Node in MWTM. The following table shows the technologies supported by MWTM in which the SAMI is used and how they appear in MWTM.
ITP
Not applicable
CSG2
1
GGSN R8
6
GGSN R9
6
HA R4.0
6
HA R5.0
1
BWG R1
6
BWG R2
6
The 7600 routers that house the mSEF-related SAMI cards are manageable in MWTM; and if they are discovered, they appear in MWTM as a Node object with the MWTM feature type of mSEF. A Cisco 7600 router that houses SAMI cards functioning as an ITP appears in MWTM as a Node object with the MWTM feature type of ITP.
What is a managed node? For network scalability planning, how do I count managed nodes in MWTM versus the number of SAMI cards?
In MWTM a managed Node is defined as a network element that has a unique management IP address and responds to an SNMP poll. In some cases, each processor on a SAMI card responds individually to SNMP requests and has a unique management IP address. (Refer to the prior FAQ section for information on which technologies instantiate multiple IOS images on a SAMI card.) For scalability planning purposes, use the following table to estimate the number of managed nodes:
7600-ITP
1
7600-mSEF
1
SAMI-CSG2
1
SAMI-GGSN R8
6
SAMI-GGSN R9
6
SAMI-HA R4.0
6
SAMI-HA R5.0
1
SAMI-BWG R1
6
SAMI-BWG R2
6
Why does the HA subscriber count show the count by processor and not per SAMI card?
The MWTM Subscriber report attempts to report the number of subscribers per SAMI card. The SAMI card can, in certain instances, host multiple IOS images with separately addressable management IP addresses. Typically, each IOS image on a SAMI card, when polled for a serial number, returns the serial number of the SAMI card. In the case of SAMI cards running HA R4.0, which present six IOS images, a null serial number is returned. MWTM cannot correlate the individual IOS images to a given SAMI card, and, therefore, cannot aggregate the subscriber counts.
When I enable CiscoWorks integration, why do some devices have the options to Launch CiscoView and Device Center, while other screens have the Device Center option only and not CiscoView?
CiscoView is for the chassis level only, and the Launch CiscoView option is available for 7600 chassis supervisor cards. CiscoView is not supported for SAMI cards.
