Tasks

You can access the following groups of tasks:

Fault Management Tasks

Use the Network Presenter to perform most of the fault management tasks. You can use the Fault category of the SNMP Data Presenter to view interface status.

You can access the Network Presenter from the HP OpenView Launcher:

  1. Select the Tools tab.
  2. Expand the NNM category.
  3. Double-click on Network Presenter. The Network Presenter appears.

You can use the Fault menu on the Network Presenter to perform the following tasks.

Tasks Checking for Node Capabilities

You can use the Network Presenter to check node for remote DMI capabilities, web management, and web server capabilities. If the node supports DMI, ovcapsd will register with that node for NNM to receive DMI events. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

To poll on one or more node objects:

  1. Select the nodes you wish to check.
  2. Select Fault:Network Connectivity->Capability Poll.

Tasks Diagnosing Communication Problems Between NNM and a Node

You can use the Network Presenter to diagnose communication problems between NNM and a node. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

To poll on one or more nodes:

  1. Select the nodes you wish to check.
  2. Select Fault:Network Connectivity->Poll Node.

Action

NNM polls nodes automatically at a predetermined interval. You can perform a Poll Node operation at any time to obtain real-time information about the selected nodes.

When you perform the Poll Node operation on selected nodes, the following occurs:

The Poll Node operation performs all checks sequentially on a per node basis. Once all checks are complete for one node, the operation begins the series of checks for the next node.

If the node does not support SNMP, status is the only check performed.

Tasks Diagnosing Connectivity Between Two Nodes

You can use the Network Presenter to check connectivity between two remote nodes by transmitting packets between the nodes. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

  1. Select two nodes, a source node and a destination node. The source node must be an HP 9000 or Sun SPARCstation running the HP OpenView SNMP Agent software.
  2. Select Fault:Network Connectivity->Remote Ping.

Behavior

The Remote Ping operation is like the Ping operation except that you can execute it from a remote node. The Remote Ping operation sends one ICMP Echo packet per second from one remote node to another. (The transmitted packet size is 64 bytes.) The output displays the number of packets sent and lost, and the round-trip times.

Tasks Diagnosing Local Management System Connectivity

You can use the Network Presenter to check connectivity between the local management system and another node or nodes. This enables you to diagnose network connectivity problems by testing networking protocols. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

Select Fault:Network Connectivity->Test IP/TCP/SNMP.

Behavior

When you select multiple nodes, the input and output for all nodes appear in one table.

The operation tests the following protocols:
IP Protocol Sends an ICMP Echo request (ping) to check the IP connectivity; determines whether you can communicate with a remote node (that is, whether you can send a packet and get it back). The output is either the time, in milliseconds, that it takes for the exchange to complete, or the output is an error.
TCP Protocol Performs a TCP connection to TCP port #23 (telnet) to determine whether you can connect to a remote node. The output is either an OK or an error. This test may fail since some NT workstations may not have a telnet server installed.
SNMP Protocol Gets a system description, via SNMP, using the community name configured through NNM on the Windows NT operating system or a UNIX system using the SNMP Configuration operation. If the test is unsuccessful, either the node does not support SNMP, the system is not up, or the community name is wrong. The output is either an OK or an error.

Tasks Locating IP Routes Between Nodes

You can use the Network Presenter to locate specific IP routes between selected nodes. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

  1. You must select two nodes from the map. The menu command is unavailable until you have selected two nodes.
    2. All gateways between the selected nodes must have their community names correctly set in ovsnmp.conf for the Locate Route operation to work.
  2. Select Fault:Network Connectivity->Locate Route:via SNMP.

Behavior

The operation lists the source name, source address, gateway (Next Hop), and gateway address for each object on the path (route). Reading the left column provides you with a complete list of source and gateway names.

The Locate Route operation is useful for diagnosing connectivity problems (for example, one node cannot communicate with another).

Task Topic Obtaining Status Information

You can use the Network Presenter update the open map and database with status information about selected objects. Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

To perform a status poll on one or more nodes:

  1. Select the nodes you wish to check.
  2. Select Fault:Network Connectivity->Status Poll.

Behavior

The Status Poll operation is performed automatically at a predetermined interval. You can perform a Status Poll operation at any time to obtain real-time status information about the selected nodes.

