HP OpenView's new Java-based web interface further expands NNM's network management capabilities. A part of NNM's base product, the web interface and its applications present the same information about NNM that is available from the NNM management station. This information is now presented in a familiar, operator-friendly format that you can access from a remote client system running a web browser. From your web browser on any PC or UNIX system (the term UNIX system refers to HP-UX and Solaris only), you can log onto the Web and access NNM on the management station to display maps and submaps. You can easily monitor the status of your network from any place at any time.
The HP OpenView Web lets you:
You can read about the following concepts:
The Event Browser is now called the Alarm Browser.
The following functionality is available with the HP OpenView Network Node Manager Web Alarm Browser.
The Alarm Browser performs the following operations:
If you have a read-only Alarm Categories window, the deleted alarms will reappear next time the Alarm Categories window is started, since deleted alarms are not saved from a read-only Alarm Categories window.
Each category in the Alarm Categories window has its own Alarm Browser window. The Alarm Browser window contains a scrolled list of alarms belonging to the associated category. The Alarm Browser also contains status on the number of alarms in the window, their severity, and any filtering information.
The Alarm Categories window contains push buttons corresponding
to each of the alarm categories. NNM defines a set of default
categories. You can add categories, delete categories,
or modify the alarms assigned to a category.
The push buttons in this window light up to indicate when alarms
have been received and have not been deleted from the Alarm Browser.
The color of the push button reflects the most severe
unacknowledged alarm in the
category, or background color if no alarms are present. The
All Alarms category contains all the alarms that are present in
the other categories. The list of categories can be modified.
The colors for each of the categories are:
normal is Green
warning is Cyan
minor is Yellow
major is Orange
critical is Red
Clicking on one of the indicator push buttons will bring up the corresponding Alarm Browser.
The menu bar of the HP OpenView Web Alarm Browser contains the following menus:
The toolbar is located under the menu bar and contains the following buttons.
The content area lists the alarms in chronological order with the most recent alarm at the bottom of the list.
For each alarm, the list shows the following.
| Ack | Indication that the alarm has been acknowledged. |
| Corr | Indication of a correlated alarm. |
| Severity | The severity of the alarm. |
| Date And Time | The date and time when the alarm occurred. |
| Source | An identifier (such as a hostname) for the network object where the alarm originated. |
| Message | A brief description of the alarm. |
The status bar at the bottom of the window contains a table, listing total number of alarms in all categories and the number of alarms sorted by severity. This table shows the count for all the alarms in the alarm log file.
The date in the status frame indicates the time that the data was last received from the server.
The Filter Alarms dialog box lets you select which alarms you would like displayed in the Alarm Browser window. You can set several filtering criteria, which must all be true for the alarm to be displayed.
The filters will not take affect until you click the [OK]
or [Apply] button. When you click [OK]
or [Apply], the filter will affect the display of
alarms currently in the Alarm Browser window.
Each Alarm Browser window has its own Filter Alarms dialog box. That is,
you will see a separate Filter Alarms dialog box for each Alarm Browser window.
For example, when you select Set Filters from the
Error Alarms Browser you will get a Filter Alarms dialog box. Then, if
you select
Set Filters from the Threshold Alarms Browser, you will
see another Filter Alarms dialog box.
You can specify the following filtering criteria:
Specify the severity level of alarms that you want to display in the content area. You can select one or more of the following severity levels:
| Critical | An object is not functioning. |
| Major | An object has serious problems that are likely to impede the normal use of the object. |
| Minor | An object has a minor problem that should not impede the normal use of the object. |
| Warning | An object may face a potential problem. |
| Normal | An object is in a normal operational state. |
Specify how recent the events are that you display in the content area by using spin box.
Specify a node name to display the alarms on that node in the content area. You can specify IP addresses, complete hostnames, partial hostnames, and wildcards. For example, entering "dal" in the Node text box will display alarms for the following nodes: "dal.dog.com" and "dal.pal.com".
If no nodes are in the list, this filter is ignored. When filtering by node, the filter will match any alarm that comes from a node that either matches the string literally or pattern matches the string (if it contains pattern matching notation). Also, it will find the object identifier for the node (if valid), and match on that object identifier. If the name of the node has changed, the old name will still pass the filter since the object identifier is still valid, since it is the same object. As a special case, if the node is in the form #NUM, the alarm will pass if the node of the alarm has an object ID NUM.
Specify a pattern to search for and display alarms that match the pattern in the content area. If the alarm's message does not contain the indicated string, it will not be displayed. If the string is empty, this filter is ignored.
Specify whether to display alarms that are acknowledged, unacknowledged, or both.
You can use the File menu to save or print either the
selected alarms or all of the alarms in the current Alarm Browser window.
You can also use the File menu to close the Alarm
Browser window.
To save the alarms, select File:Save and specify a
filename in the text box.
The file is saved on the network management server that NNM is running
on.
To print the alarms, specify the name of a printer that is attached to
the network management server that NNM is running on.
From the Actions menu you can perform the following
actions on alarms in the Alarm Browser:
You can acknowledge alarms using the following criteria:
Every Alarm Browser window will be affected by the acknowledgment of alarms.
Acknowledge->Selected acknowledges only
the alarms in this browser that are selected (highlighted).
Acknowledge->All in Browser
acknowledges all the alarms that are displayed in this browser.
You can unacknowledge alarms using the following criteria:
Every Alarm Browser window will be affected by the unacknowledgment of alarms.
UnAcknowledge->Selected unacknowledges only
the alarms in this browser that are selected (highlighted).
UnAcknowledge->All in Browser
unacknowledges only the alarms that are displayed in this browser.
You can delete alarms using the following criteria:
Every Alarm Browser window will be affected by the deletion of alarms.
Delete->Selected deletes only the alarms
in this browser that are selected (highlighted).
Delete->All in Browser deletes all the alarms in the
browser.
Alarm Details command displays a read-only tabbed
dialog box that contains a Details tab and a
Correlations tab.
The Details tab:
The top of this dialog box provides information on the underlying characteristics that uniquely define an event. These characteristics are then associated with an event name. The fields that provide the event's identifying characteristics are Sources, Event Identifier, Generic Trap, Specific Trap, and Enterprise ID.
When this dialog box is brought up from the Alarm Browser, it will show the actual parameters, along with the parameters for the event. These will differ in cases where the named event is a default for the actual event. As an example, if the Enterprise ID received is .1.3.6.1.4.1.24, but no event is configured for that enterprise, it will default to .1.3.6.1.4. In this case, both the actual enterprise (.1.3.6.1.4.1.24) and the configured enterprise (.1.3.6.1.4) will be displayed.
The lower portion of the box provides a brief explanation of the nature or cause of the event, as well as information on the type of data that was associated with the event before it was formatted and placed in the event database on the management system.
The Correlations tab lists the alarms that
make up the correlated alarm.
Activates the Network Presenter using the submap containing the node you have selected in the Alarm Browser.
Displays the Event Correlation Configuration window. Event correlation modifies the flow of events by recognizing patterns of events and replacing them with a single event. Event correlation can reduce the number of alarms displayed in your Alarm Browser.
Changes the category of an alarm.
This menu command brings up a choice of the categories to which these
alarms may be
reassigned. If you are not in the All Alarms Browser,
the selected
alarms will be removed from the current browser and placed in the browser
for the selected category.
Changes the severity of the selected alarms. This is useful if you want to keep the alarm in the browser but want to reset the indicator in the Alarm Categories window so that any new alarms of this priority level will cause a notification by changing the color of the indicator light.
Configure alarm filtering for this browser window by using the
Set Filters command. The current filters are
displayed on the bottom status line of the Alarm Browser window.
Click Alarm Filters
for information filtering alarms.
Use the Clear Filters command to turn off any
alarm filtering in effect.
Use the Help menu to obtain information on how
to use the Alarm Browser.
A map is a conceptual layout of your network and its systems. You can define properties for a map, but you cannot view it directly; instead, you view the submaps that comprise the map. Submaps are typically organized hierarchically to show an increasing level of detail.
You can compare the relationship between maps and submaps in Network Node Manager to an atlas. The submaps are the maps in the atlas, while the map is the atlas itself. In an atlas, you can view a page of the entire world, or by turning a page, you may view a particular continent, a country, a state, a city, or even specific parts of a city. When viewing the entire world, your perspective is distant. If you turn to a city map, you get a much closer view. In Network Node Manager, when you view your network, you are actually viewing a part of your network. The view may be presented in a high level submap, one that represents your entire network, spanning the world, or a more detailed view of any portion of the network.
You can create multiple maps, but only one map is open at a time for any given session of Network Node Manager. Different maps can be used for defining different management regions or for different presentations of the same management region. Different maps can be tailored to the needs of individual operators.
An object represents a particular entity or resource in a networked systems environment. An object might represent a physical piece of equipment on the network, the components of a node on the network, or parts of the network itself.
Each object is composed of a group of attributes (properties) that describe the object. For example, a computer object might include an attribute called Host Name. You can change the description of an object by changing the value of its attributes. Applications can define attributes that are used to manage the object.
Objects are represented graphically on your map by symbols. For example, a computer could be represented by a symbol composed of the outline for the computer symbol class and the bitmap for a workstation symbol subclass.
This dialog box lists the selection name. The information that will
appear in the Comments section is not available to the
Network Presenter for this release.
Lists the attribute categories for the object. These categories include
Capabilities and General. Select
the category whose values you want to view.
The attributes in the
Capabilities list determine which menu commands are
enabled or
disabled when this object is in the Selection list. These
attributes are defined as capabilities in a field registration
file.
Values for these attributes may be set in several ways:
The General Attributes list displays the
object attributes for the object you selected.
This information can also appear in application-specific dialog boxes.
General attributes are not specific to any one application. Values assigned to these attributes are not verified by applications. General attributes can display attributes of certain objects you want to track, for example, the physical location of a resource on the network.
The specific fields in this dialog box depend on the applications that register a field for this dialog box.
The General Attributes list shows attributes that applications choose to display in this dialog box. The default general attributes are:
| isSNMPSupported | When isSNMPSupported is True, the object supports SNMP. |
| isSNMPProxied | When isSNMPProxied is True, the object is proxied by another node. All SNMP requests will go to the proxy node rather than directly to the object. |
| SNMP Agent | This is a mix of software vendor and the hardware that the agent runs on. |
| Vendor | Name of the manufacturer of the resource on the network. |
The SNMP Data Presenter displays results of operations that present tabular or textual data for managed SNMP nodes selected from the map. You can invoke the SNMP Data Presenter by selecting target nodes in the content area of the Network Presenter and then selecting the SNMP Data Presenter from the Network Presenter menu or from the Launcher.
When accessed from the Launcher, the scoping pane of the SNMP Data Presenter contains three categories, with actions under each category, in a tree format. You can click on the category items to expand them and then click on an action to execute that action. You can also use the category drop down to choose a category to expand. The results of an action are shown in the content area.
You can view the following data:
You can view the following data:
You can view the following data:
You can view the following data:
For example, if you wanted to know if a node is executing the Telnet server, you could use the Services command to see if the node is listening with Telnet TCP port number 23.
You can view the following data:
You can list the management systems (by address) that are configured to receive events (traps) from the node you specify. The specified node must be an HP 9000 or Sun SPARCstation running the HP OpenView SNMP Agent software.
The SNMP Trap Recipients operation lists the address of the management system to which the specified node is sending its events. If multiple systems are listed, the specified node sends its events to all the management systems listed.
You can view the interface status from either the Performance or Fault category.
Depending on the name specified in the Node Name text box, this operation will either list the status attributes for the specified interface or status attributes for the interfaces on the specified node.
This operation is useful for troubleshooting the node or interface. If you specify more than one node or interface, you can view the data for each node in the content area.
| Index | The MIB instance of the interface on the specified node. The MIB instance is an internal counter on the system. You need to know the instance when you set up MIB data collection. |
| Interface | The textual interface name as assigned by the managed device. |
| Status | The combined administrative and operational status of the
interface. Possible values are:
|
| Last Status Change | The date and time that the interface entered its current operational status. |
| Status Notifications | This field indicates whether status notifications, such as Link Up and Link Down traps, are generated by the managed device when the interface changes state. Typically this option is "On" only for the lowest layer interface in an interface stack relationship. |
| Loopback Mode | This field indicates whether the DS1 or E1 interface is in
loopback mode and if so, what type of loopback mode it is in.
Possible values are:
|
| Send Code | The type of code (data) currently being transmitted on the
DS1 or E1 interface. Possible values are:
|
| Line Status | Indicates the current DS1 or E1 specific line status condition
associated with the interface. One or more of the following
conditions may exist on the line:
|
| Loopback Mode | This field indicates whether the DS3 or E3 interface is in
loopback mode and if so, what type of loopback mode it is in.
Possible values are:
|
| Send Code | The type of code (data) currently being transmitted on the
DS3 or E3 interface. Possible values are:
|
| Line Status | Indicates the current DS3 or E3 specific line status condition
associated with the interface. One or more of the following
conditions may exist on the line:
|
| Section Status | The current SONET or SDH specific status condition associated
with the SONET/SDH Section. One or more of the following
conditions may exist on the line:
|
| Line Status | The current SONET or SDH specific condition associated with the
SONET/SDH line. One or more of the following conditions may exist:
|
| Path Status | The current SONET or SDH specific status associated with the
SONET/SDH Path. One or more of the following conditions may exist
on the line:
|
| Virtual Tributary Status | The current SONET or SDH specific status condition associated
with the SONET/SDH Virtual Tributary (VT). One or more of the
following conditions may exist on the line:
|
The SNMP Authentication Failures operation lists the management systems that caused an authentication failure on the specified nodes. Authentication failures occur when a management system sends an SNMP request with an incorrect community name.
The list shows all the failures that have happened on the node you specified. The specified nodes must be an HP 9000 or Sun SPARCstation running the HP OpenView Extensible SNMP Agent software. If you specify more than one node, the data for all the nodes is shown in the content area.
For each authentication failure that has occurred on the specified node, the following information is reported.
| Unauthorized System | The address of the system causing the authentication failure. |
| Time since Failure | The amount of time that has elapsed since the authentication failure occurred. |
You can list the TCP connections table for the remote SNMP nodes you specify. The specified nodes must support SNMP. If you specify more than one node, you can view the data for all the nodes in the content area. For each node listed in the specified node's TCP connection table, the operation lists the following information.
| Local Address | The local address of the TCP connection; includes its associated port number or service name. |
| Remote Address | The remote address of the TCP connection; includes its associated port number or service name. |
| (state) | The state of the TCP connection as defined by the TCP protocol (for example, ESTABLISHED, CLOSED-WAIT). |
The output lists the associated port numbers by default. If the product can match the port number with a service name, the output lists the service name instead.
You can list the available file system space on an HP OpenView SNMP Agent node. The specified node must be an HP 9000 or Sun SPARCstation running the HP OpenView SNMP Agent software. If you specify more than one node, you can view the data for each node in the content area.
For each file system that is physically on the specified node, the operation lists the following information.
| Filesystem | The name of the file system. |
| kbytes | The total number of kilobytes of disk space. |
| used | The number of kilobytes used. |
| avail | The number of kilobytes available. |
| capacity | The percent of total capacity being used. |
| Mounted on | The directory name on which the file system is mounted. |
Depending on the name specified in the Node Name text box, this operation will either list the common attributes for the specified interface or common attributes for all interfaces on the specified node. This operation is useful for verifying information related to each node or interface, and for generating reports.
For the specified interface, you may see one or more of the following categories of information, depending on the type of interface specified.
| Name or Address | The name or the IP address of the interface, as assigned by the network administrator. |
| Index/Interface # | The interface index, or interface number of the interface within the SNMP agent of the managed device. |
| Interface/Interface Name | The interface name as assigned by the managed device. |
| Status | The combined administrative and operational status of the
interface. Possible values are:
|
| Alias | A textual name or description of the interface, as assigned by the network administrator. |
| Type | The type of network interface. When an interface consists of multiple layers, such as such as a Frame Relay Data Link running over a serial line, the interface type is reported as the higher layer. |
| Capacity | The maximum bandwidth (bytes/second) of each interface. The
value reported is abbreviated into the following units of
measure as applicable:
|
| Physical Address | The physical address of the interface. Interfaces such as IEEE 802.3 have a physical address by which the interface is identified. |
| MTU | The Maximum Transmission Unit is included only for packet-oriented interfaces. The value specifies the largest packer size, in bytes, that a single packet send on this interface may contain. |
| Promiscuous Mode | Some packet-oriented interfaces support Promiscuous Mode, where all traffic on the network can be passed up to a higher layer application listening on the interface, as opposed to receiving only traffic addressed to that interface. A value of "On" indicates that the interface is operating in Promiscuous Mode. A value of "Off" indicates that the interfaces is not operating in, or does not support, Promiscuous Mode. |
| Management Scheme | The Data Link Connection Management scheme for the Frame Relay
interface. Possible values are:
|
| Address Format | The address format in use on the Frame Relay interface.
Possible values are:
|
| Address Length | The length of the Frame Relay interface address, in bytes, in accordance with the above address format specification. |
| Maximum VCs Allowed | The maximum number of Virtual Circuits that can be configured on this Frame Relay interface. |
| Broadcast Mode | This field indicates whether the Frame Relay interface is configured to operate in broadcast mode. When the value is "On", the interface may be broadcast to multiple recipients. When the value is "Off", traffic flows only in a point-to-point configuration. |
| Status Inquiry Interval | The amount of time, in seconds, between successive Status Inquiry Messages. |
| Full Inquiry Interval | The amount of time, in seconds, between successive Full Inquiry Messages. |
| Sampling Period | The number of Status Inquiry Intervals configured as the sampling period. |
| Fault Threshold | The number of Status Inquiry Intervals, within a given sampling period, that the Status Inquiry Message must go unanswered before the Frame Relay interface is declared down. |
| Circuit ID | The transmission line provider's circuit identifier of the DS1/E1 line. It can be used to facilitate communication with the provider during troubleshooting. |
| Line Type | The type of DS1 or E1 circuit. Possible values are:
|
| Line Coding | The line coding technique used to maintain a synchronized data
signal on the DS1 or E1 circuit. The possible values are:
|
| Signaling | The supported variation for signaling mode. Possible values are:
|
| Clock Source | The source of the clock used by the signaling mechanism to
transmit data. Possible values are:
|
| Loopback Mode | This field indicates if the interface is in loopback mode,
and if so, what type of loopback mode. Possible values are:
|
| Facilities | The type of use of the facilities data link. Possible values are:
|
| Line Type | The type of DS3 or E3 circuit. Possible values are:
|
| Line Coding | The line coding technique used to maintain a synchronized data
signal on the DS3 or E3 circuit. The possible values are:
|
| Clock Source | The source of the clock used by the signaling mechanism to
transmit data. Possible values are:
|
| Loopback Mode | This field indicates if the interface is in loopback mode,
and if so, what type of loopback mode. Possible values are:
|
| Facilities | The type of use of the facilities data link. Possible values are:
|
| Circuit ID | The transmission line provider's circuit identifier of the DS3/E3 serial line. It can be used to facilitate communication with the provider during troubleshooting. |
| Line Type | The type of physical line attached to the interface. Possible
values are:
|
| Line Coding | The line coding in use for this interface. Possible values are:
|
| Signaling | This field indicates whether SONET or SDH signaling is used on this interface. |
| Circuit ID | The transmission line provider's circuit identifier of the SONET/SDH serial line. It can be used to facilitate communication with the provider during troubleshooting. |
| Instance | The interface index associated with the ATM interface. |
| ILMI VPI/ILMI VCI | An ATM interface uses one of the Virtual Channel Connections configured on the interface as the ATM Local Management Interface (ILMI). These two fields report the Virtual Path Identifier (VPI) and the Virtual Channel Identifier (VCI) that uniquely identify the ILMI VCC. |
| VPCs Allowed | The maximum number of Virtual Path Connections (VPCs) that may be configured on the ATM interface. Each VPC is identified by a Virtual Path Identifier (VPI) that is unique to the ATM interface. |
| VPCs Configured | The number of Virtual Path Connections currently configured on the ATM interface. |
| VCCs Allowed | The maximum number of Virtual Channel Connections (VCCs) that may be configure don the ATM interface. Each VCC is identified by a Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) pair that is unique to the ATM interface. |
| VCCs Configured | The number of Virtual Channel Connections currently configured on the ATM interface. |
| Address Format | The type of ATM address configured for use on the ATM interface.
Possible values are:
|
| Administrative Address | The address assigned to the ATM interface for administrative purposes. |
| Neighbor IP Address | The IP address of the system connected to the far end of the ATM interface. |
| Neighbor Interface | The textual name of the interface on the system connected to the far end of the ATM interface. |
You can list the IP and link addresses for the specified remote SNMP nodes. From this list you can determine the IP and interface addresses associated with nodes without looking through configuration files. The specified nodes must support SNMP. If you specify more than one node, you can view the data for each node in the content area.
For each interface on the specified node, the command lists the following information.
| Index | The MIB instance of the interface on the specified node. The MIB instance is an internal counter on the system. You need to know the instance when you set up MIB data collection. |
| Interface | The interface name (of the specified node) that is associated with the node and the link address. |
| IP address | The address for the specified node. |
| Network Mask | The network mask for the specified node. |
| Network Address | The network address for the specified node. |
| Link Address | The link address associated with the node name. |
You can list the routing table information for the remote SNMP nodes you specify. This information determines how IP packets are routed on the nodes. Use the routing table operation for diagnosing connectivity problems (for example, one node cannot communicate with another). The specified nodes must support SNMP. If you specified more than one node, you can view the data for each node in the content area.
For each specified node, the operation lists the following information.
| Destination | "default" is a route that the system uses when it cannot find a specific route. |
| Gateway | The name of the next gateway between the specified node and the destination. |
| Type | The type can be: - Direct (to a directly connected LAN) - Invalid (currently not available) - Remote (through a remote gateway) |
| Mask | A filter to select a group of nodes. |
| Interface | The name of the interface that is used to reach the destination. |
You can list the ARP (Address Resolution Protocol) Cache table for the remote SNMP nodes you specify. The ARP Cache operation is useful for diagnosing connectivity problems because it indicates whether two nodes have a different link address for a third node. The specified nodes must support SNMP. If you specify more than one node, you can view the data for each node in the content area.
Each row in the ARP Cache table consists of the following information.
| Node | The node name or address of the destination node. |
| Link Address | The link address associated with the destination node. |
| Entry Type | The type of mapping. |
| Interface | The interface name (of the specified node) that is used to access the destination node. |
You can list the services that the remote SNMP nodes you specify are configured to support. For example, if you wanted to know if a node is executing the Telnet server, you could use the IP Services operation to see if the node is listening with Telnet TCP port number 23. The specified nodes must support SNMP and TCP/IP. If you specify more than one node, you can view the data for each node in the content area.
For the specified node, the command lists the following information.
| Protocol | The service protocol (either TCP or UDP). |
| Port | The port to which the service is bound. |
| Service | The service for which the node is listening (for example, SNMP, Telnet, NFS); if blank, the service is unknown. |
The system information operation displays information about the system, such as location and system contact. You must specify nodes that support SNMP. If the specified nodes also support MIB-II and the device has been fully configured, additional information may also be available.
You can view the following information about each node specified.
The Network Presenter is a Java-based interface for viewing maps. It provides another way of viewing the map data that is on a management station or management console from any machine with a web browser that supports Internet Explorer or Netscape Communicator.
The Network Presenter communicates with the management station to get registration information, map data, and map object data. It provides read-only access to the map data and has dynamic updates to reflect the changes that occur on the management station. You can navigate through submap views, select symbols, and view object properties.
The window consists of the following areas.
| Title Bar | The open submap name appears here. |
| Menu Bar | The menu bar appears at the top of the submap window. The menu bar contains commands for network management, troubleshooting, and analysis. |
| Context Box | The context box contains an entry for each symbol in the NNM's root submap that has a child submap. If the URL that invokes the Network Presenter specifies an object, then that is the initial context, otherwise, the first symbol in the list of symbols on NNM's root submap is the default context. |
| Toolbar | The toolbar buttons display shortcuts for frequently used commands. |
| Symbols | Icon and connection symbols that are shown in the scoping pane and content area, represent the objects in your network. Connection symbols are only shown in the content area when the graphical view is selected. Connection symbols are not displayed in the tabular view or in the scoping pane. |
| Scoping Pane | The scoping pane is the vertical pane on the left side of the window. The scoping pane in the Network Presenter contains symbol names for icon symbols that are presented in the submap displayed in the content area. |
| Content Area | The contents of the submap appears here. The submap displays symbols and graphics that convey information about systems, connections, and other parts of your network. |
| Status Bar | The status bar displays the map names, submap names, and submap status. The status bar also shows symbol names on the left side when the mouse is over a symbol in a graphical view in the content area. |
The items in the menu bar are organized according to the type of functionality provided. Because applications can register new menu commands on the menu bar, the specific items on your menu bar may vary.
The menu bar for the Network Presenter contains the following menus:
| Map | Items under the Map menu are generally
associated with the manipulation of files. In the
Map menu, you can close a submap, or exit
the Network Presenter. |
| Edit | Items under the Edit menu enable you to
view the selected object's properties. Click
Object Properties for more information.
|
| View | Items under the View menu enable you to
change the amount and appearance of the data that is displayed
in the content area. These items include:
|
| Performance | Items under the Performance menu are associated
with the performance of nodes presented in the Network Presenter.
Use the
SNMP Data Presenter to
display performance data on selected SNMP managed nodes. |
| Configuration | Items under the Configuration menu are
associated with the configuration of nodes presented in the
Network Presenter. Use the SNMP Data Presenter to display performance
data on selected SNMP managed nodes. |
| Fault | Items under the Fault menu are associated
with diagnosing network problems. Items include:
|
| Tools | Items under the Tools menu are associated
with tools available in the Network Presenter. These items
include:
|
| Help | Items under the Help menu allow you to access
the online help for the HP OpenView Web product. |
The toolbar contains shortcut buttons for frequently used commands. When visible, the toolbar appears directly under the menu bar.
| Click this button: |
To: |
|
![]() |
Close |
Close this submap. |
![]() |
Top Level |
Display the top level submap of the context that appears in the context box. For example, the top level submap of the Internet submap. |
![]() |
Up One Level | Display the submap that is one level up. |
![]() |
Panner |
Display the Panner window. |
![]() |
Display in New Window | Display in a new window, the information currently presented in the parent window. |
![]() |
Tabular | Display the data in the content area in a tabular format. |
|
|
Graphical | Display the data in the content area in a graphical-icon format. |
Use the Panner window to zoom in on sections of a submap.
To zoom in on an area of the submap, drag the arrow pointer in the Panner window to draw a selection rectangle around the objects you want to view more closely. When you release the mouse button, the submap zooms in on the area encompassed by the selection rectangle.
To zoom in on a different area of the submap, put the arrow pointer in the selection rectangle, hold down mouse button 1, and drag the selection rectangle to a different position in the Panner window. The view in the submap changes simultaneously. Use the scroll bars in the submap window to move the selection rectangle in smaller increments.
To zoom out and redisplay all the symbols in the submap, Click
[All].
A symbol is a graphical representation of a particular object. An object can be represented by symbols in several submaps, or even by multiple symbols in the same submap.
The submap's schematic representation of the network is created from symbols that represent network segments and connections. Symbols can represent a variety of entities on the network such as: a PC-board, a computer, a printer, a group of computers or printers, a subnet, a connection between two computers, the interface for an entire network.
A symbol has properties that are unrelated to the object that it represents. Symbol properties include:
| Symbol variety | There are two varieties of symbols: icon or connection. |
| Symbol type | The symbol type determines the visual appearance of the symbol. |
| Symbol status | Symbols can display status information through the use of color. |
| Symbol behavior | A symbol can either open a submap (explodable behavior) or perform an action on an object or set of objects (executable behavior). The Network Presenter does not support executing the action associated with an executable symbol. |
Items in the scoping pane allow you to control the information presented in the content area. The symbols listed in the scoping pane initially have a plus sign (+) next to them. Leaf node symbols are not shown in the scoping pane.
There are two cursors associated with the scoping pane. The selection cursor is represented by a solid blue box around the name in the scoping pane. The location cursor is represented by a hollow black box around the name in the scoping pane. When both are for the same symbol, the selection cursor appearance overrides the location cursor.
You can select an item by using the selection button to click on the icon or the name in the scoping pane. This will display the symbols child submap in the content area. Click on the expansion control (+) or (-) to expand or collapse the tree list in the scoping pane. If a child submap does not exist, the (+) expansion control is removed when you click on it. Double-click on a symbol to expand and display a child submap.
The content area contains the contents of the submap. A submap consists of related symbols that are displayed in a single window. Each submap provides a particular view of a network environment contained in a map. You can open and display multiple submaps of the open map at the same time by using the ``Display in New Window'' menu command or toolbar button.
A graphic serves as a background for the symbols in a submap. A graphic can provide contextual information, such as a floor plan for systems, a map of geographically diverse sites, and so forth. The CompuServe Graphics Interface File (GIF) format is supported.
Network Node Manager provides a standard, top level submap for each context. For example, the top-level submap of the IP Internet context. Below the top level submap, other submaps are organized hierarchically. You can also create an independent submap that is not a member of a hierarchy.
The status bar contains the following information:
[Auto-Layout]
when automatic layout is enabled.The status bar does not contain the map access permissions.
The HP OpenView Launcher is an integration point for the HP OpenView Web user interfaces. The Launcher provides a central location from which you can launch all of the applications that have been integrated into the HP OpenView Web.
Closing the Launcher disables applications that were started from the Launcher.
The Launcher window contains two panes with the following information:
The top pane of the window presents a hierarchical tree list of categories and links to functionality. Beneath the hierarchical list are a set of tabs that provide different approaches for accessing functionality or information. Each approach is indicated by a small icon that is presented on the tab. You can click on a specific tab to access categories with a specific approach.
The tabs are:
| Object | Contains object oriented categories and links to applications that provide views of objects for monitoring the objects and acting on the objects. | |
| Tasks | Contains categories and links for performing management tasks associated with the categories. The contents under each category also includes tasks for configuring management capabilities associated with that category. For example, the Diagnostics and Fault Management category contains links to functionality for diagnosing and resolving faults. This category also contains access to functionality for configuring fault notification. | |
| Information and Reporting | Contains integration points for tools that act on similar types of objects. This tab allows multiple tools to be accessed by means of a category name that represents all of the tools of a given type. | |
| Tools | Contains the application-based categories and links for specific executables within an application. | |
| Management area (user configurable) | This tab is only available when it has been configured, by the user, in the registration file. This tab allows customization of categories and links for matching the way HP OpenView functionality will be used in your management environment. | |
| Help | Contains categories and links to online help for HP OpenView web applications and third party applications. |
The bottom pane of the window contains the active help area. The active help area displays a short help message explaining the function of the category or link that the cursor is placed over. Active help for the tabs is only available when you click on the tab.
Clicking on the expansion control (+) or (-) or the category name, causes the expansion or collapse of that category. Links do not have expansion controls. Clicking on a link in the tree list will bring up a window with the related functionality.
Clicking on a tab other than the active tab displays the hierarchical list associated with that tab.