|
|
The "ViewRunner Maps and Views" chapter presents details of how to create and use ViewRunner for HP OpenView maps and views and how they are used for provisioning and managing the Cisco 6100s. Specifically, this chapter describes:
To better understand and use ViewRunner for HP OpenView maps and views, you should have some basic knowledge of HP OpenView IP mapping. "View Map Integration with HP OpenView" section has some basic information on how ViewRunner is integrated with HP OpenView mapping. For further information, access the HP OpenView online Help system or consult HP OpenView documentation.
As discussed more fully in "ViewRunner for HP OpenView Overview", the primary navigation tool for the Cisco 6100 equipment network is by way of OV maps and views. Moving around in these tools is done by menus and by various mouse actions.
There are three ViewRunner for HP OpenView client applications used to provision, monitor, and manage Cisco 6100s:
| Application | Functional Description |
|---|---|
View Admin | This client is responsible for managing and displaying ViewRunner's user administrative privilege configuration. |
View Map | This client is responsible for logging in a user and displaying the hierarchical view of the Cisco 6100 Network. View Map is started when a user starts OpenView Windows (ovw) for a View Map enabled map. |
View LoopRunner | This client is responsible for displaying the Chassis View of the Cisco 6100. This client also provides windows to configure Cisco 6100 physical resources such as chassis, modules, and ports, and for logical resources such as pools and subscribers. |
View Admin is the client application used for managing and displaying ViewRunner user administrative privileges. For information on user administration, please see the ViewRunner for HP OpenView Installation and Administration Guide.
View Map displays the logical containment hierarchy for Cisco 6100 equipment. It is similar to HP's IP Map application, and makes use of HP OpenView submaps to create the various levels in the hierarchy. The submaps that form the hierarchy are user configurable, and can be geographically based or divided along other lines. Typically, the hierarchy is based on the division of a network along geographical boundaries, which is different from the network-based division found in HP OpenView's IP Map. The location hierarchies are used to partition Cisco 6100s into management domains, such as geographical, functional, or customer.
The first time you invoke the ViewRunner for HP OpenView application, you must create a new View Map. The default HP OpenView map does not support ViewRunner. Therefore, to use ViewRunner, OpenView Maps must be created that have View Map enabled. Existing maps cannot be modified to support View Map.
The steps for creating a new View Map are shown in the following table. Each of these steps is explained in detail with example screen shots in the remainder of this section.
| Description of Steps | Sequence of Events |
|---|---|
From the server workstation, login to ViewRunner for HP OpenView. | Command line for the ksh and sh shells: Command line for the csh shell: Opening screen: |
From the Root window, select Map > Maps > New... from the drop down menu to begin creating a new map. | Map > Maps > New... |
From the New Map window, enter a name for the new map and configure the new map. | Fields moving down the screen: |
From the View Map Configuration window, enable ViewRunner for this map. | In the radio button: |
From OpenView Windows WARNING box, return to the Root window to see new map. | OK |
When you enter ViewRunner for HP OpenView the first time, you access the default Root map. The default view contains only one icon, the IP Internet icon, which represents the standard navigational submap for HP OpenView.
To create a new View Map for ViewRunner to use to manage Cisco 6100s, follow the procedures below. (See Table 2-1 for a quick summary of the steps required to create a new View Map.)
Step 1 Click on the Map menu and select the Maps option from the drop down menu, and then choose New... from the next drop down menu:
When you select the New... option from the Map menu, the New Map dialog appears:
The following table defines the fields on the New Map dialog:
| Field/Button | Description |
|---|---|
Name | Allows you to enter a name for the new map. |
Layout for Root Submap | Displays the selection for the layout of the Root submap. This is the positioning of the various submaps in each view. |
Compound Status | Lists the options for the Compound Status scheme for a map. Note For the highest severity alarm to be propagated to higher level domains, you must select the Propagate Most Critical option under Compound Status. |
Configurable Applications | Lists IP Map and View Map as the configurable applications installed on the OpenView platform. Note You must select True for ViewRunner to be enabled for this map. |
Comments | Enables you to record comments for a map. |
Step 2 Enter the name for the new map.
Step 3 Choose the Row/Column option from the drop down menu in the Layout for Root Submap field. The default is Row/Column, so you can just skip to the next step unless you want to change the layout of the submap view. Click on the Help button at the bottom of the screen for more information on the layout options.
Step 4 Choose the Compound Status for this map by selecting one of the listed options. Your decision of which option to choose is based on how far up the hierarchy you want alarms to be propagated. Choosing Propagate Most Critical is the recommended option.
Step 5 Click on the View Map option in the Configurable Applications field. This activates the Configure For This Map... button.
Step 6 Click on the Configure For This Map... button. The ViewMap Configuration window appears:
Step 7 Select the True option, then press the Verify button and then the OK button. This returns you to the New Map window.
Step 8 Click the OK button. The following warning appears:
Step 9 Click on the OK button to display the new map you created, or Cancel to remain in the current window.
By enabling ViewRunner, the application creates four new icons that display in the Root window, the World View, the New Equipment View, the Subtend Locations View, and the New Subtend Cisco 6100s.
Since this is the first time the ViewRunner server has been started up and a new map created, Cisco 6100s that are currently provisioned but have not been moved to a location within the World submap will be discovered, and their icons will appear in the New Equipment submap at the next IP map polling interval.
To make this new View Map the default map for the user, follow the instructions below:
Step 1 Select Map > Maps > Open/List
Step 2 Choose the new map with the cursor
Step 3 Press Set User Default
The World submap is the top level logical View Map location in a hierarchy. It typically contains a hierarchy of locations based on the division of a network along geographical boundaries. This is different from the network-based division found in HP OpenView's IP Map.
The World submap contains Location submaps and/or Wire Centers. The symbol for the World submap is created automatically by View Map, and therefore, cannot be added manually by the user.
Double clicking on the World submap icon opens to its contents. You can also right click the icon, and choose the Open option from the pop up menu that appears.
The New Equipment Wire Center contains Cisco 6100s that have been discovered by ViewRunner or provisioned within the network, but which have not been assigned to a Wire Center within the World hierarchy.
Cisco 6100s are placed here by ViewRunner system discovery or by manual operations. Once the Cisco 6100 is provisioned in the network, the system will discover it at the next IP polling interval, or a user manually adds the Cisco 6100 using Edit > Add Object menu.
Double clicking on the New Equipment Wire Center icon opens to its contents. You can also right click the icon, and choose the Open option from the pop up menu that appears.
The Subtend Locations submap is the top level logical View Map view of a subtended network. It contains a view of the relationships of Cisco 6100s in a subtended group. This is different from the network-based division found in HP OpenView's IP Map and from the geographical locations of a standard Cisco 6100 network.
The Subtend Locations submap contains a view of subtended Cisco 6100s that have been placed in Subtend Locations submaps. ViewRunner currently does not support mixing Location hierarchies and Subtend Locations hierarchies.
Double clicking on the Subtend Locations submap icon opens to its contents. You can also right click the icon, and choose the Open option from the pop up menu that appears.
The New Subtend Cisco 6100s submap contains a view of the relationships among Cisco 6100s in a subtended network that have been provisioned by the user within the network, but which have not been assigned to a Subtend Location.
Subtend groups are placed in the New Subtend Cisco 6100s submap automatically when a user identifies the head node by selecting it and then selects Assign to New Subtend Group from the Cisco 6100 symbol menu (right click on the Cisco 6100 symbol).
Double clicking on the New Subtend Cisco 6100s Wire Center icon opens to its contents. You can also right click the icon, and choose the Open option from the pop up menu that appears.
Location submaps represent intermediate levels in the logical map hierarchy. They typically contain other Location submaps and/or Wire Centers. The location symbols are added to World and/or Location submaps manually as described in this section. Double clicking on the Location icon opens to its contents.
Once a new View Map has been created and the World submap exists, the Administrator can define the locations and wire centers into which Cisco 6100s are placed to be managed. The steps for adding locations to a World submap are shown in the following table. Each of these steps is explained in detail with example screen shots in the remainder of this section.
| Description of Steps | Sequence of Events |
|---|---|
From the Root window, double click on the World icon. | World |
From the World window, click on the Edit menu to begin adding a new object to the World submap. | Edit > Add Object |
From the top half of the Add Object : Palette window, scroll right/left to display all symbol classes. Select Location to get subclasses. | Location |
From the bottom half of the Add Object : Palette window, scroll right/left to display all symbol subclasses. Drag and drop a subclass symbol to the World submap window. | Choose a subclass based on your particular geographical model of the network. Drag and drop it to the World window using the middle mouse button. |
From the Add Object window, enter a label for the location and accept defaults for the rest. | <Name> (in Label: field) OK |
To add a location to the World submap, follow the procedures below. (See Table 2-3 for a list of the steps required to add a location.)
Step 1 Double click on the World icon in the Root window to open the contents of the World submap. (At this point, there should be no locations present.)
Step 2 From the World window, choose Edit > Add Object as shown below. This opens the Add Object : Palette window.
Step 3 From the Add Object : Palette window, choose the symbol class by clicking on it once as shown below. Scroll right or left to display all the available symbol classes.
Step 4 Choosing a Location symbol displays the symbol subclasses in the lower part of the Add Object : Palette window. From the subclasses, choose Site (or other subclass which most reflects your geographic model of your network.)
Step 5 Using the middle mouse key, drag and drop the Site subclass location to the World window. This opens the Add Object window for defining the Site location.
Step 6 Enter a name for this object in the Label: field, and press OK to accept the defaults for the rest. If you want to know more about the other options on this window, please consult HP OpenView online Help.
Wire Centers represent a specific location at the bottom of the Location hierarchy. They contain Cisco 6100 equipment only and are added to the Location submap manually as described in this section. Double clicking on the Wire Center icon opens to its contents.
Once a Location has been established in the World submap, the Administrator can define the wire centers into which Cisco 6100s are placed to be managed. The steps for adding a Wire Center to a Location submap are shown in the following table. Each of these steps is explained in detail with example screen shots in the remainder of this section.
| Description of Steps | Sequence of Events |
|---|---|
From the World window, double click on the Location icon. | Location |
From the Location window, click on the Edit menu to begin adding a new object to the Location submap. | Edit > Add Object |
From the top half of the Add Object : Palette window, scroll right/left to display all symbol classes. Select the Cisco DSL symbol class to display the subclasses. | Cisco DSL |
From the bottom half of the Add Object : Palette window, drag and drop the Wire Center subclass symbol to the Location submap window. | Drag and drop Wire Center to the Location window. |
From the Add Object window, enter a label for the wire center and accept defaults for the rest. | <Name> (in Label: field) OK |
To add a wire center to the Location submap, follow the procedures below. (See Table 2-4 for a list of the steps required to add a wire center.)
Step 1 Double click on the Location icon in the World window to open the contents of the Location submap. (At this point, there should be no wire centers present.)
Step 2 From the Location window, choose Edit > Add Object as shown in Figure 2-6. This opens the Add Object : Palette window.
Step 3 From the Add Object : Palette window, scroll right to display the Cisco DSL symbol class. Choose the Cisco DSL symbol class by clicking on it once.
Step 4 Choosing the Cisco DSL symbol displays the symbol subclasses in the lower part of the Add Object : Palette window. From the subclasses, choose Wire Center.
Step 5 Using the middle mouse key, drag and drop the Wire Center subclass location to the Location window. This opens the Add Object window for defining the Wire Center.
Step 6 Give the Wire Center a name and press OK to accept defaults on the rest. This adds the Wire Center to the Location submap, as shown in the next figure.
Cisco 6100s are placed in Wire Centers from the New Equipment Wire Center in the Root window for provisioning and management.
Cisco 6100s are moved from the New Equipment Wire Center where they appear first after system discovery to the Wire Center(s) found at specific Locations defined for a particular deployment scheme. (Cisco 6100s can be added to the Wire Center submap manually as described in the next section.)
Double clicking on the Cisco 6100 icon launches the Chassis View of the Cisco 6100. This is the beginning of the service provisioning for this Cisco 6100 as will be explained later in this guide.
Once a Wire Center has been established in the Location submap, the Administrator can move Cisco 6100s to that wire center to be provisioned and managed. The steps for moving a Cisco 6100 to a Wire Center are shown in the following table. Each of these steps is explained in detail with example screen shots in the remainder of this section.
| Description of Steps | Sequence of Events |
|---|---|
From the Root window, double click on the New Equipment icon. | New Equipment |
From the New Equipment window, click on the Edit menu to cut the Cisco 6100 from this submap. | Edit > Cut: From This Submap |
In the Wire Center window, click on the Edit menu to paste the Cisco 6100 to this submap. | Paste |
To move a Cisco 6100 to the Wire Center submap, follow the procedures below. (See Table 2-6 for a list of the steps required to add a Wire Center.)
Step 1 Double click on the New Equipment icon in the Root window to open the contents of the New Equipment submap. (At this point, there should newly discovered Cisco 6100s present.)
Step 2 Open the Edit menu and select Cut: From This Submap to cut the Cisco 6100 from the New Equipment window in preparation for pasting it to the particular Wire Center.
Step 3 Go to the Wire Center window and select Edit > Paste to put the Cisco 6100 into that Wire Center.
Once the Cisco 6100s have been pasted into the Wire Center, all of the parent objects change their background color to match the highest outstanding alarm in the Wire Center. If there are no alarms, all of the icons are green. The map must be set to Propagate Most Critical for this to work as described.
Normally, Cisco 6100s are moved from the New Equipment Wire Center, where they appear first after system discovery, to the Wire Center(s) found at specific Locations defined for a particular deployment scheme. However, a Cisco 6100 can be added to the Wire Center submap manually before the system has time to discover it or as a pre-provisioning method before the Cisco 6100 is deployed.
Once a Wire Center has been established in the Location submap, the Administrator can add Cisco 6100s to that wire center to be provisioned and managed. The steps for adding a Cisco 6100 to a Wire Center manually are shown in the following table. Each of these steps is explained in detail with example screen shots in the remainder of this section
| Description of Steps | Sequence of Events |
|---|---|
From the Root window, navigate to the Location submap and double click on the Wire Center icon into which you want to add a Cisco 6100. | Wire Center |
From the Wire Center window, click on the Edit menu and select Add Object. | Edit > Add Object |
From the top half of the Add Object : Palette window, scroll right/left to display all symbol classes. Select the 6100 DSLAM symbol class to display the subclasses. | 6100 DSLAM |
From the bottom half of the Add Object : Palette window, drag and drop the Cisco 6100 or 6100 LOC subclass symbol to the Wire Center submap window. | Drag and drop Cisco 6100 or Cisco 6100 LOC to the Location window. |
From the Add Object window, enter a label for the Cisco 6100 and then select ViewMap from the Object Attributes field and click on the Set Object Attributes button. If the node is being managed by the inband management channel, put the Ethernet IP address in the IP Address field and the inband management IP address in the Inband IP Address field. Leave the Inband IP Address field blank if the node is not being managed through the inband management channel. | <Name> (Label: field) ViewMap (Object Attributes field) Set Object Attributes |
In the Set Object Attributes window, enter a unique IP address for the Cisco 6100, enter the text to be used as the CLLI code identifier for the Cisco 6100, set the Read Community string to public, and set the Write Community string to private. | IP Address Relay Rack Info CLLI code (defaults to hostname) Read Community - public Write Community - private |
Apply your changes by verifying your entries and pressing OK back to the Wire Center submap. | Verify OK OK |
To add a Cisco 6100 to the Wire Center submap, follow the procedures below. (See Table 2-6 for a list of the steps required to add a wire center.)
Step 1 Navigate from the Root window to the Wire Center submap where you want the new Cisco 6100 to be represented.
Step 2 Click on Edit > Add Object from within the Wire Center submap, and the Add Object window appears.
Step 3 Enter a name in the Label: field for the Cisco 6100 in the Add Object window. Then select ViewMap in the Object Attributes field and click Set Object Attributes.
Step 4 Enter the following in the fields on the Set Object Attributes window:
Step 5 Enter Verify, OK, and then OK to finish adding the Cisco 6100 to the Wire Center.
While the Cisco 6100 is being added, its icon will be displayed with a blue background, indicating that its Operational State is unknown.
When HP OpenView discovers a node, it assigns a selection name to it. If the Cisco 6100's IP address is found in a naming service (/etc/hosts, DNS, or NIS+), OpenView uses the name there for the selection name. If the Cisco 6100 is not in one of the naming services, OpenView uses the IP address for the selection name. The selection name also is used as the label for the symbol.
Then ViewRunner assigns the selection name to the Common Language Location Identifier (CLLI) code attribute and assigns the Cisco 6100's IP address to the 6100 IP address attribute. The user can later change the CLLI code for a Cisco 6100 as explained in the following section.
You can change the CLLI code for the Cisco 6100 through the 6100 Properties > Configuration dialog. If the label is changed using Describe/Modify Symbol, that change will be lost when the map is reopened. The label will revert to the original CLLI code.
To change the CLLI code, use the following procedures.
Step 1 Open the 6100 Properties > Configuration window.
Step 2 Highlight the System Name/CLLI Code entry.
Step 3 Type the new CLLI code.
Step 4 Press OK or Apply.
After changing the CLLI code from the automatically assigned IP address to the new CLLI code, the label on the icon in the Wire Center is updated, and the title line on the 6100 Chassis View is updated to use the new CLLI code.
Changed labels for Cisco 6100s are not updated automatically in its Subtend Group. To update the label, use the following procedures:
Step 1 Select any of the Cisco 6100s in the Subtend Group
Step 2 Select Synchronize This Subtend Group from the OpenView Configuration menu or from the right mouse click on the Cisco 6100.
The labels used in the Subtend Group will be the new ones.
To delete a Cisco 6100, use the Edit > Delete From All Submaps menu option. However, if you use the Delete From This Submap option, it will actually delete the Cisco 6100 from all submaps. Deleting a Cisco 6100 removes all information related to the Cisco 6100 from the database, and it deletes the symbol in IP Map for this Cisco 6100.
If the Cisco 6100 is still in communication with ViewRunner, and IP Discovery is turned on, the next auto-discovery cycle will re-add the Cisco 6100 to the New Equipment window.
To delete a Location, use the Edit > Delete from All Submaps menu option. However, if you use the Delete From This Submap option, it will actually delete the Location from all submaps. When the Location is deleted all child Locations and Wire Center(s) will be deleted as well.
All Cisco 6100s in the Wire Center(s) within the deleted Location will be moved back to the New Equipment window. There is only one instance of a Cisco 6100 symbol that is in existence at a time in View Map (excluding subtend group icons).
View Map supports hierarchies of Locations. Cisco 6100s can be moved anywhere in that hierarchy. Once one has been moved into the hierarchy, you can use HP OpenView's Locate function to find it. You use IP Map (Root menu), not ViewRunner to locate Cisco 6100s in the network. ViewRunner objects will still be available for the Cisco 6100, but the status color for the icon will be an IP Map color (red for lost communications and green for proper communications).
You can use Locate > Objects > By Selection Name or Locate > Objects > By Attribute.
If you locate the Cisco 6100 by attribute, you can locate by:
Locating a Cisco 6100 by attribute will find Cisco 6100s in both Location hierarchies and in subtend network hierarchies. When the Locate by Attribute screen comes up, follow these procedures.
Step 1 Select the attribute on which to search.
Step 2 Select the type of search you want on the string
(a) Pattern matching
(b) Exact match
Step 3 Enter a search string and click on Apply.
The Located and Highlighted field in the window will contain all matches for the search string. If you double click on the submap of the desired match, the Wire Center window containing the
Cisco 6100 will open with the Cisco 6100 highlighted, but not selected. If you single click on the desired submap and click on the Select button, the Wire Center will open with the Cisco 6100 both highlighted and selected.
Subtending is the process of layering Cisco 6100s in a hierarchical tree up to three layers deep (a maximum of seven Cisco 6100s). The subtended Cisco 6100s can be in any Location or Wire Center within the network. ViewRunner will display the relationships between the nodes as you have defined them.
To create a new Subtend Group for View Map follow these procedures:
Step 1 Select the Cisco 6100 that will be the head node (the one that is connected to the ATM network)
Step 2 Select Add to New Subtend Group from the Configuration menu or the right mouse menu.
This creates a new Subtend Group in the New Subtend Cisco 1600s window. The name of the new group includes the IP address of the head node which may differ from the CLLI code. The new Subtend Group will have the head Cisco 6100 in its New Object Holding Area. Its name will be its CLLI code.
Step 3 To add more Cisco 6100s to the Subtend Group, select them and use the menu item Edit > Copy: From this Submap, the Paste them into the new Subtend Group window. If you cut the Cisco 6100s instead of copying them, some unexpected behavior will result.
Once the Cisco 6100s are part of the new Subtend Group, you can establish the relationships among them.
Step 1 Select the Edit > Add Connection option from the menu line and choose your connection type.
Step 2 Then, in the View Map window, choose the source Cisco 6100 and the destination Cisco 6100. The source Cisco 6100 is the one whose NI is being connected to another Cisco 6100's subtend node.
The Add Connection dialog will request a label for the connection. You can enter any text since it will be replaced by ViewRunner anyway.
Step 3 Next, a dialog will open asking you to choose the subtend port to which to connect. The new subtend connection will appear in the top half of the new Subtend Group window.
Alternatively, you can use the following procedures to establish the relationships between subtend nodes.
Step 1 Select the source (child) node
Step 2 Hold down the Ctrl key and select the destination (parent) node
Step 3 Select Configuration > Make Subtend Connection
Choosing the arrow icon on the toolbar takes you to the parent node of the subtended Cisco 6100.
To remove a Cisco 6100 from a Subtend Group, you must first delete its subtend connection, then remove the Cisco 6100 from the group. The procedures for doing this are as follows:
Step 1 Select the connection (the line between the two Cisco 6100s)
Step 2 Select Edit > Delete > From All Submaps. This moves the subtended Cisco 6100's icon back to the holding area.
Step 3 Select the Cisco 6100 in the holding area
Step 4 Select Remove from Subtend Group from the Configuration menu or the right mouse menu.
Configuring subtend hierarchies works the same way as configuring Location hierarchies. However, ViewRunner currently does not support mixing Location hierarchies and Subtend Network hierarchies.
To create a Subtend Location, you use basically the same procedures as if you were creating a Location hierarchy.
When you delete a Subtend Location or one of its parents, it will move all of the subtend groups back to the New Subtend 6100s window. However, deleting a Subtend Group will not delete the Cisco 6100 from the Oracle database. It just removes the Cisco 6100s' subtending information from the database and their MIBs.
Map synchronization is the process of synchronizing the current OpenView database map information with the information from the Oracle database. This process basically verifies that all ViewRunner map symbols stored in the Oracle database are also stored in the OpenView database for use by View Map with the same symbol type/attributes and location within the World or New Equipment window hierarchy.
Since multiple simultaneous users can modify the master Oracle database, map synchronization is needed to have their updates propagate dynamically to all other user's read/write maps. Map synchronization is needed also to assure that all maps are synchronized from one master source.
The user may specify either automatic or manual layout of nodes within a map. Using manual layout, the map synchronization process retains the manual layout of the nodes within a map. In automatic layout, map synchronization deletes the nodes and re-adds them to synchronize with the database.
View Map is integrated into HP OpenView's IP Map polling process, so if fail-safe auto discovery of Cisco 6100 equipment is desired, IP Map must be enabled for the map and IP Polling must be set.
Follow these steps to set the polling interval:
Step 1 Click on the Options menu at the top of the submap or the Location submap to open the drop down menu.
Step 2 Select Network Polling Configuration: IP from the drop down menu to access polling interval options.
Step 3 Change the fixed discovery polling settings as desired for seconds, minutes, or hours. You can also choose to use auto adjust polling by accessing the menu as shown below.
The auto adjust polling is best suited to more stable networks. As the poller executes, if not new nodes are discovered, the polling interval is increased, reducing network traffic. When a node is discovered during a poll, the interval will be decreased until such time as no nodes are discovered.
As might be expected with the fixed polling interval, the interval is set to a fixed timeout.
This window is used to allow the user to provide information related to the ATM switch to which a Cisco 6100 is connected. While this screen is under review, its basic purpose is to let the operator know how the ATM switch is configured as well as the way in which the operator should access that ATM switch' s element management system.
You access the ATM Switch Properties window from the Configuration menu
The first edit box is a free form text area that the operator can use to describe the access point to the ATM network, which is typically an ATM edge switch. The second edit box is another free form text area that the operator can use to either describe the ATM switch's management system, or possibly to provide the command line required to execute the management system and have it provide status and configuration information for the ATM switch.
View LoopRunner is the application that provides a front panel view of a Cisco 6100. It allows you to view the status, manage the configuration, and check the performance of a Cisco 6100.
View LoopRunner is composed of a Chassis View and a number of status and configuration dialogs. The latter are used to display status and manage the configuration of systems, chassis, slots, modules, ports, subscribers, and permanent virtual circuits (PVCs).
The 6100 Chassis View provides the top-level user interface to manage a single Cisco 6100. It provides both menu bar operations and a bitmap front panel view of the Cisco 6100 that displays color-coded status of configured modules. The pictorial bitmap displays the Multiplexer Chassis (MC) with all the ATU-C modules installed in that chassis and each Line Concentration Chassis (LCC) with all the LIMs installed.
Access the Chassis View by:
The Chassis View serves as the top level display in a hierarchy of windows/dialogs which allow the user to view/add/modify/delete the different entities throughout the Cisco 6100. From 6100 Chassis View, a user can view all status information, manage all configurations, and check the performance of the Cisco 6100.
All Cisco 6100 "traps" or error conditions are logged in the Error Events category of the OpenView Events Categories window.
To open a particular Events window, select one of the options in the Event Categories window which should be open on your screen. It open automatically when you start ViewRunner. The Events Categories window allows you to select the types of alarms and events.
In the Event Categories window, colors indicate the various types of alarm acknowledgements. The following describes how colors are used in the Event Categories window:
The following figure shows the Event Browser window for All Events showing only part of the critical alarms having been acknowledged.
See the chapter on "Events and Alarms Management" for more information about alarms. See the Cisco 6100 Series Maintenance and Troubleshooting Guide for details about the types of Cisco 6100 alarms displayed by ViewRunner and their severity.
Posted: Fri Oct 8 12:50:19 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.