When you perform the Status Poll operation on selected nodes, any status changes since the last Status Poll operation was performed are reflected on any open submaps that display a symbol of the selected nodes.

Task Topic Sending Packets to a Remote Node

You can use the Network Presenter to determine if two nodes or interfaces can communicate with one another. The Ping operation sends one ICMP Echo packet per second from the local management system to a remote node. (The transmitted packet size is 64 bytes.) The output displays the number of packets sent and lost, and the round-trip times.

Click on accessing the Network Presenter for information on how to access this presenter.

Procedure

  1. Select one or more nodes that you wish to ping.
  2. Select Fault:Network Connectivity->Ping.

Behavior

The operation executes continuously until you click [Stop].

You can execute the Ping operation only from a manager. To change the node name to which you are executing this operation, follow these steps.

  1. Click [Stop].
  2. Change the name in the To field.
  3. Click [Restart].

To execute the Ping operation from a remote node, use the Fault:Remote Ping command.

If you select more than one node, the operation uses the first node selected as input.

The selected node is input to the To field; it identifies the destination node.

Task Topic Using the Network Presenter

You can access the Network Presenter from the HP OpenView Launcher in the following ways:

You can use the Network Presenter to perform the following tasks:

See Also
Network Presenter

Task Topic Navigating Through Submaps

You can navigate between submaps in the following ways.

Explodable symbol In the content area you can open a submap by double-clicking an explodable symbol of the submap.
Scoping pane You can select from a hierarchical list of objects which will result in this object's contents being presented in the content area.
Navigation buttons You can navigate using the submap navigation buttons, located in the tool bar of each submap window.
See Also
Network Presenter

Alarm Management Tasks

Use the Alarm Browser to perform the alarm management tasks. You can access the Alarm Browser from the HP OpenView Launcher in the following ways:

  1. Select the Tools tab.
  2. Expand the NNM category.
  3. Select Alarm Browser.

OR

  1. Select the Information and Reports tab.
  2. Expand the Faults and Alarms category.
  3. Select NNM Alarm Browser.

You can also access the Alarm Browser from the Fault menu of the Network Presenter.

You can perform the following tasks using the Alarm Browser:

Task Topic Acknowledging Alarms

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

You can acknowledge an alarm, yet not delete it. Once acknowledged, an alarm will still be visible, but it will not affect the color propagated into the Alarm Categories window. You can acknowledge an alarm from the Alarm Browser in the following ways:

After acknowledging an alarm, a check mark will appear in the Ack field.

All users of the Alarm Browser view alarm acknowledgments. To delete acknowledged alarms, you must use the acknowledge filter and then select Actions:Delete->All in Browser. Make sure that you have only the acknowledge filter set before you perform the deletion.

Task Topic Browsing Alarms for a Node

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

To see all the alarms for a particular node:

Task Topic Changing an Alarm Category

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

To change an alarm category:

This only affects the selected alarms. Future alarms of the same type will continue to go to the old category. You must modify the event to specify a new category using the Event Configuration operation to have old and new alarms be recategorized.

Task Topic Deleting Alarms

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

Alarms continue to appear in the Alarm Browser until you delete them or the maximum number of alarms for the browser has been reached. The primary reason to delete alarms is so you can determine when new alarms occur. If you do not delete alarms, each button in the Alarm Categories window will continue to show status color for all alarms, and you may not know when new alarms occur.

You can delete alarms either individually or all at once, using choices under the Actions:Delete menu command in each Alarm Browser. To delete acknowledged alarms, you must use the acknowledge filter and then select Actions:Delete->All in Browser. Make sure you have only the acknowledge filter set before you perform the deletion. All users of the Alarm Browser will view this change.

Once deleted, the same alarms do not reappear. Though an alarm will appear in two windows, you need only delete the alarm in one window. This clears the alarm in every Alarm Browser that it appears.

If you do not want to delete an alarm, you can assign it to a new category. Click Changing an Alarm Category for more information.

Task Topic Displaying Alarms

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

To view alarms, click on the button (in the Alarm Categories window) that corresponds to the category you want to view.

To exit any of the Alarm Browsers, select File:Close.

Each Alarm Browser lists undeleted alarms in chronological order. The oldest alarm is at the top; the most recent alarm appears at the bottom of the list. The scroll bar must be at the bottom for you to see new alarms as they appear on the list. Each Alarm Browser lists the following information about each alarm:

