|
|
This chapter details how to create and use ViewRunner for HP OpenView maps and views and how they are used to provision and manage the Cisco 6100 Series systems.
This chapter contains the following sections:
To better understand and use ViewRunner for HP OpenView maps and views, you should have some basic knowledge of HP OpenView IP mapping. See the "Integrating ViewMap with HP OpenView" section for 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.
The primary navigation tool for the Cisco 6100 Series equipment network is OpenView maps and views. (For a more complete discussion, see "Integrating ViewMap with HP OpenView.") Moving around in these tools is done using menus and various mouse actions.
Table 2-1 describes the three ViewRunner for HP OpenView client applications that are used to provision, monitor, and manage Cisco 6100 Series systems.
| Application | Functional Description |
|---|---|
View Admin | This client is responsible for managing and displaying ViewRunner's user administrative privilege configuration. |
ViewMap | This client is responsible for logging in a user and displaying the hierarchical view of the Cisco 6100 Series network. ViewMap is started when a user starts OpenView Windows (ovw) for a ViewMap-enabled map. |
View LoopRunner | This client is responsible for displaying the 6100 Chassis View of the Cisco 6100 Series system and performance and fault monitoring. This client also provides dialog boxes to configure Cisco 6100 Series physical resources such as chassis, modules, and ports, and for logical resources such as pools and subscribers. |
View Admin is the client application that is 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.
The first time you invoke the ViewRunner for HP OpenView application, you must create a new ViewMap. The default HP OpenView map does not support ViewRunner. Therefore, to use ViewRunner, you must create OpenView maps that have ViewMap enabled. Existing maps cannot be modified to support ViewMap.
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.
Follow these procedures to create a new ViewMap so that ViewRunner can manage Cisco 6100 Series systems:
Step 2 Enter the name for the new map.
In the Layout for Root Submap field, the default is Row/Column, so no action is required unless you want to change the layout of the submap view. Click Help at the bottom of the window for more information on the layout options.
Step 3 Under Compound Status, select one of the listed options. Decide which option to choose based on how far up the hierarchy you want alarms to be propagated. Choosing Propagate Most Critical, as shown in Figure 2-2, is the recommended option.
Step 4 Click the ViewMap option in the Configurable Applications field, as shown in Figure 2-2. This activates the Configure For This Map button.
 |
