OPENLANE DCE MANAGER USER’S GUIDE Document No.
Copyright E 1999 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, 8545 126th Ave. N.
Contents About This Guide H H H H H H H 1 Document Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product-Related Documents . . . . . . . .
Contents 2 Using the DCE Manager H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 H Discovering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Discovering Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Discovering FrameSaver Remote Site Units . . . . . . . . . . . . . . . . . . . . 2-3 H Accessing the DCE Manager . . . . . . . . . . .
Contents 4 Configuring Devices and Device Interfaces H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 H Setting Community Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 H Starting a Telnet Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 H Setting or Changing Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6 Performing Loopback Modes and Pattern Tests H Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 H Isolating Device Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Determining the Type of Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Diagnosing Problems with the Management Link . . . . . . . . . . . . . . . .
About This Guide Document Purpose The OpenLanet Data Communications Equipment (DCE) Manager Release 4.3 is a collection of components that run as part of the Hewlett-Packard (HP) OpenView (herein referred to as OpenView) or NetView network management system.
About This Guide H NextEDGEt 9192 and 9195 Multiservices Access System H FrameSaver SLV 9580 T3 ATM DSU H ACCULINK Access Controller (AAC), Front Load and Full Expansion H Digital Access and Cross-Connect System (DACS) Low-Speed Interface Unit (LSIU) See Table 1-1, OpenLane DCE Manager Functions, for a complete list of supported devices. Document Audience The DCE Manager can be installed and used on Hewlett Packard (HP-UX), Sun (Solaris), and IBM (AIX) systems.
About This Guide Section Description Chapter 6 Performing Loopback Modes and Pattern Tests. Describes how to set loopback modes and send pattern tests to check the integrity and performance of a device. Also describes how to use loopback modes and pattern tests to isolate a problem on a device or the line. Appendix A SNMP Management Connectivity. Gives examples of management connectivity, including device configuration. Glossary Defines acronyms and terms used in this document.
About This Guide Product-Related Documents viii Document Number Document Title 582-510-100 ACCULINK Access Controller Reference Guide 3150-A2-GB21 ACCULINK 315x CSU Operator’s Guide 3160-A2-GB21 ACCULINK 3160, 3161, 3164, and 3165 DSU/CSU Operator’s Guide 3170-A2-GB20 ACCULINK 3172 and 3174 DSU/CSU Operator’s Guide 3360-A2-GB20 ACCULINK 3360, 3364, AND 3365 E1 NTU Operator’s Guide 5216-A2-GN10 Hotwire 5216 Remote Termination Unit (RTU) Customer Premises Installation Instructions 5246-A2-GN1
About This Guide 7800-A2-GB26-80 Document Number Document Title 8000-A2-GB27 Hotwire DSLAM for 8310/8312 MVL and 8510 RADSL Cards Network Configuration Guide 8000-A2-GB90 Hotwire 8100/8200 Interworking Packet Concentrator (IPC) User’s Guide (Feature No.
About This Guide Contact your sales or service representative to order additional product documentation. Most Paradyne documents are also available on the World Wide Web at: http://www.paradyne.com Select Library → Technical Manuals See the following documents for more information about services, applications, and network deployment for your specific devices: H DSL Sourcebook H Frame Relay Sourcebook Reference Documents Black, Ulysses. Network Management Standards. The OSI, SNMP and CMOL Protocols.
About This Guide World Wide Web Sites The following sections list World Wide Web sites that may be of interest. At the time of this writing, the web sites are current. HP OpenView Web Site For the latest information on HP OpenView, visit the following web site: http://www.openview.hp.com/index.asp For information on installing and setting up OpenView, see the Hewlett Packard (HP) Network Node Manager Products Installation Guide.
About This Guide OpenLane DSLAM Configurator Web Site The OpenLane DSLAM Configurator is used to quickly and efficiently configure a DSLAM chassis and its associated endpoints.
Setting Up the DCE Manager 1 OpenLane DCE Manager Overview The OpenLane DCE Manager provides an integrated set of components that you can use to administer, configure, monitor and diagnose Paradyne’s Simple Network Management Protocol (SNMP) network access devices. It is available on HP-UX and Solaris systems running the HP OpenView Network Node Manager (herein referred to as OpenView), or AIX systems running NetView.
Setting Up the DCE Manager Features of the DCE Manager The DCE Manager offers several features that you can use to manage devices and device interfaces, including Data Link Connection Identifiers (DLCIs), Network Access Module (NAM) cards, Management Communication Controller (MCC) cards, Digital Subscriber Lines (DSL) cards and DSL endpoints.
Setting Up the DCE Manager Devices Supported by the DCE Manager Table 1-1 lists the supported devices and major functions of the DCE Manager. A check mark (n) indicates that a function is supported. For a complete list and description of functions, see Using the DCE Manager Components in Chapter 2, Using the DCE Manager. Table 1-1. OpenLane DCE Manager Functions Functions Config Dev.
Setting Up the DCE Manager Preparing to Install the DCE Manager Before you install the OpenLane DCE Manager Release 4.3, check the contents of the distribution package and ensure that your system meets the requirements as outlined in the following sections. In addition to the requirements listed, read the OpenView or NetView release notes, which provide the latest information on the use of each product. H For HP-UX and Solaris systems: /opt/OV/ReleaseNotes/attGEM/attGEMr1.
Setting Up the DCE Manager Verifying Hardware Requirements The following lists the minimum hardware requirements needed to install the DCE Manager on HP, Sun, or IBM platforms: H 64 MB of RAM minimum H 50 MB of free hard disk space H 128 MB of swap space (for HP or SUN workstations only) H 196 MB of swap space (for IBM workstations only) Setting Kernel Parameters (HP-UX Only) Table 1-2 shows the recommended HP-UX kernel parameter settings. These parameters can be set using the sam command.
Setting Up the DCE Manager OpenView and NetView establish a management link to devices using one of the following methods: H Local Area Network (LAN), using a router or LAN adapter H Leased line H Dial-up connection Discovery and management of devices is straightforward over a LAN and leased-line connections. Once the hardware and software are configured, OpenView discovers the devices and maintains a continual diagnostic link to them.
Setting Up the DCE Manager Installing the DCE Manager The DCE Manager software is available on the World Wide Web (WWW) and on CD-ROM for HP-UX, Solaris, and AIX platforms. The following sections describe how to access and install the DCE Manager software. Installing the DCE Manager on HP-UX or Solaris This section describes how to download and install the DCE Manager software on HP-UX or Solaris operating platforms. " Procedure To install the DCE Manager on a HP-UX or Solaris system: 1.
Setting Up the DCE Manager 5. Start the install program. — If you downloaded the software from the World Wide Web, change to the directory where you uncompressed the file and run the installation program: cd ./DCEinstall — If you mounted the CD-ROM for HP systems: cd /tmp/cdrom/DCE/HP-UX10 ./DCEinstall — If you mounted the CD-ROM for Sun systems: cd /tmp/cdrom/DCE/SOLARIS2 ./DCEinstall 6. Respond to the installation prompts.
Setting Up the DCE Manager 8. Enter the software license key. The prompts you receive vary depending on whether or not you have a current license key. — If you have a software license key, the following prompt appears: Do you want to enter a new software key? (y/n) Enter y to enter the software license key. A new prompt appears. Enter n if you want to enter the software license key at a later date.
Setting Up the DCE Manager Installing the DCE Manager on AIX This section describes how to install the DCE Manager software on the AIX operating platforms. For information on the system commands used in the following procedure, refer to the AIX documentation set. " Procedure To install the DCE Manager on an AIX system: 1. Log in as root. 2. Set your path variables as follows: PATH=/usr/bin:$PATH:/usr/OV/bin export PATH 3. Access the install program.
Setting Up the DCE Manager 5. Specify whether or not you want to continue with the installation. The prompts vary depending on whether or not the DCE Manager is currently installed on your system. — If the DCE Manager is currently installed on your system, the following prompt appears: Do you want to remove the existing product? (y/n) Enter y to remove the installed version of the DCE Manager. After removing the installed version, the installation process asks if you want to install the DCE Manager.
Setting Up the DCE Manager 10. Unmount the CD-ROM: /etc/umount /tmp/cdrom 11. Exit from root. 12. Reboot your machine. The DCE Manager is automatically integrated into the NetView application. When you start the NetView application, the DCE Manager is available from the Configuration or Fault menus. Verifying the Installation The following sections provide you with the information you need to verify the installation of the DCE Manager software and the version of the DCE Manager software installed.
Setting Up the DCE Manager Determining the Version of the DCE Manager If you need to determine the version of the DCE Manager that is installed on your system, type the following at the system prompt: H For HP-UX and Solaris systems: /opt/OV/bin/attGEMRel H For AIX systems: /usr/OV/bin/attGEMRel Viewing Management Information Base (MIBs) Files The DCE Manager uses internal copies of MIB files to manage devices and device interfaces.
Setting Up the DCE Manager Removing the DCE Manager This section describes how to remove the DCE Manager from HP-UX, Solaris, or AIX operating platforms. " Procedure To remove the DCE Manager: 1. Log in as root on the system where the DCE Manager is installed. 2. Set the PATH variable and export the path using the commands for your operating platform: — For HP and Sun systems: PATH=$PATH:/opt/OV/bin:/sbin:/usr/sbin export PATH — For AIX systems: PATH = $PATH:/usr/OV/bin:/etc:/usr/etc export PATH 3.
Setting Up the DCE Manager NMS System Setup for the DCE Manager In most instances, an NMS workstation is connected to a router. With this setup, the NMS can easily access devices on other subnets. However, if the NMS is not attached to a router (such as a hub), you must create explicit routes to the other subnets. To do this, use the route command from the command line to manipulate the NMS routing table manually. See the route manpage for command line arguments.
Setting Up the DCE Manager 1-16 May 1999 7800-A2-GB26-80
Using the DCE Manager 2 Overview The OpenLane DCE Manager is integrated with OpenView during the installation process. Thus, any device that is discovered by OpenView can be managed using the components of the DCE Manager. A subset of DCE Manager functions are available from the OpenView menus. However, to use all of the features of the DCE Manager, or to perform an action on a device interface, you must open a Device Display.
Using the DCE Manager Each device in a submap is presented as a device icon. Device icons display the model number, device type, and the device selection name as shown in the following table. The color of each device icon presented in a submap represents the status of that device as described in Chapter 5, Monitoring Devices.
Using the DCE Manager Discovering FrameSaver Remote Site Units A FrameSaver remote site unit is not automatically discovered because it is not colocated and resides outside of the local domain of the FrameSaver unit and the NMS. To force discovery, add map or subinterface statements to the router at the central site to ensure that management traffic destined for the remote site units is routed to the FrameSaver unit at the central site.
Using the DCE Manager The following example shows the DCE Manager submenu cascade that is available from the OpenView Fault menu. See Components Available from the OpenView DCE Manager Submenus on page 2-6, which lists and describes the use of each of the previously listed functions. Accessing the Device Display from OpenView The DCE Manager Device Display is used to perform operations on devices and device interfaces.
Using the DCE Manager The following figure is an example of a DCE Manager Device Display window. Using the menus or toolbar within the Display Device, you can perform various operations on a device or device interface. Using the DCE Manager Components You can access the DCE Manager components from both the OpenView and Device Display menus. The OpenView menus offer those DCE Manager components that can be performed on a device only.
Using the DCE Manager Components Available from the DCE Manager Submenus The DCE Manager is available from the OpenView Configuration and Fault menus as a menu item. Selecting the DCE Manager from either menu provides a submenu of DCE Manager functions. Table 2-1 and 2-2 list and describe these components. Table 2-1.
Using the DCE Manager Components Available from the Device Display Menus The DCE Manager Device Display menus contain options which you can use to perform various operations on devices and device interfaces. Likewise, the Device Display toolbar and pop-up menus (as described in the following sections) provide a shortcut to some of these menu items. Depending on the device or interface you are viewing, some options are not available. Table 2-3 lists and describes the Device Display menus. Table 2-3.
Using the DCE Manager Table 2-3. Device Display Menus (2 of 2) Menu Menu Item Description Diagnose Identity Displays information about the selected device, such as device type, model, release number, version number, device uptime, etc. Status Displays operational and administrative status on a device. Some of the fields can be modified. DLCI Status Displays details about DLCIs, such as the operational and administrative status, tests results, and Frames Dropped by Outbound Enforcement.
Using the DCE Manager Components Available from the Device Display Toolbar The Device Display toolbar appears below the menus and offers a shortcut to the most commonly used menu selections.
Using the DCE Manager Using the Device Display The DCE Manager Device Display window offers a front or rear view of a device. Each Device Display window specifies the DCE Manager component name, IP address, Hostname, or Device name. Component IP Address, Host, or Device Name Within the Device Display windows, device interfaces are represented by icons. Operations within the Device Display can be performed on the device itself or a device interface.
Using the DCE Manager Understanding the Device Display Interface Icons Icons are used to represent each of the device interfaces in the Device Display. The following table displays each icon used and specifies the interface it represents. Icon Interface RJ11 connector RJ48 connector DB9 DB15 DB25 DB26 DB50 V.35 Generic connector representing logical data interfaces. Within the Device Display, color is used to indicate the operational and administrative state of an interface.
Using the DCE Manager Performing an Operation on a Device Interface You can perform an operation on a device interface using the Device Display menus, toolbar, or pop-up menus. The following procedures describe how to select a device and perform an operation using any of these options. If a menu item or toolbar option is dimmed, it is unavailable for the device interface you selected. " Procedure To select a device interface and perform an operation from the menus or toolbar: 1.
Using the DCE Manager " Procedure To select a device interface and access the pop-up menu: 1. Position the cursor over an interface and press the right mouse button. A pop-up menu appears. 2. Select the operation you want to perform from the pop-up menu. The options available to you depend on the device interface you select. The menu items are described in Table 2-3, Device Display Menus. Position the cursor over a device interface icon and press the right mouse button to display the pop-up menu items.
Using the DCE Manager Managing Devices Behind the DSLAM Chassis A Device Display for the various DSLAM chassis displays the cards configured for each chassis. The Device Display for a DSLAM chassis varies depending on the type of chassis selected. There are three types of DSLAM chassis: H The 8600 DSLAM chassis is an independent, standalone system that consists of three slots, with one slot reserved for the MCC card and the remaining slots used to house the DSL cards.
Using the DCE Manager " Procedure To launch a Device Display of a 5446 or 79xx endpoint from the Device Display for a DSLAM chassis: 1. Open the Device Display for a DSLAM chassis: 2. Position the mouse over the DSL card interface and click on the right mouse button. A pop-up menu appears. 3. Select Remote Device Display from the pop-up menu. The Device Display for an endpoint appears. If an endpoint is not connected to the interface, this option is dimmed on the pop-up menu.
Using the DCE Manager " Procedure To launch a Device Display of an endpoint from an OpenView submap: 1. Open the Device Display for the DSLAM chassis. 2. Click on the Administer menu and select Show Submap. An OpenView submap that lists the available endpoints appears. 3. Double-click on endpoint icon to open the Device Display. A Device Display is available for the 5446 and 79xx endpoints only. For other endpoints, you can obtain information about the endpoints using the identity option.
Administering Devices 3 Overview Using the DCE Manager, you can perform various administrative operations, which include: H Updating device information H Setting polling intervals H Managing and unmanaging devices H Displaying other submaps H Resetting device firmware and cards Updating Device Information The DCE Manager maintains a device database, which provides configuration information for each device known to the DCE Manager.
Administering Devices " Procedure To update the DCE Manager’s device database: 1. Open a Device Display window. 2. Click on the Administer menu in the Device Display window and select Device Sync. On receipt of a Change Configuration Notification (CCN) trap, device synchronization occurs automatically. Polling Devices By default, devices are queried periodically for operational and administrative status, while the Device Display component is present.
Administering Devices You can change the default poll rate for all devices by changing the value of the attGEMdd*pollRate parameter in the /opt/OV/att/attGEM/GEMDD.res file (or the /usr/OV/att/attGEM/GEMDD.res file for AIX systems). The value of the parameter represents the poll rate in minutes. The default is 1 minute. To suspend polling, set the polling interval to zero (0).
Administering Devices Opening a Submap An OpenView submap presents a view of your network. You can open the submap that is associated with the device you are viewing. " Procedure To display the submap associated with a device: 1. Open a Device Display window. 2. Click on the Administer menu and select Show Submap. Resetting Devices and Cards Resetting a device or card performs a warm start of that device or card remotely. The following procedures describe how to reset a device or card.
Configuring Devices and Device Interfaces 4 Overview By using the DCE Manager, you can perform various configuration operations, which include: H Starting a Telnet session H Displaying and setting select device parameters H Storing multiple configuration images within a device’s memory H Adding, deleting, or modifying the Injection table (for 5446 devices only) H Saving and restoring a configuration to and from a file Before you set or change the configuration values of a known device or device i
Configuring Devices and Device Interfaces Setting Community Names The Community Names of the physical device is set from the Front Panel of the device itself, or by issuing commands in a Telnet session. To set the Read/Write Community Names of the device as configured in OpenView, you must use the SNMP Configuration dialog as described in the following procedure. " Procedure 1. Click on the OpenView Options menu and select SNMP Configuration. The SNMP Configuration dialog appears. 2.
Configuring Devices and Device Interfaces Starting a Telnet Session A Telnet session opens a separate terminal window, which you can use to access a devices’ craft interface. From the craft interface, you can perform various operations on a device as documented in the user documentation for that device. A Telnet session is started from a Device Display window or the OpenView submap. The following procedures describe how to start a Telnet session from either a Device Display or OpenView.
Configuring Devices and Device Interfaces Setting or Changing Configuration Options You can display configuration options for most devices, device interfaces, and DLCIs. With the exception of DLCIs, you can also set certain configuration options.
Configuring Devices and Device Interfaces Setting or Changing Configuration Parameters on a Device Interface To display and set configuration parameters for a device interface, use the Device Configuration dialog. Minimally, this dialog provides a description of the device interface, interface type, and speed of the interface in bits per second.
Configuring Devices and Device Interfaces Displaying and Modifying DLCI Options on FrameSaver Devices To display the current settings for DLCIs on FrameSaver devices, use the DLCI Configuration dialog. " Procedure To display or modify DLCI options: 1. Open the Device Display for a 912x or 962x. 2. Position the mouse over the Network DDS Frame Relay Server interface. A pop-up menu appears. 3. Select DLCI Options from the menu. A DLCI Configuration dialog similar to the following appears. 4.
Configuring Devices and Device Interfaces Creating Injection Table Configurations for 5446 RTUs The injection table specifies the address, mask, type and status of the service provider or host routes configured for 5446 RTUs as described in the following table. Table 4-1. Parameter Descriptions Parameter Description Address Specifies the address of the Network Address Provider (NAP), Service Provider, Host Address, or Default Gateway for 5446 RTUs. The address format is Z.x.x.
Configuring Devices and Device Interfaces For 5446 RTUs, the default Community Name is private, not public as it is with most devices. Ensure that you have set the Community Name as described in the Setting Community Names on page 4-2, before adding or modifying the injection table. Adding Entries to the Injection Table The injection table can contain up to four service provider entries and up to 27 host routes for each 5446 RTU. " Procedure To add an entry: 1. Open a Device Display for a 5446 RTU. 2.
Configuring Devices and Device Interfaces Modifying the Injection Table You can modify the address, mask, type, or status of an injection table entry. " Procedure To modify an injection table entry: 1. Open a Device Display for a 5446 RTU. 2. Position the cursor over a DSL interface and press the right mouse button. A pop-up menu appears. 3. Select Injection Table from the pop-up menu. The IP Injection dialog appears. 4. Click on the entry you want to modify. 5. Change the parameters as appropriate. 6.
Configuring Devices and Device Interfaces Copy Configuration You can create a duplicate or modified image of a device configuration and store it within the configuration area of the device itself. This is useful if you want to restore an image or if you want to have multiple configurations available. " Procedure To create a copy of a configuration image: 1. Select a device of which you want multiple configuration images. 2. Click on the OpenView Configuration menu and select DCE Manager.
Configuring Devices and Device Interfaces Saving and Restoring Device Configuration Images Device configurations set through the craft interface or the DCE Manager are stored in a configuration image on the device. Some devices support the transfer of a binary configuration image from a device to a UNIX file. This is referred to as uploading. Conversely, a configuration image stored in a UNIX file can be transferred from the UNIX file back to the device of origin only. This is called downloading.
Configuring Devices and Device Interfaces 4. Log into the Telnet dialog as either Superuser or Manager. You are then prompted to enter your password in a Telnet dialog similar to the following. 5. Enter the name of file in the Configuration Data File text input file in the Upload/Download dialog where the image is to be stored. 6. Select Upload from the Upload/Download dialog. 7. Click on the Apply button in the Upload/Download dialog.
Configuring Devices and Device Interfaces Downloading Configuration Images A configuration image from an AAC device that has been uploaded and stored in a UNIX file can be restored by performing a download operation. CAUTION: A configuration image retains the IP address of the device from which it is uploaded. If you choose to download a configuration image to a device other than the one you uploaded from originally, you must change the IP address. " Procedure To restore a configuration image: 1.
Configuring Devices and Device Interfaces 5. Click on the Select button in the Upload/Download dialog to search for a configuration image to download. 6. Select a file from the File Selector dialog, then click on OK. NOTE: You must not select a configuration image file that was uploaded from another device. Each configuration image contains information and options specific to the particular device from which the configuration image was transferred. 7. Click on Download in the Upload/Download dialog. 8.
Configuring Devices and Device Interfaces 9. Click on Close to close the Upload/Download dialog. 10. Click on the Telnet dialog. If the transfer was successful, the following message appears: Transfer is successful. Press any key to continue. 11. Press Return. You are prompted to reboot the system as follows: A reboot is required to activate the new configuration. OK to reboot the system (y/n)? Enter y to download the configuration image and reset the device.
Configuring Devices and Device Interfaces 4-16 May 1999 7800-A2-GB26-80
Monitoring Devices 5 Overview You can both identify and obtain status of devices and device interfaces using features of the DCE Manager. Specifically, you can: H Monitor devices and device interfaces through the use of color-coded icons H Use the OpenView event log to view categories of events H Obtain a description of a device or device interface H Display detailed status on a device or device interface This chapter discusses these options in more detail.
Monitoring Devices Obtaining Device Status through Color Within the OpenView submaps, the color used for DCE Manager device icons is derived from the standard OpenView colors, which indicate the alarm state of a device. The following table lists the colors used and defines the associated alarm state. You can change these colors as described in the OpenView user documentation. Table 5-1. DCE Manager Device Icon Status Colors Color State Salmon In test.
Monitoring Devices Obtaining Device Interface Status through Color The DCE Manager Device Display dialog presents a visual view of the rear of a device. The color of each interface on the device shows the last known operational and administrative state of each interface. Table 5-2 lists and describes the use of each color. Table 5-2.
Monitoring Devices Monitoring Devices Using the OpenView Event Log When OpenView is started, an Event Categories dialog appears. The Event Categories dialog reads the OpenView Event Log and organizes all alarms/events into six groups. By selecting one of the Event Categories, you can open an Event Browser dialog for that group.
Monitoring Devices Each entry within the Event Browser dialog presents the following information: H Severity of the alarm or event, where color indicates severity level: Normal – Green Warning – Cyan Minor – Yellow Major – Orange Critical – Red H Date and time of the alarm or event H Name of the network element where the alarm or event originated H Description of the alarm or event Because devices have alarms and events that differ from those of OpenView, the DCE Manager provides its own m
Monitoring Devices Mapping DCE Manager Alarms and Events within OpenView Devices have alarm and event categories that differ from those used by OpenView. Thus, the DCE Manager provides its own mapping as described in Table 5-3 for some of the most common alarm and events. Table 5-3.
Monitoring Devices Understanding Paradyne Formats Used in the Event Browser Dialog The Message column of the OpenView (or NetView) Event Browser dialog displays a consistent format for SNMP traps for all Paradyne devices, with one exception (described later). The Message column displays from 2 to 4 fields of information separated by a colon (:).
Monitoring Devices Handling Proxy Address Resolution Protocol (ARP) for DSL Cards When configuring a Hotwire DSLAM system, the user can choose to have the DSL cards Proxy ARP for the remote 5446 Remote Termination Units (RTUs). This configuration is attractive in large networks because it simplifies the configuration needed on the router. In certain network configurations however, the use of Proxy ARP on the DSL cards causes OpenView to log a major event.
Monitoring Devices " Procedure To obtain the identity of a device from within OpenView: 1. Display an OpenView submap. 2. Click on the device you want to identify. 3. Click on the Fault menu and select DCE Manager. The DCE Manager submenu opens. 4. Select Identity from the DCE Manager submenu. A Device Identity dialog appears. The information displayed in the dialog varies depending on the device type you selected. The following examples shows the identity of a FrameSaver SLV 9124 device.
Monitoring Devices " Procedure To obtain the identity of a card: 1. Open a Device Display. The Device Display representation of the 916x and 926x devices display a NAM card, which supports the Identity component. Likewise, the Device Display for a DSLAM chassis displays the MCC card and DSL cards, which support the Identity component also. 2. Position the mouse over the card you want to examine and press the right mouse button. A pop-up menu appears. 3. Select Identity from the pop-up menu.
Monitoring Devices Obtaining the Status of Devices and Interfaces When you request status on a device or device interface, operational status is displayed always and, depending on the type of device you selected, administrative status can also be displayed. A status request at the DSL or NAM card level provides the operational status of each port on a card. You can obtain status information on a device from within OpenView or a Device Display.
Monitoring Devices " Procedure To obtain status on a device from within a Device Display: 1. Open a Device Display. 2. Click on the Diagnose menu and select Status, or press the Status button on the toolbar. A Device H & S dialog is displayed, where H & S represents Health and Status. " Procedure To obtain status on a device interface: 1. Open a Device Display. 2. Position the mouse over the device interface you want to examine and press the right mouse button. A pop-up menu appears. 3.
Monitoring Devices The following is an example of an SLV Status dialog: The following is an example of a VP/VC SLV Status dialog: 7800-A2-GB26-80 May 1999 5-13
Monitoring Devices " Procedure To obtain status on the MCC, DSL, or NAM card: 1. Open a Device Display that contains the MCC, DSL, or NAM card. 2. Press the right mouse button over the MCC, DSL, or NAM card. A pop-up menu appears. You can select this option from both the Diagnose menu and toolbar also. 3. Select Status from the pop-up menu. A Status dialog appears. The following example shows Health and Status for DSL card.
Monitoring Devices Monitoring Interface Status on AAC Devices A size limit has been implemented on the number of SNMP requests that can be sent to an ACC device. This size limit varies depending on the firmware revision and the network connectivity of the AAC device. The DCE Manager Device Display has a default limit set on the number of interface status requests that can be sent to an ACC device in a single SNMP request. The default limit is 5.
Monitoring Devices 5-16 May 1999 7800-A2-GB26-80
Performing Loopback Modes and Pattern Tests 6 Overview Loopback modes and pattern tests check the integrity and performance of network devices and, to some extent, the network itself. This chapter describes how to: H Isolate device problems H Use loopback modes H Use pattern tests H Run tests Isolating Device Problems There are several ways that you are notified of problems with a device, and several methods you can use to resolve it.
Performing Loopback Modes and Pattern Tests Determining the Type of Problems The following table highlights some of the more common problems you can encounter when working with devices. Table 6-1. Device Troubleshooting Table Notification Problem Go To . . . OpenView submap displays a device symbol in blue (unknown). Connection between management system and device has been lost. Diagnosing Problems with the Management Link on page 6-3 OpenView submap displays a device symbol in red.
Performing Loopback Modes and Pattern Tests Diagnosing Problems with the Management Link You can manage a device from OpenView through an Ethernet, leased-line, or dial-up connection. If the management connection is lost to a functional (green) device, the device symbol that is displayed on the OpenView submap turns blue and the line connected to it turns red. The colors of the interface symbols on the Device Display correspond to their last known states.
Performing Loopback Modes and Pattern Tests Using Loopback Modes The following sections discuss the various type of loopback modes available and describes how to use each. Although only DCE Manager supported devices are used in the following examples, the loopback modes and pattern tests are defined in MIBs. Line Loopback The Line Loopback (LLB) mode loops the information received on the Network T1 interface back to the network as close to the network interface as possible.
Performing Loopback Modes and Pattern Tests Payload Loopback The Payload Loopback (PLB) mode loops the information received on the Network T1 interface back to the network after it has passed through the receive and transmit framing section (i.e., the CSU) of the DSU/CSU. This loopback is useful for determining whether the problem is with the T1 facility or in the circuitry of the remote device.
Performing Loopback Modes and Pattern Tests Connectivity Tests (PVCs Only) The Connectivity Test is a PVC loopback test, which is unique to 962x and 912x devices only. Other available tests devices are described throughout the chapter. " Procedure To open the dialog for PVC loopback tests on 962x and 912x devices: 1. Open a Device Display for a 962x or 912x device. 2. Position the cursor over an active interface and press the right mouse button. A pop-up menu appears. 3.
Performing Loopback Modes and Pattern Tests DTE Loopback The DTE Loopback (DLB) performs an equivalent function on the DTE T1 interface that the LLB does on the Network T1 interface (see the figure below). It is useful for isolating problems on the DTE T1 line. For the DLB, a DTE device or test equipment must generate data to be looped back.
Performing Loopback Modes and Pattern Tests Data Channel Loopback The Data Channel Loopback (DCLB) loops the data for a particular synchronous data port back to the network interface after the information has passed all the way through the DSU/CSU (i.e., just before it is sent to the customer’s equipment, either through the Network T1 interface or the DTE T1 interface, see the figure below). It is useful for verifying the end-to-end integrity of a circuit for a particular interface.
Performing Loopback Modes and Pattern Tests As described in Using Loopback Modes on page 6-4 and Using Pattern Tests on page 6-11, the remote loopback Send V.54 Up Code and Send FT1 Up Code put a remote device in loopback mode, while Send V.54 Down Code and Send FT1 Down Code take a remote device out of loopback mode. You can use these codes in troubleshooting, as described in Using Pattern Tests on page 6-11.
Performing Loopback Modes and Pattern Tests CSU or External Network Loopback CSU loopback is an external loopback that is located as close as possible to the network interface (see figure below). DSU DTE Port DTE Interface CSU DDS Network Port Aggregate DDS Leased-Line Access Unit 496-14929 DSU or Internal Network Loopback DSU loopback is an Internal loopback that is located as close as possible to the customer interface serving the DTE (see figure below).
Performing Loopback Modes and Pattern Tests External DTE Loopback DTE External Loopback loops the user data port back to the DTE interface on a per-interface basis without affecting operation of the remaining interfaces. This loopback is located as close as possible to the customer interface (see figure below).
Performing Loopback Modes and Pattern Tests The following figure demonstrates a pattern test combined with a loopback mode that tests both ends of a circuit. DEVICE B DEVICE A DSU/CSU Sending/Monitoring a QRSS Test Pattern T1 NETWORK DSU/CSU in Loopback (LLB or PLB) 496-15097 NOTE: You can send a 1-in-8 pattern out of the Network T1 interface, but you cannot monitor it.
Performing Loopback Modes and Pattern Tests Setting the Community Name Before you set loopback modes or run pattern tests, ensure that the Write Community Name matches that of the device on which you want perform the action. To set the Write Community Name from within OpenView: 1. Click on the Options menu and select SNMP Configuration. The SNMP Configuration dialog appears. 2. Fill out fields as appropriate and click on OK to apply the changes and close the dialog.
Performing Loopback Modes and Pattern Tests Starting Tests Pattern tests can test one end of a circuit or both ends of a circuit. This section describes how to use each of these methods. To test one end of a circuit, you must have a device (Device A) send a pattern to another device (Device B), where Device B monitors the integrity of the pattern and tests one end of a circuit as shown in the following figure.
Performing Loopback Modes and Pattern Tests To test both ends of a circuit, you must have a device (Device A) send a pattern to another device (Device B). Device B loops the pattern back to Device A so that Device A can monitor the integrity of the pattern and test both ends of the circuit as shown in the following figure. DEVICE B DEVICE A T1 NETWORK Sending/Monitoring a Test Pattern In Loopback 496-15094 " Procedure To test both ends of a circuit: 1.
Performing Loopback Modes and Pattern Tests Checking the Pattern Test Results When you start a pattern test, loopback test, or both, a dialog similar to the following appears. Using the dialog, you can select the type of test you want to run, and the results of the test are displayed in the Results field of the dialog. The following results can be returned from a Monitor Pattern test. H In Sync No Bit Errors Indicates that the device is operational.
SNMP Management Connectivity A Overview This appendix provides examples of device management through LAN adapters, routers, and PPP/SLIP connections. Also included are the device settings used to achieve this connectivity. These examples do not represent all the possible configurations. Connecting Devices through a LAN Adapter LAN adapters connect devices to Ethernet networks as shown in Figure A-1. The figure shows a 3364 or 9621 device connected to a LAN adapter.
SNMP Management Connectivity 3364 Device Configuration The following device settings configure a 3364 device for the operation depicted in Figure A-1. Refer to the ACCULINK 336x E1 Network Termination Unit Operator’s Guide for a description of how to configure the device using the device’s front-panel interface. A-2 User Options Value Self-Test Enab Com Use SNMP Com Typed Async Com Clk Int, Ext Com Rate 19.
SNMP Management Connectivity 7800-A2-GB26-80 General SNMP Options Value System Name 3364dev System Location NJMIS System Contact Charlie Parker CommunityName1 Public Access 1 R/W CommunityName2 not used Access 2 not used IP Adr XXX.020.041.221 NetMask 255.255.255.000 Com IP Adr XXX.020.041.221 Com NetMask 255.255.255.000 Com Link PPP Aux IP Adr not used Aux NetMask not used Def Netwk Com SNMP Trap Options Value Num Trap Mgrs 1 Trap 1 IP Adr XXX.020.040.
SNMP Management Connectivity 9621 Device Configuration The following device settings configure a 9621 device for the operation depicted in Figure A-1. Refer to the FrameSaver 9620 User’s Guide for a description of how to configure the device using the device’s terminal interface. A-4 User Interface Options: Communication Port Value Port Use Net Link Port Type Asynchronous Data Rate (Kbps) 19.
SNMP Management Connectivity Management and Communications Options: Value Communications Protocol Node IP Address XXX.020.040.197 Node Subnet Mask 255.255.255.000 Communication Port IP Address XXX.020.040.197 Communication Port Subnet Mask 255.255.255.000 Communication Port Link Protocol PPP Alternate COM Port IP Address XXX.020.021.002 Alternate COM Port Subnet Mask 255.255.255.
SNMP Management Connectivity Connecting Devices Through a Router Figure A-2 shows an AAC device connected to a LAN router. The device configurations that enable this type of connectivity are given in AAC Device Configuration. Management Systems HP Openview (XXX.020.040.021) Ethernet LAN Router XXX.20.41.143 (AAC) Network 496-15158 Figure A-2.
SNMP Management Connectivity Connecting Devices Through SLIP/PPP Connections Figure A-3 shows an 3174 device connected to the management system through a PPP Connection. The device configurations that enable this type of connectivity are given in 3174 Device Configuration on page A-8. Management Systems HP Openview (XXX.20.197.1) XXX.20.XXX.2 (3174) Network SNMP PPP/SLIP Figure A-3.
SNMP Management Connectivity 3174 Device Configuration The following device settings configure a 3174 device for operation as shown in Figure A-3. Refer to the ACCULINK 317x E1 Data Service Unit /Channel Service Unit Operator’s Guide for a description of how to configure the device using the device’s front-panel interface. A-8 User Options Value Self-Test Enab Com Use SNMP Com Typed Sync Com Clk Int Com Rate 19.2 Aux Use SNMP Aux Rate 19.
SNMP Management Connectivity 7800-A2-GB26-80 General SNMP Options Value System Name 3174dev System Location NJMIS System Contact Charlie Parker CommunityName1 public Access 1 R/W CommunityName2 not used Access 2 not used IP Adr XXX.020.191.002 NetMask 255.255.255.000 Com IP Adr XXX.020.191.002 Com NetMask 255.255.255.000 Com Link PPP Aux IP Adr not used Aux NetMask not used Def Netwk Com SNMP Trap Options Value Num Trap Mgrs 1 Trap 1 IP Adr XXX.020.040.
SNMP Management Connectivity This page intentionally left blank.
Glossary 1-in-8 Test A test pattern consisting of a one (1) followed by seven zeros (on the network only). 511 A random bit test 511 bytes in length. AAC ACCULINK Access Controller. A T1 product which permits connection to a variety of network services. alert An occurrence of interest within the network. Alerts include alarms and change of status experienced by modems and data service units, as well as alarms experienced by multiplexers, and event messages reported by multiplexers.
Glossary buffer A storage device used to compensate for differences in the data flow rate when transmitting data from one device to another. busied out One of a device’s operational states. When a device is in the busy out (or make busy) state, it will not be able to answer calls. If the busied out device is on a rotary, the rotary will skip the device when servicing incoming calls. A device that has its dial line busied out may switch to the service line for further use.
Glossary DL DLB DTE Loopback. Loopback mode that loops the information received on the DTE T1 network interface back to the network as close to the network interface as possible. DLC DL Data Link Control Layer. SNA layer responsible for the transmission of data between two nodes over a physical link. DLCI Data Link Connection Identifier. The virtual circuit number corresponding to a particular connection between two destinations. This number is used as part of the frame relay header.
Glossary frame relay A high-speed connection-oriented packet switching WAN protocol using variable-length frames. frame relay header The DLCI identifier contained within the frame relay packet. frame relay switching The ability to route frame relay packets based on the source port and frame relay header (DLCI). The header contains a DLCI identifier that distinguishes the port for which the data is intended. FT1 Fractional Timing 1. ANSI standard for DCLB tests. HDLC High-Level Data Link Control.
Glossary NMS Network Management System. A computer system used for monitoring and controlling network devices. OOF Out Of Frame. An error condition in which frame synchronization bits are in error. out of threshold One or more of the analog parameter thresholds has been exceeded. The probable cause is poor line conditions or improper threshold settings. Thresholds may be set through NMS commands. pattern test A local test causing the device to transmit and monitor for a particular test pattern.
Glossary Sub-tree Truncation Downstream health and status information has been truncated due overflowed system limits with large amounts of health and status information in the subnetwork. Recover this information by sending device health and status commands to specific modems. synchronous transmission Transmission in which the data characters and bits are transmitted at a fixed rate with transmitter and receiver synchronized.
Index Numbers 3100 and 3300 devices, functions supported, 5100 devices, functions supported, 1-3 5216 and 5246 devices, functions supported, 5446 devices functions supported, 1-3 modifying injection table, 4-7 5446 RTUs, discovery of endpoints, 2-2 7110 and 7112 devices, functions supported, 7610 and 7612 devices, functions supported, 797x and 798x devices, functions supported, 79xx endpoints, discovery of, 2-2 8100 and 8200 devices, functions supported, 8310 devices, functions supported, 1-3 8510 devices,
Index D DACS LSIU devices, functions supported, 1-3 Data Channel Loopback, 6-8 Data Link Connection Identifier, setting options, 4-6 Data Terminal Loopback, 6-8 DCE Manager accessing from NetView, 2-3 accessing from OpenView, 1-15, 2-3 administrative tasks, types of, 1-2 backing up and restoring images, 4-11 changing AAC size limit, 5-15 components of, 2-5 configuration operations, types of, 1-2 configuring devices, 4-1 copying configuration images, 4-10 determining state of devices, 5-11 determining versi
Index using External Network Loopback, 6-10 using Internal Network Loopback, 6-10 using Line Loopback, 6-4 using Payload Loopback, 6-5 using pop-up menus, 2-8 using Repeater Loopback, 6-7 device management, examples of, A-1 device requirements, 1-5 device status obtaining from Device Display, 5-12 obtaining through color, 5-2 devices adding to network, 3-1 alarm descriptions, 5-2 alarm mapping, 5-6 backing up and restoring images, 4-11 configuring, 4-1 connecting through SLIP/PPP, A-7 copying configuration
Index F M FrameSaver devices, discovering remote site units, 2-3 Management Information Base Files, 1-13 management link diagnosing problems, 6-3 losing connection, 6-3 MCC cards obtaining identity of, 5-10 obtaining status, 5-14 resetting, 3-4 setting community names, 4-2 menus, accessing components, 2-6 MIB files, browsing, 1-13 monitoring operations, types of, 1-2 H hardware requirements, 1-5 Health and Status dialogs, 5-11 Help menu, contents of, 2-8 Hewlett-Packard, Network Node Manager, 1-4 HP Op
Index submaps definition of, 2-1 identifying devices, 5-9 opening , 3-4 opening a Device Display, 2-4 use of device icons, 2-2 systems installing DCE Manager on AIX, 1-10 on HP-UX and Solaris, 1-7 removing DCE Manager, 1-14 requirements for OpenView, 1-6 setting HP-UX kernel parameters, 1-5 supported platforms, 1-4 using with AIX, 1-4 using with HP-UX, 1-4 using with Solaris, 1-4 P parameters, displaying on a device, 4-4 pattern tests, 6-1 checking community names, 6-13 checking results, 6-16 obtaining st