The All Alarms Browser window lists the most recent alarms. When the list reaches the maximum size and another alarm occurs, the oldest alarm is removed from both the All Alarms Browser and from any other Alarm Browser in which it appears.

You may receive alarms for nodes that do not appear on the map. For example, if an SNMP agent is not in your management region, but is configured to send traps to the manager, you will receive alarms for that agent (for example, when it starts up).

Task Topic Filtering Alarms

Click accessing the Alarm Browser for information on how to display the Alarm Browser. Within any Alarm Browser, you can filter based on one or more criteria. These criteria all must be true for the alarm to be displayed. The criteria are:

You use filtering to reduce the number of alarms displayed or to perform deletions on certain types of alarms. The status of the filtering is shown at the bottom of the Alarm Browser, showing how many alarms are in the category, as well has how many of each severity are displayed. If filtering is on, the status will change to indicate that a subset of the alarms in the category are displayed. You can then perform operations based selected alarms, or all the alarms in the browser.

To see all the critical alarms:

  1. Click the All Alarms category push button from the Alarms Category window.
  2. Click View:Clear Filters from the All Alarms Browser window. This will clear all filter so that you will be sure to have only the severity filter set.
  3. Select View:Set Filters from the All Alarms Browser window; the Set Filters dialog box appears.
  4. Click the by Severity tab. Make sure that only the Critical check box is selected.
  5. Click [Apply]. You now see only the critical alarms in the All Alarms Browser window.

After resolving all these alarms, you will want to delete them. If you pick Actions:Delete->All in Browser, the category light will change from red to the next most severe color.

Remember, all deletions are will be viewed by every user of the Alarm Browser.

Task Topic Selecting Alarms Within a List

Click accessing the Alarm Browser for information on how to display the Alarm Browser.

To delete and to highlight alarms, you must first select alarms from the list. This selection model works like the selection model for objects on the map. However, selecting alarms in the Alarm Browser has no effect on the objects selected on the map.

When an alarm is selected, the text appears in reverse video.

Performance Management Tasks

Use the SNMP Data Presenter to perform the performance management tasks.

You can access the SNMP Data Presenter from the HP OpenView Launcher or from the Network Presenter.

Launcher:

  1. Select the Tools tab.
  2. Expand the NNM category.
  3. Select SNMP Data Presenter.
  4. From the SNMP Data Presenter, select the Performance category from the top left pane.

Network Presenter

  1. Select one or more nodes that support SNMP.
  2. Select Performance:SNMP Data Presenter.

You can perform the following tasks using the Performance category.

Task Topic Monitoring Interfaces

You can list the interfaces on remote SNMP nodes using the following procedure.

This operation is useful for diagnosing performance problems since it provides information on incoming and outgoing SNMP node traffic and associated errors. The operation is also useful for diagnosing connectivity problems since it lists the status of interfaces.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select one or more nodes that supports SNMP.
  2. Select Performance:Network Activity->Interface Status:Overview
    3. .

Behavior

For each interface on the specified node, the operation 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 textual interface name as assigned by the managed device.
Status The combined administrative and operational status of the interface. Possible values are:
  • Disabled--The interface is administratively disabled.
  • Up--The interface is enabled and working normally.
  • DOWN--The interface is enabled but is not working properly.
  • Testing--The interface is in a testing mode.
  • Dormant--The interface is waiting for a connection to become active.
  • Missing--The interface is configured, but no hardware is present.
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.

DS1/E1 Status

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:
  • Off--The DS1 interface is in normal transmission state.
  • Payload Loop--The received signal is looped after it is processed by the interface's framing function.
  • Line Loop--The received signal is looped before being processed by the interface.
  • Other--Some other, vendor-specific, loopback.
