cc/td/doc/product/wanbu/vns/vns_30
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Reinstalling VNS Interface Drivers

Reinstalling VNS Interface Drivers

The interface drivers for the E1 Network Interface Cards (E1 NICs) and the Frame Relay Card are pre-installed at the factory. These drivers are supplied on tape in case there is an event that requires that they be reinstalled.

This appendix contains the following sections:


Note Never reinstall an VNS interface driver without first contacting the Cisco Product Support.

E1 NIC Driver Installation

Tape 3 contains the E1 NIC driver package (i.e., CoE1) and a readme file with these installation instructions. The CoE1 driver package is designed to run with Solaris 2.4, the operating system of the VNS. The tape is in tar format.

To extract the contents of the tape, follow these steps:

Step 1 Connect a tape drive to the VNS.

Step 2 Insert tape 3 into the tape drive.

Step 3 Extract the contents of the tape into a directory using the following command:

tar xvf /dev/<tape_dev>

where <tape_dev> should be replaced with the specific tape drive attached to your VNS.

The contents of the tape will be extracted under the directory: /tmp

Step 4 Change your working directory to the directory containing the E1 NIC driver, CoE1DRV.

cd /tmp/Release.2.1

Step 5 Add the driver package to the VNS with the command:

pkgadd -d \Qpwd\Q CoE1DRV

The system messages during pkgadd are self explanatory. The default installation of the directory of the E1 NIC driver package is /opt.

Step 6 Verify that the driver installed correctly with the following command:

pkginfo | grep CoE1DRV

A message similar to the following should be displayed:

system CoE1DRV CoSystems E1 Device Driver Release 2.9.1

If a similar line is not displayed, repeat the installation procedure, watching the screen closely for error messages.

E1 NIC Configuration

The E1 Line parameters of the E1 NIC must be changed to match the parameters of the CVM or CDP on the attached node. These parameters are similar to those configured with the node's configure circuit line (cnfcln) command. The parameters at the E1 NIC and the node's CVM or CDP must match one another.

To edit the E1 NIC configuration, use vi to edit the file:

/etc/default/comunich.sys

The following are the configurable parameters:

Line Coding

AMI or HDB3

Signaling

CAS or CCS

CRC

CRC disabled or enabled

Equalizer

75-ohm coaxial or 120-ohm twisted pair

International bit

Selected or not selected, bit value if selected

National bits

Selected or not selected, bit values if selected

Local loop back

Enabled or disabled

Remote loopback

Enabled or disabled

The parameters are declared as keyword=parameter pair. Each set is uniquely identified by unit number.

Starting the E1 NIC Driver Daemon

After you have set the E1 NIC configuration parameters, you can start the E1 NIC Driver Daemon by following these steps:

Step 1 Change your working directory to /opt/CoE1DRV/bin.

Step 2 To run the daemon, enter from the shell prompt

./comunichd -r

(if you have only one E1 NIC in your VNS) or

./comunichd -r -u

(if you have two E1 NICs in your VNS).

The LED on the E1 NIC should glow if the E1 NIC is up and the line is synchronized.

Deinstalling the E1 NIC Driver

To deinstall the E1 NIC driver, run:

pkgrm CoE1DRV

Frame Relay Card Driver Installation

To reinstall the Frame Relay Card driver, follow these steps:

Step 1 Login to your VNS as root.

Step 2 Connect a tape drive to your VNS.

Step 3 Insert Tape 1 into the tape drive.

Step 4 Type these commands:

#NONABI_SCRIPTS=TRUE
#export NONABI_SCRIPTS
# /etc/init.d/volmgt stop
# pkgadd -d /dev/????

Step 5 Reboot your VNS by entering the following Solaris command:

boot -r

(boot with reconfiguration)

As the VNS is rebooting, watch your terminal screen carefully for messages about address selection errors. If the system comes up without displaying any error messages, go to step 6. If an address selection error is indicated, to the Troubleshooting the Frame Relay Card Driver Installation section.

Step 6 Verify the installation, by entering the following command:

pkginfo -l | grep ADAX

The pkginfo program , with the -l for long argument, will list the Frame Relay Card drivers that have been installed. The output should appear similar to the following:

PKGINST: ADAXapcs NAME: ADAX apcs Driver VENDOR: Copyright ADAX, Inc., 1988 - 1996 PKGINST: ADAXfr NAME: ADAX Frame Relay/PPP VENDOR: ADAX, Inc.

If similar lines are not displayed, repeat the installation procedure, watching the screen closely for error messages.

Removing the Frame Relay Card Driver

To remove the Frame Relay Card driver, follow these steps:

Step 1 From the UNIX prompt, type the command:

# pkgrm

Step 2 Follow the menu-driven instructions for removing the software package. The pkgrm program displays a list of numbered options. Choose the number that corresponds to ADAX APC DRIVER and press Enter. A message similar to the following one will be displayed:

Confirm

Do you really want to remove ADAX APC BOARD DRIVER,
for APC-PCX/APC-MCX, Version x.x

Strike ENTER when ready
or ESC to stop.

Step 3 Press Enter. The pkgrm program displays these messages:

Checking . . .

Removing APC device driver . . .

The UNIX operating system will now be rebuilt.

The ADAX APC BOARD DRIVER,
APC-PCX/APC-MCX, Version 2.4.x is now removed.

You can now shut down the VNS and reboot it. If necessary, reinstall the Frame Relay Card software.

Frame Relay Card Configuration Files

The following VNS files are normally installed at the factory:

If the Frame Relay Card drivers have to be reinstalled, these files should be checked to see if they contain the factory settings.


Note In any of the file fragments shown here, the "#" character precedes comments on the same line.

Frame Relay General Configuration File (fr.cf)

The Frame Relay General Configuration file (fr.cf) is installed at /usr/net/fr/fr.cf. The contents of the fr.cf file should contain the following lines:

# # ADAX Frame Relay daemon configuration file # mode LAC # TCP/IP compatibility mode: ATT, SCO, LAC, or WOL prom YES debug 0 # debug level: 0 (off), 1, 3, 5, 7, 9 (most output) # End of fr.cf

Frame Relay Port Configuration File (fr_config)

The Frame Relay Port Configuration file (fr_config) is installed at /usr/net/fr/fr_config. The contents of fr_config should contain the following lines:

port 0 HOST RS449 N393 0 INARP NO port 8 PID 0xCC port 9 PID 0xDD TRANS # End of fr_config

The factory sets the following necessary parameters:

Frame Relay Mapping (fr_conv)

This Frame Relay Address Mapping file (fr_conv) is installed at /usr/net/fr/fr_conv. It normally includes the IP address to DLCI mapping for any IP networks accessible across frame relay.

This file will appear similar to the following:

# # ADAX Frame Relay IP address to DLCI (0, . . . , 1023) to port mapping # # IP Address Frame Relay DLCI Port 205.9.8.1 12 0 # Router's Serial 0 (SV+ gateway) # # Raw Frame Relay port - 35 0 35 9 # PRI using DLCI 35 # End of fr_conv

Network Command File (rc.inet)

This Network Command file (rc.inet) is installed at /usr/net/fr/rc.inet. It typically contains the appropriate network commands to enable routing across the VNS's IP Frame Relay network. This shell script is executed at boot time from /etc/rc2.d/S72fr (normally installed at the factory).

This file will appear similar to the following:

ifconfig frmux0 frhost plumb -arp ifconfig frmux0 frhost up # # frnet is defined in /etc/networks # frhost is defined in /etc/inet/hosts route add net frnet frhost 0 # # Use cisco (router) serial port as gateway # nms-net is defined in /etc/networks # nms-net-gateway is defined in /etc/inet/hosts # /usr/net/fr/set_addr -h \Qnawk '/frhost/ { print \$1 } ' /etc/hosts\Q -port 0 # End of rc.inet
Note There must be only one "frhost" present in /etc/inet/hosts for the "set_addr" line to work.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.