Note To get more information about any one of the options on the New Map window, go to the HP OpenView online Help system. |
Table 2-2 defines the fields in the New Map window.
| Field | 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.
| ||
Configurable Applications | Lists IP Map and ViewMap as the configurable applications installed on the OpenView platform.
| ||
Comments | Enables you to record comments for a map. |
Step 5 Click Configure For This Map. The ViewMap Configuration dialog box shown in Figure 2-3 appears.
Step 6 Select True, then click Verify and OK. This returns you to the New Map window.
Step 7 Click OK. The warning shown in Figure 2-4 appears.
Step 8 Click OK to display the new map you created, or Cancel to remain in the current window.
By enabling ViewRunner, the application creates the following four new icons that display in the Root window, as shown in Figure 2-5:
This is the first time the ViewRunner server has been started up, and a new map has been created. Therefore, Cisco 6100 Series systems that are currently provisioned but have not been moved to a location within the World submap are discovered, and their icons appear in the New Equipment submap at the next IP map polling interval.
To make this new ViewMap your default map, follow these steps:
Step 2 Click on the name of the new map you just created to select it.
Step 3 Click Set User Default
The World submap is the top-level logical ViewMap 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 or Wire Centers. The symbol for the World submap is created automatically by ViewMap, and therefore, cannot be added manually by you.
To open the World submap contents, double-click on the World submap icon. You can also right-click the icon, and choose Open from the menu that appears.
The New Equipment wire center contains Cisco 6100 Series systems that have been discovered by ViewRunner or provisioned within the network, but that have not been assigned to a wire center within the World hierarchy.
Cisco 6100 Series systems are placed here by ViewRunner system discovery or by manual operations. Once the Cisco 6100 Series is provisioned in the network, the system discovers it at the next IP polling interval, or you can manually add the Cisco 6100 Series using the Edit > Add Object menu.
To open the New Equipment wire center contents, double-click on the New Equipment wire center icon. You can also right-click the icon, and choose Open from the menu that appears.
The Subtend Locations submap is the top-level logical ViewMap view of a subtended network. It contains a view of the relationships of Cisco 6100 Series systems 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 Series network.
The Subtend Locations submap contains a view of subtended Cisco 6100 Series systems that have been placed in Subtend Locations submaps. ViewRunner currently does not support mixing Location hierarchies and Subtend Locations hierarchies.
To open the Subtend Locations submap contents, double-click on the Subtend Locations submap icon. You can also right-click the icon, and choose Open from the menu that appears.
The New Subtend Cisco 6100s submap contains a view of the relationships among Cisco 6100 Series systems in a subtended network. Both have been provisioned by a user within the network but 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. This is identified by selecting it and then selecting Assign to New Subtend Group from the Cisco 6100 Series symbol menu (right-click the Cisco 6100 Series symbol).
To open the New Subtend Cisco 6100s wire center contents, double-click on the New Subtend Cisco 6100s wire center icon. You can also right-click the icon, and choose Open from the menu that appears.
Map synchronization is the process of synchronizing the current OpenView database map information with the information from the Oracle database. This process verifies that all ViewRunner map symbols that are stored in the Oracle database are also stored in the OpenView database. This way, the symbols can be used by ViewMap with the same symbol type or attributes and the same location within the World or New Equipment window hierarchy.
Because multiple simultaneous users can modify the master Oracle database, map synchronization is needed to have the updates propagate dynamically to all other users' read or write maps. Map synchronization is also needed to ensure that all maps are synchronized from one master source.
You can 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.
Location submaps represent intermediate levels in the logical map hierarchy. They typically contain other Location submaps or Wire Centers. The location symbols are added to World or Location submaps manually as described in this section. To open the Location submap contents, double-click on the Location icon.
Once a new ViewMap has been created and the World submap exists, the Administrator can define the locations and wire centers into which Cisco 6100 Series systems are placed to be managed. The steps for adding locations to a World submap follow. Each step is explained in detail with example figures.
|
Note Throughout this process, access HP OpenView online Help to get more information about the symbol classes or subclasses. ViewRunner uses Location as the class for the hierarchy of the World submap. |
To add a location to the World submap, follow these steps.
Step 2 From the World 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, choose the symbol class by clicking on it once. Scroll right or left to display all of the available symbol classes.
Step 4 Choose the Location symbol to display the symbol subclasses in the lower part of the Add Object : Palette window as shown in Figure 2-7. From the subclasses, choose Site (or other subclass that most reflects the geographic model of your network.)
Step 5 Using the middle mouse button, drag and drop the Site subclass location to the World window. This opens the Add Object window, as shown in Figure 2-8, for defining the Site location.
Step 6 Enter a name for this object in the Label: field, and click 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 Series equipment only and are added to the Location submap manually as described in this section. To open the Wire Center contents, double-click on the Wire Center icon.
|
Note The New Equipment wire center behaves like all other wire centers except for the following: ---Symbol is created automatically by ViewMap. ---Symbol cannot be deleted. ---Cisco 6100 Series systems discovered by ViewRunner are put there prior to their being associated with a specific Wire Center down the hierarchy. |
Once a Location has been established in the World submap, the Administrator can define the wire centers into which Cisco 6100 Series systems are placed to be managed. The steps for adding a Wire Center to a Location submap follow. Each step is explained in detail with example figures.
|
Note Throughout this process, access HP OpenView online Help to get more information about the symbol classes or subclasses. ViewRunner uses Cisco DSL as the class to display the Wire Center subclass symbol. |
To add a wire center to the Location submap, follow these steps:
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 Choose the Cisco DSL symbol to display 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 button, 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 click OK to accept defaults on the rest. This adds the Wire Center to the Location submap, as shown in Figure 2-11.
Cisco 6100 Series systems are placed in Wire Centers from the New Equipment wire center in the Root window for provisioning and management.
Cisco 6100 Series systems are moved from the New Equipment wire center, where they appear after system discovery, to the wire center(s) found at specific locations that are defined for a particular deployment scheme. (Cisco 6100 Series systems can be added to the Wire Center submap manually as described in the next section.)
Double-clicking the Cisco 6100 Series system icon launches the 6100 Chassis View of the Cisco 6100 Series system. This is the beginning of the service provisioning for this Cisco 6100 Series system, which is explained in the ViewRunner for HP OpenView Digital Off-Hook Provisioning Guide and the ViewRunner for HP OpenView Direct Connect Provisioning Guide.
Once a Wire Center has been established in the Location submap, the Administrator can move Cisco 6100 Series systems to that wire center to be provisioned and managed. In addition, the Administrator can move Cisco 6100 Series systems between other wire centers. The steps for moving a Cisco 6100 Series system to a Wire Center follow. Each step is explained in detail with example figures.
To move a Cisco 6100 Series system to the Wire Center submap, follow these steps.
Step 2 From the Edit menu, select Cut: From This Submap as shown in Figure 2-12, to cut the Cisco 6100 Series system from the New Equipment window in preparation for pasting it to a particular Wire Center.
Step 3 Go to the Wire Center window and select Edit > Paste to put the Cisco 6100 Series system into that Wire Center, as shown in Figure 2-13.
Once all of the Cisco 6100 Series systems 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.
|
Note Copying and pasting a Cisco 6100 Series system to move it to a Wire Center has the same effect as cutting and pasting it. A Cisco 6100 Series system can be present in only one Wire Center, including the New Equipment window. When a copied Cisco 6100 Series system is pasted into a new Wire Center, the original Cisco 6100 Series symbol is removed from the submap from which it was copied. |
Normally, Cisco 6100 Series systems are moved from the New Equipment wire center, where they appear after system discovery, to the wire center(s) found at specific locations that are defined for a particular deployment scheme. However, a Cisco 6100 Series system can be manually added to the Wire Center submap before the system has time to discover it or as a preprovisioning method before the Cisco 6100 Series system is deployed.
Once a Wire Center has been established in the Location submap, the Administrator can add Cisco 6100 Series systems to that wire center to be provisioned and managed. The steps for manually adding a Cisco 6100 Series system to a Wire Center follow. Each step is explained in detail with example figures.
To add a Cisco 6100 Series system to the Wire Center submap, follow these steps:
Step 2 From the Wire Center window, select Edit > Add Object. The Add Object window appears.
Step 3 From the top half of the Add Object : Palette window, scroll right or left to display all symbol classes. Select the 6100 DSLAM symbol class to display the subclasses.
Step 4 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.
Step 5 From the Add Object window, enter a label for the Cisco 6100 Series system and then select ViewMap from the Object Attributes field and click Set Object Attributes.
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.
Step 6 As shown in Figure 2-14, enter the following in the fields on the Set Object Attributes dialog box:
Step 7 Apply your changes by verifying your entries and clicking OK to return to the Wire Center submap.
Step 8 Click Verify and OK and then click OK again to finish adding the Cisco 6100 Series system to the Wire Center.
While the Cisco 6100 Series system is being added, its icon displays 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 IP address for the Cisco 6100 Series system is found in a naming service (/etc/hosts, DNS, or NIS+), OpenView uses the name there for the selection name. If the Cisco 6100 Series system 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.
Next, ViewRunner assigns the selection name to the CLLI Code attribute and assigns the IP address for the Cisco 6100 Series system to the 6100 IP address attribute. You can later change the CLLI Code for a Cisco 6100 Series system as explained in the following section.
|
Note The selection name continues to be used as the source in the Error Events Browser. |
You can change the CLLI Code for the Cisco 6100 Series system through the 6100 Properties dialog box Configuration tab. If the label is changed using Describe/Modify Symbol, that change is lost when the map is reopened. The label reverts to the original CLLI Code.
To change the CLLI Code, follow these steps:
Step 2 Highlight the System Name/CLLI Code entry.
Step 3 Type the new CLLI Code.
Step 4 Click 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 Chassis View dialog box is updated to use the new CLLI Code.
Changed labels for Cisco 6100 Series systems are not updated automatically in its subtend group. To update the label, use the following steps:
Step 2 Select Synchronize This Subtend Group from the OpenView Configuration menu or, right-click the mouse on the Cisco 6100 Series system and choose Synchronize This Subtend Group.
The labels used in the subtend group are the new ones.
From a Wire Center, to delete a Cisco 6100 Series system, select Edit > Delete From All Submaps. However, if you use the Delete From This Submap option, it actually deletes the Cisco 6100 Series system from all submaps. Deleting a Cisco 6100 Series system removes all information related to the Cisco 6100 Series system from the database, and it deletes the symbol in IP Map for this Cisco 6100 Series system.
If the Cisco 6100 Series system is still in communication with ViewRunner and IP Discovery is turned on, the next autodiscovery cycle re-adds the Cisco 6100 Series system to the New Equipment window.
|
Note ViewRunner does not currently support the Unmanaged State for Cisco 6100 Series systems. |
To delete a Location, select Edit > Delete from All Submaps. However, if you use the Delete From This Submap option, it actually deletes the Location from all submaps. When the Location is deleted, all child Locations and Wire Center(s) are deleted as well.
All Cisco 6100 Series systems in the Wire Center(s) within the deleted Location are moved back to the New Equipment window. There is only one instance of a Cisco 6100 Series system symbol that is in existence at a time in ViewMap (excluding subtend group icons).
ViewMap supports hierarchies for Locations. Cisco 6100 Series systems 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. To locate Cisco 6100 Series systems in the network, you use IP Map in the Root menu, not ViewRunner. ViewRunner objects are still available for the Cisco 6100 Series system, but the status color for the icon is an IP Map color (red for lost communications and green for proper communications).
There are two menu options that you can use to locate a Cisco 6100 Series system in the network. You can use Locate > Objects > By Selection Name, or you can use Locate > Objects > By Attribute, as shown in Figure 2-16.
If you locate the Cisco 6100 Series system by attribute, you can locate by
Locating a Cisco 6100 Series system by attribute, as shown in Figure 2-17, finds Cisco 6100 Series systems in both Location hierarchies and in subtend network hierarchies. When the Locate by Attribute window appears, follow these steps:
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 Apply.
The Located and Highlighted field in the window contains 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 Series system opens with the Cisco 6100 Series system highlighted, but not selected. If you click on the desired submap and click Select, the Wire Center window opens with the Cisco 6100 Series system both highlighted and selected.
Subtending is the process of layering Cisco 6100 Series systems in a hierarchical tree up to three layers deep (a maximum of seven Cisco 6100 Series systems). The subtended Cisco 6100 Series systems can be in any Location or Wire Center within the network. ViewRunner displays the relationships between the nodes as you have defined them.
To create a new Subtend Group for ViewMap, follow these steps:
Step 2 Select Add to New Subtend Group from the Configuration menu, as shown in Figure 2-18, or click the right mouse button.
This creates a new Subtend Group in the New Subtend Cisco 6100s window. The name of the new group includes the IP address of the head node, which can differ from the CLLI Code. The new Subtend Group has the head Cisco 6100 Series system in its New Object Holding Area, as shown in Figure 2-19. Its name is its CLLI Code.
Step 3 To add more Cisco 6100 Series systems to the Subtend Group, select them and use the Edit > Copy From this Submap menu and paste them into the new Subtend Group window. If you cut the Cisco 6100 Series systems instead of copying them, some unexpected behavior results.
Once the Cisco 6100 Series systems are part of the new Subtend Group, you can establish the relationships among them.
Step 2 Then, in the Subtend Group window, choose the source Cisco 6100 Series system and the destination Cisco 6100 Series system. The source Cisco 6100 Series system is the one whose network interface is being connected to the subtend node of another Cisco 6100 Series system.
The Add Connection window requests a label for the connection. You can enter any text you choose because ViewRunner replaces it.
Step 3 Next, a window opens asking you to choose the subtend port to which you want to connect. The new subtend connection appears in the top half of the new Subtend Group window, as shown in Figure 2-21.
You can also use the alternate method in the following steps to establish the relationships between subtend nodes:
Step 2 Press and 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 Series system.
To remove a Cisco 6100 Series system from a Subtend Group, you must first delete its subtend connection, then remove the Cisco 6100 Series system from the group. The procedures for doing this follow:
Step 2 Select Edit > Delete > From All Submaps. This moves the icon for the subtended Cisco 6100 Series system back to the holding area.
Step 3 Select the Cisco 6100 Series system in the holding area.
Step 4 Select Remove from Subtend Group from the Configuration menu or click the right mouse button.
Configuring subtend hierarchies works the same way as configuring Location hierarchies. However, ViewRunner currently does not support mixing Location hierarchies and Subtend Network hierarchies. A subtend hierarchy
To create a Subtend Location, you use basically the same procedures as if you were creating a Location hierarchy. To create a subtend network location
When you delete a Subtend Location or one of its parents, it moves all of the subtend groups back to the New Subtend 6100s window. However, deleting a Subtend Group does not delete the Cisco 6100 Series system from the Oracle database. It just removes the subtending information for the Cisco 6100 Series system from the database and the Management Information Base.
ViewMap is integrated into HP OpenView's IP Map polling process. If fail-safe autodiscovery of Cisco 6100 Series 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 2 Select Network Polling Configuration: IP from the menu to access polling interval options, as shown in Figure 2-23.
Step 3 Change the fixed discovery polling settings as desired for seconds, minutes, or hours, as shown in Figure 2-23.
You can change the network polling setting by clicking on the - symbol next to the Used Fixed Discovery Polling Interval field to change the selection to Use Auto Adjust Polling Interval. See Figure 2-24.
The autoadjust polling is best suited to more stable networks. As the poller executes, if new nodes are not discovered, the polling interval increases, reducing network traffic. When a node is discovered during a poll, the interval decreases until such time as nodes are not discovered.
As might be expected with the fixed polling interval, the interval is set to a fixed timeout.
You can provide information in this window that relates to the ATM switch to which a Cisco 6100 Series system is connected. The purpose of this window is to let the operator know how the ATM switch is configured as well as the way in which the operator should access the element management system for that ATM switch.
You access the ATM Switch Properties window, which is shown in Figure 2-25, 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 management system for the ATM switch, or 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 Series system. It allows you to view the status, manage the configuration, and check the performance of a Cisco 6100 Series system.
View LoopRunner is composed of a chassis view and a number of status and configuration dialog boxes. The latter are used to display status and manage the configuration of systems, chassis, slots, modules, ports, subscribers, and permanent virtual connections (PVCs).
The Chassis View window provides the top-level user interface to manage a single Cisco 6100 Series system. It provides both menu bar operations and a bitmap front panel view of the Cisco 6100 Series system that displays a color-coded status of configured modules. The pictorial bitmap displays the multiplexer chassis having all of the ATU-C or STU-C (Direct Connect systems only) modules installed and with each Cisco 6110 having all the LIMs installed (DOH systems only).
Access the Chassis View by right-clicking a Cisco 6100 Series system icon in one of the Wire Center submaps. The Chassis View serves as the top-level display in a hierarchy of dialog boxes that allow you to view, add, modify, or delete the different entities throughout the Cisco 6100 Series system. From the Chassis View window, shown in Figure 2-26, you can view all status information, manage all configurations, and check the performance of the Cisco 6100 Series system.
All Cisco 6100 Series system traps (or error conditions) are logged in the Error Events category of the OpenView Event Categories window.
To open a particular event window, select one of the options in the Event Categories window (shown in Figure 2-27), which opens automatically when you start ViewRunner. The Event Categories window allows you to select the type of alarms and events.
In the Event Categories window, colors indicate the various types of alarm acknowledgements. The following list describes how colors are used in the Event Categories window:
Figure 2-28 shows that in the All Events Browser only part of the critical alarms have been acknowledged.
See "Viewing Events and Alarms," for more information about alarms. Refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide for details about the types and severity of Cisco 6100 Series alarms displayed by ViewRunner.
Posted: Thu Mar 2 10:16:27 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.