Send Code The type of code (data) currently being transmitted on the DS1 or E1 interface. Possible values are:
  • Normal Data
  • Line--Request for Line Loopback.
  • Payload--Request for Payload Loopback.
  • Reset--Request Loopback Transmission.
  • QRS--Quasi-Random Signal test pattern.
  • 511--Fixed 511 bit test pattern.
  • 3in24--Fixed 3 bits set in 24 test pattern.
  • Other--Proprietary test pattern.
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:
  • Normal--The DS1/E1 line is operating normally.
  • RcvLOP--Received Loss of Frame (Yellow Alarm).
  • XmtLOF--Sending Loss of Frame (Yellow Alarm).
  • RcvAIS--Received Alarm Indication Signal.
  • XmtAIS--Sending Alarm Notification Signal.
  • LOT--Loss of Frame (Red Alarm).
  • LOS--Loss of Signal.
  • Looped--Near end is in Loopback state.
  • T16AIS--E1 TS16 Alarm Indication Signal.
  • RcvLOMF--Received TS16 Loss of MultiFrame.
  • XmtLOMF--Sending TS16 Loss of MultiFrame.
  • RcvTest--Receiving test pattern.
  • Fault--Other/proprietary failure detected.

DS3/E3 Status

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:
  • Off--The DS3 interface is in normal transmission state.
  • Payload Loop--The received signal is looped after it is processed by the interface's framing function.
  • Line Loop--The received signal is looped before being processed by the interface.
  • Other--Some other, vendor-specific, loopback.
Send Code The type of code (data) currently being transmitted on the DS3 or E3 interface. Possible values are:
  • Normal Data
  • Line--Request for Line Loopback.
  • Payload--Request for Payload Loopback.
  • Reset--Request Loopback Transmission.
  • DS1 Loop--Request DS1/E1 Loopback within the DS3/E3 frame.
  • Test--Sending test pattern.
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:
  • Normal--The DS3/E3 line is operating normally.
  • RcvRAI--Received Remote Alarm Indication (Yellow Alarm).
  • XmtRAI--Sending Remote Alarm Indication (Yellow Alarm).
  • RcvAIS--Received Alarm Indication Signal.
  • XmtAIS--Sending Alarm Notification Signal.
  • LOF--Loss of Frame (Red Alarm).
  • LOS--Loss of Signal.
  • Looped--Near end is in Loopback state.
  • T16AIS--E1 TS16 Alarm Indication Signal.
  • RcvTest--Receiving test pattern.
  • Fault--Other/proprietary failure detected.

SONET/SDH Status

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:
  • Normal--The SONET/SDH section is operating normally.
  • LOF--Loss of Frame.
  • LOS--Loss of Signal.
Line Status The current SONET or SDH specific condition associated with the SONET/SDH line. One or more of the following conditions may exist:
  • Normal--The SONET/SDH line is operating normally.
  • AIS--Alarm Indication Signal.
  • RDI--Remote Defect Indication.
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:
  • Normal--The SONET/SDH path is operating normally.
  • STS-LPR--STS Loss of Pointer.
  • STS-AIS--STS Alarm Indication Signal.
  • Unequipped--The SONET Path is idle.
  • Mismatch--Signal Label Mismatch.
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:
  • Normal--The SONET/SDH VT is operating normally.
  • VT-LOP--VT Loss of Pointer.
  • V-AISL--VT Path Alarm Indication Signal.
  • VT-RDI--VT Path Remote Defection Indication.
  • VT-RFI--VT Path Remote Failure Indication.
  • Unequipped--The SONET VT is idle.
  • Mismatch--Signal Label Mismatch.

Task Topic Monitoring Authentication Failures

You can list the management systems that caused an authentication failure using the following procedure. Authentication failures occur when a management system sends an SNMP request with an incorrect community name.

The list shows all failures that have happened on the specified node.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select one or more nodes that are HP 9000s or Sun SPARCstations running the HP OpenView Extensible SNMP Agent software.
  2. Select Performance:Network Activity->SNMP->SNMP Authentication Failures.

Behavior

For each authentication failure that has occurred on the node, the following information is reported.
Unauthorized System The IP Address of the system causing the authentication failure.
Time since Failure The amount of time that has elapsed since the authentication failure occurred.

Task Topic Monitoring TCP Connections

You can list the TCP connection table for remote SNMP nodes using the following procedure.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select one or more nodes that support SNMP.
  2. Select Performance:Network Activity->TCP Connections.

Behavior

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.

Task Topic Monitoring Disk Space

You can list the available file system space on an HP OpenView SNMP Agent node using the following procedure.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select nodes that are an HP 9000s or Sun SPARCstations running the HP OpenView SNMP Agent software.
  2. Select Performance:Disk Space.

Behavior

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.

Configuration Management Tasks

Use the SNMP Data Presenter to perform the configuration management tasks.

