Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
ACC Installation and Configuration Guide > Chapter 2 Software Installation and Verification

Installation Verification

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The loopback test can be used to verify that the ACC hardware and software have been properly installed, and are functional.

NOTE: This test assumes that at least one ACC multiplexer card will be used. If no multiplexer cards will be used on the system, refer to the section “Systems Without Mux Cards”.

Loopback Configuration Requirements

The ACC product provides a loopback protocol module (PORTTEST) which is included in the download file. This can be used to run a loopback test which exercises the ACC multiplexer card, any attached multiplexer interchange panel or cable, and the specified multiplexer port. The loopback test is run using the loopback test feature (the lb command of the zmntr utility. (See the ACC Utilities Reference Guide.)

The test requires the following:

  • At least one ACC Mux card must be installed into the system, and it must have a multiplexer interchange panel (or output cable if the card is 2-Channel) attached.

  • The ACC product must be installed and the system must have been rebuilt and rebooted.

  • The external loopback test, which can be used to test a specific port, requires that a loopback hood be attached to that port. (If a loopback hood is not available, an internal loopback test can be run which just exercises the interface card.)

  • For dual interface configurations, only one ACC multiplexer card should be attached to the multiplexer panel at a time.

NOTE: The 4-channel E1/T1 and 8-channel PCI ACC cards do not require any configuration to perform the ZMNTR "LB" loopback test, with the exception that a loopback hood must be connected to a port in order to run an "External" loop test. This section of the manual does not apply for these card types.

Cabling and Clock Source Requirements

When testing a single port looped back on itself, you connect a terminated connector or loopback hood to one of the ports on either the multiplexer panel or the (2-Channel) output cable. This serves to connect the Receive Clock (RC) to the External Timing Clock (ETC), or CCITT circuit 115 to CCITT circuit 113. Refer to the hardware reference manual for more details.

NOTE: A Loopback hood and cable is supplied with the Interchange Panel or Cable accessory.

For this type of loopback test, the Internal clock mode is required. (See the ACC Utilities Reference Guide for a description of valid ACC clock modes.) Referring to the sample configuration files in Appendix A “Files, Utilities, and Daemons” of this manual, note that the Port-Definition statements, which are automatically generated during installation, define clock mode for even-numbered ports as “Int”, and for odd-numbered ports as “Ext” or external clock mode as follows:

8-Channel & 2-Channel

Port-Definition
Port 0:0 RS232 57600 Int SDLC x1 NRZ
Port 0:1 RS232 57600 Ext SDLC x1 NRZ
Port 0:2 RS232 57600 Int SDLC x1 NRZ
Port 0:3 RS232 57600 Ext SDLC x1 NRZ
Port 0:4 RS232 57600 Int SDLC x1 NRZ
Port 0:5 RS232 57600 Ext SDLC x1 NRZ
Port 0:6 RS232 57600 Int SDLC x1 NRZ
Port 0:7 RS232 57600 Ext SDLC x1 NRZ

Port 1:0 RS232 57600 Int SDLC x1 NRZ
Port 1:1 RS232 57600 Ext SDLC x1 NRZ

NOTE: If you are using an 8-port PCI card with an external loopback cable, you need to specify the clocking parameter "ExIn" for an external DTE configured port.

If you intend to test a single port looped back on itself, it is convenient to choose one of the predefined even-numbered ports, since the configuration file provides the required clock mode. Alternatively, edit the loopback.answ configuration file to reflect your needs. The .answ file is generated with entries for an RS-232 panel, if you are using a different panel type (e.g. RS-449, X.21, V.35), you must edit the loopback.answ and set the port mode as appropriate for the specific card and panel type combination. Note that the "Ext" clocking may need to be modified to "ExIn" for other panel types (see note above).

If either the .answ or .tmem file does not exist, or no longer reflects the current location of the hardware, recreate this file and run ttgen on this file:

     # cd /opt/acc/cfg
# /opt/acc/lbin/acc_bld_lpbk -o loopback.answ \
-t sample_header -p loopback
# /opt/acc/bin/ttgen -o loopback.answ loopback.tmem

Do not proceed until ttgen has been run successfully.

More information on using /opt/acc/lbin/acc_bld_lpbk, a sample loopback configuration file, and an example of running ttgen is shown in the sections “Configuration Scripts” and “Sample ttgen Configuration File” of Appendix A.

Bringing Up ZCOM Mux Subsystem

Before any of the features of the ZCOM Mux Subsystem can be accessed, it must be started up by running zmasterd (located in /opt/acc/bin) with an appropriate .tmem file. The /opt/acc/cfg/loopback.tmem file should be used, followed by performing the loopback verification test:

# zmasterd cold /opt/acc/cfg/loopback.tmem

Messages indicating whether or not the ZCOM Mux subsystem was started successfully will be logged to the file /var/opt/acc/log/XXX.tlog, where XXX represents the day of the week (i.e. mon.tlog, tue.tlog, etc.).

The following listing is an example of what might be displayed when the ZCOM Mux subsystem is started successfully. Note that in this example, the /opt/acc/cfg/loopback.answ file is configured to start up two mux cards.

------------------------------------------------------------------
Tue Jun 20 16:45:38 1998: zmlog: message logging resumed
------------------------------------------------------------------
16:45:37 zmast 00101 Launched daemon zmlog, pid 10663.
16:45:37 zmast 00117   Zmasterd daemon start running...
16:45:37 zmast 00101 Launched daemon zmon, pid 10665.
16:45:38 zmon 00002 Resource manager (Rev 1.32) for ZCOM 6.2.0.0
16:45:38 zmon 00003 Cold start with: /opt/acc/cfg/loopback.tmem
16:45:39 zmon 00100 Card 0 starting up ...
16:45:39 zmon 00100 Card 1 starting up ...
16:45:46 zmon 00110 Card 0 startup successful, card READY
16:45:46 zmon 00110 Card 1 startup successful, card READY
16:45:46 zmon 00020 Cold start completed, ZCOM system ready
16:45:46 zmon 00004 Waiting for ZMON requests ...
16:45:46 zmast 00101 Launched daemon znode, pid 10674.
16:45:57 zcom 00165 Node 123 is now UP

Zmasterd starts the daemons that are listed with “start” statements in the /opt/acc/cfg/zmasterd_list file. For the base ACC product, zmasterd starts the zmlog logging facility, zmon, and znode.

If any error is reported during the start up procedure, it may be necessary to stop the ZCOM subsystem by running:

# /opt/acc/bin/zmasterd stop

The error should be addressed, and then the ZCOM subsystem should be restarted. Refer to the ACC Error Guide, for information on the messages reported by zmlog.

Note that file /opt/acc/cfg/zmasterd_list refers to /opt/acc/cfg/loopback.tmem by default. If another .tmem file is be used, you should update this file accordingly. Refer to the ACC Utilities Reference Guide for more information on the use of zmasterd.

Performing the Loopback Test

The loopback test is run by using the lb command of zmntr utility program.

You should run both the internal and external loopback tests (as well as either the RS-232 or V.35 test on 8-Channel interfaces). This will verify the following:

  • The ACC Mux card has been properly installed, and has been recognized by the HP-UX system.

  • The ACC driver software has been configured into the system properly.

  • The ZCOM Mux subsystem has been started up successfully.

  • The ACC interface card, as well as the mux panel (or cabling) and the mux ports within that panel can be communicated with (at least those ports that have been specified in the test).

NOTE: The .answ configuration files provided with the ACC product include the appropriate configuration for using the zmntr loopback test. Refer to the ACC Utilities Reference Guide for more information on zmntr, its loopback test options, and the related configuration requirements.

The following two examples show loopback tests being performed on port 0 of mux 1 (Z7200A card).

In the first example, the port is not connected to a loopback hood. The i test option is used which performs internal checks on the interface card only. In this example, the interface card is good and all tests pass.

Example 1

ZMNTR> lb 1 0 i

Loopback test on Mux 01 port 0, zlu 0710
Loopback protocol functionality .. OK
RS232 RTS/CTS internal loopback .. OK
RS232 DTR/DCD internal loopback .. OK
ISCC data loopback test .......... OK
RS232 internal data loopback ...... OK

In the second example, both internal and external tests are performed by using the ie test option. In this example, the loopback hood is not connected to the port being tested, and therefore the external tests fail.

Example 2

ZMNTR> lb 1 0 ie

Loopback test on Mux 01 port 0, zlu 0710
Loopback protocol functionality .. OK
RS232 RTS/CTS internal loopback .. OK
RS232 RTS/CTS external loopback .. Test failed (RTS/CTS)
RS232 DTR/DCD internal loopback .. OK
RS232 DTR/DCD external loopback .. Test failed (DTR/DCD)
RS232 DTR/DSR external loopback .. Test failed (DTR/DCD)
ISCC data loopback test .......... OK
RS232 internal data loopback ..... OK
RS232 external data loopback ..... Data test timed out

For a 4-port E1/T1 Mux card, the results of these same test would appear as follows:

ZMNTR> lb 1 0 i

Internal loopback on card 1 port 0 :Passed
ZMNTR> lb 1 0 ie

Internal loopback on card 1 port 0 :Passed
Loopback message lost
External loopback on card 1 port 0 :Failed

ZMNTR> exit
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.