Table Of Contents
Mobile Wireless Fault Mediator Release 2.2.1 Graphical User Interface User Guide
What is the MWFM GUI?
Prerequisites
Related Documentation
Before Getting Started
Accessing the MWFM GUI
Using the MWFM Fault Monitor Console
Viewing Network Alerts
Viewing Detailed Information About an Alert
Deleting an Alert
Viewing Network Events
Viewing Detailed Information About an Event
Deleting an Event
Using the MWFM Device Alerts/Events Console
Using the MWFM Administration Console
Configuring MWFM
Configuring Switch Telnet
Adding NMS
Adding Networks or Devices for Discovery
Listing Devices
Using the MWFM HeartBeat Console
Troubleshooting
Viewing CiscoWorks2000-Related Messages
Resolving Error Messages and Conditions
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Mobile Wireless Fault Mediator Release 2.2.1 Graphical User Interface User Guide
The Cisco Mobile Wireless Fault Mediator (MWFM) Release 2.2.1 provides alarm filtering and correlation for the Gateway GPRS Support Node (GGSN) routers or Packet Data Serving Node (PDSN) routers in CDMA2000 networks and their neighboring Catalyst switches. MWFM is an event processing and correlation engine. It uses the topology model of the network to correlate a stream of network events (generated as a result of polling) according to the location of the device in the network and the class of the device on which the event occurred. Based on the correlation process, MWFM can upgrade more severe events to alerts.
This document describes how to use the CiscoWorks2000 desktop MWFM graphical user interface (GUI) to monitor events and alerts processed by the MWFM.
Note 
This document is to be used in conjunction the MWFM documentation listed in the "Related Documentation" section.
This document contains the following information:
• What is the MWFM GUI?
• Prerequisites
• Related Documentation
• Before Getting Started
• Accessing the MWFM GUI
• Using the MWFM Fault Monitor Console
• Using the MWFM Device Alerts/Events Console
• Using the MWFM Administration Console
• Using the MWFM HeartBeat Console
• Troubleshooting
• Obtaining Documentation
• Obtaining Technical Assistance
What is the MWFM GUI?
The MWFM GUI enables you to use the CiscoWorks2000 desktop interface to view information about alerts and events processed by the MWFM server. The CiscoWorks2000 desktop is a GUI that runs in a web browser. For more information about the CiscoWorks2000 desktop, see Getting Started with the CiscoWorks2000 Server.
Prerequisites
In addition to the requirements listed in the Read Me First—Mobile Wireless Fault Mediator Release 2.2.1 document, you need the following:
•To access the MWFM GUI on Solaris 7, you need Netscape 4.76 or later.
•To access the MWFM GUI on Windows 2000 Professional, you need Microsoft Internet Explorer 5.5 or later or Netscape 4.76 or later.
Related Documentation
Use this document in conjunction with the following CiscoWorks2000 for Mobile Wireless and CiscoWorks2000 documents:
•Read Me First—Mobile Wireless Fault Mediator Release 2.2.1
•Release Notes for Mobile Wireless Fault Mediator Release 2.2.1
•Cisco Mobile Wireless Fault Mediator Release 2.2; Fault Engine Reference Guide
•Cisco Mobile Wireless Fault Mediator Release 2.2; Topology and Platform Modeling Reference Guide
•Cisco Mobile Wireless Fault Mediator Release 2.2; Java API Guide
•Getting Started with the CiscoWorks2000 Server
•Installing and Setting Up CD One 5th Edition
•Release Notes for CiscoWorks2000 CD One, 5th Edition
The CiscoWorks2000 for Mobile Wireless documentation library is available online at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2k4mw/index.htm
The CiscoWorks2000 documentation library is online at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/index.htm
Before Getting Started
Before you can access the MWFM GUI, the following tasks must be completed:
| |
Task
|
For Detailed and Custom Installation, Refer To:
|
Step 1
|
Install the CiscoWorks2000 CD One, 5th Edition. This typically takes about 40 minutes.
|
•Installing and Setting Up CD One 5th Edition (for your platform)
•Release Notes for CiscoWorks2000 CD One, 5th Edition (for any last-minute updates)
|
Step 2
|
Install the MWFM 2.2.1 component from the CiscoWorks2000 for Mobile Wireless, Release 1.2 bundle.
|
•Read Me First—Mobile Wireless Fault Mediator Release 2.2.1
|
Step 3
|
Install the Java 2 SDK Standard Edition 1.3.1 on the client machine.
|
•The Sun website at http://java.sun.com/j2se/
|
Step 4
|
Start the MWFM server.
|
•Read Me First—Mobile Wireless Fault Mediator Release 2.2.1
|
Accessing the MWFM GUI
Note For detailed information about using the CiscoWorks2000 desktop, see Getting Started with the CiscoWorks2000 Server.
To access the MWFM GUI, do the following:
Step 1 Access the CiscoWorks2000 desktop by entering the following URL:
http://server-name:1741
where server_name is the name of the CiscoWorks2000 Server and 1741 is the default TCP port.
CD One uses port 1741 for the CiscoWorks2000 server. Make sure that you append :1741 to the end of your server name or IP address when accessing the server through your browser.
In the main CiscoWorks2000 desktop, the Login Manager appears.
Step 2 If you have just installed the CiscoWorks2000 package and are logging in for the first time, enter admin in both the User Name and Password fields of the Login Manager ( Figure 1).
Figure 1 Initial Login
Step 3 Click Connect or press Enter. You are now logged in to the CiscoWorks2000 desktop.
Step 4 To access the MWFM GUI, select the MWFM drawer from the navigation tree. The Fault Console folder is displayed.
Using the MWFM Fault Monitor Console
This section contains the following information about using the MWFM Fault Monitor Console:
• Viewing Network Alerts
• Viewing Detailed Information About an Alert
• Deleting an Alert
• Viewing Network Events
• Viewing Detailed Information About an Event
• Deleting an Event
Viewing Network Alerts
Note For comprehensive information about event generation and correlation and the data processed by MWFM, refer to the Cisco Mobile Wireless Fault Mediator 2.2 - Fault Engineering Reference Guide.
You can view a list of alerts that have been processed by MWFM from the Alerts Console window. An alert is a correlated event that has been deemed significant enough to warrant the attention of a network administrator.
The alerts displayed in the Alerts Console window are color-coded based on their severity, where:
•Red—Critical alert
•Orange—Major alert
•Cyan—Minor alert
•Yellow—Warning alert
•Green—Cleared alert
Note You cannot adjust the colors in which alarms are displayed on the Alerts Console window.
To view a list of alerts via the Alerts Console window, do the following:
Step 1 Select Fault Monitor Console > Network Alerts. The Alerts Console Refresh Interval window is displayed ( Figure 2).
Figure 2 Alerts Console Refresh Interval Window
Step 2 Specify a time interval for display updates (the default is 30 seconds) and click Submit. The Alerts Console window is displayed ( Figure 3).
Figure 3 Alerts Console Window
The Alerts Console window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of alerts in each category of severity.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
Device
|
IP address or host name of the device associated with the alert.
|
Fault Type
|
Type of fault that has occurred.
|
AlarmID
|
Event ID of the alert.
|
Severity
|
Severity of the alert. Possible values are Critical, Major, Minor, Warning, and Cleared.
|
Count
|
Number of identical alerts that have occurred.
|
LastNotify
|
Last time the alert was changed.
|
Step 3 (Optional) To refresh the information displayed on the Alerts Console window before the next automatic refresh, click Refresh Now.
Step 4 (Optional) To view detailed status for the current MWFM processes, click HeartBeat. MWFM displays the HeartBeat console ( Figure 16). See the "Using the MWFM HeartBeat Console" section for more information.
Viewing Detailed Information About an Alert
To view detailed information about an alert, open the Alerts Console window ( Figure 3), then double-click on the line of the alert, or right-click the line and select Details from the popup menu. A popup window containing the details of the alert is displayed ( Figure 4).
Figure 4 Alert Detail Popup
The Alert Detail popup contains information similar to the following. This information might vary depending on the type of alert.
Field
|
Description
|
EventType
|
Type of event. Possible values are EVENT, DATA, or ALERT.
|
CauseType
|
Type of event (root cause or symptom). Possible values are UNKNOWN, SYMPTOM, or ROOT.
|
Dist
|
Distribution engine.
|
AlertType
|
Type of alert.
|
Count
|
Number of identical alerts that have occurred.
|
AlarmID
|
Event ID of the alert.
|
Device
|
IP address or host name of the device associated with the alert.
|
ClassName
|
Name of the associated Active Object Class. Possible values include GGSN, GGSN3.0, PDSN, Catalyst, CiscoNonCatalyst, or HomeAgent.
|
Description
|
Textual description of the event.
|
FaultType
|
Name of the poll definition that created the event.
|
Severity
|
Open Systems Interconnect (OSI) severity code associated with the alert. Possible values are CLEAR, UNKNOWN, WARNING, MINOR, MAJOR, CRITICAL, or NONE.
|
Contact
|
Contact group responsible for the device that generated the event.
|
AssignedTo
|
Person to which the event has been assigned.
|
Acknowledged
|
Whether the event has been formally acknowledged. Possible values are YES (acknowledged) or NO (unacknowledged).
|
Location
|
Location of the device that generated the event.
|
CorrelatedId
|
List of associated events by correlating the event ID.
|
EventGroupId
|
Group to which the alert belongs.
|
ActionGlyph
|
Alert display glyph (icon).
|
CreateTime
|
Time of the first occurrence of the alert.
|
LastNotify
|
Last time the alert was changed.
|
ActionType
|
Type of action the alert represents. Possible values are NEW (a new alert), UPDATE (an updated alert), or DELETE (a deleted alert).
|
InternalAction
|
Internal action associated with the event. Possible values are ACK, UNACK, ASSIGN, TOOL, INTCLEAR, CLEARALL, or CLEARCHAIN. For more information on these fields, see the Cisco Mobile Wireless Fault Mediator 2.2 - Fault Engineering Reference Guide.
|
PollingAgent
|
Polling agent location (for example, the IP address or host name of the polling agent). Polling agents are responsible for retrieving requested information from the network.
|
ExtraInfo
|
List of additional information.
|
Deleting an Alert
Any alert can be deleted by an operator with security privilege of Network Operator (NO) or higher.
To delete an alert, open the Alerts Console window ( Figure 3), then select the line of the alert and click Delete Alert, or right-click the line and select Delete from the popup menu. MWFM asks you to confirm the deletion. When you confirm, the selected alert is deleted from the database and the Alerts screen is refreshed.
Note The deleted alert may reappear with a different Alarm ID if the fault condition (such as a ping fail) still exists in the network. This procedure deletes the alert, but does not correct the fault condition.
Viewing Network Events
Note For comprehensive information about event generation and correlation and the data processed by MWFM, refer to the Cisco Mobile Wireless Fault Mediator 2.2 - Fault Engineering Reference Guide.
You can view a list of events occurring in the network from the Events Console window. The events displayed are primary events generated by MWFM active monitoring and devices present in the network. Active monitoring-related events are typically those events generated by polling agents such as Ping Polling Agent and the Simple Network Management Protocol (SNMP) Polling Agent. Device-generated events are typically SNMP notifications and syslog messages.
These events are gathered by the MWFM server and are correlated with topology information by the event correlation engine. The event correlation engine can then promote these events to alerts, depending on the event correlation methods employed.
The events displayed in the Events Console window are color-coded based on their severity, where:
•Red—Critical event
•Orange—Major event
•Cyan—Minor event
•Yellow—Warning event
•Green—Cleared event
Note You cannot adjust the colors in which events are displayed on the Events Console window.
To view a list of events from the Events Console window, do the following:
Step 1 Select Fault Monitor Console > Network Events. The Events Console Refresh Interval window is displayed ( Figure 5).
Figure 5 Events Console Refresh Interval Window
Step 2 Specify an time interval for display updates (the default is 2 minutes) and click Submit. The Events Console window is displayed ( Figure 6).
Figure 6 Events Console Window
The Events Console window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of events in each category of severity.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
Device
|
IP address or host name of the device associated with the event.
|
Fault Type
|
Type of fault that has occurred.
|
AlarmID
|
Event ID of the event.
|
Severity
|
OSI severity code associated with the event. Possible values are CLEAR, UNKNOWN, WARNING, MINOR, MAJOR, CRITICAL, or NONE.
|
Count
|
Number of identical events that have occurred.
|
LastNotify
|
Last time the event was changed.
|
Step 3 (Optional) To refresh the information displayed on the Events Console window before the next automatic refresh, click Refresh Now.
Step 4 (Optional) To view detailed status for the current MWFM processes, click HeartBeat. MWFM displays the HeartBeat console ( Figure 16). See the "Using the MWFM HeartBeat Console" section for more information.
Viewing Detailed Information About an Event
To view detailed information about an event, open the Events Console window ( Figure 6), then double-click on the line of the event, or right-click the line and select Details from the popup menu. A popup window containing the details of the event is displayed ( Figure 7).
Figure 7 Event Detail Popup
The Event Detail popup contains information similar to the following. This information might vary depending on the type of event.
Field
|
Description
|
AlarmID
|
Event ID of the event.
|
Device
|
IP address or host name of the device associated with the event.
|
ClassName
|
Name of the associated Active Object Class. Possible values include GGSN, GGSN3.0, PDSN, Catalyst, CiscoNonCatalyst, or HomeAgent.
|
Description
|
Textual description of the event.
|
FaultType
|
Name of the poll definition that created the event.
|
EventType
|
Type of event. Possible values are EVENT, DATA, or ALERT.
|
Severity
|
OSI severity code associated with the event. Possible values are CLEAR, UNKNOWN, WARNING, MINOR, MAJOR, CRITICAL, or NONE.
|
Contact
|
Contact group responsible for the device that generated the event.
|
AssignedTo
|
Person to which the event has been assigned.
|
Acknowledged
|
Whether the event has been formally acknowledged. Possible values are YES (acknowledged) or NO (unacknowledged).
|
Location
|
Location of the device that generated the event.
|
CorrelatedId
|
List of associated events by correlating the event ID.
|
EventGroupId
|
Group to which the event belongs.
|
ActionGlyph
|
Event display glyph (icon).
|
CreateTime
|
Time of the first occurrence of the event.
|
LastNotify
|
Last time the event was changed.
|
Count
|
Number of identical events that have occurred.
|
CauseType
|
Type of event (root cause or symptom). Possible values are UNKNOWN, SYMPTOM, or ROOT.
|
ActionType
|
Type of action the event represents. Possible values are NEW (a new event), UPDATE (an updated event), or DELETE (a deleted event).
|
InternalAction
|
Internal action associated with the event. Possible values are ACK, UNACK, ASSIGN, TOOL, INTCLEAR, CLEARALL, or CLEARCHAIN.
|
PollingAgent
|
Polling agent location (for example, the IP address or host name of the polling agent). Polling agents are responsible for retrieving requested information from the network.
|
ExtraInfo
|
List of additional information.
|
Deleting an Event
Any event can be deleted by an operator with security privilege of Network Operator (NO), Network Administrator (NA), or System Administrator (SA).
To delete an event, open the Events Console window ( Figure 6), then select the line of the event and click Delete Alert, or right-click the line and select Delete from the popup menu. MWFM asks you to confirm the deletion. When you confirm, the selected event is deleted from the database and the Events screen is refreshed.
Note The deleted event may reappear with a different Alarm ID if the fault condition (such as a ping fail) still exists in the network. This procedure deletes the event, but does not correct the fault condition.
Using the MWFM Device Alerts/Events Console
To use the Device Alerts/Events console, use the following procedure:
Step 1 Select Device Alerts/Events in the left panel. The Alerts/Events Console for Device window is displayed ( Figure 8).
Figure 8 Alerts/Events Console for Device Window
The Alerts/Events Console for Device window contains the following fields:
Field
|
Description
|
Device
|
Drop-down list box of IP addresses or host names for devices currently monitored by MWFM.
|
Selected Device
|
IP address or host name of the selected device, for which you want to view alerts or events.
|
Refresh Interval (in seconds)
|
Time interval, in seconds, for display updates. The default value is 90 seconds.
|
Step 2 To show alerts for a device, select a device and an appropriate refresh interval, then click Show Alerts. The Alarms Console for Device window ( Figure 9) is displayed.
Figure 9 Alarms Console for Device Window
The Alarms Console for Device window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of alerts for the device in each category of severity.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
Device
|
IP address or host name of the device.
|
Fault Type
|
Type of fault that has occurred.
|
AlarmID
|
Event ID of the alert.
|
Severity
|
Severity of the alert. Possible values are Critical, Major, Minor, Warning, and Cleared.
|
Count
|
Number of identical alerts that have occurred.
|
LastNotify
|
Last time the alert was changed.
|
Step 3 (Optional) To view detailed information about an alert, double-click on the line of the alert, or right-click the line and select Details from the popup menu. A popup window containing the details of the alert is displayed ( Figure 4). See the "Viewing Detailed Information About an Alert" section for more information.
Step 4 (Optional) Any alert can be deleted by an operator with security privilege of Network Operator (NO) or higher.
To delete an alert, select the line of the alert and click Delete, or right-click the line and select Delete from the popup menu. MWFM asks you to confirm the deletion. When you confirm, the selected alert is deleted from the database and the Alerts screen is refreshed.
Note The deleted alert may reappear with a different Alarm ID if the fault condition (such as a ping fail) still exists in the network. This procedure deletes the alert, but does not correct the fault condition.
Step 5 (Optional) To refresh the information displayed on the Alarms Console for Device window before the next automatic refresh, click Refresh Now.
Step 6 (Optional) To view detailed status for the current MWFM processes, click HeartBeat. MWFM displays the HeartBeat console ( Figure 16). See the "Using the MWFM HeartBeat Console" section for more information.
Step 7 To show events for a device, select a device and an appropriate refresh interval, then click Show Events. The Events Console for Device window ( Figure 10) is displayed.
Figure 10 Events Console for Device Window
The Events Console for Device window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of events in each category of severity.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
Device
|
IP address or host name of the device.
|
Fault Type
|
Type of fault that has occurred.
|
AlarmID
|
Event ID of the event.
|
Severity
|
OSI severity code associated with the event. Possible values are CLEAR, UNKNOWN, WARNING, MINOR, MAJOR, CRITICAL, or NONE.
|
Count
|
Number of identical events that have occurred.
|
LastNotify
|
Last time the event was changed.
|
Step 8 (Optional) To view detailed information about an event, double-click on the line of the event, or right-click the line and select Details from the popup menu. A popup window containing the details of the event is displayed ( Figure 7). See the "Viewing Detailed Information About an Event" section for more information.
Step 9 (Optional) Any event can be deleted by an operator with security privilege of Network Operator (NO), Network Administrator (NA), or System Administrator (SA).
To delete an event, select the line of the event and click Delete, or right-click the line and select Delete from the popup menu. MWFM asks you to confirm the deletion. When you confirm, the selected event is deleted from the database and the Events screen is refreshed.
Note The deleted event may reappear with a different Alarm ID if the fault condition (such as a ping fail) still exists in the network. This procedure deletes the event, but does not correct the fault condition.
Step 10 (Optional) To refresh the information displayed on the Events Console for Device window before the next automatic refresh, click Refresh Now.
Step 11 (Optional) To view detailed status for the current MWFM processes, click HeartBeat. MWFM displays the HeartBeat console ( Figure 16). See the "Using the MWFM HeartBeat Console" section for more information.
Using the MWFM Administration Console
The MWFM Administration Console enables you to perform the following tasks:
• Configuring MWFM
• Configuring Switch Telnet
• Adding NMS
• Adding Networks or Devices for Discovery
• Listing Devices
Configuring MWFM
An operator with security privilege of Network Administrator (NA) or System Administrator (SA) can configure general MWFM parameters, such as the MWFM domain name, the IP address of the DNS server, and the location of the syslog file.
To view and change the current configuration, use the following procedure:
Step 1 Click General Setup in the left panel. MWFM displays the Configure FM Server console ( Figure 11).
Figure 11 Configure FM Server Console
The Configure FM Server console contains the following fields:
Field
|
Description
|
Domain Name
|
Domain name associated with this instance of MWFM.
|
DNS Server IP Address
|
IP address of the DNS server.
|
Syslog File Location no. 1
|
First syslog file that MWFM monitors for alarm conditions.
|
Syslog File Location no. 2
|
Second syslog file that MWFM monitors for alarm conditions. If this field is blank, MWFM monitors only the first syslog file.
|
Step 2 To change a field, enter the new name, IP address, or file location, then click Submit. MWFM asks you to confirm the changes. When you confirm, MWFM uses the changed configuration.
If you specify an incorrect name or an invalid IP address, MWFM issues an appropriate error message.
Configuring Switch Telnet
An operator with security privilege of System Administrator (SA) or higher can Telnet to a Catalyst switch that is running Cat OS.
To access a Catalyst switch via Telnet, use the following procedure:
Step 1 Click Switch Telnet Configuration in the left panel. MWFM displays the Switch Telnet Configuration console ( Figure 12).
Figure 12 Switch Telnet Configuration Console
The Switch Telnet Configuration console contains the following fields:
Field
|
Description
|
Device IP Address
|
IP address of the Catalyst switch.
|
Subnet Mask
|
Subnet mask for the Catalyst switch.
|
Username
|
Username, if required by the Catalyst switch.
|
Password
|
Password, if required by the Catalyst switch.
|
Login Prompt
|
Prompt for login, if any (such as Login: or Username:)
|
Password Prompt
|
Prompt for the password, if any (such as Password: or Username:)
|
Console Prompt
|
Prompt for the console, if any (such as catalyst or cat6k)
|
Step 2 To add Telnet information, enter the appropriate information in the fields, then click Submit. MWFM asks you to confirm the changes. When you confirm, MWFM uses the changed configuration.
If you specify an invalid IP address or subnet mask, MWFM issues an appropriate error message.
Adding NMS
An operator with security privilege of Network Administrator (NA) or System Administrator (SA) can add an NMS station as an MWFM trap recipient.
To add an NMS station to MWFM, use the following procedure:
Step 1 Click Add NMS in the left panel. MWFM displays the Trap Recipients console ( Figure 13).
Figure 13 Trap Recipients Console
The Trap Recipients console contains the following fields:
Field
|
Description
|
IP Address
|
IP address of the NMS station to which MWFM traps are to be forwarded.
|
Port Number
|
Port number of the NMS station to which the MWFM traps should be sent.
|
Starting Sequence ID
|
Starting trap sequence ID to be used by MWFM when sending traps to the NMS station.
Note Starting and ending sequence IDs for different NMS stations must not overlap.
|
Ending Sequence ID
|
Ending trap sequence ID, after which MWFM is to roll over the sequence number.
Note Starting and ending sequence IDs for different NMS stations must not overlap.
|
Step 2 To add a new NMS station, enter the appropriate information in the fields, then click Submit. MWFM asks you to confirm the addition. When you confirm, MWFM begins sending traps to the new NMS station.
If you specify an invalid IP address, port number, or sequence ID, MWFM issues an appropriate error message.
Adding Networks or Devices for Discovery
An operator with security privilege of Network Administrator (NA) or System Administrator (SA) can add new networks or devices for MWFM to monitor.
To add a new network or device, use the following procedure:
Step 1 Click Add Device/Subnet in the left panel. MWFM displays the Add Networks/Devices for Discovery console ( Figure 14).
Figure 14 Add Networks/Devices for Discovery Console
The Add Networks/Devices for Discovery console contains the following fields:
Field
|
Description
|
Network IP Address
|
IP address of the network or device to be added.
|
Subnet Mask
|
Subnet mask for the network.
|
Network/Device
|
Radio button that specifies whether you are adding a network or a device. The default setting is Network.
|
SNMP Community Strings
|
Community strings to be used by MWFM to access the devices in the network. Separate multiple SNMP community stings with commas.
|
Step 2 To add a new network or device, enter the appropriate information in the fields, select the correct radio button, then click Submit. MWFM asks you to confirm the addition. When you confirm, MWFM begins monitoring the new network or device.
If you specify an invalid IP address or subnet mask, MWFM issues an appropriate error message.
Listing Devices
To view a list of all devices in the network that are currently monitored by MWFM, along with their interfaces, use the following procedure:
Step 1 Click List Devices in the left panel. MWFM displays the List Devices/Disable Monitoring window ( Figure 15).
Figure 15 List Devices/Disable Monitoring Window
The List Devices/Disable Monitoring window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of devices monitored by MWFM.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
DeviceName
|
IP address or host name of the device.
|
Interface
|
Description of the device/interface.
|
ClassName
|
Name of the active object class associated with the device. Possible values include Catalyst, Cisco7200, CiscoNonCatalyst, GGSN, GGSN30, PDSN, and HomeAgent.
|
IfIndex
|
Index of the device/interface.
|
IpAddress
|
IP address of the device/interface.
|
Mask
|
Subnet mask of the device/interface.
|
RelatedTo
|
List of network elements connected the device/interface.
|
Monitored
|
Status of monitoring of the device by MWFM.
|
Radio Button
|
Device selector for disabling device monitoring or showing alerts or events for a device.
This button is displayed only in the first line for each device.
|
Step 2 (Optional) To disable monitoring for a device, select the device's radio button, then click Disable. MWFM asks you to confirm that you no longer want to monitor the device. When you confirm, MWFM marks the device for disabling and asks you to confirm the restart of some of the MWFM processes. This option is not valid for Main Node.
Step 3 (Optional) To enable monitoring for a device, select the device's radio button, then click Enable. MWFM asks you to confirm that you want to monitor the device. When you confirm, MWFM marks the device for enabling and asks you to confirm the restart of some of the MWFM processes. This option is not valid for Main Node.
Step 4 (Optional) To view all alerts for a device, select the device's radio button, then click Alerts. MWFM displays the Alarms Console for Device window ( Figure 9). See the "Using the MWFM Device Alerts/Events Console" section for more information. This option is not valid for Main Node and the devices that are not monitored.
Step 5 (Optional) To view all events for a device, select the device's radio button, then click Events. MWFM displays the Events Console for Device window ( Figure 10). See the "Using the MWFM Device Alerts/Events Console" section for more information. This option is not valid for Main Node and the devices that are not monitored.
Step 6 (Optional) To view detailed status for the current MWFM processes, click HeartBeat. MWFM displays the HeartBeat console ( Figure 16). See the "Using the MWFM HeartBeat Console" section for more information.
Step 7 (Optional) To refresh the information displayed on the List Devices/Disable Monitoring Console window, click Refresh Now. (The window is not automatically refreshed, except when you delete a device.)
Using the MWFM HeartBeat Console
Each MWFM GUI console window displays a color-coded HeartBeat button, which enables you to view detailed status for the current MWFM processes.
The color of the HeartBeat button indicates the aggregated status of the MWFM processes, where:
•Red—Indicates that more than 40% of the MWFM processes are in Dead, Failed, or Sick states.
•Orange—Indicates that between 20% and 40% of the MWFM processes are in Dead, Failed, or Sick states.
•Green—Indicates that less than 20% of the MWFM processes are in Dead, Failed, or Sick states.
The color of the HeartBeat button is refreshed every 15 seconds, based on the HeartBeat records polled from the backend.
To view detailed status for the current MWFM processes, open one of the console windows, then click HeartBeat. MWFM displays the HeartBeat console ( Figure 16).
Figure 16 HeartBeat Console Window
Each individual line in the HeartBeat Console window is color-coded, where:
•Red—Indicates that the process is in Dead, Failed, or Sick state.
•Orange—Indicates that the process is in WaitHB or WaitPreconds state.
•Green—Indicates that the process is in Alive, ForkService, Idle, or Shutdown state.
The HeartBeat Console window contains the following fields:
Field
|
Description
|
Upper Left Corner of Table
|
Summary of HeartBeat records.
|
Upper Right Corner of Table
|
Last time the window was refreshed.
|
ServiceID
|
Service ID of the service.
|
ServiceName
|
Name of the service.
|
ProcessID
|
Process ID of the service.
|
ServiceState
|
Current state of the service. Possible states are:
•Alive—Process operating normally.
•Dead—Process exits after Sick, HeartBeat missed again.
•Fail—Retry count exceeded.
•ForkService—Forking the process.
•Idle—Initial state.
•Shutdown—Process shutting down and will not be restarted.
•Sick—Unidentified problems with process. The HeartBeat received was greater than twice the average interval.
•WaitHB—Waiting for the first HeartBeat.
•WaitPreconds—Waiting for dependent services to go primary.
|
To sort the table based on the data in a particular column, click the header of the column. To reverse the sort order, click the header a second time.
This data in this window refreshes every 15 seconds.
Troubleshooting
The following sections contain information that might be helpful when troubleshooting error messages or conditions.
Viewing CiscoWorks2000-Related Messages
To view CiscoWorks2000-related messages that do not display on the GUI, do the following:
•Use the Native JVM's Java Console (supplied with your browser) to view Java-related messages that do not display on the GUI. To use the Native JVM's Java Console, you must first enable and open the Java console.
To enable the native JVM console when using Internet Explorer:
–Select Tools > Internet Options > Advanced.
–Click Java Console.
–To open the console select View > Java Console.
To enable the native JVM console when using Netscape:
–Select Preferences > Advanced > Enable Java.
–To open the console select Communicator > Tools > Java Console.
•View the following logfiles:
–/opt/CSCOpx/objects/jrun/jsm-cs2000/logs/stdout.log—Contains messages logged by the server when relevant servlets are evoked from the GUI.
–/var/adm/CSCOpx/log/error.log—Contains error log messages.
Resolving Error Messages and Conditions
The CiscoWorks2000 Desktop Does Not Appear on the Browser
If the CiscoWorks2000 desktop does not appear on the browser, verify that the CiscoWorks2000 Server is running correctly.
To verify the CiscoWorks2000 processes are running correctly, on the server running CiscoWorks2000, do the following:
Step 1 Log in as root.
Step 2 Enter <$NMSROOT>/bin/pdshow (where $NMSROOT is the directory in which CiscoWorks2000 is installed). Note that the command is case-sensitive.
Step 3 Verify the following processes are running:
•WebServer
•JRunProxyServer
Step 4 For any process shown as not running, enter pdexec <process name> at the prompt.
Step 5 Wait 5 minutes for the process(es) to start.
On Solaris:
Step 1 Telnet to the machine.
Step 2 Become root.
Step 3 Start the CiscoWorks2000 server by entering /etc/init.d/dmgtd start (case sensitive).
Step 4 Verify the following processes are running:
•WebServer
•JRunProxyServer
Step 5 For any process shown as not running, enter /opt/CSCOpx/bin/pdexec <process name> at the prompt.
Step 6 Wait 5 minutes for the process(es) to start.
Note If you do not have telnet or console access, open a browser and log in to CiscoWorks2000 Server. From the server desktop, select Server Configuration > Administration > Process Management > Process Status. Scroll to the line item "CollectionMgr." State should show "Running Normally," or "Program Started."
Error Message "No Java 2 SDK Support for Applet" Displays
If the error message "No Java 2 SDK Support for Applet Displays" on the MWFM console, download and install the Java 2 SDK Standard Edition 1.3.1 on the client machine from the Sun website (http://java.sun.com/j2se/) and restart the GUI.
Error Message "Please check if mwfm Server is up and running" Displays
If the error message "Please check if mwfm Server is up and running" displays, verify that the MWFM Server is functioning normally as explained below.
Verifying that the MWFM Server is Functioning Normally
If CiscoWorks2000 is running properly, but yet you are unable to access the MWFM GUI, try the following:
•Verify that the MWFM server is up and running properly by entering ps ef | grep riv and verifying that riv_auth and riv_f_amos display in the process list
•Verify that the username and password provided in the AuthSchema.cfg file located in the MWFM /etc directory uses a root/ciscomwfm combination.
•View the stdout.log file located in /opt/CSCOpx/objects/jrun/jsm-cw2000/logs/ for print statements from the servlets on the server which are being invoked from the GUI.
•View the GUI for a time-out message. Restart the GUI.
If none of the above explains or fixes the condition, the MWFM Server processor load could be high. Server load is initially high due to multiple processes consuming CPU at the same time which can cause occasional timeouts from the rendezvous. This condition is significantly reduced after the MWFM discovery process is completed.
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
http://www.cisco.com
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain 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 to
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you 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 the following URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco services 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 the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; 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 will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following 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). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, 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, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0206R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