You can access the SNMP Data Presenter from the HP OpenView Launcher or from the Network Presenter.

Launcher:

  1. Select the Tools tab.
  2. Expand the NNM category.
  3. Double-click on SNMP Data Presenter.
  4. From the SNMP Data Presenter, select the Configuration category in the top left pane.

Network Presenter:

  1. Select one or more nodes that support SNMP.
  2. Select Configuration:SNMP Data Presenter.

You can perform the following configuration management tasks using the using the SNMP Data Presenter.

Task Topic Viewing Interface Properties

You can 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.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select nodes that support SNMP.
  2. Select Configuration:Network Configuration->Interface Properties.

Behavior

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.

General Properties

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:
  • Disabled--The interface is administratively disabled.
  • Up--The interface is enabled and working normally.
  • DOWN--The interface is enabled but is not working properly.
  • Testing--The interface is in a testing mode.
  • Dormant--The interface is waiting for a connection to become active.
  • Missing--The interface is configured, but no hardware is present.
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:
  • bps--bits per second.
  • Kbps--Kilobits per second.
  • Mbps--Megabits per second.
  • Gbps--Gigabits per second.
  • Tbps--Terabits per second.
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.

Frame Relay Properties

Management Scheme The Data Link Connection Management scheme for the Frame Relay interface. Possible values are:
  • No LMI configured (no management scheme is in use)
  • LMI Revision 1
  • ANSI T1.617 Annex D
  • ANSI T1.617 Annex B
  • CCITT Q933 Annex B
  • ANSI T1.617a Annex D
Address Format The address format in use on the Frame Relay interface. Possible values are:
  • Q921 (13 bit DLCI)
  • Q922-M (11 bit DLCI)
  • Q922-N (10 bit DLCI)
  • Q911 Standard DLCI
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.

DS1/E1 Serial Line Properties

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:
  • DS1-ESF--Extended SuperFrame DS1.
  • DS1-ATT--AT&T D4 Format DS1.
  • E1--CCITT G.704.
  • E1-CRC--CCITT G.704 with CRC.
  • E1-MF--CCITT G.704 with TS16 Multiframing.
  • E1-CRC-MF--CCITT G,704 with CRC and TS16 Multiframing.
Line Coding The line coding technique used to maintain a synchronized data signal on the DS1 or E1 circuit. The possible values are:
  • JBZS--Jammed Bit Zero Suppression.
  • B8ZS--Bipolar Eight Zero Suppression.
  • HDB3--E1 Zero Code Suppression.
  • ZBTS1--Zero Byte Time Slot Interchange.
  • AMI--Alternate Mark Inversion.
Signaling The supported variation for signaling mode. Possible values are:
  • None--No bits are reserved for signaling on this channel.
  • Robbed Bit--T1 Robbed Bit Signaling is in use.
  • Channel Associated--E1 Channel Associated Signaling is in use.
  • Common Channel--Common Channel Signaling is in use (DS1 channel 24, E1 channel 16).
Clock Source The source of the clock used by the signaling mechanism to transmit data. Possible values are:
  • Received Clock--From the CPE (router); also known as Loop Timing.
  • Local Clock--A local clock source is in use.
  • Through Timing--The recovered received clock from another interface is also used for transmission on this interface.
Loopback Mode This field indicates if the interface is in loopback mode, and if so, what type of loopback mode. Possible values are:
  • Off--The DS1 interface is in normal transmission state.
  • Payload Loop--The received signal is looped after it is processed by the interface's framing function.
  • Line Loop--The received signal is looped before being processed by the interface.
  • Other--Some other, vendor-specific, loopback.
Facilities The type of use of the facilities data link. Possible values are:
  • ANSI-T1-403--ANSI T1-403 recommended FDL exchange.
  • ATT-54016--AT&T Extended Superframe FDL exchange.
  • Other--Proprietary facilities exchange.
  • None--The facilities data link is not used.

DS3/E3 Serial Line Properties

Line Type The type of DS3 or E3 circuit. Possible values are:
  • DS3-M23--ANSI T1.107-1988 (Asynchronous).
  • DS3-SYNTRAN--ANSI T1.103-1988 (Synchronous).
  • DS3-CbitParity--NASI T1.107a-1989 (Asynchronous).
  • DS3-ClearChannel--ANSI T1.102-1987.
  • E3-Framed--CCITT G.751.
  • Es-PLCP--ETSI T/NA(91)18.
  • Other--Proprietary.
