Table Of Contents
Getting Started with Cisco WAN Manager
Performing a Warm Start of CWM
Performing a Cold Start of CWM
Network Topology View Popup Menus
Multiple Peer Group Navigation
Understanding the Security Manager Requirements
Navigating with Security Manager
Security Manager Menu Bar, Buttons, and Access Tabs
Logging and Tracking User Activities
Accessing the Audit Trail Log Files
Displaying the Server and Log File Configuration
Viewing the List of Active CWM Users
Monitoring the CWM Health Status
Configuring the SNMP Community String
Setting Up Nonstandard Community Strings
Accessing Community Strings and FTP Passwords
Listing Node IDs, Names, and IP Addresses
Configuring Device Preferences
Disabling the Automatic Node ID
Navigating with the Configurator
Getting Started with Cisco WAN Manager
This chapter describes how to get started with Cisco WAN Manager (CWM).
Contents of this chapter include:
•
Navigating the Client Desktop
•
•
Initializing CWM
This section provides information about initializing CWM.
The following procedures are described:
•
•
Note
•
Performing a Warm Start of CWM
A warm start of CWM consists of stopping the application, then restarting it. When you perform a warm start of CWM, the application continues to use data in the existing Informix database.
Note
Caution
You can execute a warmstart only if the cold start is completed successfully. To verify if the cold start is completed successfully, complete the following procedure:
Step 1
Step 2
azure% vi ~svplus/log/.DBKR_SYNCHUP_MESSAGEStep 3
If the sync-up complete message is not found, you can execute a cold start again. The cold start complete message is normally printed on the console when the cold start sync-up completes.
Note
To perform a warm start of CWM, complete the following procedure:
Step 1
Step 2
Step 3
Welcome to Cisco Wan Manager Release 12_Aug23.SOL28 Fri Aug 23 012Cisco Wan Manager is being run from the workstation, "azure". by svplusMAIN MENU---------1) Start Core2) Stop Core3) Start DesktopX) ExitCore is runningenter number or x to exit:2You can verify the status of the core. The above example shows that the core is running.
Step 4
Step 5
It should take less than three minutes for all of the processes and messages to end.
Note
Step 6
Performing a Cold Start of CWM
This section describes how to perform a cold start of CWM.
Note
The following coldstart scripts are supported:
•
•
•
You can replace the <opt> parameter with -F to remove all data that includes configuration data, user data, and network data. If no option is selected, network data is removed and nonnetwork data remains intact.
Caution
To perform a cold start of CWM, complete the following steps:
Step 1
Step 2
Step 3
Welcome to Cisco Wan Manager Release 12_Aug23.SOL28 Fri Aug 23 012Cisco Wan Manager is being run from the workstation, "azure". by svplusMAIN MENU---------1) Start Core2) Stop Core3) Start DesktopX) ExitCore is runningenter number or x to exit:2You can verify the status of the core. The above example shows that the core is running.
Step 4
It should take several minutes for all of the processes and messages to end, depending upon the number of nodes in the network.
Step 5
Step 6
Step 7
The following example shows the cold start script without the option -F parameter that removes all network data while preserving the existing user data:
azure% coldstartStep 8
Step 9
Launching CWM Server
Upon launching CWM, the main menu is displayed. The CWM main menu enables you to initiate and terminate the CWM core processes and to access the CWM desktop window. You can also use the main menu to get the name of the current database.
To launch the CWM server, complete the following steps:
Step 1
Step 2
a.
b.
The following example is shown:
login: svplusPassword: Last login: Fri Oct 11 14:27:15 from 171.71.29.94Sun Microsystems Inc. SunOS 5.8 Generic February 2000azure%
Note
•
–
–
tballraker18% updateftpinfoUsage: updateftpinfo <ftp user> [<ftp password>]tballraker18%Step 3
azure% CWMWelcome to Cisco Wan Manager Release 12_Aug23.SOL28 Fri Aug 23 012Cisco Wan Manager is being run from the workstation, "azure". by svplusMAIN MENU---------1) Start Core2) Stop Core3) Start DesktopX) ExitCore is runningenter number or x to exit:If the error message Environment Variable DISPLAY not set is displayed when you attempt to start the main menu and the display is not being xhosted to another workstation, enter the following syntax:
azure% setenv DISPLAY machine_name:0.0
To select any of the CWM main menu options listed in Table 2-1, specify the number and press Return.
You can verify the status of the CWM core.
Note
.
Step 4
Press Return.
Observe the messages that are displayed. Notice the gateway and standalone nodes socketed messages to the IP-LAN addresses.
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 messages are displayed on the workstation screen:
Ilb Error: Synchronous request to <unidentified actor failed by timeout>.
Note
A Link0 down message is displayed and followed by a Link0 up for each gateway node. If communication is established to the gateway node and everything is working correctly, a group of Link1 up messages for all nodes are displayed.
If displayed, you can disregard several ILOG RT-Broker messages, the EMSD dumping message, and any server EMDAEMON not registered messages. These messages are normal.
Note
After you see Link 0, Link 1, and gateway node messages indicating the connections are up, continue to the next step. If there is a problem with a Link connection, you will not see all connections come up.
Note
Step 5
Step 6
Step 7
a.
b.
Figure 2-1 CWM Login Window
Step 8
Figure 2-2 displays the CWM Desktop.
Figure 2-2 CWM Desktop Window
Launching CWM Client
CWM Client is a software component that permits you to access and use the features of a CWM Server workstation from a network connected client system. It is designed to run on either Sun Solaris or a Windows 2000 based client machine under Sun Microsystem's WebStart utility. For more information on the requirements, refer to the instructions in the Cisco WAN Manager Installation Guide for
Solaris 8, Release 12.
Note
CWM supports multiple GUIs.
To install the CWM Client, refer to the instructions in the Cisco WAN Manager Installation Guide for Solaris 8, Release 12. After the installation and if you are launching the CWM Client for the first time, perform the following steps:
Step 1
Step 2
For example, http://cwmhost:1551 or http://cwmhost.company.com:1551.
Note
After launching the CWM Client the second time, WebStart prompts you to create a desktop shortcut.
For subsequent launches, complete the following steps:
Step 1
Note
Step 2
The default username and password is svplus.
Exiting CWM
This section provides information about exiting CWM.
To exit the CWM application, complete the following steps:
Step 1
Step 2
Click OK when prompted to confirm the operation.
Step 3
Step 4
Step 5
Depending upon the number of nodes in the network, it might take several minutes for all the processes and messages to end.
Step 6
Step 7
Navigating the Client Desktop
The following sections are on how to navigate the client desktop:
The client desktop provides a menu bar and a toolbar that correspond to the principal CWM applications. You click on a particular icon to launch the corresponding application you need for network management, monitoring, report generation, and administrative tasks. Figure 2-3 shows the Network Topology Main window.
Figure 2-3 Network Topology Main Window
Menu bar
Toolbar
Status bar
Topology view
View selection tabs
Browse window
Hierarchy view
Overview window
Menus and Toolbar
The configuration, managing, and monitoring options for configuring your switches are available from menus and a toolbar.
Figure 2-4 shows the menu bar and toolbar.
Figure 2-4 Menu Bar and Toolbar
Menu Bar
The menu bar provides a complete list of options for managing your switches. The options and functions are listed in Table 2-2.
Note
Table 2-2 Menu Bar
—
Alt-F
Save
Ctrl-S
Alt-S
Saves the current positions of the nodes, trunks, and group information in all of the views. Also, the current map, view size and view zoom level are all saved to the user.home directory. The files are parsed the next time CWM is launched.
Ctrl-P
Alt-P
Prints the current view of the Network Topology window.
Exit
—
Alt-X
Exits the CWM application and closes the main window.
—
Alt-E
Group
—
—
Creates or deletes a node or group of nodes.
Search
—
—
Searches for a node by using the node name or the node IP address.
—
Alt-V
Layer
—
—
Turns on or turns off the display for the IP Address, Node Name, and Trunk Name.
Zoom
—
—
Provides different levels of zoom functions for resizing the view of the Network Topology window.
Background
—
—
Changes the color or map view of the Network Topology window.
Options
—
—
Displays the CWM Topology Option window.
PNNI Hierarchies
—
—
Displays the following levels of peer groups:
•
•
Refresh
—
—
Refreshes the current Network Topology view.
—
Alt-A
Network
—
—
Displays the following network objects:
•
•
•
•
•
•
•
•
PNNI Network
—
—
Displays the following PNNI network objects:
•
•
Peer Groups
—
—
Displays the following peer groups:
•
•
•
PNNI Node
—
—
Brings up a PNNI Node Information window for operations specific to a selected node.
Trunk
—
—
Provides information about an individual trunk.
Note
Stop Connection Trace
—
—
Stops a connection trace that is currently in progress.
Stop Showing Prefer Route
—
—
Stops the preferred route animation.
—
Alt-P
Connection Manager
—
—
Creates end-to-end connections or PVCs2 . For more information, see "Managing Connections."
Network Browser
—
—
Displays a hierarchical representation of network information in a table format. For more information, see "Monitoring Network Faults."
Service Class Template Manager
—
—
Creates the SCT3 files that are loaded to the nodes, and are associated with the interfaces on cards within these nodes. For more information, see "Configuring Service Class Templates."
Statistics Collection Manager
—
—
Controls and manages the statistics collection. For more information, see "Collecting Statistics."
Security Manager
—
—
Provides user access privileges to perform specific tasks such as viewing topology or establishing and managing connections. For more information, see the "Configuring CWM User Access" section.
CWM Administration
—
—
Monitors users, audit logs, and processes on the CWM Server. The following functions are
•
•
•
For more information, see the "Viewing the List of Active CWM Users" section.
CiscoView
—
—
Supports card, line, and port configuration on the Cisco MGX 8220,
Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8950, Cisco MGX 8850, Cisco IGX 8400 Series, Cisco BPX 8600 Series, and Cisco BPX SES PNNI Controller. For more information, see the "Configuring Device Preferences" section.The following functions are
•
•
•
•
Gateway Monitor
—
—
Provides you with CWM gateway information that includes the role of the CWM workstation as Primary CWM, Secondary CWM, or Tertiary CWM.
For more information, see "Cisco WAN Manager Peer-to-Peer Communication."
—
Alt-T
Config Save and Restore
—
—
Launches the Configuration Save and Restore application. For more information, see "Cisco WAN Manager Operations."
SW/FW Images
—
—
Launches the Image Downloader application. For more information, see "Cisco WAN Manager Operations."
—
Alt-U
Configuration
—
—
Configures the audible alarm.
Acknowledge
—
—
Acknowledges the audible alarm function and configuration.
—
Alt-H
About
—
—
Displays information for the versions of the CWM Server and the CWM Client.
On Icons/Trunks
—
—
Displays information to interpret the icons and symbols that represent the network elements found in the Topology Graph window.
On Color
—
—
Interprets the color of the icons that are displayed in the Topology Graph window.
1 MPG = multiple peer groups
2 PVC = permanent virtual circuit
3 SCT = service class template
Toolbar
The toolbar buttons display the CWM applications, common usage tasks, and access to the layout of the network topology.
You can separate the toolbar from the network topology window or position it vertically instead of horizontally. To separate the toolbar, left-click in the toolbar position handler and drag the toolbar to the desired location. Move the pointer over an icon to display the feature.
Table 2-3 lists the toolbar functions, from left to right on the toolbar.
Table 2-3 Toolbar Buttons
Connection Manager
Creates end-to-end connections or PVCs1 .
Network Browser
Displays a hierarchical representation of network information in a table format.
Service Class Template Manager
Creates the SCT2 files that are loaded to the nodes, and are associated with the interfaces on cards within these nodes.
Statistics Collection Manager
Controls and manages the statistics collection.
Security Manager
Provides user access privileges to perform specific tasks such as viewing topology or establishing and managing connections.
CWM Administration
Monitors the users, audit logs, and processes on the CWM Server.
CiscoView
Supports only card, line, and port configuration. For more information, see Table 2-2.
Save Configuration
Saves the configurational or the selected node.
Prints the Network Topology window.
Zoom In
Zooms into the current submap image.
Zoom Out
Zooms out of the current submap image.
Layout Tree
Displays a tree view of the selected node.
Layout Spring
Displays a spring view of the selected node.
Layout Circular
Displays a circular view of the selected node.
1 PVC = permanent virtual circuit
2 SCT = service class template
Popup Menus
The popup menus are available from the Network Topology window.
Network Topology View Popup Menus
The network topology view popup menus are navigation, network, and background. To display the navigation (see Figure 2-5) nd the network (see Figure 2-6) popup menus, click a specific network cloud, and right-click.
If you click a network from the hierarchy tree, you can also choose the network popup menu options.
For information about view references, see Figure 2-3.
Table 2-4 describes the options and tasks.
Note
Table 2-4 Network Topology View Popup Menus
New Submap
Displays a New Submap window that contains an expanded view of the selected network.
Lock
Locks the selected network in place.
Show Parent Map
Returns to the parent overlay submap.
Show Root Map
Returns to the root overlay submap.
Node Zoomable
Displays the zooming capability of the node when the network topology view is zoomed.
Display Prefer Route
Displays all available SPVC preferred routes for a selected source node. For more information, see the "Displaying SPVC Preferred Route" section.
Display Link Status
Displays the link status of all nodes in the current submap.
Note
VSI Consistency Check
Lists errors and VSI trunk end partition information.
Note
Expand Network in View
Displays the expanded view of the network.
Expand Network in Submap
Displays the expanded view in a submap.
Collapse Network in View
Shows a collapsed view of the selected node in the Network Topology window.
Collapse all Networks
Shows a collapsed view of the entire network.
Display Nodes
Displays all nodes for the selected network.
Display Trunks
Displays all trunks for the selected network.
Set Color
Selects or clears the background color of the current view.
Set Map
Selects and saves topology backgrounds for a directory of maps with a variety of ILV images.
Clear Map
Clears the background map.
1 AR = AutoRoute
Figure 2-5 displays the navigation popup menu.
Figure 2-5 Navigation Submenu Options
Figure 2-6 displays the network submenu options.
Figure 2-6 Network Submenu Options
Figure 2-7 displays the background popup menu. For information about view references, see Figure 2-3.
Figure 2-7 Background Submenu Options
Displaying SPVC Preferred Route
This section describes how to display a SPVC preferred route along with the animation.
For information about how to manage a SPVC preferred route, see "Managing Connections," "Managing a Preferred Route Connection" section.
To display the SPVC preferred route for a selected source node by using network topology, complete the following procedure:
Step 1
For information about view references, see Figure 2-3.
Figure 2-8 Display Preferred Route
Step 2
Step 3
The preferred route path is shown with a colored, animated circle (see Figure 2-9) that matches the color from the selected Route ID column.
Figure 2-9 Preferred Route Animation
Step 4
Step 5
Figure 2-10 Stop Preferred Route Animation
Step 6
Trunk Popup Menu
To display the trunk popup menus, right-click on a trunk.
For information about view references, see Figure 2-3.
Table 2-5 describes the options.
Note
Figure 2-11 shows the trunk popup menu.
Figure 2-11 Trunk Popup Menu
Navigation Popup Menu
To display the navigation popup menu, click a node, and right-click. For information about view references, see Figure 2-3.
Table 2-6 describes the options and tasks. If you click a node from the hierarchy tree, you can also choose the node popup menu options.
Note
Multiple Peer Group Navigation
Network Topology displays a PNNI logical routing topology that consists of MPGs, which support multiple levels of peer groups.
MPG displays
•
•
•
•
•
Lines represent links between peer groups and nodes. The links between peer group leader (PGL) and the parent logical group node (LGN) in the upper peer group are shown in two dotted lines beside the node and peer group.
To monitor the PNNI network, click the PNNI view tab from the Network Topology main window. Figure 2-12 displays the PNNI view. For information about view references, see Figure 2-3.
Figure 2-12 PNNI View Window
The following browse functions are for the PNNI view:
•
•
Understanding MPG LED Colors
Each icon is a different color according to the corresponding status of the logical node representation.
Table 2-7 lists the colors and description for MPG display.
Table 2-7 MPG LED Colors
green
Specifies PNNI status is up.
gray
Specifies that the corresponding physical node is unreachable.
MPG Popup Menus
To display MPG popup menus, right-click on a peer group cloud or a link. Table 2-8 describes the options.
Table 2-8 Multiple Peer Group Popup Menus
Display Node Info
Displays the PNNI Node Information window.
Display Link Info
Displays the PNNI Up Links window.
Peer Group Info
Displays the Peer Group Information window.
Navigation
Expands a peer group by choosing the Inplace Submap.
Expand All Networks
Displays all the networks.
Collapse All Networks
Collapses the network into one cloud.
Peer Groups (right-click away from a peer group or logical node)
Expand All Peer Groups
Displays all the logical nodes in the peer group.
Collapse All Peer Groups
Collapses the peer group into one cloud.
Background (right-click away from a peer group or logical node)
Set Color
For a definition, see Table 2-4.
Set Map
For a definition, see Table 2-4.
Clear Map
For a definition, see Table 2-4.
Displaying Links
To display link information, complete the following procedure:
Step 1
The Display PNNI Up Links window (see Figure 2-13) shows the link information.
Figure 2-13 Display PNNI Up Links Window
Table 2-9 lists the parameter definitions.
Step 2
Displaying PNNI Nodes
To display PNNI nodes, complete the following procedure:
Step 1
The PNNI Node Information window (see Figure 2-14) appears.
Figure 2-14 PNNI Node Information
Table 2-10 lists the parameter definitions.
Table 2-10 PNNI Node Parameters
Node Name
Specifies the name of the PNNI node.
ATM Address
Specifies AESA1 or an ATM address prefix.
PNNI Node ID
Specifies the PNNI node ID of the PNNI node.
Peer Group ID
Specifies the peer group ID for the peer group of the PNNI node.
PGL Priority
Specifies the leadership priority value that the node can advertise for the nodal information group for the given peer group.
The value of 0 is used with nodes that are not capable to be PGL2 or LGN3 .
Peer Group Leader
Specifies whether the peer group is a leader.
Parent Node ID
Specifies the parent node ID of the parent.
Restricted Transit Flag
Specifies whether or not the node is restricted to support SVC4 transit for the node.
Complex Node Flag
Specifies whether or not the node uses the complex node representation.
Branching Restricted
Indicates whether the node supports additional point-to-multipoint branches.
Level
Specifies the PNNI level of the node.
Lowest Level
Specifies if the node acts as a lowest level node or if the node is a logical group node that is active when of the other nodes in the switch becomes a peer group leader.
1 AESA = ATM end system address
2 PGL = peer group leader
3 LGN = logical group node
4 SVC = switched virtual circuit
Step 2
Displaying Peer Groups
To display peer group information, complete the following procedure:
Step 1
Figure 2-15 displays the Peer Group Information window.
Figure 2-15 Peer Group Information Window
Table 2-11 lists the parameters.
Step 2
Configuring CWM User Access
The following tasks are used to configure CWM user access:
•
•
You can configure user access by using the security manager application, which provides controlled access to multiple users of CWM, based on the user's UNIX user ID and password. The security manager application is launched from the CWM Client desktop.
By using security manager, you can
•
•
By default, only the svplus user can start and stop the CWM core processes. The svplus user has sufficient access privileges to launch all CWM applications and administer security manager.
Other users are assigned access privileges that enable them to perform operations within security-controlled applications. Depending on the setting of access privileges by those who administer security management, the operations are limited. Without the proper access privileges, users cannot launch security-controlled applications.
Understanding the Security Manager Requirements
Before you can use security manager, you must:
•
Note
•
To add a user, complete the following steps:
Step 1
Step 2
host% suPassword:Step 3
host% cd /usr/users/svplus/toolsStep 4
host% # ./addnewuser <username>
For example, <username> is the name of the user to add. The username must be 1 to 8 alphanumeric characters.
Step 5
Note
Step 6
Step 7
Launching Security Manager
To launch security manager, choose Apps > Security Manager or click the Security Manager icon from the toolbar.
After the Security Manager application is launched, the New User window is displayed by default as shown in Figure 2-18.
Navigating with Security Manager
This section describes the navigation of security manager.
Security Manager Menu Bar, Buttons, and Access Tabs
The configuration options (see Figure 2-16) for user access are available from the menu bar and access tabs.
Figure 2-16 Security Manager Configuration Options
Security Manager Menu Bar
The menu bar provides a complete list of options for user access. The options and tasks are listed in Table 2-12.
Security Manager Button Options
The buttons and tasks are listed in Table 2-13.
Security Manager Access Tabs
The access tabs (see Table 2-14) display the configuration tasks that you need to configure CWM user access.
Creating New Users
To create a new user, complete the following steps:
Step 1
Figure 2-17 All Users Window
Note
•
Step 2
The username must be 1 to 8 alphanumeric characters.
Figure 2-18 Security Manager Window
Step 3
Note
Step 4
Step 5
Note
Figure 2-19 Create User Confirmation
Step 6
Viewing Users
To view a new user in a list of all users, perform the following the steps:
Step 1
Figure 2-20 View User Window
Step 2
The access privileges for the selected user are listed in the right panel of the window. All applications and access privileges are greyed out. Unchecked boxes indicate the absence of a particular privilege in a specific application.
Modifying Users
To modify a user, perform the following steps:
Step 1
Figure 2-21 Modify User Window
Step 2
(see Figure 2-21).Step 3
Click Save.
Step 4
Deleting Users
To delete a user, perform the following procedure:
Step 1
Step 2
Click Delete.
Step 3
Figure 2-22 Delete User Dialog
Step 4
Creating New Profiles
You can create profiles to allow users to perform specific tasks within CWM. Depending on their access privileges, users are granted access to controlled applications. You can create a security profile to give a user read, create, modify, or delete privileges to one or more of the controlled applications. For example, network browser is a read-only application; whereas, users can be given create and modify privileges for connection manager.
You can set up a profile to grant all privileges to one of the applications and some privileges to another application. A profile can be created for users who require only read access to observe an application but at the same time provide detailed security control.
Table 2-15 defines the access privileges.
To create new profiles, perform the following procedure:
Step 1
Figure 2-23 All Profiles Window
Step 2
(see Figure 2-24) is displayed.Figure 2-24 New Profile Window
Step 3
Note
Step 4
Note
Step 5
Viewing Profiles
To verify that the profile is created or modified, complete the following steps:
Step 1
Figure 2-25 View Profile Window
Step 2
The access privileges are listed in the right pane of the window. All applications and access privileges are grayed out. Unchecked boxes indicate the absence of a particular privilege in a specific applications.
Modifying Profiles
To modify an existing profile, complete the following steps:
Step 1
Figure 2-26 Modify Profile Window
Step 2
Step 3
Note
Step 4
Click OK to confirm the request.
Step 5
Figure 2-27 Users with Profile Window
Step 6
Deleting Profiles
To delete a profile, complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Logging and Tracking User Activities
The following tasks are used to log and track user activities:
•
•
•
For a list of supported applications under the application name parameter, see Table 2-24.
Restricting User Access
CWM Administration manages user security. CWM Administration allows restricted access logins to enable users to perform tasks based on detailed access privileges. The user svplus still exists and should be used by experienced and trusted system administrators.
CWM Administration provides controlled access through the user's UNIX userID and password by customizing user-access profiles. The user access profiles comprise a list of access privileges for users for a specific function (see Table 2-16).
For each action, a user is given privileges to read, create, modify, or delete functions, or a user may have all privileges to manage all or some actions. For definitions of the access privileges, see Table 2-15.
Note
Table 2-16 lists the access privileges required for applications launched from the CWM desktop.
Table 2-17 lists the access privileges required for applications launched from the HP OpenView.
Table 2-18 lists the access privileges required for applications launched from the UNIX prompt.
Table 2-19 lists the access privileges required to perform security-controlled operations within the Connections Manager application.
The CWM Network Topology application is linked to Security Manager which checks a user's access privileges before providing access to the Topology application on the CWM desktop. A user without access privileges will find the Topology icon on the CWM desktop to be grey, inactive, and unable to launch the Topology application. Table 2-20 lists the access privileges.
The CWM Statistics Collection Manager is linked to Security Manager, which checks a user's access privileges before providing access to SCM. A user without access privileges can not launch the SCM application.
Table 2-21 lists the access privileges required to perform security-controlled operations within the SCM application.
Table 2-22 lists the access privileges for all CWM applications. The "X" indicates that read, create, modify, or delete functions are available for the specified application; the All function is used for the purpose of including all access privileges that are available for the specified application.
Table 2-22 CWM Applications and Access Privileges
Connection Manager1
X
X
X
X
X
X
X
X
Network Topology
X
—
X
—
X
X
X
X
Statistics Collection Manager
X
X
X
X
X
X
X
X
Service Class Template Manager
X
X
X
X
X
X
X
X
Image Download
—
X
—
—
X
X
X
X
Node Resync
X
—
—
—
X
X
X
X
Configuration Save and Restore
X
X
X
X
X
X
X
X
CWM Administration
X
—
—
—
X
X
X
X
Network Browser
X
—
—
—
X
X
X
X
Security Manager
X
X
X
X
X
X
X
X
xpvc Preferred Configurator
X
X
X
X
X
X
X
X
CiscoView
X
—
X
—
X
X
X
X
Configurator
X
X
X
X
X
X
X
X
BERT
X
—
X
—
X
X
X
X
CUG
X
X
X
X
X
X
X
X
1 Multiple delete and single delete columns are also shown.
Note
Accessing the Audit Trail Log Files
Audit trail allows CWM to record activities across different modules in a persistent file. Each audit trail record describes an event and are grouped by date. Only root and members of a specific user group have read permission to the audit trail log files through the UNIX shell on the CWM Server. The specific user group is a specific UNIX user group that is either an existing one or a new one. The audit trail log files are also shown through the CWM Administration GUI. If a CWM user has read access to the CWM Administration GUI, the user has read access to the audit trail log files. The name of the group is a configurable parameter. The user is allowed to retrieve the audit trail records.
Note
Displaying the Server and Log File Configuration
The audit trail server is a central CWM back-end server that is used to record audit trail records coming from CWM front-end applications to a central log file. The audit trail server also maintains the audit trail log files.
Audit trail log files have security restrictions for access and can be read only by users within a specified group, and can be modified or deleted only by root. Also, the audit trail is designed as a feature internally to CWM with no external dependencies or interdependencies with any ATM switch that is managed by CWM.
Before CWM is started, you can use the Network Configurator to configure nodes. For more information about using the Network Configurator, see the "Configuring Nodes" section. After CWM is started, you can use all CWM applications, for example, Connection Manager, Network Browser, and so forth. The audit service monitors all user activities.
After CWM is installed, the audit trail server is automatically started to provide audit service at all times.
Note
After you reboot the CWM workstation, complete the following procedure if you want the audit service to run before CWM is started:
Step 1
Step 2
a.
b.
Step 3
tballraker18% cd /usr/users/svplus/scriptstballraker18%Step 4
Step 5
tballraker18% cd /usr/users/svplus/scripts/Installtballraker18%Step 6
Note
Audit trail logging is done per CWM workstation and each CWM workstation performs an independent audit trail log. There is no communication or synchronization between CWM workstations regarding an audit trail.
All audit trail log files are in ASCII format and can be retrieved by any text editor. These files provide records that are logged to a central log file and separated by date, with one log file for each day. The following log file is configured:
•
•
•
•
The configuration file follows the convention used by other CWM configuration files. The configuration file for the audit log is located in the $CWM_HOME/config/AuditLogger.conf directory. From the AuditLogger.conf file, you can set the directory to store the audit log file. The default setting is $CWM_HOME/log/AL.
The following example is from the AuditLogger.conf file:
############################################################################## Configuration settings for CWM audit trail server: AuditLogger.# Descriptions:# OUTPUT - The directory for storing audit trail log files.# DATES - The number of dates to keep audit trail log files.# Obsolete log files are deleted automatically by AuditLogger.# READGROUP - The name of the user group whose member can read the audit trail# log files. Only root and members from this group have read# permission for the audit trail log files.# LISTENERS - The number of listener threads to serve AuditLogger's clients.# Valid range: 5 - 15.# PROCESSORS - The number of processor threads to process client requests.# Valid range: 5 - 25.# DBLEVEL - The level in setting up application logging.# Valid range: 1 - 5. (1 is the most serious).## Notes:# 1. Comment lines start with # as the 1st character.# 2. While modifying, change only the value. Do not alter the parameter names.# 3. The default settings:# OUTPUT: /usr/users/svplus/log/AL# DATES: 45# READGROUP: svplus# LISTENERS: 5# PROCESSORS: 5# DBLEVEL: 5# 4. When reading, LISTENERS and PROCESSORS are confined to the valid range.# 5. When reading, if invalid parameters are read for others, default are used.# 6. Configuration parameters are read only once during AuditLogger start-up.# 7. For modifications to take effect, restart CWM core (cold/warm) is needed.###############################################################################OUTPUT: /usr/users/svplus/log/ALDATES: 45READGROUP: svplusLISTENERS: 5PROCESSORS: 5DBLEVEL: 5If the audit log services terminate, the end user may or may not be notified, which depends on the settings in the AuditLoggerMsg.conf file as shown in the following example:
#################################################################### Configuration settings for notification messages of Audit Trail## SHOWMSG: 0 means not show anything to the end user, 1 means show# something. The default value is 0.## MSGCONTENT: XXXXXXX. The specified message will be shown to the end# user if SHOWMSG is 1.###################################################################SHOWMSG: 1MSGCONTENT: This is a system issue, please contact the administratorViewing the List of Active CWM Users
To view the list of active users along with the hostname and time logged on, choose Apps > CWM Administration. The CWM Administrator GUI window is displayed (see Figure 2-28).
Figure 2-28 CWM Administrator Window
Table 2-23 lists the parameters of the CWM Admin GUI window.
Viewing the Audit Trail Log
By using the audit trail viewer, you can view audit log files for specified days either as a whole file or portions of the file. The audit trail viewer allows you to sort, filter, and search for specific log entries. All read, create, modify, and delete activities are monitored and logged to a file.
To view the audit trail log files, complete the following procedure:
Step 1
(see Figure 2-29).Figure 2-29 Audit Trail Viewer
Step 2
Table 2-24 lists the parameter definitions.
Step 3
Step 4
Monitoring the CWM Health Status
You can monitor the current CWM status such as collecting health-related data, reporting significant events to network operators, and browsing through the historical status. For example, network management interface problems can also impact the functionality of CWM such as connection provisioning. The following types of network management health information are monitored:
•
•
•
Events are grouped into the following categories:
•
•
•
To monitor the CWM health status, complete the following procedure:
Step 1
(see Figure 2-30).Figure 2-30 Health Check
Step 2
Configuring the SNMP Community String
The following tasks are used to configure the SNMP community string:
•
•
•
CWM configures the community strings for SNMP management and supports various multi-service-switching devices.
Caution
The Network Configurator does not require the CWM core to be running; therefore, it is used when the CWM core is up and running or when the CWM core is down.
To configure the SNMP community string, you must change the community strings on the devices through the CLI. Telnet to the switch to configure the community strings at the switches. The community string are configured for the following nodes:
•
•
•
•
•
•
•
•
Table 2-26 describes the various options involved in configuring the SNMP.
Table 2-26 SNMP Configuration Options
Network Configurator
After saving the community strings information, the CWM processes use the new community strings for SNMP accesses. The Primary CWM also sends the configured community strings to other Secondary CWMs through the CWM Gateways.
For more information, see the "Configuring Nodes" section.
Prior to Release 12, CWM supported configurable community strings for Cisco BPX, Cisco IGX, Cisco MGX 8220, Cisco MGX 8850 (PXM1), and Cisco MGX 8850 (PXM45) nodes. The Network Configurator configures the SNMP community strings for all the nodes managed by CWM. If a node is not configured using the Network Configurator, the default SNMP community strings are used.
Note
Since users must configure the community strings on both the devices through CLI, and at the CWM stations through the Configurator, there is a possibility of typing in mismatched community strings. This results in the node with the mismatched community strings either not discovered or unreachable to CWM.
Note
SNMP access security
Enter the nodeinfocfg command on CWM by using a secured shell to change the community strings and passwords.
For more information, see the "Accessing Community Strings and FTP Passwords" section.
CiscoView
Launch a device management platform called CiscoView to enter the read or write community string for a specified device from the Users Preference window (see Figure 2-32).
For more detailed information, see the "Configuring Device Preferences" section. For instructions on launching CiscoView through CWM, see "Managing Devices."
Setting Up Nonstandard Community Strings
The standard community strings are defined as default community strings. If you configure the standard community strings to a different value, the standard community strings are defined as nonstandard community strings.
To set up nonstandard community strings or to change an FTP password, enter the runConfigurator command at the CLI prompt to use the Configurator GUI to change nonstandard community strings or FTP passwords, which are used by CWM applications.
The following community string defaults for CiscoView are displayed in asterisks (*) from the User Preferences window (see Figure 2-32):
DEFAULT_RO_STRING=publicDEFAULT_RW_STRING=privateThese strings are used only when
1.
2.
Note
Accessing Community Strings and FTP Passwords
By using a secured shell (SSH), the nodeinfocfg command sets the SNMP community strings and FTP passwords in CWM. The nodeinfocfg command provides authentication and secure communication on who is entering the command.
Note
All configuration changes for SNMP and FTP are made to the node_info table when CWM is online or offline. If primary CWM is online, all applications interested in the node_info changes are notified and propagated to all secondary CWMs. If CWM is offline, all changes to the node_info table are assigned only to the local database.
Note
Table 2-27 lists the functions of the nodeinfocfg command.
Table 2-28 lists the parameters of the nodeinfocfg command.
The nodeinfocfg command returns 0 for success. If the nodeinfocfg command is not successful, a nonzero value is returned. Table 2-29 lists the exit values and error messages.
Changing Community Strings
To change the SNMP get community strings for selected nodes, complete the following procedure:
Step 1
Step 2
azure% nodeinfocfg snmp -m go [-s <node_ids>]To configure the SNMP get community string for the selected nodes, replace <node_ids> with your chosen node IDs. For parameter definitions, see Table 2-28.
The following example is shown:
tballraker18% nodeinfocfg snmp -m go -s 12-16execute "snmp"svplus@tballraker18's password:Step 3
a.
b.
c.
The following example is shown:
svplus@tballraker18's password:ILOG RT-Broker 2.300, licensed to "CISCO Systems"NewGetString:Re-enter NewGetString:>>>update through topod<<<tballraker18%To change the SNMP set community strings for all nodes, complete the following procedure:
Step 1
Step 2
tballraker18% nodeinfocfg snmp -m soexecute "snmp"svplus@tballraker18's password:tballraker18%For parameter definitions, see Table 2-28.
Step 3
a.
b.
c.
The following example is shown:
svplus@tballraker18's password:ILOG RT-Broker 2.300, licensed to "CISCO Systems"NewSetString:Re-enter NewSetString:>>>update through topod<<<tballraker18%To change SNMP set community string for all nodes remotely by using SSH, complete the following procedure:
Step 1
Step 2
The following example is shown:
tballraker18% ssh -t tballraker18 nodeinfocfg snmp -m so
Note
For parameter definitions, see Table 2-28.
Step 3
a.
b.
c.
The following example is shown:
svplus@tballraker18's password:ILOG RT-Broker 2.300, licensed to "CISCO Systems"NewSetString:Re-enter NewSetString:NewSetString:Re-enter NewSetString:>>>update through topod<<<tballraker18%
Changing the FTP Passwords
To change the FTP password for the current FTP user for all nodes, complete the following procedure:
Step 1
Step 2
tballraker18% nodeinfocfg ftpexecute "ftp"svplus@tballraker18's password:For parameter definitions, see Table 2-28.
Step 3
a.
b.
c.
The following example is shown:
ILOG RT-Broker 2.300, licensed to "CISCO Systems"NewFtpPassword:Re-enter NewFtpPassword:>>>On-line mode: update through topod<<<tballraker18%To change both the FTP username and password for all nodes, complete the following procedure:
Step 1
Step 2
azure% nodeinfocfg ftp -u ftpuserFor parameter definitions, see Table 2-28.
Step 3
a.
b.
c.
The following example is shown:
ILOG RT-Broker 2.300, licensed to "CISCO Systems"NewFtpPassword:Re-enter NewFtpPassword:>>>On-line mode: update through topod<<<tballraker18%
Listing Node IDs, Names, and IP Addresses
This section describes how to list node IDs, names, and IP addresses.
To list the node name, complete the following procedure:
Step 1
Step 2
mgx885013 is the node name that is used in the following example:
azure% nodeinfocfg list mgx885013ID NAME IP_ADDRESS== ==== ==========1 mgx885013 172.29.23.116azure%To list the node with the applicable IP address, complete the following procedure:
Step 1
Step 2
The following example lists the IP address 172.29.23.117:
azure% nodeinfocfg list 172.29.23.117ID NAME IP_ADDRESS== ==== ==========2 nmsbpx12 172.29.23.117azure%To list the node ID for all the nodes in the node_info table, complete the following procedure:
Step 1
Step 2
azure% nodeinfocfg listID NAME IP_ADDRESS== ==== ==========0 105p2cw3 172.29.162.1071 105p2cw4 172.29.162.1082 105p1cw1 172.29.162.1003 105p1cw3 172.29.161.1044 105p2cw2 172.29.162.1035 105jup5 172.29.162.119azure%
Configuring Device Preferences
To provide fault and configuration management for all the devices, use CiscoView by choosing
Apps > CiscoView. After you choose a device, the front view of the device is displayed
(see Figure 2-31).Before you can manage your connections, set up you device configurations such as the polling frequency or the number of retries from the SNMP in the User Preferences window.
For information on the LED colors, see Table 5-15 of "Monitoring Network Faults."
Figure 2-31 CiscoView—Front View of Device
Table 2-30 lists the options and tasks for the device preferences.
To configure the device preferences, perform the following procedure:
Step 1
The User Preferences window (see Figure 2-32) shows SNMP and Community tabs.
Figure 2-32 User Preferences Window
Step 2
The default value varies by device.
A typical value is every 60 sec. To disable polling frequency, set the value to zero. If you set the polling frequency below 60 sec for a number of devices, it may slow down your network. It is advisable to use low polling frequencies in specific testing situations and increase them when you have finished testing. Do not poll faster than every 5 sec.
Step 3
A timeout indicates the amount of time it takes to reach a device. If it takes longer than the time specified, the device is considered to be either unreachable or down. The interval value is specified in seconds. The default is 3 sec.
As a guideline, the timeout value should be set to twice the average end-to-end delay in your network. If you have a network with several slow links, you may need to set the timeout to a higher value. If you have only LAN links in your network, a value of 20 sec is reasonable to account for processing delays and timer accuracy. In high traffic situations, you may experience timeouts. You should not reduce the polling frequency because this may cause a general error. Increase the timeout interval if you consistently experience timeouts.
Step 4
The retries value indicates how many times CiscoView retries an unresponsive device. In busy networks, SNMP datagrams can be discarded. The retries value allows the application to continue operation during network problems. A setting of 1 is considered a reasonable value.
Warning
Step 5
You can enter the write community string for a device after you display the device. For example, if you did not specify the write community string when you first opened the device display, you can make changes to a device or a port setting. You can enter the write community string in the Write Community field without exiting and reopening the window.
Step 6
The Alias option displays text labels, which is the default. MIB textual labels are user-friendly aliases of the MIB descriptor. The Descriptor option displays actual variable names (MIB descriptors) used to manage devices, for example, locIfOutBitsSec, is output bits per second.
Step 7
Configuring Nodes
To configure nodes, you must use the Network Configurator application. By using the Network Configurator, Java-based application of CWM, you can:
•
•
Disabling the Automatic Node ID
If you are using the Configurator for the first time, you must edit the Topod.conf file located in the /usr/users/svplus/config directory to disable automatic unique node ID generation.
To disable the automatic unique node ID generation, complete the following procedure:
Step 1
Step 2
azure% cd /usr/users/svplus/configStep 3
Step 4
azure% vi Topod.conf# Set the Debug LevelDebug Level 2#Auto Node Id Generation FlagAutoNodeId TRUE# No of Children to be started by topodChildren linktopoc filetopoc ILMITopoc# No of networks managed per svmainNetworkNumber 1# No of Core ClientsCore emsd rtm eventdStep 5
The following example is shown:
# Set the Debug LevelDebug Level 2#Auto Node Id Generation FlagAutoNodeId false# No of Children to be started by topodChildren linktopoc filetopoc ILMITopoc# No of networks managed per svmainNetworkNumber 1# No of Core ClientsCore emsd rtm eventd
Starting the Configurator
To start the Configurator, complete the following procedure:
Step 1
Step 2
azure% runConfigurator <machine name> <login> <password>Replace <machine name> with the applicable machine. Replace <login> with the username. The default is svplus. Replace <password> with the applicable password. The default is svplus.
The Network Configurator main window (see Figure 2-33) appears that allows you to add, delete, and modify nodes.
Figure 2-33 Network Configurator Main Window
Navigating with the Configurator
This section describes the navigation of the Configurator.
Configurator Menu Bar
The configuration options for user access are available from the menu bar. Table 2-31 provides a complete list of options.
Adding Nodes
To add a new node, complete the following steps:
Step 1
Step 2
Click Ok.
Figure 2-34 Node Dialog—Community Strings
Step 3
Click Ok.
Figure 2-35 Node Dialog—Device Information
The Network Configurator validates the new node by ensuring its IP address and unique node name. The node is displayed in the Network Configurator main window if the node information is valid.
Close the Node Dialog window.
Step 4
Note
Deleting Nodes
To delete a node, complete the following steps:
Step 1
Step 2
If the node is successfully deleted, it disappears from the Network Configurator main window.
Note
Modifying Nodes
To modify a node, complete the following steps:
Step 1
Step 2
Note
Click Ok.
Step 3
Note
•
Starting HP OpenView
To start the HP OpenView application, complete the following steps:
Step 1
Step 2
Step 3
azure% # ovw &Several windows are displayed including warnings, Event Categories, and status updates. Eventually the Root window is displayed.
Note
From the pull-down menus, you can launch all of the CWM features. Many menu items are disabled until an appropriate element is selected, such as a node in the topology.
The IP map contains the HPOV view of the attached IP network. The CWM map contains the CWM nodes, which are displayed directly from CWM.
Use the buttons in the Event Manager window to view desired event categories.
