Using Technician Interface Software BayRS Version 13.00 Site Manager Software Version 7.00 Part No.
4401 Great America Parkway Santa Clara, CA 95054 8 Federal Street Billerica, MA 01821 Copyright © 1998 Bay Networks, Inc. All rights reserved. Printed in the USA. October 1998. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.
Bay Networks, Inc. Software License Agreement NOTICE: Please carefully read this license agreement before copying or using the accompanying software or installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE.
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs. 4. Limitation of liability.
Contents Preface Before You Begin .............................................................................................................xix Text Conventions ............................................................................................................. xx Acronyms ........................................................................................................................xxii Bay Networks Technical Publications ................................................................
Console Port Parameters ...............................................................................................2-5 Using Autoscript Files ...................................................................................................2-19 Sample Autoscript Files .........................................................................................2-20 Customizing Autoscript Files ..................................................................................
Transferring a File .........................................................................................................4-13 In-Band File Transfers ............................................................................................4-14 Out-of-Band File Transfers .....................................................................................4-17 Displaying the Contents of a File ..................................................................................4-17 Deleting a File ........
Chapter 6 Managing Events Overview .........................................................................................................................6-2 Logging and Displaying Event Messages .......................................................................6-2 Applying Write Filters to the Events Log ..................................................................6-3 Displaying Active Write Filters ..................................................................................
Configuring Scheduled Boot Services ..........................................................................8-14 Adding Scheduled Boot Services to a Router ........................................................8-14 Scheduling Boot Events .........................................................................................8-15 Managing Scheduled Boot Services ......................................................................8-20 Disabling or Reenabling Scheduled Boot Services on a Router ........
Enabling and Disabling SecurID Authentication ...........................................................8-50 Enabling SecurID Authentication ............................................................................8-50 Disabling SecurID Authentication ...........................................................................8-52 Managing SNMP Secure Mode ....................................................................................8-53 Setting the Router to Operate in Secure Mode ................
Chapter 9 Managing Aliases Creating and Displaying an Alias ....................................................................................9-2 Inserting Parameters in an Alias ..............................................................................9-3 Inserting Character Strings in an Alias .....................................................................9-5 Debugging Aliases ..........................................................................................................
Hardware Configuration ................................................................................................. B-9 Out-of-Band File Transfers from a UNIX Workstation .................................................. B-10 Opening a Connection .......................................................................................... B-10 Transferring Files from a Router to a UNIX Workstation ....................................... B-10 Transferring Files from a UNIX Workstation to a Router ........
Configuring Syslogd on a UNIX Workstation ............................................................... C-13 Configuring Syslog on the Router ................................................................................ C-15 Task 1: Logging In to the Router’s Technician Interface ........................................ C-15 Task 2: Defining a Slot Mask for Syslog on the Router ......................................... C-16 Task 3: Creating Syslog on the Router .........................................
Figures Figure 1-1. SecurID Login Procedure and Interface Dialog .......................................1-8 Figure 1-2. SecurID PIN Assignment Procedure and Interface Dialog ......................1-9 Figure 1-3. Technician Interface Welcome Screen ...................................................1-10 Figure 4-1. Sample Dinfo Display ...............................................................................4-6 Figure 4-2. Sample NVFS Directory Listing ........................................
Figure C-1. Syslog and Syslogd Operations .............................................................. C-3 Figure C-2. Router Event Message Filtering for One Host ........................................ C-5 Figure C-3. Syslog Message Encapsulation .............................................................. C-9 Figure C-4. Syslog Message Composition ...............................................................
Tables Table 4-1. NVFS Commands ....................................................................................4-3 Table 4-2. Router Software Images ..........................................................................4-4 Table 5-1. DOS File Management Commands ........................................................5-3 Table 5-2. DOS File Attributes ................................................................................5-11 Table 5-3. DOS File Attributes Table 6-1.
Preface The Technician Interface is a command-line interface that lets you manage Bay Networks routers. You can use the Technician Interface to install a router, maintain or diagnose router operation, and monitor and configure certain basic router functions. Before You Begin If you are responsible for installing or maintaining a Bay Networks® router or BayStream™ platform using Bay Networks Technician Interface commands, you need to read this guide.
Using Technician Interface Software Note: Before you can access the Technician Interface using Telnet, the platform must have at least one assigned IP address. Although there is no limit to the number of Telnet connections that you can make to the Technician Interface, we recommend that you establish no more than one Telnet session per platform.
Preface ellipsis points (. . . ) Indicate that you repeat the last element of the command as needed. Example: If the command syntax is: ethernet/2/1 [ ] . . ., you enter ethernet/2/1 and as many parameter-value pairs as needed. italic text Indicates file and directory names, new terms, book titles, and variables in command syntax descriptions. Where a variable is two or more words, the words are connected by an underscore.
Using Technician Interface Software Acronyms xxii ACE advanced communications engine APPN Advanced Peer-to-Peer Networking ARP Address Resolution Protocol AT Appletalk ATM asynchronous transfer mode AURP Appletalk Update-based Routing Protocol BGP Border Gateway Protocol BootP Bootstrap Protocol CLNP Connectionless Network Protocol CPU central processing unit CRC cyclic redundancy check CSMA/CD carrier sense multiple access with collision detection DCM Data Collection Module DLC
Preface 303561-A Rev 00 FTP File Transfer Protocol GAME Gate Access Management Entity GMT Greenwich mean time HDLC high-level data link control HSSI High-Speed Serial Interface ICMP Internet Control Message Protocol IGMP Internet Group Membership Protocol IP Internet Protocol IPX Internet Packet Exchange Protocol ISDN Integrated Services Digital Network ISO International Organization for Standardization LAN local area network LAP-B Link Access Procedure-Balanced LED light emitti
Using Technician Interface Software xxiv PIN personal identification number PPP Point-to-Point Protocol PPX parallel packet exchange PROM programmable read-only memory QENET Quad Ethernet RAM random access memory RARP Reverse Address Resolution Protocol RIF routing information field RFC Request for Comment SAP service access point SDLC Synchronous Data Link Control SIMM single inline memory module SMDS switched multimegabit data service SNAP SubNetwork Access Protocol SNMP Sim
Preface VINES Virtual Network Systems WAN wide area network XB translation bridge XNS Xerox Networking Systems Bay Networks Technical Publications You can now print Bay Networks technical manuals and release notes free, directly from the Internet. Go to support.baynetworks.com/library/tpubs/. Find the Bay Networks product for which you need documentation. Then locate the specific category and model or version for your hardware or software product.
Using Technician Interface Software How to Get Help For product assistance, support contracts, or information about educational services, go to the following URL: http://www.baynetworks.
Chapter 1 Introducing the Technician Interface The Technician Interface provides management access to a Bay Networks router by means of: • Telnet (in-band) connection to the router • Direct or dial (out-of-band) connection to the router’s console port You can use the Technician Interface to install a router, and to maintain or diagnose router operation. In addition, you can use the Technician Interface to monitor and configure certain basic functionality in a Bay Networks router.
Using Technician Interface Software Differences from Site Manager The Technician Interface running on the router, and the Site Manager application running on a PC or UNIX workstation, both manage the router software. The Technician Interface differs from Site Manager as follows: • The Technician Interface resides in the router’s operating system kernel and automatically loads when you boot the router.
Introducing the Technician Interface Running the Technician Interface The Technician Interface software entity normally runs on one slot only, except as noted otherwise in the following table: Router Model Slot AN®, ANH™, ARN™ Slot 1 only ASN Slots 1 to 4, individually or simultaneously, depending on the number of ASN routers stacked and the setup of the back panel for each router BN (BLN®, BLN-2, BCN®) Slot 2 ™ LN® or CN® with SYSCON-II flash Any slot (one slot only) system controller If you res
Using Technician Interface Software Note: You must press the return key after every Technician Interface command. Technician Interface commands and passwords are case-sensitive. Use upper- and lowercase as indicated. The User login entry allows you to enter read-only commands. These only read information from the router. The Manager login entry allows you to enter any Technician Interface commands. Certain commands read information from the router and/or write information to the router.
Introducing the Technician Interface If you enable this feature on a router, you enter in addition to a login entry a SecurID PASSCODE™ after the Passcode prompt, as follows: Login: Password: Passcode: (if enabled) If your SecurID administrator enables the SecurID client on a router you need to access, you see the Passcode prompt at login time. When you enter a valid PASSCODE, you receive Technician Interface login privileges to the router.
Using Technician Interface Software Note: If the SecurID system denies you access to a router after four login attempts, the system then removes your PIN from the current list of valid SecurID users. To reactivate your SecurID PIN, you must request reactivation from the SecurID administrator of your network. Newly installed routers initially do not require SecurID authentication for Technician Interface login privileges. (The network administrator must first enable the feature on the router.
Introducing the Technician Interface Figure 1-1 shows the complete authentication procedure and interface dialog you may encounter when attempting a login to a router configured with SecurID client software. Whenever you enter information that the SecurID client considers incorrect, you receive more prompts until you log in successfully, or until the SecurID client denies you further access to the router.
Using Technician Interface Software Open a Telnet connection to the router: >telnet Trying . Connected to Escape character is '^]".
Introducing the Technician Interface Card is in "new PIN" mode? no A yes Enter a passcode after the Enter Passcode prompt from the router: From Figure 1-1 Login: Password: Enter Passcode: no New PIN required.
Using Technician Interface Software Technician Interface Welcome Screen When you initially boot a router (during installation) using the configuration file ti.cfg, you receive login prompt on your console display or Telnet connection.
Introducing the Technician Interface Your network administrator can change the Technician Interface prompt you receive on a local or remote ASCII console or Telnet connection screen. For instructions on how to change the Technician Interface login prompt you receive on a local or remote ASCII terminal or console screen, see Chapter 2. For instructions on how to change the Technician Interface login prompt you receive on a remote Telnet screen, see Configuring TCP Services.
Using Technician Interface Software Login Configuration For instructions on changing the default values associated with the console port, see “Configuring Console Port Parameters” in Chapter 2. For instructions on changing the default values associated with Telnet access to the Technician Interface, see Configuring IP Utilities. For information about changing the default values associated with SecurID services, see “Enabling and Disabling SecurID Authentication” in Chapter 8.
Introducing the Technician Interface Starting a Manager Session from Within a User Session You can initiate a Manager session within a User session by entering the following command: system The Password prompt appears at this time if your network administrator configured a password for Manager access. Enter the password after the prompt. The Technician Interface prompt appears when the system logs you in. Enter logout to terminate the Manager session.
Using Technician Interface Software The router software currently includes embedded scripts for the following router software entities: • CSMACD • TCP • IP • TFTP • IPX • SNMP • FR • SYNC • FTP • TELNET You can also use menus (described in Using Technician Interface Scripts) as an alternative way of accessing the full set of scripts.
Chapter 2 Configuring the Console Port To configure a router’s console port parameters using the Technician Interface, you have to change the default parameter settings associated with the console port on the back of the router.
Using Technician Interface Software Overview You access the Technician Interface software through a console or modem attached to a router serial port. The number of Technician Interface sessions you can establish for a router depends on the number of serial ports available on that router. • The SRM-L board has one serial port (labeled “Console”), allowing you to establish one session on a Backbone Node platform.
Configuring the Console Port Using the list Command You can list and review all serial port attributes by entering the following command line at the Technician Interface prompt: list wfSerialPortEntry Using the set Command Enter one of the following Technician Interface commands to configure a console port parameter: set wfSerialPort Entry..
Using Technician Interface Software Example: The following commands set the Parity parameter to Odd: set wfSerialPortEntry.wfSerialPortParity.1 2 or set wfSerialPortEntry.10.1 2 Note: You can use s instead of set. Using the commit Command Enter the following command after issuing one or more set commands: commit The commit command causes the changes you made to the configuration to take effect in active memory, but not in flash memory.
Configuring the Console Port Console Port Parameters This section describes parameters for configuring the serial (console) port on the router.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Port Disable wfSerialPortDisable 2 Default: 1 (Enable) Options: 1 (Enable) | 2 (Disable) Function: Enables or disables the console port. Instructions: Select the status of the console port. Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: set wfSerialPortEntry.2.
Configuring the Console Port Parameter: Attribute Name: Attribute Number: Port Number wfSerialPortNumber 4 Default: None Options: 1| 2| 3|4 Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: The port number for the information being displayed. Not all routers have four physical ports. The system places a configured port that doesn’t exist into the Not present state. You cannot change this parameter. get wfSerialPortEntry.4. 1.3.6.1.4.1.18.3.3.2.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: wfSerialPortSlot 6 Default: None Options: Set by the system Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: The slot on which the login session for the console port is running. The system sets this number. You cannot change this parameter. get wfSerialPortEntry.6. 1.3.6.1.4.1.18.3.3.2.11.1.1.
Configuring the Console Port Parameter: Attribute Name: Attribute Number: Baud Rate wfSerialPortBaudRate 8 Default: 9600 Options: 9600 | 4800 | 1200 | 600 | 300 Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Specifies the rate of data transfer between the console and the router. Set according to your console requirements. set wfSerialPortEntry.8.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: wfSerialPortParity 10 Default: 1 (None) Options: 1 (None) | 2 (Odd) | 3 (Even) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Enables or disables data error detection for each character transmitted or received. Use the 2 (Odd) or 3 (Even) setting to enable data error detection. Use the 1 (None) setting to disable data error detection. set wfSerialPortEntry.10.
Configuring the Console Port Parameter: Attribute Name: Attribute Number: Modem Enable wfSerialPortModemEnable 12 Default: 2 (Disable) Options: 1 (Enable) | 2 (Disable) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Specifies whether the terminal connects directly or via a modem to the Technician Interface. Use the 1 (Enable) setting to configure the terminal for connection via a modem to the Technician Interface.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: More Enable wfSerialPortMoreEnable 14 Default: 1 (Enable) Options: 1 (Enable) | 2 (Disable) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Specifies whether the Technician Interface pauses after each screen fills with data. Select 1 (Enable) to configure the Technician Interface to pause after each screen fills with data.
Configuring the Console Port Parameter: Attribute Name: Attribute Number: Login Timeout wfSerialPortLoginTimeOut 16 Default: 1 min Options: 1 to 99 min (99 indicates infinity) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Specifies the number of minutes the Technician Interface waits to time out when no one has pressed the enter key after the Login prompt. This parameter is valid only when Modem Enable is set to 1 (Enable).
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: wfSerialPortCommandTimeOut 18 Default: 15 min Options: 1 to 99 min (99 indicates infinity) Function: Specifies the number of minutes that can elapse before the Technician Interface disconnects the Telnet session, if you do not enter a command at the command prompt. This parameter is valid only when Modem Enable is set to 1 (Enable).
Configuring the Console Port Parameter: Attribute Name: Login Script Search Path wfSerialPortInitialSearchPath Attribute Number: 28 Default: 2: Options: A string of valid volume numbers, depending on your login ID (Manager or User) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Specifies a list of file system volumes for the system to search if the manager or the user login script file does not contain a volume specification.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: User’s Login Script wfSerialPortUserAutoScript 30 Default: None Options: None or autouser.bat. A script named autouser.bat exists within the Technician Interface software. You can use the script as is, or you can modify it to suit your requirements. Function: Instructions: Executes the user’s login script file automatically at login. If you did not change the name of the user’s login script file, accept the default.
Configuring the Console Port Parameter: Attribute Name: Attribute Number: Force User Logout wfSerialPortUserAbortLogoutDisable 31 Default: 2 (Disable) Options: 1 (Enable) | 2 (Disable) Function: Instructions: Specifies whether or not the user can execute a Control-c (^C) to break out of a user autoscript at login (when a user autoscript is in effect). Set the parameter to Enable to prevent the user from using ^C to break out of the user autoscript at login.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: wfSerialPortAutoSaveNumFiles 33 Default: 0 (log autosave off) Options: 1 to 99 Function: Specifies the number of times the system saves the events log to a new file automatically when the log is full. The system saves the log the maximum number of times you specify, or until the memory card or diskette drive on the router becomes full.
Configuring the Console Port Using Autoscript Files You can configure the Technician Interface to use the autoscript files automgr.bat and autouser.bat, so that the Technician Interface executes certain commands every time you log in as either a Manager or User.
Using Technician Interface Software Sample Autoscript Files The following autoscript files for the Manager login and the User login are configured using the Technician Interface software. Manager login autoscript: ####################################################################### # # Autoscript for Manager # Copyright 1995 Bay Networks Inc.
Configuring the Console Port Customizing Autoscript Files You can customize the automgr.bat or autouser.bat scripts by entering the appropriate commands or aliases into the script. See Chapter 9 of this guide and the Writing Technician Interface Scripts guide for information about aliases and script files. Use vi or another text editor to edit automgr.bat or autouser.bat on your workstation. Then transfer the files via TFTP or XMODEM to the router where the scripts are located.
Chapter 3 Using Operating Commands The basic Technician Interface operating commands allow you to: • Display online help. • Pause and scroll text on a screen. • Terminate a command. • Repeat the command last entered. • Repeat a command recently entered. • Load a command into memory. • Ping a remote IP, IPX, OSI, VINES, AppleTalk, or APPN address. • Display the ATM ARP table for a specific IP interface address.
Using Technician Interface Software Displaying Online Help Use the help command to display online Help text for any Technician Interface command, as follows: help [] When you enter help, followed by a space and the name of a command, the console displays a detailed description of the command along with its syntax requirements. For example, when you enter help date, the console displays a detailed description of the date command.
Using Operating Commands Enter the following command to set or display the more mode: more [-s] [on | off] <#_of_lines> -s Prevents the console from displaying output on Enables the more mode off Disables the more mode Examples: more Displays more mode on or more mode off. more on Enables the more mode; pauses the system and prompts you to continue when a screen fills. more -s on 24 Enables the more mode; sets screen size to 24 lines; no output displayed. more on
Using Technician Interface Software Enter the following to execute the last command you entered, where is the optional number of times you want to execute the command. (The default is 1 time.
Using Operating Commands Example: $> dinfo (Command 1) VOL STATE TOTAL SIZE FREE SPACE CONTIG FREE SPACE --------------------------------------------------------------2: FORMATTED 4194304 745101 697153 4: FORMATTED 4194304 2106021 2106021 $> dir 2: (Command 2) Volume in drive 2: is Directory of 2: File Name Size Date Day Time -----------------------------------------------------bn.exe 3271441 06/12/95 Mon. 16:35:07 12568 06/12/95 Mon. 16:38:57 152524 06/12/95 Mon.
Using Technician Interface Software Image: beta/9.00/1 Created: Tue Jun 6 13:08:17 EDT 1995 $> $> history (Displays the history list) 1 dinfo 2 dir 2: 3 stamp history 2 (Repeats the second command currently in the history list) dir 2: Volume in drive 2: is Directory of 2: File Name Size Date Day Time -----------------------------------------------------bn.exe 3271441 06/12/95 Mon. 16:35:07 12568 06/12/95 Mon. 16:38:57 152524 06/12/95 Mon. 16:39:00 128 06/12/95 Mon.
Using Operating Commands Currently, you can load only the telnet command into memory. The exec telnet command is useful when booting a Bay Networks router over a network using BootP. Using exec telnet locks the telnet command into memory, in case the connection to the BootP server fails.
Using Technician Interface Software IP Ping When you issue the ping command for IP, the ping program sends an Internet Control Message Protocol (ICMP) echo request to the remote IP address you specify. The remote device responds if it can be reached, and the console displays the response or the result of the request.
Using Operating Commands The console displays one of the following messages when you issue a ping command. If you enter a value in the argument, the system displays one of the following messages for the default ping, plus one for each additional ping: • An alive message: This message appears if the system receives an ICMP echo response from the target device within the allowed. The message also indicates the size of the test packet. A sample message follows: ping: 192.32.1.
Using Technician Interface Software Examples: ping -ip 192.32.1.151 Pings the device at IP address 192.32.1.151 and waits up to 5 seconds (default) for a response. The console displays one of the following messages: ping: ping: ping: ping: ping -ip 192.32.13.200 -p 192.32.1.151 is alive (size = 16 bytes) 193.32.1.151 does not respond ICMP host unreachable from 192.32.243.1 192.32.1.
Using Operating Commands IPv6 Ping When you issue the ping command for IP version 6 (IPv6), the ping program sends an Internet Control Message Protocol version 6 (ICMPv6) echo request to the remote IPv6 address you specify. The remote device responds if it can be reached, and the console displays the response or the result of the request.
Using Technician Interface Software The console displays one of the following messages when you issue a ping command. If you enter a value in the argument, the system displays one of the following messages for the default ping, plus one for each additional ping: • An alive message: This message appears if the system receives an ICMP echo response from the target device within the allowed. The message also indicates the size of the test packet.
Using Operating Commands Examples: Pings the device at the IPv6 address ping -ipv6 3FFE:1300:0003:0011:0000:0001: 3FFE:1300:0003:0011:0000:0001:A2A5:2159 and waits up to 5 seconds (default) for a A2A5:2159 response. Same as above, but displays the intervening hop ping -ipv6 3FFE:1300:0003:0011:0000:0001: addresses to the destination and the time it took to reach them before displaying the response A2A5:2159 -p message for each ping.
Using Technician Interface Software IPX Ping When you issue the ping command for IPX, the router sends an IPX configuration request packet to the remote IPX address that you specify. If the remote device is listening on socket number 456h for an IPX configuration request packet, it responds if it can be reached, and the console displays a message indicating that the device is alive or does not respond.
Using Operating Commands An IPX address in decimal notation consists of a 4-byte network address and a 6-byte host address, where • Each byte is a number from 0 to 255. • A period separates successive address bytes (for example, 0.1.23.47.0.0.0.1.2.55). Note: If you issue an IPX ping to an entity on a token ring network, you must enter the host portion of the IPX address in byte-swapped form (noncanonical form). [-t] [-r] are optional.
Using Technician Interface Software • An invalid parameter specified message: This message appears if the network or host address is all 0s, all Fs, or not a valid IPX address. A sample message follows: IPX ping: invalid parameter specified • A resource error message: This message appears if the router cannot allocate a buffer for the request because none are available. A sample message follows: IPX ping: resource error Examples: ping -ipx 0xAB12.0xCD1234 Pings the device at the IPX address 0xAB12.
Using Operating Commands OSI Ping When you issue the ping command for OSI, the router sends a Connectionless Network Protocol (CLNP) echo request to the remote network service access point (NSAP) address you specify. The remote device responds with a CLNP echo response if it can be reached, and the console displays the response or the result of the request.
Using Technician Interface Software • A is unreachable message: This message appears if the local Bay Networks router cannot find the specified address in its routing table. OSI ping: 49000400000a12121200 is unreachable • An NSAP address is too short message: This message appears if the NSAP address is too short. The minimum allowed NSAP address length is 20 hexadecimal characters (10 bytes).
Using Operating Commands Examples: ping -osi 49000400000a12121200 Pings the device at the NSAP address 49000400000a12121200 and waits up to 5 seconds (default) for a response.
Using Technician Interface Software VINES Ping When you issue the ping command for VINES to a remote VINES device, it responds if it can be reached, and the console displays the response or the result of the request. Enter the following to ping a remote device running VINES: ping -vines . [-t] [-r] [-s] [-p] . is the required VINES address of the remote device.
Using Operating Commands The console displays one of the following messages when you issue a ping command. If you enter a value in the argument, the system displays one of the following messages for the default ping, plus one for each additional ping: • An alive message: This message appears if the system receives a response from the target device within the allowed. The message also indicates the size of the test packet. A sample message follows: VINES ping: 2705682.
Using Technician Interface Software Examples: ping -vines 2705682.8003 Pings the device at the VINES address 2705682.8003 and waits up to 5 seconds (default) for a response. The console displays one of the following messages: VINES ping: 2705682.8003 is alive VINES ping: 2705682.8003 does not respond VINES ping: 2705682.8003 is unreachable ping -vines 2705682.8003 -p All of the above, but displays the intervening hop addresses to the destination before displaying the response message for each ping.
Using Operating Commands AppleTalk Ping When you issue the ping command for AppleTalk to a remote AppleTalk device, the console displays the response from the remote device (if the ping reaches the device) or the result of the request. AppleTalk ping uses the AppleTalk Echo Protocol. Enter the following to ping a remote device running AppleTalk: ping -at . [-t] [-r] [-s] .
Using Technician Interface Software • A does not respond message: This message appears if the address of the target device is resolved, but the system does not receive a response from the target device within the allowed. A sample message follows: AT ping: 100.5 does not respond • A is unreachable message: This message appears if the local Bay Networks router cannot find the specified address in its routing table. A sample message follows: AT ping: 100.
Using Operating Commands Examples: ping -at 100.5 Pings the device at the AppleTalk address 100.5 and waits up to 5 seconds (default) for a response. The console displays one of the following messages: AT ping: 100.5 is alive AT ping: 100.5 does not respond AT ping: 100.5 is unreachable ping -at 100.5 -t3 -r8 Pings the device at the AppleTalk address 100.5 eight successive times and waits up to 3 seconds for a response to each ping.
Using Technician Interface Software APPN Ping When you issue the ping command for APPN to a remote APPN device, the console displays the response from the remote device (if the ping reaches the device) or the result of the request. APPN ping uses the APING (APPN Ping) Transaction Program (TP) to send an APING request to the APINGD TP running on the remote device.
Using Operating Commands The console displays one of the following messages when you issue a ping command: • An alive message: This message appears if the system receives a response from the target device within the allowed. A sample message follows: APPN ping: bay is alive • A did not complete in the time allowed message: This message appears if the node is alive but congested, the data transfer time exceeded the timeout, or the directory search is not complete.
Using Technician Interface Software ping -appn raleigh -r100 -s2000 -m#inter Pings the device at the APPN address raleigh 100 successive times, sending 2000 bytes of data with each ping and specifying the interactive mode.
Using Operating Commands Displaying the ATM ARP Table for an Interface You can display the ATM ARP tables for a specific IP interface address by entering the atmarp command during a Technician Interface session.
Using Technician Interface Software [2:1]$ atmarp table -v 128.185.97.73 Vpi.vci Atm address IP address Life ------- ----------------------------------------- ----------------0.63 39000000000000000000000000.0000a20d74aa01 128.185.97.74 399 [2:1]$ atmarp table -a 128.185.97.73 ATM address ----------------------------------------39000000000000000000000000.0000a20d74aa01 Vpi.vci -------0.63 Examples (client): [2:1]$ Vpi.vci ------0.63 [2:1]$ atmarp table -v 128.185.97.
Using Operating Commands 303561-A Rev 00 3-31
Chapter 4 Managing a Nonvolatile File System You can use the Technician Interface to manage nonvolatile file system (NVFS) files on a Bay Networks router. When you manage an NVFS, you can: • Use multiple memory cards. • Name files. • Display the status of each memory card installed in the router. • Display a directory. • Change the active volume. • Copy a file from one volume to another, or to the same volume. • Transfer a file. • Display the contents of a file. • Delete a file.
Using Technician Interface Software Overview The NVFS file system on the router reads and writes to one or more memory cards. Memory cards exist in 2-MB, 4-MB, and 8-MB sizes. Each memory card provides system access to the software image and configuration file during a cold start. (A cold start occurs when you cycle the power on the router, or after you enter the diags command.) Each FRE® module (BLN, BLN-2, BCN) in a router can host one memory card.
Managing a Nonvolatile File System Table 4-1.
Using Technician Interface Software The system boots from the default router software image (Table 4-2) and configuration file (config) if you do not specify the boot image and configuration file when booting. See Table 4-2 for a list of router software images associated with particular routers and processor modules. Table 4-2. Router Software Images Image Router Processor ace.out FN, LN, CN, ALN ACE module afn.exe AFN Motorola CPU an.exe AN, ANH Motorola CPU arn.exe ARN Motorola CPU asn.
Managing a Nonvolatile File System Naming Files: Rules and Conventions The rules for naming files are as follows: • You must specify the volume location (slot number) of any file you reference and of any file you create. The sections that follow detail the syntax requirements, including the slot number specification, for each command. • File names must start with an alphabetical character. The remaining characters must be alphanumeric, and may also include the underscore (_) character and dot (.
Using Technician Interface Software Displaying the Status of All Memory Cards Enter dinfo to display the status of all memory cards currently installed in the router. Figure 4-1 shows a sample dinfo display of a system with memory cards installed in slots 2 and 5. $ dinfo VOL STATE TOTAL SIZE FREE SPACE CONTIG FREE SPACE --------------------------------------------------------------2: FORMATTED 2097152 228663 220209 5: FORMATTED 4194304 1356883 1356883 $ TS0010A Figure 4-1.
Managing a Nonvolatile File System When you delete a file on a memory card, the file becomes inaccessible, but the data remains on the card. Eventually, all space is used. The compact command copies the active files to memory, erases the memory card, and copies the files back to the memory card. This command frees up space to prevent or respond to a file allocation failure. See “Compacting File Space” on page 4-19 for more information about this feature.
Using Technician Interface Software $ dir Volume in drive 5: is Directory of 5: File Name Size Date Day Time -----------------------------------------------------pvc0.cfg 6872 10/14/94 Fri. 13:51:12 fr.al 5616 09/16/94 Fri. 08:04:26 fr.VIII 10158 09/28/94 Wed. 15:25:48 mfg.log 172052 11/03/94 Thurs. 16:24:28 config 7132 11/11/94 Fri. 15:42:01 bn.exe 2635353 01/05/95 Thurs. 09:08:55 4194304 bytes - Total size 1356883 bytes - Available free space 1356883 bytes - Contiguous free space $ TS0012A Figure 4-2.
Managing a Nonvolatile File System The factory-default file names are as follows: ace.out The router software image for the FN, LN, CN, and ALN. You cannot read or change this file. The system automatically refers to this binary file for booting instructions unless you use the boot command to specify a different router software image. an.exe afn.exe arn.exe asn.exe bn.exe s5000.exe The router software image for the AFN. The router software image for the AN and ANH. The router software image for the ARN.
Using Technician Interface Software config The default configuration file. The system refers to this binary file for configuration data when booting. You can change the configuration by copying an alternative configuration file to config. You can also use the boot command to specify a different configuration file. This file must have the config file name for the system to configure automatically after booting. We recommend that you copy config to a new backup file name before overwriting it. debug.
Managing a Nonvolatile File System Changing the Active Volume Use the cd command to change the active volume, as follows: cd : is the slot number of the volume. The system displays the new active volume. If you enter the cd command without specifying a volume, the system displays the present working directory, as follows: cd Present Working Directory: 2: Copying a File Use the copy command to make a copy of a file.
Using Technician Interface Software Copying Files from NVFS to DOS When copying files from NVFS to DOS on FN, LN, or CN routers equipped with Flash System Controllers, make sure that the NVFS file name contains no more than eight characters with an optional extension of no more than three characters preceded by a dot (xxxxxxxx.xxx). NVFS file names can consist of one to 15 characters; DOS file names can consist of one to eight characters with an optional one- to three-character extension.
Managing a Nonvolatile File System Transferring a File Depending on conditions existing within your network, you can transfer files between Bay Networks routers and remote workstations using either of two methods: • In-band (using Technician Interface tftp commands and a route through your high-speed, IP network) • Out-of-band (using Technician Interface xmodem commands and a route through a lower-speed, dial network) You can transfer a file in-band whenever • You can dial in to the Technician Interfa
Using Technician Interface Software In-Band File Transfers The tftp command invokes the Trivial File Transfer Protocol (TFTP) software to transfer a file between a Bay Networks router and another router or host capable of serving tftp file transfer requests. The TFTP software resides within the IP router. Consequently, you must load TFTP on the router and enable it (see Quick-Starting Routers for instructions).
Managing a Nonvolatile File System Caution: The destination system in a file transfer automatically overwrites any file already on its volume that has the same file name. If enough space does not exist on the file system for the new file, and the new file has the same name as an old file, the old file will be destroyed and the new file will be corrupted. This occurs because TFTP copies the new file over the old and runs out of space before completing the copy.
Using Technician Interface Software Caution: The local system erases the file if you enter its address in the field of the tftp command. The system executes one TFTP request at a time for the duration of the file transfer. The destination system stores the file under the name you specify. If you do not enter a destination name, the system defaults to the source file name. Examples: tftp put 192.32.1.62 2:config2.cfg 3:newconf Sends a copy of config2.
Managing a Nonvolatile File System If you enter: The local system: tftp dark put install.bat dark:2:install.bat Transfers a copy of the install.bat file to volume 2 on the router known as “dark.” Out-of-Band File Transfers Appendix B in this guide describes how to transfer files out-of-band (via the dial telephone network), by means of the xmodem command. Displaying the Contents of a File Use the type command to display the contents of a file.
Using Technician Interface Software Examples: type 2:install.bat Displays the contents of the install.bat file, which is stored on the volume in slot 2. type -x 3:config Displays the config file, which is stored on the volume in slot 3. This file is displayed in hexadecimal format. Deleting a File Use the delete command to delete files that you specify. You can use the wildcard characters * and ? when issuing the delete command. Caution: You cannot recover a file after it is deleted.
Managing a Nonvolatile File System Examples: delete alt.cfg Deletes the alt.cfg file on the active volume delete 2:l6_22.log Deletes the l6_22.log file on volume 2 delete 3:*.log Deletes all files with the log file name extension on volume 3 delete 4:???.
Using Technician Interface Software The following message appears: Compacting file system on volume :... This may take several minutes...Please wait... 100% Complete Compaction completed The space is compacted when the Technician Interface prompt reappears.
Managing a Nonvolatile File System Partitioning a Memory Card or SIMM Memory partitioning enables you to use commands such as the compact command on one partitioned volume at a time. Partitioning also enables you to store copies of boot images and configuration files on each partition to provide redundancy. The partition command only works with a 4-MB or greater memory card or SIMM used with an AN or ASN loaded with Version 8.10 or later router software.
Chapter 5 Managing a DOS File System You can use the Technician Interface to manage DOS files on a Bay Networks router. This chapter is intended only for users whose routers are equipped with a diskette drive. To manage a DOS file system, you do the following: 303561-A Rev 00 • Name files. • Mount and unmount a volume. • Change the present working directory. • Display a directory. • Label a diskette. • Create and remove a directory. • Rename a file or directory.
Using Technician Interface Software Overview The DOS file system on the router reads and writes to the diskette. The diskette gives the system access to the software image and configuration file during a cold start. (A cold start occurs after you cycle power on the router.) The DOS file system accepts the DOS commands that you use to manage the files and directories on the diskette. (For a list of these commands, see Table 5-1.
Managing a DOS File System Table 5-1.
Using Technician Interface Software Naming Files and Directories The rules for naming files and directories are as follows: • File names and directory names must start with an alphabetical character. The remaining characters must be alphanumeric, and may also include the underscore (_) character. Spaces are not allowed. • DOS directory and file names can consist of one to eight characters.
Managing a DOS File System Mounting a Volume Use the mount command to make the diskette drive available. Enter the following command when you install a diskette: mount a: The screen displays a File System Check Report (Figure 5-1). $ mount a: Device label: Directory: A:\ File System Check Report: Allocated but unused clusters : 0 Used but unallocated clusters : 0 Cluster chains shared between files: 0 File size is wrong : 0 Missing EOF : 0 Directory errors : 0 TS0013A Figure 5-1.
Using Technician Interface Software The File System Check Report entries are as follows: • Allocated but unused clusters shows the number of reserved sectors not allocated to files. The router may in some cases be able to recover from this error when mounting the volume. The Technician Interface displays a message indicating success or failure after a recovery attempt. Enter the unmount a: and mount a: commands to determine whether DOS fixed the error.
Managing a DOS File System Unmounting a Volume Use the unmount command to make the diskette drive unavailable before you remove a diskette, reboot the router, or reset slot 2. When you issue the unmount command without using a -f argument, the system reports an error if files are in use at the moment you issue the command.
Using Technician Interface Software Examples: cd Displays the present working directory cd \old Changes the present working directory to the subdirectory old cd \old\logs Changes the present working directory to the subdirectory old\logs cd .. Changes the present working directory to the parent directory cd \ Changes the present working directory to the root directory Displaying a Directory Use the dir command to display a list of the files in a directory.
Managing a DOS File System $ dir a: Performing mount check... Volume in drive A: is Directory of A:\ File Name Size Date Day Time Attributes -----------------------------------------------------------------. 0 01/01/92 Wed. 12:00:00 -d---.. 0 01/01/92 Wed. 12:00:00 -d---ACE.OUT 1302081 01/04/95 Wed. 02:30:22 a----TI.CFG 184 09/13/94 Tues. 23:40:58 a----CONFIG 184 06/15/94 Wed. 22:35:04 a----TOMACIP 1760 06/16/94 Thurs. 00:54:18 a----TOMAC.CFG 3544 08/16/94 Tues. 23:07:00 a----AURP.CFG 4264 10/04/94 Tues.
Using Technician Interface Software The factory-default file names are as follows: ace.out The router software image for the FN, LN, CN, and ALN. You cannot read or change this file. The system automatically refers to this binary file for booting instructions unless you use the boot command to specify a different router software image. an.exe afn.exe arn.exe asn.exe bn.exe s5000.exe The router software image for the AFN. The router software image for the AN and ANH.
Managing a DOS File System s5000diag.exe A copy of the diagnostics image resident on a System 5000 router. You cannot read or change this file. config The default configuration file. The system refers to this binary file for configuration data when booting. You can change the configuration by copying an alternative configuration file to config. You can also use the boot command to specify a different configuration file.
Using Technician Interface Software Table 5-2 identifies the DOS file attributes that can appear in a DOS directory display, and their meanings. See “Changing File Attributes” on page 5-20 for more information about file attributes. Table 5-2. DOS File Attributes Attribute Flag Meaning a Archive needed d Subdirectory v Volume ID s System file h Hidden r Read-only file Labeling a Diskette Use the label command to change or display a diskette’s internal label.
Managing a DOS File System Creating a Directory Use the mkdir command to create a new directory.
Using Technician Interface Software Renaming a File or Directory Use the rename command to change a file name or directory name. Note: You cannot rename a file whose attributes are h (for hidden) or s (for system). See “Changing File Attributes” on page 5-20 for instructions on changing these protections. If you specify a path to the file or directory, the file is moved to the new directory. The new file or directory must reside on the same diskette as the original.
Managing a DOS File System Copying a File Use the copy command to make a copy of a file. You can use the wildcard characters * and ? when issuing the copy command to copy multiple files. The new file must reside on the same diskette as the original. (Use a PC to copy a file from one diskette to another.) Caution: The system automatically overwrites any file in the directory that has the same file name as the file you are copying.
Using Technician Interface Software Copying Files from DOS to NVFS When copying files from DOS diskettes to NVFS memory cards, you must specify the destination file name in the command. DOS file names are in uppercase. The NVFS file names for the router software image and the configuration file must be in lowercase. Caution: The router will fail to boot from a memory card whose image and configuration file have uppercase names.
Managing a DOS File System Transferring a File Depending on conditions in your network, you can use either of two methods to transfer files to and from Bay Networks routers and remote workstations: • In-band (using Technician Interface tftp commands and a route through your high-speed IP network) • Out-of-band (using Technician Interface xmodem commands and a route through a lower-speed, dial network) You can transfer a file in-band whenever • You can dial in to the Technician Interface port of a rout
Using Technician Interface Software In-Band File Transfers The tftp command invokes the TFTP software to transfer a file between a Bay Networks router and another router or host capable of serving tftp file transfer requests. The TFTP software resides within the IP router. Consequently, you must load the TFTP software on the router and enable it (see Quick-Starting Routers for instructions).
Managing a DOS File System [] is the name to which you want to transfer the file. If you do not enter a name, the system defaults to the you specified for the source file. Caution: The local system erases the file if you enter its address in the field of the tftp command. The system executes one TFTP request at a time for the duration of the file transfer. The destination system stores the file under the name you specify.
Using Technician Interface Software Out-of-Band File Transfers Appendix B describes how to transfer files out-of-band (using facilities outside the IP network), using the xmodem command. Changing File Attributes The attr command changes the DOS file attributes. These attributes are displayed when you enter the dir command. You cannot delete or rename a file whose attributes are s (for system) or h (for hidden).
Managing a DOS File System To assign a single attribute to a file, use the hex value associated with the attribute you want in the attribute command. For example, enter the following command to assign the read-only file attribute to a file named config located in the present working directory: attr 0x01 config To assign multiple attributes to a file, add the hex values associated with the attributes you want and enter the total in the attribute command.
Using Technician Interface Software Displaying the Contents of a File Use the type command to display the contents of a file. Before displaying a file, you can enable the more function to display the file one screen at a time. Enter the following to display a file: type [-x] -x is an optional command to display the file in hexadecimal format. This allows files containing nonprintable information to be viewed. is the name of the file you are displaying.
Managing a DOS File System Deleting a File Use the delete command to delete files that you specify. You can use the wildcard characters * and ? when issuing the delete command. Caution: You cannot recover a file after it is deleted. The delete command does not prompt you to verify a deletion. Enter the following to delete a file in the present working directory: delete You can enter del or delete when deleting a file.
Chapter 6 Managing Events You can use the Technician Interface to: • Specify events you want to include in, or exclude from, the events log • Specify events you want to display from the events log • Save an events log to a file • Configure the router to save the events log to a new file automatically when the log becomes full • Display an events log file previously saved • Clear event messages from the events log See Event Messages for Routers for information about the event display format or a
Using Technician Interface Software Overview The operating software in each processor module logs (stores) events in a first in first out (FIFO) memory buffer. When you issue a command to display or save the current log, the system sorts the events from all processor modules in chronological order. You can also clear events from all slots or from a single slot. The event logs are checksum protected during a warm start. (Issuing the boot or reset command or pressing the Reset button warm-starts the router.
Managing Events • To enable the router to read only certain messages from the events log to the console display, add read filter arguments to the log command. You can select or specify event types by: -- Entity code -- Severity level -- slot number -- Event date -- Event time -- Event number or number range Applying Write Filters to the Events Log During normal operation, the events log captures all event messages generated internally by the router.
Using Technician Interface Software Table 6-1. 6-4 Log Command Options Option Variable Function -e Specifies the name of the software service for which the router will log (write) event messages to the local events log, or exclude from the events log. When you specify an , you must • Use uppercase letters. • Enter the in quotes when that name contains spaces (for example, “FRAME RELAY”).
Managing Events Examples: log -i -fdft Includes only debug, fault, and trace events log -i -fdi -s2 Includes only debug and info events on slot 2 log -i -ff -eGAME Includes only fault events for the router operating system entity log -i -fd -s2 -eOSPF Includes only debug events for OSPF running on slot 2 log -i Includes no events (none are specified) log -i -fdfitw Includes all events (all severity levels are specified) log -x -fd Excludes only debug events log -x -fdfitw -eIP Excludes all e
Using Technician Interface Software Applying Read (Display) Filters to the Events Log Enter the following command to display the events stored in all event buffers: log The system sorts the events and displays them in chronological order. For information about the event display format or about specific events, see Configuring and Managing Routers with Site Manager. Note: To stop the command, press Control-c (hold the control key and press c).
Managing Events enables continuous polling of the system’s events log and display of new event messages. The -p option uses a default rate of 5 seconds. You can change this by entering a in seconds. The system displays the events that occur between polling intervals. is an event code number or a range of event code numbers. The system displays the events associated with the specified event code. -w enables the log command to provide console output in wide format.
Using Technician Interface Software Saving the Events Log You can save the events in the current event buffer to a file for later retrieval. Caution: The system automatically overwrites any file on the volume that has the same file name. To avoid overwriting an existing file, display a list of the volume’s contents (with the dir : command) and determine the file names already in use. Enter the following. save log : is the volume on which to store the file.
Managing Events Examples: 303561-A Rev 00 save log 2:10_12.log Saves all events to a file named 10_12.log in slot 2. save log 2:10_12.log -d10/ 12/95 Saves events logged since October 12, 1995 to a file named 10_12.log in slot 2. save log 2:temp.log -t09:02:00 Saves events logged since 9:02 today to a file named temp.log in slot 2. If it is earlier than 9:02, the system saves all events logged since 9:02 yesterday. save log 3:tftp.
Using Technician Interface Software Saving the Events Log Automatically Note: Use this feature only for troubleshooting a Bay Networks router. We recommend that you leave this feature disabled (default) at all other times. You can configure any model of Bay Networks router to save the entire events log automatically. The system saves the file just prior to overwriting the oldest messages in the log. This feature helps to prevent the loss of event message information accumulated in the log over time.
Managing Events Parameter: Autosave Volume Attribute Name: wfSerialPortAutoSaveVolume Attribute Name: 34 Default: None Options: Any valid memory card volume (slot) number from 1 to 14 or the diskette drive designation, -a Function: Instructions: Command: MIB Object ID: Specifies the target volume where the system stores new log files saved through the log autosave feature.
Using Technician Interface Software Models 5380 and 5580 -- System 5000 hubs support up to 14 instances of the wfSerialPortEntry object. Each instance corresponds to one of the 14 possible hub slots. Enable the log autosave feature only on one slot occupied by a Model 5380/5580 router in a System 5000 hub. (Multiple 5380/5580 boards installed in the same System 5000 hub operate as one logical router if that hub contains an ATM/PPX backplane.
Managing Events Displaying an Events Log File Previously Saved You can use the log command to display a log file you previously saved. Enter the following to display a log file, where identifies the volume and is the name of the log file you want to display: log [:] The system reads the log file, which is stored in binary format, and forwards an ASCII representation to the console. The event format is identical to the format of the current log display.
Using Technician Interface Software Clearing Events Clearing events from the events log buffer is useful if you want to conduct an experiment and examine the events log afterwards. Note: You may want to save the log to a file for later retrieval before clearing it. See “Saving the Events Log” on page 6-8. Enter the clearlog command with one or more of the following parameters to clear all events from an event buffer or buffers, where
Chapter 7 Accessing the MIB You can use the Technician Interface to access and manage the Bay Networks management information base (MIB). This chapter assumes you already know how to manage the MIB, but you need instructions on entering MIB management commands at the Technician Interface console. See Appendix A for more information.
Using Technician Interface Software Listing MIB Objects You can display MIB object names and their associated identifiers using the list command. When you want to display or change a MIB value but do not know its object or attribute name, use this command.
Accessing the MIB Examples: list Displays all object names and their associated object identifiers: wfCSMACDEntry = 1.3.6.1.4.1.18.3.4.1.1 wfFddiEntry = 1.3.6.1.4.1.18.3.4.4.1 wfFddiSmtEntry = 1.3.6.1.4.1.18.3.4.15.1.21 . . . list wfCSMACDEntry Displays all attribute names and associated attribute identifiers of the wfCSMACDEntry object: wfCSMACDDelete = 1 wfCSMACDEnable = 2 wfCSMACDState = 3 . . .
Using Technician Interface Software Getting MIB Values The get command displays the value of a MIB object. You can also insert a wildcard character (*) into the attribute name or into the instance identifier to display the values of multiple objects. Enter the following to display one or more object identifiers and their associated values: get
Accessing the MIB The following examples demonstrate ways to display the value of an attribute. The attribute in these examples is named wfSnmpDisable. Its instance ID is 1, object name is wfSnmp, and object identifier is 1.3.6.1.4.1.18.3.5.3.5.1. The instance ID of 0 is reserved for base record objects. Specifying the base record instance ID in the get command is optional. The second example demonstrates how to obtain a group of values associated with an object.
Using Technician Interface Software Setting MIB Values The set command modifies the value of an instance. You set an instance by specifying its object.attribute.instance. You may use names or identifiers to specify object groups and attributes; use only an appropriate identifier or index value to specify the instance. Note: When you enter the set command, the attribute is set on each running processor module. Enter the following to change the value of an object instance: set
Accessing the MIB is the required new value of an instance of an object. This value may be one of the following, depending on the data type: • Integer, unsigned integer types: decimal number • IP addresses: dotted-decimal format (for example, 192.32.0.0) • Octet strings: hexadecimal numbers starting with 0x • Display strings: strings enclosed in double quotes See the Bay Networks MIB to determine the data type.
Using Technician Interface Software Examples: Entering one of the following: set wfSnmp.wfSnmpDisable.0 1 set 1.3.6.1.4.1.18.3.5.3.5.1.1.0 1 set wfSnmp.1.0 1 Changes the value of wfSnmp.wfSnmpDisable.0 (1.3.6.1.4.1.18.3.5.3.5.1.1.0) to 1 to enable SNMP Changes the value of wfIpInterfaceEntry.WfIpInterfaceEnable.192.3 2.13.99 to 2, which disables IP for the set wfIpInterfaceEntry.2.192.32.13.99.3 interface whose IP address is 192.32.13.
Accessing the MIB Saving the Configuration You can copy all MIB values from operating RAM to a configuration file for later retrieval. You use the save config command to copy the configuration in memory to the default configuration file or to an alternative configuration file.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: MIB II Counters Enable wfSysMibCounterEnable 12 Default: 1 (Enable) Options: 1 (Enable) | 2 (Disable) Enables or disables the following five counters in the MIB for Version 8.10 and later router software: Instructions: Command: MIB Object ID: 7-10 • ifInUcastPkts • ifInNUCastPkts • IfINUnknownProtos • ifOutUcastPkts • ifOutNUcastPkts Set to 1 (Enable) to enable the five counters on all circuits and slots.
Chapter 8 System Administration You can use the Technician Interface to perform the following system administration tasks: 303561-A Rev 00 • Configure the AN, ARN, or ASN router’s boot or configuration sources when booting. • Configure AN, ANH, ARN, or ASN initial interfaces. • Boot the router. • Configure and manage scheduled boot services. • Restart a slot. • Reset a slot. • Run diagnostics. • Display the version number of the Bay Networks router software.
Using Technician Interface Software • Configure search depth for hardware compression. • Display a greeting or message before the login prompt. • Customize the Technician Interface Welcome message. • Record console messages to a file. • Enable Internal Clocking Mode. • Respond to QENET underflow errors. • Monitor IP routes (for IP, OSPF, and BGP). A table of all the Technician Interface commands and their associated access levels appears at the end of this chapter (Table 8-4).
System Administration Configuring the Boot Source To use Directed Netboot, you must use the bconfig command to specify the following: • The IP address of the server where the router’s software image and configuration file reside • The full path name of the software image and configuration file You must use the bconfig command once to specify the location of the software image, and again to specify the location of the configuration file.
Using Technician Interface Software Table 8-1. Options for the bconfig Command Option Description image Specifies information about the router’s software image config Specifies information about the router’s configuration file local Indicates that the specified file (image or config) resides in the router’s local file system network Indicates that the specified file resides on a network server Specifies the IP address of the host where the image or configuration file resides.
System Administration Configuring Initial Interfaces and Netboot Operation You can use the ifconfig command to do the following: • Configure the router’s initial IP interface to the network. You also use the same procedure to configure other synchronous interfaces for the network booting procedure. • Configure Ethernet interfaces for the network booting procedure. • Enable or disable network booting on an interface. The following sections describe each use of the ifconfig command.
Using Technician Interface Software Table 8-2. Options for the ifconfig Command Setting Description Slot setting: -s Specifies the slot containing the interface you want to configure. The slot corresponds to the ASN slot ID, which can be 1 to 4. If you omit this argument, ifconfig uses the current slot. Default setting: -d Resets the router’s IP interface settings to the default values.
System Administration Configuring an Ethernet Interface for Network Booting To configure an Ethernet interface for network booting of a router, use the following command format: ifconfig [-s ] [-d] [ []] Table 8-3 describes the ifconfig command arguments for configuring the router’s Ethernet interface. Table 8-3. Settings for the ifconfig Command (Ethernet Interface) Setting Description Slot setting: -s
Using Technician Interface Software Enabling and Disabling Interfaces with ifconfig To enable an AN or ANH interface for the network boot process or to disable an interface from the network boot process, use the following command formats: ifconfig -disable ifconfig -enable To enable an ASN interface for the network boot process or to disable an interface from the network boot process, use the following command formats: ifconfig [-s
System Administration Booting the Router The Technician Interface provides the following commands for booting: • The boot command warm-starts the entire system. Pressing the Reset button on the front panel of the router initiates the same procedure. You can override the default router software image and configuration by specifying an alternative router software image and an alternative configuration file when entering the boot command.
Using Technician Interface Software A warm start occurs when you hot-swap a module, press the Reset button, or issue the boot or reset command. The processor module boots without running diagnostics. When you hot-swap a module, the DIAG LED on the front panel and LED 8 on the FRE module daughterboard behind the RFI shield remain on, indicating that diagnostics have not been run. (We recommend that you issue the diags command when you hot-swap a board.
System Administration You can also boot the entire system by naming a specific image or configuration file. With this “named boot” operation, the system uses the image or configuration file name that you specify instead of the default image or configuration file. Use the following syntax to perform a named boot operation: boot : : boot :- : boot : :- identifies the volume that contains the .
Using Technician Interface Software Examples: boot The system uses the default router software image (for example, bn.exe) and the configuration file (config) on the volume to come up with the valid boot name boot 2:- 2:- The system uses the (default) router software image on volume 2 and the (default) configuration file (config) on volume 2 or boot 2:bn.exe 2:config boot 2:net1.exe 3:- The system uses the net1.
System Administration If the PCMCIA/Floppy switch is in the PCMCIA setting, and you boot the router, the following occurs: 1. The router boots from 1:ace.out if it is available. If not, it boots from 2:ace.out if it is available. If both are unavailable, a boot error occurs. 2. The router configures from 1:config if it is available. If not, it configures from 2:config if it is available. If both are unavailable, a configuration error occurs.
Using Technician Interface Software If you choose N (no), the system terminates shutdown and displays the following message on the console device: Shutdown aborted. Upon issuing this message, the system performs a boot operation using the image and configuration files you specified originally. If you chooseY, the system continues the shutdown attempt. We recommend that you terminate this procedure after no more than one additional shutdown attempt.
System Administration a. Define a slot mask for scheduled boot services on the router. You must define a slot mask for the RUIBOOT entity, before creating the scheduled boot service on the router. The slot mask identifies the slots on which the system loads and runs RUIBOOT. Enter the following at the Technician Interface prompt: BN [3]: set wfServices.wfRuiBootLoad.0 0x7FFE0000 BN [3]: commit This command allows RUIBOOT, once created, to run on all slots.
Using Technician Interface Software Note that the instance ID does the following: Octet 1 Octet 2 • Specifies when the scheduled boot event will occur • Comprises 11 octets, each of which contains in decimal notation one element of the date and time you want to specify for the boot event (Figure 8-1) Octet 3 Octet 4 Octet 5 Octet 6 Octet 7 Octet 8 Octet 9 Octet 10 Octet 11
System Administration The following table specifies acceptable values for each octet of : Field Values (decimal notation) Octet No. Year 1996 to 9999 1 and 2 Month 1 to 12 3 Day 1 to 31 4 Hour 0 to 23 5 Minute 0 to 59 6 Second 0 to 60* 7 Deci-seconds 0 to 9 8 Direction offset from UTC ASCII 43 (for “+”) ASCII 45 (for “-”) 9 Hours offset from UTC 0 to 11 10 Minutes offset from UTC 0 to 59 11 * Use 60 for leap-second.
Using Technician Interface Software Octet 1 Octet 2 Octet 3 Octet 4 Octet 5 Octet 6 Octet 7 Octet 8 Octet 9 Octet 10 Octet 11 19 98 05 26 13 30 15 00 45 09 22 TS0021A Figure 8-2. RUIBOOT Date and Time Example 3. Specify a boot image name. Specify a router software image name for that entry, as follows: BN [3]: set wfRuiBootTable.
System Administration 4. Specify a configuration file name, as follows: BN [3]: set wfRuiBootTable.wfRuiBootConfigName. “config2” BN [3]: commit The name you specify belongs to the RUIBOOT table entry that has the same instance ID. 5. Add additional scheduled boot events. To add more scheduled boot events to the router configuration, repeat steps 2 through 4, otherwise, go to step 6. 6.
Using Technician Interface Software Managing Scheduled Boot Services This section describes how to • Disable or reenable scheduled boot services on the router. • Disable or reenable a scheduled boot event made for an earlier time on the router. • Change the name of the router software image and/or configuration file you want the router to boot with at a later time. • Delete entries from the RUIBOOT table of scheduled boot events. • Delete scheduled boot services from the router.
System Administration Modifying Attributes for Scheduled Boot Events You can modify • The name of the router software image file • The name of the router configuration file You cannot directly modify the date, time, or UTC offset (attribute wfRuiBootDateAndTime) for a scheduled boot event. If you need to change any of these for an existing entry in the RUIBOOT table of scheduled boot events, proceed as follows: 1. Delete the entry from the RUIBOOT table of scheduled boot events. 2.
Using Technician Interface Software Restarting a Slot The restart command allows you to restart the GAME image currently in use on specified slots. Restarting a slot does not reboot with a new router software image. You restart slots by entering the slot number or numbers after the restart command. Not entering a slot number when issuing the restart command, restarts all slots.
System Administration Restarting After Crossnet Shutdown Notification (BayStream Only) On BayStream platforms only, you can use the -shutdown option of the restart command to restart the GAME image on one or more slots, following a “graceful crossnet shutdown”on the same slots. With this option, the system notifies the remote end of any associated frame relay switch (frsw) PVCs to expect a loss of connectivity.
Using Technician Interface Software Resetting a System or Slot The reset command allows you to reboot one or more slots with a new router software image. You reset one or more slots by entering the slot number or numbers after the reset command. If you do not enter a slot number when issuing the reset command, the entire system reboots with the default router software image and configuration. Entering the reset command without entering at least one slot number is equivalent to entering the boot command.
System Administration 5. The resetting processor module loads the configuration image and initiates the services provided by the slot; connectivity is thus reestablished. The resetting processor module alerts the other processor modules that it can receive packets. 6. The other processor modules resynchronize their routing tables accordingly. To reboot the entire system, enter only reset at the command line prompt. To reset only the processor module or modules you specify by
Using Technician Interface Software Table 8-4. Router Reset Commands and Respones You issued a reset command from a Technician Interface session (console or Telnet) on one slot, and the target you specified was: (None) A slot other than the slot The same slot on which the on which the session is session is running running reset reset
System Administration Note: If you reset the slot in which the Technician Interface is running, the Technician Interface resets with the next available slot on a multislot system, or with the same slot on a single-slot system. Resetting After Crossnet Shutdown Notification (BayStream Only) On BayStream platforms only, you can use the -shutdown option of the reset command to reset one or more slots, following a “graceful crossnet shutdown” on the same slots.
Using Technician Interface Software If you choose N (no), the system terminates shutdown and displays the following message on the console device: Shutdown aborted. Upon issuing this message, the system performs the reset operation. If you choose Y, the system continues the shutdown attempt. We recommend that you terminate this procedure after no more than one additional shutdown attempt. Running Diagnostics The diags command cold-starts one or more specified slots or the entire system.
System Administration Examples: diags Runs diagnostics and reboots the entire system diags 1 Runs diagnostics for and reboots slot 1 diags 1-5 Runs diagnostics for and reboots slots 1, 2, 3, 4, and 5 diags 4,6 Runs diagnostics for and reboots slots 4 and 6 The system runs diagnostics on the associated slot or slots, loads the router software image, loads the configuration, and initiates the router software services. When you issue the diags or diags
Using Technician Interface Software Table 8-5. Router Diagnostic Commands and Respones You issued a diag command from a Technician Interface session (console or Telnet) on one slot, and the target you specified was: (None) Command-> diag The same slot on which the session is running A slot other than the slot on which the session is running diag diag
System Administration When you issue the Technician Interface diags command to test and reboot a specific module, the test and reboot process may take anywhere from 2 1/2 minutes to 10 minutes to complete, depending on the memory configuration of the board. For example, when you issue the diags command for a FRE-2 processor module with 8 MB of DRAM, the process takes approximately 3 minutes to complete.
Using Technician Interface Software Examples: diags -on [] The ARN executes all power-up diagnostics at subsequent restarts. diags -off [] The ARN skips power-up diagnostics at subsequent restarts. diags The ARN restarts immediately and executes complete diagnostics. Turning Off the DIAG Indicator LED The DIAG LED lights during diagnostics and goes out after diagnostics have determined that the processor module and its associated link module are functional.
System Administration Halting Packet Transfer Between Slots When you reset a slot containing a processor (FRE or ACE) module, the router automatically halts packet transfer between the resetting slot and the other slots in the router. Packet transfer automatically resumes after the slot is operational again. When you hot-swap a FRE module, the router also automatically halts and then resumes packet transfer.
Using Technician Interface Software The executable software consists of the following binary files: • The diagnostics image file is named frediag.exe. To upgrade with a new diagnostics image, transfer the new frediag.exe file to the file system, issue the readexe command to validate it, and issue the prom -w command to load (write) it onto the diagnostics PROM. The diagnostics PROM device supplies the FRE processor module with diagnostic instructions during a cold start.
System Administration When the system boots, it automatically loads the default router software image (unless you specify another router software image) from another slot into memory on the processor module or, if another slot is unavailable, from the file system to memory. To upgrade with a new image, transfer the image to the file system and reset the system; do not use the prom -w command when upgrading with a new router software image. Note: You cannot edit executable files.
Using Technician Interface Software $ readexe 5:bn.exe Processing contents of '5:bn.exe'... ---------------------------------- Module name: krnl_bn.exe --------------------------------Validating header checksum... OK Validating image checksum...
System Administration -- Entry point indicates the location in memory of the first software instruction when the file is loaded into memory. This field is 0 if the file is compressed. • PROM storage address space indicates the location in the PROM for the frediag.exe and freboot.exe software. This field is 0 if the file is not stored in a PROM.
Using Technician Interface Software Upgrading and Verifying a PROM You use the prom command to upgrade or verify the software on a diagnostics or bootstrap PROM in a Bay Networks router or BayStream platform. Only users who login as “Manager” can access the prom command. If a software release includes a PROM software upgrade, see the upgrade documentation shipped with the software for instructions on upgrading the PROMs on your router.
System Administration Upgrading PROMs Remotely Because the operations involved in upgrading PROMs place an increased load on the router, there is a greater chance that the PROM upgrade process will time out or fail during periods of peak traffic on your network. Caution: If the PROM upgrade process is interrupted, the router could be disabled. Follow these guidelines to ensure that the PROM upgrade is successful: • Store the PROM executable files (for example, frediag.exe or freboot.
Using Technician Interface Software Determining the Version of the Current Boot PROM Image To determine the version number of boot PROM images residing in a router, start a Telnet session with the router and enter the following command at the Technician Interface prompt: get wfHwEntry.19.* With a Model BLN router, for example, information similar to the following appears, with one wfHwEntry.wfHwBootPromSource line for each slot. wfHwEntry.wfHwBootPromSource.1 = (nil) wfHwEntry.wfHwBootPromSource.
System Administration With a Model BLN router, for example, information similar to the following appears, with one wfHwEntry.wfHwDiagPromSource line for each slot: wfHwEntry.wfHwDiagPromSource.2 = "/harpdiag.rel/v4.00/wf.pj/harpoon.ss/image.p/frediag.exe" wfHwEntry.wfHwDiagPromSource.3 = "/harpdiag.rel/v4.00/wf.pj/harpoon.ss/image.p/frediag.exe" wfHwEntry.wfHwDiagPromSource.4 = "/harpdiag.rel/v4.00/wf.pj/harpoon.ss/image.p/frediag.exe" wfHwEntry.wfHwDiagPromSource.5 = "/harpdiag.rel/v4.00/wf.pj/harpoon.
Using Technician Interface Software If you need more contiguous free space for the image: 2. • Delete unnecessary or obsolete files. • Compact the contents of the flash card. Transfer the PROM image files (for example, freboot.exe and frediag.exe) to the flash card. From the Technician Interface, use the tftp command. (See “In-Band File Transfers” in Chapter 4 if you need more information.) 3. Establish a Technician Interface session with the router.
System Administration 6. To verify successful completion of a PROM upgrade, enter: prom -v For example, for a boot PROM, enter: prom -v : [freboot.exe | asnboot.exe | anboot.exe] For a diagnostics PROM, enter: prom -v : [frediag.exe | asndiag.exe | andiag.
Using Technician Interface Software Viewing the Load Addresses and Sizes of Applications The loadmap command allows you to view the load address and size of each dynamically loadable application. Enter the loadmap command with one or more of the following optional parameters to view the addresses and sizes of the applications located on a specified slot or slots. The
System Administration No dynamically loadable modules on SLOT 4 ---------------------Loadmap from SLOT 2: -----------------------> vines.exe 0x304a5c60 --> drs.exe 0x30467550 --> tms380.exe 0x304760e0 --> hdlc.exe 0x304caaf0 --> dst.exe 0x30526400 ---------------------Loadmap from SLOT 5: -----------------------> fr.exe 0x310b9f00 --> hdlc.exe 0x310c67d0 --> qsync.exe 0x3111c630 ---------------------Loadmap from SLOT 3: -----------------------> arp.exe 0x3048c0d0 --> ipx.exe 0x303fec60 --> at.
Using Technician Interface Software Setting the ACE Backplane Type The backplane command allows you to set or display the ACE backplane type in nonvolatile RAM. You issue the backplane command during the initial startup of your VME-based Bay Networks router. You need only enter the backplane command once during the life of the system controller installed in slot 1 of the router, unless you insert the system controller in another type of VME router.
System Administration The date, time, and GMT offset are displayed in mm/dd/yy hh:mm:ss +|- hh:mm format. For example: Aug 29, 1997 15:26:23 [GMT+12] The GMT offset is stored as a direction (+ or -) and a value in hours and minutes. Most time zone offset values are in hours, and do not include minutes. For example, the eastern standard time (EST) zone is 5 hours behind GMT (or GMT-5).
Using Technician Interface Software Configuring NTP Using the Technician Interface When you use the Technician Interface to configure the Network Time Protocol (NTP), you must configure NTP on each slot on the router to ensure that NTP initializes correctly. You can configure NTP on each slot by setting the following MIB variable from the Technician Interface: set wfProtocols.68.0 0xffffffff;commit 68 represents the wfNTPLoad attribute.
System Administration Proceed as follows to assign a password: 1. Enter the following: password [Manager | User] The console displays one of the following messages: Changing password for User Changing password for Manager 2. Proceed to step 3 if you are logged in as Manager and you are changing the User password. Otherwise, enter the old password at the following prompt: Old password: If there is no old password, press the Return key. 3.
Using Technician Interface Software Enabling and Disabling SecurID Authentication This section describes how to enable or disable SecurID services from a Technician Interface session. Note: You enable/disable SecurID services only from a router console (an ASCII terminal or terminal emulator connected directly to the router console port). You cannot enable/disable SecurID services through a Technician Interface session supported through a Telnet connection to the router.
System Administration If you accepted the default port, the following message appears on your console display: The default port 755 will be used for SecurID services. If you entered a different port number, the following message appears on your console or Telnet display: The port will be used for SecurID services. Is this information correct? (yes/no) 3. [yes] If you entered no, go to step 4; otherwise, securelogin replies: Telnet login now requires SecurID.
Using Technician Interface Software You have completed the procedure, and you have not changed any configuration information for the SecurID client software on the router. Disabling SecurID Authentication Once the Technician Interface login prompt appears ($, or whatever your network administrator has set up for a prompt), proceed as follows to disable SecurID authentication services already enabled and active on the router: 1. Run the securelogin configuration utility. $: securelogin 2.
System Administration Managing SNMP Secure Mode Bay Networks implements an optional security mechanism for all SNMP set requests. This proprietary mechanism is an interim solution to solve some SNMP security problems until a stable, widely accepted industry-standard security solution is available. Our security system uses counters to synchronize management operations between manager and agent.
Using Technician Interface Software Setting the Router to Operate in Secure Mode The wfsnmpmode command allows you to specify whether or not you want the router to operate in SNMP secure mode. Enter the wfsnmpmode command in the following format: wfsnmpmode [1 | 3] 1 (trivial) indicates that the router should provide no additional security beyond a simple community name. 3 (proprietary) indicates that the router should operate using our proprietary security mechanism.
System Administration Resetting the Security Counter The wfsnmpseed command allows you to reset the counter used by the security mechanism. Under normal operating conditions, it is not necessary to reset the counter; this command is mainly for debugging purposes.
Using Technician Interface Software By increasing the search depth, you may enable the daughterboard to attain compression ratios higher than are possible using default or inherited search depth values. The results you achieve depend greatly on the type of data you want to compress over a circuit or line. Note, however, that increasing the compression ratio beyond a certain value on a circuit or line may also lower the throughput on that circuit or line.
System Administration WCP Search Depth Attributes The modifiable search depth attributes for the WCP entity have the following characteristics: Parameter: Attribute Name: WCP Line Search Depth wfWcpLineSearchDepth Attribute Number: 9 Default: 3 Options: 0 (no compression on this line) to 255 (maximum compression on this line) Function: Defines the depth of searching for repetitive patterns in the data you want to send over a synchronous line.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: WCP Circuit Search Depth wfWcpCircuitSearchDepth 7 Default: 256 Options: 0 (no compression on this circuit) to 255 (maximum compression on this circuit), or 256 (inherit wfWcpLineSearchDepth value on this circuit) Function: Defines the depth of searching for repetitive patterns in the data you want to send over a specific (virtual) circuit.
System Administration Displaying a Greeting or Notice Before the Login Prompt You can create a greeting, notice, caution, or warning message that appears before the Technician Interface Login: prompt. To create and initialize this message on the router, proceed as follows: 1. Create an ASCII file named ti_notice.txt on your UNIX workstation or PC. 2. Enter the text of a greeting or notice message that meets your requirements. Format the message with appropriate spacing and return characters.
Using Technician Interface Software 2. Use TFTP to copy ti_msg.txt from the router to your UNIX workstation or PC. 3. Open ti_msg.txt on your workstation or PC. 4. Edit the default Welcome message, or enter a replacement message up to 256 characters in length. Format the message with appropriate spacing and return characters. 5. Save your new version of ti_msg.txt. 6. Use TFTP to copy ti_msg.txt back to the router. The new version of the file replaces the original version on the router.
System Administration You can suspend recording temporarily by using the pause option. You can determine the state of recording by testing the global variable RECORD_STATE from a script. ON indicates the system is recording, OFF indicates recording is turned off, and PAUSED indicates that recording is temporarily suspended. To display the pause state of the record command, enter the following: record pause To change the pause state, enter record pause [on | off] on disables recording.
Using Technician Interface Software Enabling Internal Clocking Mode Within test environments and when using the HSSI crossover cable (Order No. 7832), you may need to configure Bay Networks routers from the Technician Interface to enable internal clocking mode. Enter the following at the Technician Interface prompt: set wfHssiEntry.wfHssiInternalClkTestMode.4.1 1;commit The default value, 2, enables external clocking. The new value, 1, enables internal clocking.
System Administration Then save the configuration with these changes to the configuration file. When you set the wfCSMACDAlignmentMode attribute to 1 (ALIGN_ALL), the router realigns the nonoptimally aligned frames before transmitting them. When you set the wfCSMACDAlignmentMode attribute to 3 (DISABLED), the router transmits the nonoptimally aligned frames without realigning them first.
Using Technician Interface Software Table 8-6 explains the meanings of each ip subcommand in more detail. Table 8-6. IP Subcommand Meanings Subcommand System Response routes The routing table you select by specifying appropriate command flags. RIP and EGP routes refresh only on slots that receive route updates. Route ages may be different on each slot for this reason. bgp_routes The BGP routing table you select by specifying appropriate command flags.
System Administration Table 8-7. Flag Descriptions Flag Filtering Effect Applicable Subcommands
Retrieves data for IP addresses that match your address entry in dotted decimal notation routes | bgp_routes | cache | ospf_lsdb Retrieves data for IP addresses with an address mask routes | bgp_routes | that matches your entry. Specify an IP address in ospf_lsdb dotted decimal notation.Using Technician Interface Software Table 8-7. Flag Descriptions (continued) -s Retrieves data for the slot you specify after the -s flag. routes | bgp_routes | If you also specify an address of 255.255.255.255 for cache | dvmrp_caches | mtm a given slot, the command displays only the internal cache for that slot. If you do not enter a slot number, the command retrieves only data pertaining to the slot where the Technician Interface is running.
System Administration Example (ip routes) Enter the following command to display the table of IP “best” (used or active) routes: ip routes Network/Mask Proto Age ---------------- ------ -----2.0.0.0/8 RIP 30 10.0.0.0/8 RIP 30 122.0.0.0/8 RIP 30 131.192.0.0/16 RIP 30 132.245.0.0/16 RIP 30 134.177.0.0/16 RIP 30 140.200.0.0/16 RIP 30 162.78.0.0/16 RIP 30 . . . Slot Cost ----- -----2 5 2 3 2 5 2 3 2 3 2 3 2 3 2 3 NextHop Address AS ---------------- -192.168.125.33 192.168.125.33 192.168.125.33 192.168.125.
Using Technician Interface Software Example (IP routes) Enter the following command to display the entire table of routes, including inactive, unused, and best routes: ip routes -A Network/Mask Proto Age Sl Cost NextHop Address / AS Weight ------------------ ------ -------- -- -------- ----------------/----- -------*0.0.0.0/0 RIP 20 2 2 192.32.174.33 7b9e0002 0.0.0.0/0 Direct 385 0 131071 Unreachable ffffffff 0.0.0.0/32 Host N/A 0 0 un# IP cct 0 00000000 *6.0.0.0/8 Direct 385 2 0 6.6.6.6 00000000 6.0.0.
System Administration Example (bgp routes) Enter the following command to display the entire BGP table of routes: ip bgp_routes Network/Mask Peer Rem Addr NextHop Address Org Loc Pref Best/Used ------------- ---------------- ---------------- --- ---------- --------4.0.0.0/8 3.3.3.2 3.3.3.2 IGP 8183 BEST/USED As Path: SEQ 200 5.0.0.0/8 2.2.2.3 2.2.2.3 IGP 8183 As Path: SEQ 300 ...
Using Technician Interface Software Example (bgp routes) Enter the following command to display routes announced to the peer with a local address of 3.3.3.1 and a remote address of 3.3.3.2: ip bgp_routes -N -p3.3.3.1/3.3.3.2 Network/Mask Peer Rem Addr NextHop Address Org Loc Pref ------------------ ---------------- ---------------- --- ---------1.0.0.0/8 3.3.3.2 3.3.3.1 IGP -1 As Path: SEQ 100 Multi-exit-disc -1 Aggregator 100 192.32.140.40 2.0.0.0/8 3.3.3.2 3.3.3.
System Administration Example (bgp routes) Enter the following command to display routes announced to BGP peers known to the local router: ip bgp_routes -N Network/Mask -----------------192.32.174.4/30 As Path: SEQ 2 192.32.174.8/30 As Path: SEQ 2 192.32.174.32/27 As Path: SEQ 2 192.32.174.96/27 As Path: SEQ 2 192.32.174.128/27 As Path: SEQ 2 192.32.174.160/27 As Path: SEQ 2 192.32.174.192/27 As Path: SEQ 2 Peer Rem Addr NextHop Address Org Loc Pref --------------- --------------- --- ---------192.32.
Using Technician Interface Software The column headings in screens invoked by the ip command have the following meanings: 8-72 * (asterisk) Indicates routes actively used by IP, versus routes not currently used. (The asterisk appears only when you specify the all routes [-A] flag.) Adv Router Indicates the OSPF router ID of the advertisement's originator. For router links advertisements, this field is identical to the Link State ID field.
System Administration 303561-A Rev 00 LS Type Indicates the type of OSPF link state advertisement, as follows: 0 = stub advertisement 1 = router links advertisement 2 = network links advertisement 3 = summary link (IP network) advertisement 4 = summary link (ASBR) advertisement 5 = external link advertisement See RFC 1583 for more information about LS Type. Mask Subnet mask to be combined with the destination address and then compared with the value in Destination. If the value of Destination is 0.0.0.
Using Technician Interface Software Specifying AS Path Search Patterns To retrieve only AS paths that contain a specific pattern of data, enter the following command: ip bgp_routes -R -R Indicates that a follows. The software filters the output of the ip bgp_routes command according to the contents of the . Specifies a regular expresson in terms of efficient, symbolic syntax.
System Administration Table 8-8.
Using Technician Interface Software Table 8-9. Simplified AS Pattern Matching Examples (continued) Command Operation ip bgp_routes -R 555 Match any occurrence of the string 555 in any AS path. AS path contains: ip bgp_routes -R _234 333 343_ Match any consecutive occurrence of these Autonomous Systems. ip bgp_routes -R >{ Match any AS path that contains both a SEQUENCE and a SET. AS path begins with: ip bgp_routes -R ^666_ Match any AS path that begins with AS 666.
System Administration Unlike the show ip script command, which retrieves from the router’s active MIB an aggregated view of data from IP routing tables and internal caches across all slots, the Technician Interface ip command retrieves the contents of the routing table on a single slot that you specify. For this reason, the ip command retrieves information significantly faster than the show ip command.
Using Technician Interface Software • ARP processing -- The packet has been held and an ARP request packet has been sent to the LAN for that host. When the address is resolved, the cache entry for this host is flushed (deleted) and the packet is forwarded. • Multicast processing -- The packet will be handled using information from the multicast cache. (More information follows on the multicast cache.) The internal cache is limited in size, and operates on a first in first out (FIFO) basis.
System Administration Slot/Internal Cache The router operating system maintains an “internal” cache storage space on (and for) each slot in the router. This slot-level, internal cache stores routing information captured from traffic originated on the router. For example, the PING protocol, the IP protocols, and TFTP can each generate their own traffic destined for IP address locations internal or external to the router.
Using Technician Interface Software DVMRP Caches With the ip command, you can examine the contents of the DVMRP cache on any slot that you specify. To view the DVMRP cache for any DVMRP slot on the router, enter the ip command using the following syntax: ip dvmrp_caches -s is the slot number associated with the DVMRP cache you want to examine. You must enter a slot number for the ip dvmrp_caches command.
System Administration Viewing the Multicast Table Manager Forwarding Cache The Multicast Table Manager (MTM) maintains a multicast forwarding cache table. The ip mtm command allows you to view the cache table for a particular slot. To view the MTM cache, enter the ip command using the following syntax: ip mtm -s is the slot number associated with the MTM cache you want to examine. You must enter a slot number for the ip mtm command.
Using Technician Interface Software For example, the following display shows that on this slot there is a cache entry for <192.32.27.112/32, 224.2.2.5). 224.2.2.5 192.32.27.112/32 in: 3D 5d out:(10000000) 2D1 4M2 The slot is accepting packets on circuit 3 (which is running DVMRP) for the flow (192.32.27.112/32, 224.2.2.5), and dropping packets for the flow on circuit 5 (also running DVMRP).
System Administration Determining Circuit Numbers Whenever you create a new circuit via the Technician Interface or the Configuration Manager tool, the router operating system software (GAME) maps the circuit name you assign (such as E21) to a circuit number (such as 4) in the router’s active MIB. When you use the Technician Interface ip command to display data pertaining only to a specific circuit on a router, you must enter the circuit number after the -c option flag for that command.
Using Technician Interface Software Example The following command retrieves the circuit number (attribute 5) for every entry in the IP Interface table: $ g wfIpInterfaceEntry.5.* wfIpInterfaceEntry.wfIpInterfaceCircuit.192.32.174.33.3 = 3 wfIpInterfaceEntry.wfIpInterfaceCircuit.192.32.174.66.4 = 4 wfIpInterfaceEntry.wfIpInterfaceCircuit.192.32.174.98.2 = 2 wfIpInterfaceEntry.wfIpInterfaceCircuit.192.32.175.66.1 = 1 The instance ID for each entry in this case is .
System Administration Monitoring IPv6 Routes The ip6 command allows you to display IPv6 data. You choose the type of data by specifying a in the command line. You can also selectively filter the data by specifying one or more
Using Technician Interface Software Obtaining IPv6 Route and Node Information The ip6 routes command displays IPv6 routes using the various subcommand options mentioned in Table 8-12. Table 8-12. Options for ip6 routes Command Option Description
Retrieves IPv6 addresses (prefixes) that match the address (prefix) entry Retrieves a range of IPv6 addresses (prefixes) that match your entry. Specify all or part of an IPv6 address and a prefix length from 1 to 128 bits.System Administration The IPv6 column headings have the following meanings: Prefix Indicates the prefix (address) and prefix length (from 1 to 128 bits) of the IPv6 route. Protocol Indicates the IPv6 interface protocol type.
Using Technician Interface Software Example (ip6 routes) Enter the following command to display all IPv6 routes on the device: ip6 routes Prefix ------------------------------------------::0.0.0.0/128 ::0.0.0.
System Administration Example (ip6 routes
/) Enter the following command to display the range of IPv6 addresses for the address(prefix) 3FFE:1300:0100::0 with a prefix-length of 48 bits: ip6 routes 3FFE:1300:0100::0/48 Prefix ------------------------------------------3FFE:1300:0100:0001::0000/64 3FFE:1300:0100:0002::0000/64 3FFE:1300:0100:0003::0000/64 3FFE:1300:0100:0004::0000/64 3FFE:1300:0100:0005::0000/64 3FFE:1300:0100:0006::0000/64 3FFE:1300:0100:0007::0000/64 3FFE:1300:0100:0008::Using Technician Interface Software ip6 routes -pDN Prefix ------------------------------------------FE80::0040:0522/128 FE80::0006:A240:0522/128 FE80::5E10:AF47:0101/128 FE80::0200:A2FF:FE0B:AE7E/128 Protocol ---------DynNode DynNode DynNode DynNode Next Hop Intf.
System Administration ip6 stats 1 Interface 1 (PPP to Quincy_Adams) is Up: Link: PPP at 64102 bps (circuit 3) Neighbor Discovery: Off, Router Advertisements: Off Address(es): FE80::0001:A2B0:1FBE (link-local) Rx 434756, Tx 441626, Drop 0, Err 0 Icmp In: DestUnr 0, TimeExc 0, ParmProb 0, TooBig 0 Icmp Out: DestUnr 0, TimeExc 0, ParmProb 0, TooBig 0 Icmp In: Echos 0, EchoRep 0, RS 0, RA 0, NS 0, NA 0 Icmp Out: Echos 0, EchoRep 0, RS 0, RA 0, NS 0, NA 0 Setting Modem Initialization Strings Several AT modem co
Using Technician Interface Software Technician Interface Commands and Access Levels The Technician Interface provides two access levels: • User access level accepts read-only commands. • Manager access level accepts all Technician Interface commands. Table 8-13 lists all Technician Interface commands and their associated access levels. Table 8-13.
System Administration Table 8-13.
Using Technician Interface Software Table 8-13.
System Administration Table 8-13.
Chapter 9 Managing Aliases An alias is a command you create to take the place of long or multiple commands. After creating the alias, you enter the alias name to invoke its associated commands. This chapter describes how to do the following: 303561-A Rev 00 • Create an alias in memory and enter its name to invoke its associated commands. • Display the commands associated with an alias. • Debug an alias. • Delete an alias. • Save aliases to a file in the NVFS for later retrieval.
Using Technician Interface Software Creating and Displaying an Alias You can use the alias command either to create an alias or to display the commands associated with an existing alias. Enter the following to display or create an alias: alias [ [ ["]["] ] ] is one of the following optional alias name types: • The name of the alias you are creating. The name may be one to 15 alphanumeric characters; the initial character must be alphabetical.
Managing Aliases Examples: alias Displays all aliases residing in RAM alias ebridge “set wfBrTp.2.0 1; set wfBrStp.2.0 1;commit” Creates an alias named ebridge that invokes the listed commands ebridge • Enables the translating bridge and the spanning tree bridge • Notifies all relevant software modules of set changes to the MIB alias gbridge “get wfBrTp.2.0; get wfBrStp.2.
Using Technician Interface Software The parameter number indicates the position of the value in the user entry. This feature allows you to use the same value for more than one parameter; see the last two examples. Examples: 9-4 alias scroll “more $” Creates an alias named scroll that invokes the more command and inserts the value the user enters when using the alias (as shown in the next example). scroll on Invokes the command more on.
Managing Aliases Inserting Character Strings in an Alias The echo command prints one or more strings of characters to the Technician Interface console. When the Technician Interface receives the echo request, it sends the accompanying string or strings back to the console. This command is used primarily to accompany system responses to alias commands with meaningful text. This section describes how to issue an echo command and how to insert the echo command in an alias.
Using Technician Interface Software Examples: alias ipstats “echo \; echo \“IP Input Statistics:\”; echo \; get WfIpInterfaceEntry.21.*\; echo \; echo \“IP Output Statistics:\”; echo \; get WfIpInterfaceEntry.24.*” The system creates an alias named ipstats that invokes the commands shown in quotes. Note that the text wraps as you enter text past column 80. Do not press the Return key until you have entered the entire command.
Managing Aliases Debugging Aliases The verbose command allows you to display the commands within an as an alias executes. This command is useful for locating syntax errors within the . Enter the following to display the verbose mode: verbose If the verbose mode is on, the system displays the commands as they execute. If the verbose mode is off, the system does not display the commands.
Using Technician Interface Software Examples: unalias scroll Deletes the alias named scroll unalias * Deletes all aliases from memory Saving Aliases to a File You can copy all aliases residing in RAM to a file on a volume for later retrieval. Enter the following to create an alias file: save aliases : is the volume that will store the alias file. is the name of the alias file. Example: save aliases 2:aliases.1 Creates a file named aliases.
Managing Aliases Loading Aliases from a File You can use the source aliases command to load the aliases from a file residing on the volume to active RAM. The aliases already residing in memory remain in memory; however, the system overwrites any aliases in memory that have duplicate names. Use the unalias * command if you want to delete all aliases from memory before entering the source aliases command.
Using Technician Interface Software Debugging with Predefined Aliases This section describes how to use aliases that are useful for debugging common network problems. These aliases are located in the debug.al file. Enter the following to load the aliases that are predefined for debugging, where is the volume containing the files from Bay Networks: source aliases :debug.al Note: You can also use run :debug.al. Table 9-1 shows each alias and its associated function.
Managing Aliases Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: at_cur Displays the current network start, network end, and default zone for all AppleTalk interfaces. at_it Displays the status of all AppleTalk interfaces. at_rt Displays the entries in the routing table, including the node and network IDs of the next hops in the network, the number of hops, and the status of the network. at_zones Lists the zones in the router’s zone table.
Using Technician Interface Software Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: bgp3nexthop Displays the NEXT_HOP attribute of each network advertisement received via BGP-3. bgp3metric Displays the INTER_AS_METRIC attribute of each network advertisement received via BGP-3. cctnames Displays all circuit names. ccttypes Displays all circuits and their types.
Managing Aliases Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: decpri Displays DECnet circuit priorities for all interfaces. deccost Displays DECnet circuit costs for all interfaces. decstats Displays all DECnet receive, transmit, and dropped statistics. enetstats Displays all Ethernet receive and transmit statistics. fddior Displays the number of FDDI octets received for the specified circuit. fddifr
Using Technician Interface Software Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: fr_vcs Lists all instances (configured PVCs) in the frame relay virtual circuit table. fr_vc Lists all MIB attributes for the virtual circuit table of the specified frame relay PVC. hwmods Displays slots and their associated hardware module IDs. hwnode Displays the serial number and revision level of router.
Managing Aliases Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: ipx_intf Enables or disables a specific IPX interface. 1 = Enable 2 = Disable ipx_if Displays the IPX interface record for the specified interface ID. ipx_route Displays the IPX route record for the instance ID of the particular route you specify. ipx_server Displays the IPX server table for the instance ID of the particular server you specify.
Using Technician Interface Software Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: lbstate Displays bridge interfaces and their current states. The following example shows one line in the list of interfaces, where 1 is the index and 2 is the state: wfBrTpInterfaceEntry.wfBrTpInterfaceState.1 = 2 The states are 1 = Up 2 = Down 3 = Init 4 = Not present lbstats Displays bridge receive, transmit, and dropped packet statistics. mem_info
Managing Aliases Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: ospf_intf Reports the state of all the router’s OSPF interfaces, including virtual links. The states are 1 = Down 2 = Loopback 3 = Waiting 4 = Point to point 5 = Designated router 6 = Backup designated router 7 = Other designated router ospf_lsdb Lists all interfaces in the link-state database. ospf_nbrs Reports the state of every OSPF neighbor that the router knows about.
Using Technician Interface Software Table 9-1. Aliases for Debugging Network Problems (continued) If you enter: The system: stif Displays all spanning tree bridge information for the (learning) bridge interface index you enter. You can obtain the by using the lbstate alias. stroot Displays the spanning tree designated root node identifier. ststate Displays the current state of each link running the spanning tree protocol in the node.
Managing Aliases Table 9-1. 303561-A Rev 00 Aliases for Debugging Network Problems (continued) If you enter: The system: vines_cctstats Displays VINES statistics for a specified circuit. vines_client_en Enables VINES clients.
Appendix A Using the Bay Networks Router MIB This appendix describes how to use the Bay Networks router management information base (MIB). The Bay Networks router MIB is a proprietary database that contains configuration parameters and statistics. You use the Bay Networks router MIB to obtain and change configuration parameters and statistics through the Technician Interface or through network management software.
Using Technician Interface Software Overview This section examines the structure of the Bay Networks router MIB. The object tree assigned to the Bay Networks router MIB is as follows: iso.org.dod.internet.private.enterprises.wellfleet The corresponding numeric identifier assigned to the Bay Networks router MIB subtree is as follows: 1.3.6.1.4.1.18 Figure A-1 shows an example of the hierarchy of objects. The prefix that precedes each object name identifies a Bay Networks enterprise-specific object.
Using the Bay Networks Router MIB wellfleet (enterprises.18) wfSwSeries7 (wellfleet.3) wfHardwareConfig (wfSwSeries7.1) wfHwModuleGroup (wfHardwareConfig.4) wfHwIdentities (wfHardwareConfig.5) wfHwFn (wfHwIdentities.1) wfHwLn (wfHwIdentities.2) wfHwCn (wfHwIdentities.3) wfHwAfn (wfHwIdentities.4) wfHwAn (wfHwIdentities.16) wfHwAnMpr (wfHwAn.1) wfHwAnHub (wfHwAn.2) wfHwBln (wfHwIdentities.16640) wfHwBcn (wfHwIdentities.16896)) wfHwRbln (wfHwIdentities.17152 wfHwAsn (wfHwIdentities.
Using Technician Interface Software wfLine (wfSwSeries7.4) wfCSMACDTable (wfLine.1) wfWfTokenRingTable (wfLine.2) wfAsyncTable (wfLine.3) wfFddiTable (wfLine.4) wfSyncTable (wfLine.5) wfHwFGroup (wfLine.6) wfHssiTable (wfLine.7) wfMcT1Group (wfLine.8) wfDS1E1Group (wfLine.9) wfDs1Group (wfLine.12) wfDs3Group (wfLine.13) wfSipGroup (wfLine.14) wfSipPlcpGroup (wfSipGroup.2) wfFddiGroup (wfLine.15) wfFddiSmtGroup (wfFddiGroup.1) wfFddiMacGroup (wfFddiGroup.2) wfFddiPathGroup (wfFddiGroup.
Using the Bay Networks Router MIB wfApplication (wfSwSeries7.5) wfDataLink (wfApplication.1) wfBridgeGroup (wfDataLink.1) wfBrLearning (wfBridgeGroup.1) wfBrSourceRouting (wfBridgeGroup.2) wfBrTpInterface (wfBridgeGroup.3) wfBrTrafficFilterTable (wfBridgeGroup.4) wfBrNativeModeLan (wfBridgeGroup.5) wfSpanningTree (wfDataLink.2) wfIfGroup (wfDataLink.3) wfCircuitOptsGroup (wfDataLink.4) wfDlsGroup (wfDataLink.5) wfLlcGroup (wfDataLink.6) wfSdlcGroup (wfDataLink.7) wfLapbTable (wfDataLink.
Using Technician Interface Software wfInternet wfBootpGroup (wfInternet.8) wfBootpClientGroup (wfBootpGroup.1) wfBootpServerGroup (wfBootpGroup.2) wfBootpRelayAgentGroup (wfBootpGroup.3) wfRarpGroup (wfInternet.9) wfFtpGroup (wfInternet.10) wfNetBIOSIpGroup (wfInternet.11) wfDvmrpGroup (wfInternet.12) wfIgmpGroup (wfInternet.13) wfPimGroup (wfInternet.14) wfIpv6Group (wfInternet.16) wfAppletalkGroup (wfApplication.4) wfIpxGroup (wfApplication.5) wfOsiGroup (wfApplication.6) wfVinesGroup (wfApplication.
Using the Bay Networks Router MIB Bay Networks Router MIB Files A collection of ASCII files (one per router entity) together describe the Bay Networks router MIB. These files load automatically onto the Site Manager workstation or PC when you install the Site Manager software. The Site Manager software modules read these files during startup. Site Manager installs these files at \wf\mibs on PCs, and at /usr/wf/mibs on UNIX workstations.
Using Technician Interface Software Also, the latest editions of the following textbooks provide information about these standards: • Comer, Douglas E. Internetworking with TCP/IP, Vol. 1. Englewood Cliffs, New Jersey: Prentice-Hall. • Rose, Marshall T. The Simple Book. Englewood Cliffs, New Jersey: PrenticeHall. • Stevens, Richard W. TCP/IP Illustrated, Vol. 1. Reading, Massachusetts: Addison-Wesley.
Using the Bay Networks Router MIB ifSpecific The object identifier that points to an instance of the first conceptual column in the appropriate proprietary media MIB. ipAddrEntry In certain circumstances, the index to this table, ipAdEntAddr, may not be sufficient to uniquely identify a particular instance. In these situations, the attribute ipAdEntIfIndex is appended to the instance identifier for subsequent entries with the same index.
Using Technician Interface Software authenticationFailure Issued when an SNMP access occurs. An invalid access occurs if a bad community or illegal manager address is used. Authentication traps will be masked if they are not enabled. egpNeighborLoss Issued when an acquired EGP neighbor is lost. enterpriseSpecific All Bay Networks router system log events can be sent as traps. They must be configured through the wfSnmpTrapEntityTable and the wfSnmpTrapEventTable.
Using the Bay Networks Router MIB The line number encodes several attributes of the line it represents. You can use Technician Interface list and get commands to examine and decode a line number. The individual fields of the number correspond to different attributes of a line, as follows: 0 00 00 00 0 00 | | | | | | resv chan type slot mod conn Field Purpose resv. (0-1) Reserved for future expansion, with a default value of 0.
Using Technician Interface Software Example: Line number = 102101 • chan = 1 • type = 0 • slot = 2 • mod = 1 • conn = 01 This is the only line on the first CSMACD connector on module 1 of slot 2.
Appendix B Using Out-of-Band Access to Transfer Files This appendix describes how to use the xmodem command to perform out-of-band file transfers. The xmodem command enables you to transfer files between remote workstations and Bay Networks routers when all IP routing paths between them are down. You cannot use the xmodem command to transfer files between Bay Networks routers.
Using Technician Interface Software This section describes: • The asynchronous terminal program available on UNIX and 386/486 DOS remote workstations • The Technician Interface xmodem command, its parameters, and its options • How you use the asynchronous terminal program and xmodem commands together in procedures for transferring files to and from Bay Networks routers About xmodem Bay Networks routers support xmodem as a Technician Interface command and a set of protocols for moving files between th
Using Out-of-Band Access to Transfer Files In support of Bay Networks router file management tasks, the YMODEM batch protocol has the following capabilities: • Supports batch file transfers (moving one or more files specified in a single xmodem command) • Automatically converts file names received during batch file transfer operations • Transfers binary files with error detection • Marks every transferred file with a timestamp, which indicates the most recent modification date of a file • Automati
Using Technician Interface Software The xmodem Command The following represents the syntax of the xmodem command: xmodem [sb | st | rb | rt ] < y | m | k | c | l | w | p | e | n > : ... Command Subcommands Options Source volume and source directory Files to send or Files to receive or Files to receive as TS0020B Note: You can enter the xmodem command line parameters and option flag characters in upper- or lower-case.
Using Out-of-Band Access to Transfer Files Command Parameters When you enter an xmodem command at the Technician Interface command line prompt, follow the entry with only one of the following parameters: Parameter Name Meaning or Action sb Send Binary Sends files as they exist on disk or in flash memory, without conversion. st Send Text Sends ASCII text files. rb Receive Binary Places files on disk or in flash memory, without conversion. YMODEM deletes existing files of the same name.
Using Technician Interface Software Table B-1. Option Flag Option Flags for the Xmodem Command Meaning or Action y Selects the YMODEM batch protocol for sending files. Sends in sequence any list of files you specify in the Technician Interface command line.
Using Out-of-Band Access to Transfer Files File Names The conventions for the treatment of file names by the YMODEM protocol are: • The source router or the remote workstation sends files with path names stripped and limited to eight characters plus a three-character extension. The router or workstation converts all file name characters to lowercase, and all “:” characters to “/” characters. • The target router or workstation stores received files under their transmitted names.
Using Technician Interface Software File Handling The following information applies to configuration files you transfer between a remote workstation and a Bay Networks router: • The YMODEM protocol truncates binary files received in a batch transfer operation. The YMODEM header specifies the truncated size. • YMODEM sets the file modification timestamp field in the header of all transmitted binary files. Note, however, that the timestamp is subject to a specific time-zone reference.
Using Out-of-Band Access to Transfer Files For more detailed information about these and other modem-related issues, see the user manual for the modem you want to use for Technician Interface access.
Using Technician Interface Software Out-of-Band File Transfers from a UNIX Workstation This section provides the procedures you need to: • Open a dial connection between your workstation and a specific router. • Transfer files to or from a router. • Close (hang up) the connection between the workstation and router. Opening a Connection On a SunOS platform, you can use the Terminal Interface Program or tip command to: • Establish a connection to the Technician Interface port of a router.
Using Out-of-Band Access to Transfer Files 3. Press Return to invoke the Technician Interface login prompt from the target router. The system displays the following prompt: Login: 4. Enter Manager and a password, if necessary, to log in to the router’s Technician Interface. The system displays the following message and prompt: Welcome to the Technician Interface. $ 5.
Using Technician Interface Software 8. Enter the xmodem send binary command, as follows: xmodem sby : . . . sb is a send binary file. y is the YMODEM file transfer option. is either a slot number of a memory card or the letter of the disk drive volume that contains the files you want to send to the workstation. is the name of the file you want to send from the router to the workstation.
Using Out-of-Band Access to Transfer Files Typical workstation and router responses are: ----------------XMODEM File Receive Function CRC mode requested on command line YMODEM Batch Protocol YMODEM Batch Receive Complete away for 37 seconds (the amount of time the router’s Technician Interface relinquished control to the router’s YMODEM protocol program; in other words, the duration of the file transfer operation) ! $ 11.
Using Technician Interface Software 5. Press Return to invoke the Technician Interface login prompt from the target router. The system displays the following prompt: Login: 6. Enter Manager and a password, if necessary, to log in to the router’s Technician Interface. The system displays the following message and prompt: Welcome to the Technician Interface. $ 7.
Using Out-of-Band Access to Transfer Files 10. Enter an xmodem send binary command with the print (display) transfer events and information option flag (p) set in the command line, as follows: xmodem sbyp : . . . sb is a send binary file. y is the YMODEM file transfer option. p prints (displays) important information and events pertaining to the file transfer(s) you are about to initiate.
Using Technician Interface Software Typical workstation and router responses are ----------------XMODEM Send Function File Name: atl.
Using Out-of-Band Access to Transfer Files Out-of-Band File Transfers from a Windows Workstation This section describes the Bay Networks Communications Terminal Program and its applications for logging in to the Technician Interface of a remote router, and for transferring files to and from a router. xmodem and the Bay Networks Communications Terminal Program The Bay Networks Communications Terminal Program (file name wfterm.
Using Technician Interface Software Opening Wfterm You can open Wfterm by double-clicking on its icon in the Site Manager icon group, as shown in Figure B-2. Figure B-2. Wfterm Icon Wfterm opens the window shown in Figure B-3. Figure B-3.
Using Out-of-Band Access to Transfer Files From this window, you can: • Check current settings or enter new settings for the interface to the modem locally attached to your workstation. • Initialize the locally attached modem with the current settings. • Enter a telephone number, initiate autodialing, and open a connection to a remote target router. • Log in to the Technician Interface of the remote router. • Transfer files between the router and your workstation.
Using Technician Interface Software Figure B-4. Accessing the Modem Settings Window Figure B-5. Verifying or Modifying Modem Interface Settings The settings shown in Figure B-5 reflect default operational values for any Hayes compatible modem. However, if you are sure that current interface settings for the modem locally attached to your Site Manager workstation are correct, proceed to the next section, “Initializing the Local Modem.
Using Out-of-Band Access to Transfer Files If you are unsure of the current modem interface settings, see the user manual supplied with the modem, make the required changes to the modem interface settings, and then proceed to the next section, “Initializing the Local Modem.” Initializing the Local Modem Before attempting to open a dial connection between your workstation and a remote target router, you need to initialize and “wake up” the modem locally attached to the PC.
Using Technician Interface Software Using Wfterm Telephone Call Functions You can access two telephone call functions from the Phone menu of the Wfterm startup window, as shown in Figure B-7. Figure B-7. Accessing Wfterm Telephone Call Functions Dialing a Remote Router To dial and connect to the Technician Interface port of a remote router, choose Dial Phone from the Wfterm phone menu. The Dial Command window opens (Figure B-8).
Using Out-of-Band Access to Transfer Files Figure B-8. Wfterm Dial Command Window Enter in the Dial Command window the telephone number of a router that has a configuration file you want to retrieve. Clicking on OK initiates the dialing sequence. Note: You can enter and store one telephone number in the Dial Command window. Each time you need to call a different router, enter the telephone number of that router in the Dial Command window.
Using Technician Interface Software Logging In to the Router’s Technician Interface After Wfterm connects to the Technician Interface port of a router, log in to the router’s Technician Interface as follows: 1. Press Return, if necessary, to invoke the Technician Interface login prompt from the target router. Watch for the prompt in the Wfterm base program window. The system displays the following prompt: Login: 2. At the login prompt, enter Manager.
Using Out-of-Band Access to Transfer Files Figure B-9. Wfterm File Transfer Operation Selection Window Note: Because the Wfterm utility provides more functionality than is required to support YMODEM file transfers, the File Transfers menu contains options for up to fourteen different file transfer operations. However, to transfer files between a workstation and a Bay Networks router, you need only the ymodem-send and ymodem-receive options.
Using Technician Interface Software Proceed as follows to transfer one or more files from a router to your workstation: 1. Enter a cd command to designate the disk volume or memory card “volume” that contains the files you want to transfer to your UNIX workstation. For example: cd a: (designates diskette volume a) or cd 2: (designates a memory card volume in router slot 2) 2. Enter a dir command to view the list of files in the volume/memory card.
Using Out-of-Band Access to Transfer Files Note: To ensure that files are transferred properly, do not issue the xmodem command with the parameter when you perform out-of-band file transfers to or from a Windows workstation that has Wfterm running on it. 5. To set the receiving Wfterm utility into receive mode, choose YMODEM-Receive from the File Transfers menu. Choosing this option opens the File to Transfer window, as shown in Figure B-10. Figure B-10. 6.
Using Technician Interface Software You should also see the file name appear in the receiving directory on the workstation. If the transfer was unsuccessful, you see the message: File Transfer Aborted. 8. If you are finished transferring files from the router to the Site Manager workstation, enter logout at the Technician Interface command line prompt in the Wfterm startup window. At the conclusion of file transfer operations, you can close the connection between the workstation and the router.
Using Out-of-Band Access to Transfer Files rb is a receive binary file. y is the YMODEM file transfer option. e disables the EOT verification. Note: To ensure that files are transferred properly, do not issue the xmodem command with the parameter when you perform out-of-band file transfers to or from a Windows workstation that has Wfterm running on it. 3. Set the sending Wfterm utility into send mode by choosing YMODEM-Send from the File Transfers menu.
Using Technician Interface Software Closing the Connection You can “gracefully” close the connection between your workstation and a target router after you: • Finish transferring (downloading or uploading) files between the remote router and your workstation. • Log off the Technician Interface of the target router. To close a connection, choose Hangup from the Wfterm File menu (see Figure B-7 on Figure B-7).
Using Out-of-Band Access to Transfer Files Quitting Wfterm You can quit the Wfterm utility after you: • Finish transferring files. • Log out of the Technician Interface of the target router. • Close the connection between your workstation and the target router. Quit Wfterm by choosing Exit from the File menu, as shown in Figure B-12. Figure B-12.
Appendix C Using Syslog Messaging to Monitor Router Events This appendix provides: • An overview of Syslog services on a Bay Networks router and counterpart Syslogd services on a UNIX workstation • Procedures for: -- Configuring Syslogd on a UNIX workstation -- Configuring Syslog services on a router -- Managing Syslog services on a router • An example Syslog configuration • Descriptions of Syslog MIB attributes (parameters) To use the information in this appendix, you should have experience with U
Using Technician Interface Software Syslogd is a UNIX daemon software component that receives and locally logs, displays, prints, and/or forwards messages that originate from sources internal and external to the workstation. For example, Syslogd on a UNIX workstation concurrently handles messages received from applications running on the workstation, as well as messages received from Bay Networks routers running in a network accessible to the workstation.
Using Syslog Messaging to Monitor Router Events Router Syslog software: Polls log @ slot P l o ol l s g • Polls slot logs • Retrieves event messages R m etri es ev sa es ge s • Filters retrieved messages • Maps retrieved messages into Syslog message format • Forwards Syslog messages to remote hosts Log @ slot Outgoing Syslog messages IP network Message forwarded Remote Host (Unix Workstation) UNIX workstation Message printed Syslogd daemon: • Receives syslog messages • Identifies message sources
Using Technician Interface Software Remote Hosts and Filters You use a management workstation to monitor event messages generated by specific software entities on each router in your network. To receive at a management workstation event messages from a router, you must • Enable Syslog on the router. • Define in the Syslog host table any remote hosts you want to receive messages. • Configure entity-specific message filters for each host.
Using Syslog Messaging to Monitor Router Events Entity filter for one host: Select by event number range New unfiltered messages from the events log Select by entity number (OR) Select by slot number range Select by event severity levels Filtered event messages for a designated remote host TS0002B Figure C-2. Router Event Message Filtering for One Host Polling the Events Log Syslog polls the events log buffer on the local slot to retrieve any new messages logged since the previous polling attempt.
Using Technician Interface Software Note: Although you assign each filter an index number manually through the Technician Interface, Site Manager automatically assigns an index number to each new filter you add to the configuration. When you want Syslog to select and forward from all entities event messages that satisfy severity and slot criteria that you specify, configure a filter for the wildcard entity number (255).
Using Syslog Messaging to Monitor Router Events You can specify a filter for an individual message by setting the upper and lower boundaries of the event number range equal to the same message number. If you configure an event number range of 0 to 255, Syslog ignores the range as a filtering parameter and checks instead to see if a message severity mask exists for the same entity filter. Filtering by Event Severity Level Each event message generated by the router software has a unique severity level.
Using Technician Interface Software You define a range of slot numbers for an entity filter by specifying: • An upper boundary number (MIB object wfSyslogFltrSlotUppBnd) • A lower boundary number (MIB object wfSyslogFltrSlotLowBnd) Syslog considers the upper and lower boundary numbers as part of the range. For example, you can configure an entity filter for FTP with an event number range of 5 to 27 and a slot number range of 2 to 5.
Using Syslog Messaging to Monitor Router Events [IP header] UDP data [UDP header] "{} {Syslog message}" "<[Facility] | [Level]>" "[Entity]: [Description] SLOT:[Slot Number] SEVERITY:[Severity Level] ENTITY_CODE/EVENT_CODE: [Entity_code/Event_code]" TS0003B Figure C-3. Syslog Message Encapsulation Syslog retrieves the variables shown in brackets ([ ]) from the router’s system log message or from the host table.
Using Technician Interface Software UDP Header Syslog adds to any event message that passes all filtering criteria the destination UDP port number on the remote host identified in the IP header. UDP Data The UDP data field in the Syslog packet contains a reformatted router event message, plus a priority code required by the remote host. The remote host uses this information to decide on how to handle messages received from a router.
Using Syslog Messaging to Monitor Router Events UNIX System Facility Name Facility Code (equivalent decimal value) Local 0 1 Local 1 2 Local 2 3 Local 3 4 Local 4 5 Local 5 6 Local 6 7 Local 7 8 The error level code identifies the severity level (level of urgency) of a received message for UNIX system handling decisions (such as logging, displaying, printing, or forwarding the message).
Using Technician Interface Software You determine how the severity levels of Bay Networks router event messages map to error levels on your UNIX workstation, based on requirements of the network management application software you want to use. See “Configuring Syslog on the Router” on page C-15 for instructions on how to map router event messages to UNIX system facility and error level codes.
Using Syslog Messaging to Monitor Router Events See “Configuring Syslog on the Router” on page C-15 for instructions on how to enable the Syslog time sequencing feature. Note: Enable time sequencing only when it is important for your management workstation to receive router event messages in timestamped order, rather than in order of retrieval from each slot. (When you enable the time-sequencing feature, Syslog requires more processing resources from the router.
Using Technician Interface Software To view on a UNIX workstation event messages from a Bay Networks router, open the file you designated on the workstation to receive Syslog messages from routers in your network. Example: Messages dispatched to console display: local7.debug /dev/console local7.info /dev/console local7.notice /dev/console local7.err /dev/console local7.crit /dev/console local7.alert /dev/console local7.emerg /dev/console or: local7.debug;local7.info;local ;local7.
Using Syslog Messaging to Monitor Router Events Configuring Syslog on the Router You can use Technician Interface commands to configure Syslog on a router. You configure Syslog as a sequence of tasks, where some tasks include one or more numbered steps. The following is an overview of the tasks required to configure Syslog on a router: 1. Using the console attached to the router, or using a Telnet connection to the router, open a Technician Interface session. 2.
Using Technician Interface Software Task 2: Defining a Slot Mask for Syslog on the Router Before creating the Syslog entity on the router, define a slot mask for Syslog. The slot mask identifies the slots on which the system will load and run the Syslog entity. At the Technician Interface prompt, enter: $: set wfProtocols.wfSYSLLoad.0 0x7FFE0000;commit This command enables Syslog to run on all slots, regardless of the router model. Next, create the Syslog entity on the router.
Using Syslog Messaging to Monitor Router Events 1. Configure the maximum number of active hosts served by Syslog on the router: $: set wfSyslog.wfSyslogMaxHosts.0 <1 - 10>;commit The default setting for wfSyslogMaxHosts is five hosts. You can add to the Syslog Host Table more entries than the configured maximum, but Syslog forwards messages only to the first “n” active hosts, where n = the current value of wfSyslogMaxHosts. 2.
Using Technician Interface Software 2. To define the UNIX system facility you want to receive Syslog messages from the router, enter the following: $: set wfSyslogHostTable.wfSyslogHostLogFacility. <128|136|144|152|160|168|176|184>;commit where: 3. 128 = local0 160 = local4 136 = local1 168 = local5 144 = local2 176 = local6 152 = local3 184 = local7 To optionally enable Syslog message time sequencing for the remote host, enter the following: $: set wfSyslogHostTable.
Using Syslog Messaging to Monitor Router Events Task 6: Adding an Entity Filter for a Remote Host Once you define a host in the Syslog host table, add (define) an entity-specific message filter for the host. If this is not the first filter for a given entity and remote host pair, first obtain a list of filter instances, as follows: list -i wfSyslogEntFltrEntry From the resulting list of instance IDs (of the form ..
Using Technician Interface Software 3. Set entity filter attributes, as follows: a. To define by event number(s) the event messages you want Syslog to select and forward to a specific remote host: $: set wfSyslogEntFltrEntry.wfSyslogEntFltrLogEvtLowBnd. .. <0 - 255> $: set wfSyslogEntFltrEntry.wfSyslogEntFltrLogEvtUppBnd. ..
Using Syslog Messaging to Monitor Router Events 4. Define how router event message severity levels and UNIX system error levels map to one another. In most cases, you accept the default mapping and go to Task 7. Otherwise, continue with the following instructions to customize the message mapping. Enter at the Technician Interface prompt the command line(s) appropriate for the message mapping(s) you want to change: • Change router FAULT message mapping, as follows: $: set wfSyslogEntFltrEntry.
Using Technician Interface Software Task 7: Adding More Hosts or Entity Filters If you have finished adding entity filters for this remote host, and you do not want to add another remote host at this time, go to Task 8. Otherwise, to add more hosts or entity filters to your Syslog configuration: • To add another entity filter for the same remote host, return to “Adding an Entity Filter for a Remote Host” on page C-19.
Using Syslog Messaging to Monitor Router Events Managing Syslog on a Router Once you finish configuring Syslog on a router, you may occasionally need to: • Disable or reenable the entire Syslog entity on the router. (See the next section, “Disabling or Reenabling Syslog on the Router.”) • Disable or reenable a Syslog host or filter on the router. (See “Disabling or Reenabling Syslog Hosts or Filters” on page C-24.) • Delete remote hosts or entity filters from the current Syslog configuration.
Using Technician Interface Software Disabling or Reenabling Syslog Hosts or Filters You can disable or reenable host or filter entries already defined in your Syslog configuration as follows: 1. Disable or reenable message forwarding to a Syslog host, as follows: • Disable a Syslog host anytime after adding it to the router configuration by entering the following command line: $: set wfSyslogHostEntry.wfSyslogHostDisable.
Using Syslog Messaging to Monitor Router Events • Reenable an entity filter by entering the following command line: $: set wfSyslogEntFltrEntry.wfSyslogEntFltrDisable. ..
Using Technician Interface Software Example Syslog Configuration The following is an example of a Syslog configuration procedure when: • Your management workstation has an IP address of 192.32.6.14. • You want to receive at your management workstation messages for all software entities running on a particular Bay Networks router. (This is a wildcard configuration scenario.) • You want to create and enable Syslog on a model BLN router.
Using Syslog Messaging to Monitor Router Events 4. Create a wildcard filter to forward events of type fault, warning, and debug on slots 2, 3, 4, 5: a. Create the filter as follows: $: set wfSyslogEntFltrEntry.wfSyslogEntFltrDelete. .255.1 1;commit is the address of the remote host associated with this filter. 255 is the wildcard entity number. 1 represents the index number of the filter. commit commits router system resources to the filter you are creating. b.
Using Technician Interface Software Note: If you add another filter for a specific entity, that filter takes precedence over the wildcard filter for the host you specified. When the wildcard filter transitions to the INACTIVE state, the new filter transitions to the ACTIVE state, and the remote host receives messages only through the entity-specific filter.
Using Syslog Messaging to Monitor Router Events wfSyslogEntityFilterTable (table of entity filters for one host): wfSyslogEntFltrEntry (individual entity filter entry in the entity filter table): wfSyslogEntFltrDelete wfSyslogEntFltrDisable wfSyslogEntFltrHostIndex wfSyslogEntFltrNum wfSyslogEntFltrIndex wfSyslogEntFltrOperState wfSyslogEntFltrLogEvtLowBnd wfSyslogEntFltrLogEvtUppBnd wfSyslogEntFltrSevMask wfSyslogEntFltrSlotLowBnd wfSyslogEntFltrSlotUppBnd wfSyslogEntFltrFaultMap wfSyslogEntFltrWarningMap
Using Technician Interface Software Global/Group Parameters This section describes the Syslog group/global parameters. Parameter: Attribute Name: Attribute Number: Syslog Delete wfSyslogDelete 1 Default: 1 (Create) Options: 1 (Create) | 2 (Delete) Function: Instructions: Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: Creates or deletes the Syslog service on the router. Set to 1 (Create) to create a MIB record with system defaults for the Syslog service on the router.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Syslog Operational State wfSyslogOperState 3 Default: 1 (active) Options: 1 (active) | (2) inactive Function: Instructions: Command: MIB Object ID: 303561-A Rev 00 Indicates the operational state of the Syslog service on the router. If the state is active, syslog has been enabled, and is filtering and forwarding messages to designated hosts.
Using Technician Interface Software Parameter: Attribute Name: Maximum Hosts wfSyslogMaxHosts Attribute Number: 4 Default: 5 Range: Function: Specifies the maximum number of remote hosts considered “active” and able to receive messages from the Syslog service on the router. The number includes Syslog hosts configured to receive time-sequenced messages, as well as hosts configured to receive messages nonsequentially.
Using Syslog Messaging to Monitor Router Events Host Parameters This section describes parameters you can configure for each host you add to the Syslog host table (list of remote UNIX hosts). Parameter: Attribute Name: Attribute Number: Host Delete wfSyslogHostDelete 1 Default: 1 (Create) Options: 1 (Create) | 2 (Delete) Function: Instructions: Command: 303561-A Rev 00 Adds or deletes a remote host entry in the Syslog host table.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Messaging Enable wfSyslogHostDisable 2 Default: 1 (Enable) Options: 1 (Enable) | 2 (Disable) Function: Enables or disables message forwarding from Syslog to the remote host associated with this host entry. Instructions: Set to 1 to enable message forwarding from Syslog to the remote host associated with this host entry.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Default: Range: Host UDP Port wfSyslogHostUDPPort 4 514 514 to 530 Function: Identifies the UDP port of the remote host associated with this host entry. Instructions: Set the UDP port at which the remote host associated with this host entry will receive Syslog messages from the router. Command: MIB Object ID: Parameter: Attribute Name: Attribute Number: set wfSyslogHostEntry.wfSyslogHostUDPPort.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Host Time Seq Enable wfSyslogLogTimeSeqEnable 6 Default: 2 (Disable) Options: 1 (Enable) | 2 (Disable) Function: Instructions: Enables or disables time sequencing and forwarding of Syslog (event) messages to the remote host associated with this host entry. Enable this feature only if the remote host must receive Syslog messages in the order in which they were logged on the router.
Using Syslog Messaging to Monitor Router Events Parameter: Host Operational State Attribute Name: wfSyslogHostOperState Attribute Number: 7 Default: 2 (inactive host) Options: 1 (active) | 2 (inactive) Function: Instructions: Command: MIB Object ID: 303561-A Rev 00 Indicates the operational state of this Syslog host entry on the router. If the state is active, Syslog is filtering and forwarding messages to the host at the IP address for this entry ().
Using Technician Interface Software Entity Filter Parameters This section describes the parameters you can configure for each filter (entry) you add to the Syslog entity filter table.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Filter Operational State wfSyslogEntFltrOperState 6 Default: 2 (inactive filter) Options: 1 (active filter) | 2 (inactive filter) Function: Instructions: Command: MIB Object ID: 303561-A Rev 00 Indicates the actual status of the filter. When the status is ACTIVE, Syslog filters against the criteria specified for this filter.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Default: Range: Function: Log Evt Lower Bound wfSyslogEntFltrLogEvtLowBnd 7 0 0 to 255 Along with the Log Evt Upper Bound, this parameter specifies an event number (code) or range of event numbers. The numbers correspond to event messages you want to forward to the remote host associated with this filter.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Default: Range: Function: Instructions: Command: MIB Object ID: 303561-A Rev 00 Log Evt Upper Bound wfSyslogEntFltrLogEvtUppBnd 8 255 0 to 255 Along with the Log Evt Lower Bound, this parameter specifies an event number (code) or range of event numbers. The numbers correspond to event messages you want to forward to the remote host associated with this filter.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Severity Mask wfSyslogEntFltrSevMask 9 Default: None Options: w (warning) i (information) t (trace) f (fault) d (debug) Use individually (such as f or d) or combined (such as fwitd). Function: Instructions: Identifies the severity levels of events you want to forward.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Default: Range: Function: Instructions: Slot Lower Bound wfSyslogEntFltrSlotLowBnd 10 0 0 to 14 Along with the Slot Upper Bound, this parameter specifies a slot number or range of slot numbers. Syslog forwards to the remote host associated with this filter messages logged only on the slots you specified. (Consider the location of each router in an ASN chassis as a numbered slot.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: Default: Range: Function: Instructions: Slot Upper Bound wfSyslogEntFltrSlotUppBnd 11 0 0 to 14 Along with the Slot Lower Bound, this parameter specifies a slot number or range of slot numbers. Syslog forwards to the remote host associated with this filter messages logged only on the slots you specified. (Consider the location of each router in an ASN chassis as a numbered slot.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Fault Map wfSyslogEntFltrFaultMap 12 Default: 3 (CRIT) Options: 1 (EMERG) | 2 (ALERT) | 3 (CRIT) | 4 (ERR) | 5 (WARNING) | 6 (NOTICE) | 7 (INFO) | 8 (DEBUG) Function: Instructions: Command: MIB Object ID: Maps router event messages with a severity level of fault to a UNIX system error level that Syslogd recognizes. Table C-1 describes each of these error levels.
Using Technician Interface Software Parameter: Attribute Name: Attribute Number: wfSyslogEntFltrWarningMap 13 Default: 5 (WARNING) Options: 1 (EMERG) | 2 (ALERT) | 3 (CRIT) | 4 (ERR) | 5 (WARNING) | 6 (NOTICE) | 7 (INFO) | 8 (DEBUG) Function: Maps router event messages with a severity level of warning to a UNIX system error level that Syslogd recognizes. Table C-1 describes each of these error levels. Instructions: We recommend accepting the default UNIX system error level for this severity level.
Using Syslog Messaging to Monitor Router Events Parameter: Attribute Name: Attribute Number: Trace Map wfSyslogEntFltrTraceMap 15 Default: 8 (DEBUG) Options: 1 (EMERG) | 2 (ALERT) | 3 (CRIT) | 4 (ERR) | 5 (WARNING) | 6 (NOTICE) | 7 (INFO) | 8 (DEBUG) Function: Maps router event messages with a severity level of trace to a UNIX system error level that Syslogd recognizes. Table C-1 describes each of these error levels.
Using Technician Interface Software For More Information See the instructions provided in the UNIX manual (man) pages on your workstation for more information about syslog, syslogd, and syslog.conf.
Index Symbols * wildcard, 5-2 loading from a file, 9-9 managing, 9-1 to 9-19 saving to a file, 9-8 ? wildcard, 5-2 an.exe image, 4-4, 4-9, 5-10 A AN/ARN/ASN, configuring boot and config file source, 8-2 to 8-8 ! command, 3-3 access levels manager, 8-92 to 8-95 user, 8-92 to 8-95 password protection, 1-3 via SecurID, 1-3 anboot.exe PROM image file, 4-9, 5-10 ACE backplane, 8-46 processor module, 4-4 APPN ping command, 3-26 to 3-28 ace.out image, 4-4 asn.exe image, 4-4, 4-9, 5-10 ace.
autoscripts at manager login, 2-20 at user login, 2-20 automgr.bat, 2-19 to 2-20 autouser.bat, 2-19 to 2-20 customizing, 2-21 samples, 2-20 B backplane command, 8-46 setting the, 8-46 baud rate, setting, 2-9 bconfig command, 8-3 to 8-4 BGP routes command, 8-64 bn.
NVFS cd, 4-11 compact, 4-19 copy, 4-11 delete, 4-18 dinfo, 4-6 dir, 4-7 format, 4-20 partition, 4-21 tftp, 4-14 type, 4-17 operating backplane, 8-46 bconfig, 8-3 boot, 8-9 clearlog, 6-14 date, 8-46 diags, 8-28 exec, 3-7 help, 3-2 history, 3-4 ifconfig, 8-5 loadmap, 8-44 log, 6-6, 6-13 logout, 1-12 more, 3-2 password, 8-49 ping AppleTalk, 3-23 to 3-25 ping APPN, 3-26 to 3-28 ping IP, 3-8 to 3-10 ping IPv6, 3-11 to 3-13 ping IPX, 3-14 to 3-16 ping OSI, 3-17 to 3-19 ping VINES, 3-20 to 3-22 prom, 8-33, 8-38 re
Control Point name, 3-26 conventions, text, xx copy command, 4-11, 5-15 D data bits, setting, 2-9 date command, 8-46 debug aliases, 9-10 to 9-19 DOS file attributes, 5-20 file system labeling a diskette, 5-12 managing using the Technician Interface, 5-2 to 5-23 naming files and directories, 5-4 DVMRP caches command, 8-64 E debug.
asn.exe, 4-9, 5-10 asndiag.exe, 4-9, 5-10 bn.exe, 4-9, 5-10 changing attributes of, 5-20 compacting space, 4-19 config, 4-10, 5-11 copying, 4-11, 5-15 from DOS to NVFS, 5-16 from NVFS to DOS, 4-12 debug.al, 4-10, 5-11 default names of, 4-9 deleting, 4-18, 5-23 displaying the contents of, 4-17, 5-22 freboot.exe, 4-10, 5-11 install.bat, 4-10, 5-11 names, 4-5 renaming, 5-14 s5000.exe, 4-9, 5-10 s5000diag.exe, 4-9, 5-10 syslog.conf, C-48 ti.
M IP address settings, 8-6, 8-7 cache command, 8-64 command, 8-63 to 8-84 connector setting, 8-6, 8-7 default setting, 8-6, 8-7 ping command, 3-8 to 3-10 routes command, 8-64 IPv6 ping command, 3-11 to 3-13 routes command, 8-86 stats command, 8-90 IPX ping command, 3-14 to 3-16 L label command, 5-12 lines per screen, setting, 2-11 list command, 2-3, 7-2 loadmap command, 8-44 log automatically saving the, 6-10 command, 6-6, 6-13 input filters, 6-3 displaying list of, 6-5 ouput filters, 6-6 login levels, 1-
N named boot, 8-11 NLSP ping response, 3-14 nonvolatile file system (NVFS), 4-1 NSAP address, 3-17 O online Help, 3-2 operational state of a Syslog filter, C-39 of a Syslog host, C-37 of the Syslog entity, C-31 OSI ping command, 3-17 to 3-19 OSPF LSDB command, 8-64 out-of-band file transfers from a UNIX workstation, B-10 to B-16 from a Windows workstation, B-17 to B-31 hardware configuration, B-9 overview of, B-1 to B-2 overwriting files, 5-15, 5-18 P packet transfer, halting between slots, 8-33 parameter
IPX, NLSP response, 3-14 OSI, 3-17 to 3-19 VINES, 3-20 to 3-22 S s5000.exe image, 4-9, 5-10 pinging a remote device, 3-7 to 3-27 s5000boot.exe, 4-9, 5-10 platform key, 8-37 s5000boot.exe PROM image file, 4-9, 5-10 port name, displaying, 2-7 number, displaying, 2-7 parity setting, 2-10 type, displaying, 2-8 s5000diag.
SYS I/O board, 2-1 to 2-2 Syslog configuring the router for, C-15 deleting from router, C-25 deleting remote hosts or filters, C-25 disabling or reenabling, C-23 disabling or reenabling remote hosts or filters, C-24 entity filter parameters, C-38 example configuration, C-26 global parameters, C-30 IP header, C-9 mapping router events to Syslog format, C-8 message filtering diagram, C-5 parameter descriptions, C-28 parameters Debug Map, C-47 Delete, C-30 Enable, C-30 Entity Filter Delete, C-38 Entity Filter
V verbose command (for debugging aliases), 9-7 verbose option (ping command), 3-8, 3-10, 3-11, 3-13 VINES ping command, 3-20 to 3-22 VME routers, 4-2, 8-46 volume changing the active, 4-11 displaying directory on, 4-7 displaying the active, 4-11 mounting, 5-5 unmounting, 5-7 W Welcome screen, customizing the, 1-10 wfsnmpkey command, 8-54 wfsnmpmode command, 8-54 wfsnmpseed command, 8-55 Wfterm accessing from Site Manager, B-18 dialing a remote router, B-22 file transfer functions, B-24 initializing local m