Line Coding The line coding technique used to maintain a synchronized data signal on the DS3 or E3 circuit. The possible values are:
  • B3ZS--Bipolar Three Zero Suppression.
  • HDB3--E3 Zero Code Suppression.
  • Other--Proprietary.
Clock Source The source of the clock used by the signaling mechanism to transmit data. Possible values are:
  • Received Clock--From the CPE (router); also known as Loop Timing.
  • Local Clock--A local clock source is in use.
  • Through Timing--The recovered received clock from another interface is also used for transmission on this interface.
Loopback Mode This field indicates if the interface is in loopback mode, and if so, what type of loopback mode. Possible values are:
  • Off--The DS3 interface is in normal transmission state.
  • Payload Loop--The received signal is looped after it is processed by the interface's framing function.
  • Line Loop--The received signal is looped before being processed by the interface.
  • Other--Some other, vendor-specific, loopback.
Facilities The type of use of the facilities data link. Possible values are:
  • ANSI-T1-403--ANSI T1-403 recommended FDL exchange.
  • ATT-54016--AT&T Extended Superframe FDL exchange.
  • Other--Proprietary facilities exchange.
  • None--The facilities data link is not used.
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.

SONET/SDH Interface Properties

Line Type The type of physical line attached to the interface. Possible values are:
  • SRSMF--Short Range Single Mode Fiber (optical).
  • LRSMF--Long Range Single Mode Fiber (optical).
  • MMF--Multi-mode Fiber (optical).
  • Coax--Coaxial Cable (electrical).
  • UTP--Unshielded Twisted Pair (electrical).
Line Coding The line coding in use for this interface. Possible values are:
  • NRZ--Non-Return to Zero (optical signals).
  • RZI--Return to Zero (optical signals).
  • B3ZS--Bipolar Three Zero Suppression (electrical signals).
  • CMI
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.

ATM Interface Properties

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:
  • Private
  • NSAP E164
  • Native E164
  • Other
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.

Task Topic Monitoring IP Addresses

You can list the IP and link addresses for the specified remote SNMP nodes using the following procedure.

This operation is useful for determining IP and non-IP addresses associated with a node without looking through configuration files.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select nodes that support SNMP.
  2. Select Configuration:Network Configuration->IP Addresses .

Behavior

For each interface on the specified node, the operation 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 IP 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.

Task Topic Monitoring IP Routing Table Information

You can list the routing table information for remote SNMP nodes using the following procedure. This information determines how IP packets are routed on the nodes.

This operation is useful for diagnosing connectivity problems (for example, one node cannot communicate with another).

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select a node that supports SNMP.
  2. Select Configuration:Network Configuration->IP Routing Table .

Behavior

For each node you specify, 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)
Interface The name of the interface that is used to reach the destination.

Task Topic Monitoring IP ARP Caches

You can list the ARP (Address Resolution Protocol) Cache table for remote SNMP nodes using the following procedure.

The ARP (Address Resolution Protocol) Cache operation is useful for diagnosing connectivity problems since it can tell you if two nodes have a different link address for a third node.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select a node that supports SNMP.
  2. Select Configuration:Network Configuration->IP ARP Cache .

Behavior

Each row in the ARP Cache table consists of:
Node The node name or IP address of the destination node.
Link Address The link address associated with the destination node.
Interface The interface name (of the specified node) that is used to access the destination node.

Task Topic Monitoring IP Services

You can list the services for which the specified remote SNMP nodes are configured to support.

This operation is useful for determining what services a node is configured to support. For example, if you wanted to know if a node is executing the telnet server, you could use the Services operation to see if the node is listening with telnet TCP port number 23.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select a node that supports SNMP.
  2. Select Configuration:Network Configuration->IP Services .

Behavior

For each node, the operation 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.

Task Topic Monitoring System Information

You can display the information about the system, such as system location and system contact.

Procedure

Click accessing the SNMP Data Presenter for information on how to display the data presenter.

  1. Specify or select a node that supports SNMP. If it also supports MIB-II and the operator has fully configured the device, additional information may be available.
  2. Select Configuration:System Information.

Behavior

The operation lists the information from the SNMP MIB-II system group.

You can view the following information about each node selected.