Home

Avaya Connecting BayStack AN and ANH Platforms to a Network User's Manual

image

Contents

1. Ethernet Local management 10Base T station console transceiver 10Base T Ol NIC uuw connector 10Base T Ethernet uuw transceiver station n e Figure C 1 Typical Single ANH Configuration Note In Figure C 1 the local management station directly connected through the console port can be either an ASCII or PC based terminal In larger network configurations you can also connect the ANH to an SNMP management station through a 10Base T repeater port see Figure C 4 C 5 Connecting BayStack AN and ANH Systems to a Network Configuring Multiple Hubs You can interconnect as many as four ANH units using the UTP repeater ports Note Backbone connections are usually made through the AUI port see the section Configuring an AUI Port When you configure a network with multiple ANH or other repeater hub systems you must comply with the following rules e Connect no more than four hubs e Make sure each UTP connection is no longer than 100 m e Ifa transceiver is connected to the AUI port disable the SQE signal quality error test function of the transceiver Note Minimize the number of repeaters between stations in the network by connecting hubs in a star configuration Avoid chaining hubs in a single line When connecting three or four hubs make sure the installation complies with the specifications in
2. 6 17 Connecting BayStack AN and ANH Systems to a Network Disabling DCM To temporarily disable an installed DCM board 1 From the Configuration Manager window select Platform gt DCM Global refer to Figure 6 8 The Edit DCM Parameters window appears refer to Figure 6 7 2 Set the Enable Disable parameter to DISABLE 3 Click on OK to exit the Edit DCM Parameters window If disabling the board does not work you can delete the software subsystem to totally shut down the DCM Booting DCM To reboot an installed DCM board disable and then re enable the DCM as described in the previous sections 6 18 Configuring AN and ANH Features Changing DCM Configuration Parameters To edit the DCMMW configuration parameters for an installed DCM board follow these steps 1 From the Configuration Manager window select Platform gt DCM Global Figure 6 8 Configuration M SNMP Ag File N Mo MIB Vers ET Used Unused Description Connectors 8pt EHub 25 N11 DCM COM2 COM1 XCVR1 Figure 6 8 Selecting the DCM Parameters Window The Edit DCM Parameters window appears Figure 6 9 6 19 Connecting BayStack AN and ANH Systems to a Network Cancel OK Values Help Enable Disable ENABLE Image Name Boot Option Image Save Mode Configuration Mode LOCAL Write Configuration Info NOWRITE RMON Max Host 500 RMON Default Host ENABLE RMON Default Matrix ENABLE Figure 6
3. Displaying Parameter Settings Display the router parameter settings to determine e Whether the AN ANH is set to boot using a local boot image or a remote boot image e Whether the AN ANH is set to configure using a local configuration file or a remote configuration file e The configuration of the synchronous and Ethernet connectors Enter the following Technician Interface command to display the AN ANH parameter settings getcfg The following sample responses show the default settings for an AN or ANH with one Ethernet and two synchronous interfaces Boot Options boot image network boot config network Netboot Parameters XCVR1 None COM1 EZ Install COM2 EZ Install The possible boot image and boot config settings are network and local If the setting is network the AN ANH requests the boot image or configuration file from a BOOTP server when booting If the setting is local the AN ANH uses the boot image or configuration file stored in the Flash card file system The XCVR parameter shows the current setting of the AN ANH Ethernet connectors The COM parameters show the current settings of the AN ANH synchronous connectors The possible settings for synchronous connectors are as follows e EZ Install the default setting e The IP address next hop IP address subnet mask and WAN protocol Bay Networks HDLC or Frame Relay A 10 Troubleshooting Network Boot Problems The possible settings for Eth
4. Implementation Notes Connecting the AUI Port to a Coaxial Backbone You can use the AUI port to connect an AN or ANH to a coaxial backbone through an IEEE 802 3 10Base 5 or 10Base 2 coaxial MAU Figure C 4 shows two ANH systems connected to a coaxial backbone through IEEE 802 3 MAUs An AUI cable connects the AUI port on each ANH to each MAU The SQE test is disabled on each MAU connected to the AUI port on an ANH IEEE 802 3 MA IEEE 802 3 MA ates i Coaxial backbone eas n AUI cable 50 ohm termination termination Bay Networks keg pee0neeao DA AA dA Transceiver O AUI uu Cl port Ethernet Ethernet station station Je ee L P SISISISISISISEE oooooooo Transceiver wu Ethernet Transceiver Ethernet station station SNMP management www station Figure C 4 Connecting ANH Systems through a Coaxial Backbone C 9 Symbols etc inetd conf file 3 8 3 9 etc services file 3 2 tftpboot directory 3 9 ast wf config directory 3 3 12 repeater port AN See ANH 8 repeater port AN See ANH A address See IP address addresses window BOOTP 4 17 AIX BOOTPD 3 2 TFTP
5. Verifying the Routes After adding a static route for each path to the booting routers enter the following command to display the routing table and verify the route you added netstat r Loading the Changes into Memory Once you modify the inetd conf file you must force the operating system to reread it by rebooting the workstation or by issuing a hang up signal In most cases reboot the workstation Issue a hang up signal if the workstation is performing a task that you do not want to interrupt Rebooting Reboot your workstation as follows 1 Log in as root 2 Execute the following command etc shutdown now r The r flag reboots the workstation Connecting BayStack AN and ANH Systems to a Network Issuing a Hang Up Signal Issue a hang up signal as follows 1 2 Log in as root Execute the following command to hang up on the inetd process ps aux grep inetd The system displays a line similar to this one root 148 0 0 0 0 48 0 IW Sept 14 0 07 inetd Execute the following command using the first number in the line after the word root in this case 148 kill 1 148 The inetd process rereads the inetd conf file What to Do Next Before you can use the network to boot a remote AN or ANH you must also complete the steps in Chapter 4 3 12 Chapter 4 Configuring Network Booting This chapter describes how to use Site Manager to configure network booting for AN ANH routers
6. Ensuring Ethernet Network Compliance earlier in this chapter Figure C 2 shows an ANH linked with two Model 810M hubs UTP patch cables connect each MDI port to an MDI X port For information about activating the MDI X MDI switch see Installing and Starting BayStack ANH Systems C 6 Implementation Notes Port 1 switch setto MDI Access Node Hub 5 6 1 2 j a 7 8 kli Partition humpi Pall I L DA TE A EE 2 53 4 Se E i i ACICE G LI ECHE Link MDI X UTP cable UTP cable Port 1 switch set to MDI 7 e UTP cables to Ethernet stations Figure C 2 Connecting the ANH with Other Hubs Configuring an AUI Port You can connect any IEFE 802 3 media attachment unit MAU to the AUI port on an AN or ANH For example you can use an IEEE 802 3 10Base FL fiber optic MAU FOMAU to connect to a fiber optic port on a router or hub Or you can connect the AUI port to a coaxial backbone through an IEEE 802 3 10Base 5 or 10Base 2 MAU Caution JEEE 802 3 rules require that the SQE test function be disabled on an IEEE 802 3 MAU connected to an AUI port If it is not disabled the AUI port could interrupt network transmissions until it autopartitions a
7. Set up BOOTPD to respond to booting routers as follows 1 As root view the contents of the etc directory to determine whether it already contains a bootptab file If it does contain a bootptab file disregard Steps 2 and 3 and continue with Step 4 to edit this file 3 3 Connecting BayStack AN and ANH Systems to a Network Issue the following command to copy the bootptab file to the etc directory cp usr wf config bootptab etc Use an editor to open the bootptab file in the etc directory Type the information that pertains to the ANs and ANHs in your network into the bootptab file The section that follows explains how to format your entries Use Tables 3 1 and 3 2 to determine which tags and values you need Figure 3 1 shows the sample bootptab file included with the Site Manager software The comments in this file explain the sample definitions After editing the bootptab file be sure to save the changes Note Be sure the bootptab file resides in the etc directory BOOTPD fails if it cannot find the bootptab file in etc Editing the bootptab File Enter a lt hostname gt definition in the bootptab file for each AN ANH in your network The format of each definition in the bootptab file is as follows lt hostname gt lt tg gt lt value gt lt tg gt lt value gt lt tg gt lt value gt lt hostname gt is a name you assign to a BOOTP client each router is a client lt tg gt is a BOOTP p
8. To restrict TFTPD file access to a specific directory insert the appropriate line for your operating system in the etc inetd conf file The examples in Table 3 4 restrict access to the fftpboot directory You can substitute any directory you want Table 3 4 Restricting TFTPD Access to One Directory os Sample Line to Insert in etc inetd conf Directory SunOS tftp dgram udp wait root usr etc in tftpd in tftpd s tftpboot Solaris tftp dgram udp wait root usr sbin in tftpd in tftpd s tftpboot HP UX tftp dgram udp wait root etc tftp tftp s tftpboot AIX Use the System Management Interface Tool SMIT to configure TFTP For instructions refer to the IBM guides on TCP IP daemons and the TFTP protocol You must create a symbolic link for every pathname you specify For example to set up the symbolic links for the tftpboot path use the following procedure 1 Log in to your UNIX workstation as root 2 Enter the following commands cd tftpboot In s usr In s tftpboot 3 9 Connecting BayStack AN and ANH Systems to a Network gt Caution Do not insert a slash in the cd tftpboot command a symbolic link cannot contain references to directories above the directory specified in the tftpd command line Use the S flag to provide additional security to your network This flag restricts TFTPD access to a specified directory Adding a TFTP User for an HP 9000 Follow the instructions
9. either explicitly or implicitly except by acceptance of an order for either Software or for a Bay Networks product Equipment that is packaged with Software Each such license is subject to the following restrictions 1 Upon delivery of the Software Bay Networks grants to licensee a personal nontransferable nonexclusive license to use the Software with the Equipment with which or for which it was originally acquired including use at any of licensee s facilities to which the Equipment may be transferred for the useful life of the Equipment unless earlier terminated by default or cancellation Use of the Software shall be limited to such Equipment and to such facility Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment however unless otherwise specified on the Documentation each licensed copy of such Software may only be installed on one hardware item at any time Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative Licensee may make a single copy of the Software but not firmware for safekeeping archives or backup purposes Licensee may modify Software but not firmware or combine it with other software subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license Licensee shall not make the
10. instead of the connector for example 192 32 23 3 If you configure the IP address Site Manager replaces the with the appropriate connector Click on Done to exit the window BOOTP Relay Agent Interface Parameters Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Input IP Address None Any valid IP address Specifies the IP interface that receives BOOTP request packets from an external network This interface must have BOOTP configured on it Enter the IP address of the interface through which the router will receive BOOTP requests 1 3 6 1 4 1 18 3 5 3 8 3 2 1 3 Output IP Address None Any valid IP address Specifies the IP interface that forwards BOOTP request packets to an external network Enter the IP address of the interface through which the router will forward BOOTP requests 1 3 6 1 4 1 18 3 5 3 8 3 2 1 4 4 18 Configuring Network Booting Creating the BOOTP Client Interface Table The upstream router is a booting router s next hop router By default the booting router s synchronous interfaces automatically try to get IP addresses from the upstream router This is the EZ Install process If the AN ANH using EZ Install gets its address from the upstream router and the upstream router s interface to the AN ANH is a Frame Relay group access PVC you must use Site Manager to connect to the
11. responses it receives vm rfcl1048 Se Oh SR OE se This line marks the beginning of the active definition for the AN we are naming AN Boston AN Boston ip indicates the IP address of the AN 1p 19232 5 22 T130 indicates the size of the AN s configuration file in 512 byte blocks Always use 0x0004 T130 0x0004 T129 indicates the pathname of the configuration file for the AN T129 usrl cfg AN_Bost cfg tc indicates that the general definition contains more information that applies to BOOTP transmissions to AN Boston tc general This is the active definition for the AN we are naming AN Chicago AN Chicago ip 10 0 0 4 T130 0x0004 T129 rte3 cfg AN_Chic cfg tc general Figure 3 1 Sample bootptab File 3 7 Connecting BayStack AN and ANH Systems to a Network Verifying Consistent BOOTP Service You may want to configure a second workstation as a BOOTP server for backup purposes If you do so make sure the two bootptab files match exactly Also make sure that the image and string files are from the same software version Setting Up a TFTP Server An AN ANH needs a network connection to a TFTP server to complete EZ Install Netboot or Directed Netboot You configure a UNIX workstation as a TFTP server by e Setting up TFTPD the TFTP daemon e Adding a TFTP user for an HP 9000 only e Setting up static routes to routers option
12. you can create more than one History configuration allowing you to specify different intervals for sampling statistics Interoperability Issues and Memory Use for RMON Groups You should understand the following issues about each RMON group s memory requirements and ability to operate with third party RMON network management applications 6 24 Configuring AN and ANH Features Statistics Group When you enable the DCM the RMON agent automatically creates a Statistics configuration that records data for each network interface Through your RMON network management application you can create as many Statistics configurations as memory permits up to the RMON limit of 65 535 configurations If you create multiple configurations it is possible to collect the same set of statistics for the same interface in multiple data tables The absolute values of those statistics may vary from table to table because the baseline of each statistics counter occurs when you create a configuration You may prefer however to use only one Statistics configuration to conserve memory for other RMON groups You need 200 bytes of memory for each Statistics configuration History Group When you enable the DCM the RMON agent automatically creates a History configuration that collects History data at two intervals The first configuration provides short term history by sampling statistics every 30 seconds and holding up to 50 samples in RMON t
13. 10 OSPF worksheet for B 5 outgoing interface specifying 4 15 to 4 18 P Packet Capture group 6 10 6 28 Packet Capture tool A 8 packets analyzing A 8 displaying forwarded and dropped A 14 parameters displaying A 10 pathnames 1 13 restrictions 4 2 pointer tag in bootptab 3 5 port console 1 1 Ethernet repeater 1 3 6 1 modem 1 1 pound sign in bootptab file 3 4 power loss while writing to a file 2 4 A 16 PPP wide area protocol worksheet for B 10 product series 1 1 PVC See Frame Relay Q Quick Get tool A 8 Quick Start commands B 13 defined B 1 install bat script B 12 using B 12 Quick Start procedure worksheet B 3 to B 4 R reboot DCM 6 12 receive socket BOOTP 3 2 relay agent forwarding table See BOOTP remote dialup A 7 Index 6 repeater ports Ethernet 1 3 ANH support 1 3 enabling 6 4 resetting 6 3 testing 6 3 Request for Comments 1757 6 7 6 9 Reset parameter 6 3 resetting and testing ANH 6 1 to 6 3 resetting while writing to a file 2 4 A 16 RFC 1048 3 6 RIP routing protocol worksheet for B 5 RMON agent 6 8 control parameters 6 9 control tables 6 9 data tables 6 9 groups 6 8 to 6 10 interoperability issues 6 23 to 6 29 memory use 6 24 to 6 29 RMON Default Host parameter 6 16 RMON Default Matrix parameter 6 17 RMON Max Host parameter 6 16 router software image definition of 1 6 routine startup options 2 3 RS 6000 See
14. 15 Connecting BayStack AN and ANH Systems to a Network BOOTP Relay Agent Interface Table E54 192 123 123 1 pe Delete Apply Values Forward I F Client I F Pref Serv Help Enable Disable ENABLE Hops Timeout Secs Pass Through Mode Figure 4 6 BOOTP Relay Agent Interface Table Window Click on Help or refer to Configuring SNMP BOOTP DHCP and RARP Services for a description of the parameters in the BOOTP Relay Agent Interface Table window Note Be sure the Timeout Secs parameter is set to the default 0 2 Click on Forward I F interface The BOOTP Relay Agent Forwarding Table window appears Figure 4 7 4 16 Configuring Network Booting Done Add Delete Apply Values Help l nl Enable Disable Pass Through Mode Figure 4 7 BOOTP Relay Agent Forwarding Table Window 3 Click on Add The BOOTP Addresses window appears Figure 4 8 Cancel OK Help Output IP Address Figure 4 8 BOOTP Addresses Window 4 Specify the input IP address and output IP address For help refer to the parameter descriptions that follow this procedure 5 Click on OK 4 17 Connecting BayStack AN and ANH Systems to a Network The BOOTP Relay Agent Forwarding Table window lists the connector and input IP address on the left and the connector and output IP address on the right If you enter an IP address of an interface that is not configured appears
15. 6 15 Connecting BayStack AN and ANH Systems to a Network Parameter Default Range Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID RMON Max Host 500 100 to 8128 Relates to the RMON Host group Indicates the maximum number of host addresses to be collected in each entry of the RMON host control table The maximum limit depends on the amount of Flash memory available in the DCM When the host control table reaches the maximum value the DCM deletes entries based on an LRU least recent used algorithm Recommended values based on DCM memory configurations are 2 to4 MB 2048 8 MB 4096 16 MB 8128 To verify the number of hosts configured check the MIB object wfDCMmwRMONHost using the Site Manager Statistics tool 1 3 6 1 4 1 18 3 3 2 16 1 8 RMON Default Host Enable Enable Disable Specifies whether or not to create the RMON Host Control Table at every boot Some RMON network management applications expect the DCM to set up a host configuration Others enable and disable their own configurations during normal operations Note that the DCM allows only one instance of the host control table Select Enable to create the RMON Host Control Table at the next and every subsequent reboot Select Disable to disable default creation of the RMON host control table at boot time 1 3 6 1 4 1 18 3 3 2 16 1 9 6 16 Configuring AN and ANH Feat
16. 9 Edit DCM Parameters Window 2 Set the Enable Disable parameter to DISABLE 3 Click on OK 4 Select Platform gt DCM gt Global again see Fis to return to the Edit DCM Parameters window 5 Set the Configuration Mode parameter to SHARED MEMORY 6 To use this configuration in subsequent boots set the Write Configuration Info parameter to WRITE 7 Set the Enable Disable parameter to ENABLE 8 Click on OK 6 20 Configuring AN and ANH Features Deleting the DCM Software Subsystem The ANH requires the DCMMW software to communicate with the DCM board Deleting DCMMW deactivates the DCM board Note Always try disabling the DCM board by setting the Enable Disable parameter to Disable before you delete the DCMMW software To completely deactivate the DCM board 1 From the Configuration Manager window select Platform gt DCM gt Delete DCM Figure 6 10 E Configuration M O ETR Used Unused Connectors Figure 6 10 Deleting DCM from the Configuration Manager Window Configuration Manager displays a confirmation prompt 2 Click on OK Configuration Manager deletes the DCMMW base record bringing the DCM board completely down After deleting the DCM configuration you reactivate the DCM board by selecting Platform gt DCM gt Create DCM to recreate the DCMMW record refer to Figure 6 6 6 21 Connecting BayStack AN and ANH Systems to a Network Managing the DCM Board Using the Technician In
17. AIX S saturation of router memory preventing 2 4 See also Quick Start Selftest ANH parameter 6 3 send socket BOOTP 3 2 slot number B 3 Slot Number parameter 4 11 sm subnet mask tab in bootptab 3 5 SMDS wide area protocol worksheet for B 12 sniffer See LAN protocol analyzer SNMP implementation notes 6 23 sockets BOOTP 3 2 software configuration Diagnostics Monitor 1 5 Site Manager 1 5 Technician Interface 1 5 Solaris copying BOOTPD 3 2 TFTPD access 3 9 SQE test disabling for AUI port C 8 startup options displaying A 10 initial 2 1 EZ Install 2 6 Local Boot 2 9 Netboot 2 7 2 8 Local Boot 1 15 Netboot 1 9 routine Directed Netboot 2 4 Local Boot 2 5 Netboot 2 3 selecting 2 1 Local Boot 2 3 2 5 2 6 Netboot 2 3 2 6 static routes 3 10 Statistics Manager tool A 8 string files 1 6 generating 4 3 subnet mask tag 3 5 Sun workstations 3 2 SunOS copying BOOTPD 3 2 TFTPD access 3 9 symbols in bootptab file 3 4 Index 7 synchronous interfaces 1 1 1 3 configuring 5 4 displaying MIB entry A 7 ifconfig settings 5 4 support EIA232 1 3 ETA449 422 1 3 V 35 1 3 X 21 1 3 syntax of bootptab file 3 4 System Administration Manager HP 9000 3 10 T T130 size tag in bootptab 3 5 table continuation tag 3 5 tags in bootptab 3 6 format 3 4 tc table continuation tag in bootptab 3 5 TELNET B 4 testing BOOTP C 1 testing IP interface du
18. Function Instructions MIB Object ID Connector Subnet Mask None Any valid IP subnet mask Specifies the network and subnetwork portion of the 32 bit IP address of this interface The Configuration Manager automatically calculates an appropriate subnet mask depending on the class of the network to which the interface connects However you can change the subnet mask with this parameter Either accept the assigned subnet mask or enter another subnet mask in dotted decimal notation 1 3 6 1 4 1 18 3 3 2 10 3 1 5 Connector Next Hop None Any valid IP address Specifies the IP address of the next hop router connected to this interface When the router starts up the next hop router passes the BOOTP requests and responses that initiate the transfer of the image and or configuration file between the router and the BOOTP server If the router and BOOTP server are on the same IP subnet you do not have to set this parameter Enter the IP address of the next hop router connected to the interface you are adding in dotted decimal notation 1 3 6 1 4 1 18 3 3 2 10 3 1 6 Connector Protocol Mask Point to Point Point to Point Point to Point Internal Clock Fr Relay Annexd Fr Relay Annexa Fr Relay LMI During the boot process the router will configure the synchronous interface to the specified protocol Specify the desired protocol option 1 3 6 1 4 1 18 3 3 2 10 3 1 7 4 12 Parameter Default Options Funct
19. Next Hop Routers cccceccsseceeeseneeeeeeesseeeeeeseaes 3 10 Eding ihe meon FIE cirean 3 11 vanning The HOUSE acid akira anni halal E 3 11 Loading the Changes into Memory 2 cccececeeeeneeeeeeeeeeeeaeeeeeeeeseaeeeseneeeeaas 3 11 What to DO NEXU sccicsscccssecssiiacnnessaes PEE E E T re TOE ARER ERON ER 3 12 vi Chapter 4 Configuring Network Booting Preparing Conhigiiration and Image FIGS si sicccseceriascccestnraneiereesaccrenetsasaeei orn 4 2 CAS AUNT CSAP AATF UN isone ada aaa a iaaa Aaaa aAa 4 2 Fren inoan WIIG canimin 4 3 Enabling Nethoot or Directed NolDOot sisisiisiaranininisini 4 4 Netboot and Directed Netboot Parameters ccccccccsseeeeseeeeeeeeeseeeeeeseaeeeeeneeeeas 4 5 Configuring a Netboot or Directed Netboot Interface cccecceeeeteeeeneeeeeteeeeeneeeesaees 4 8 Nelboot interace Parameters cicvsscantiystocnsntvesscaiadyssennnystsonheretyercann ane 4 11 Seimo Up Roding Patis tor Netbogt ciissranctiagatetinianiesadlamicblineiateal Mielaedtemiolaees 4 14 Enabling Roer I MGMAOS nessscnisoi ose 4 14 Creating BOOTP Relay Agent Forwarding Tables 0 tcccceseeeesseeeseeeeeeesteeeeeees 4 15 BOOTP Relay Agent Interface Parameters 05 ee Ce ere Ann 4 18 Creating the BOOTP Client Interface Table sisssinesniniinnininninniiieaada 4 19 BOOTP Client Interface Parameters ei ccctiusecesecesthiincas tunes cremudanbsacssndsatoaaiunereent aaa 4 21 Chapter 5 Configuring an Access Node as
20. SAVE Specifies whether the DCM saves the active image into its local Flash memory or keeps the image in shared DRAM only To save the DCM boot image file to the DCM board s local Flash memory writing over the existing saved image select SAVE Select the NO SAVE option if you do not want to save the DCM boot image file the image remains in DRAM until the next time the DCM board boots 1 3 6 1 4 1 18 3 3 2 16 1 5 6 14 Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Configuring AN and ANH Features Configuration Mode LOCAL LOCAL SHARED MEMORY Specifies whether to use configuration information in the DCM board Flash memory or in the DCM board s shared memory space DRAM Select LOCAL to use the default configuration information in the DCM local Flash memory Select SHARED MEMORY to use the configuration information in the DCM DRAM written by DCMMW from the ANH file system 1 3 6 1 4 1 18 3 3 2 16 1 6 Write Configuration Info WRITE WRITE NO WRITE Specifies whether or not to write the configuration information in DRAM to the DCM board s Flash memory Select WRITE to save the configuration information in DRAM to the DCM board s Flash memory writing over the existing configuration file Select NO WRITE to avoid overwriting the DCM board s configuration file 1 3 6 1 4 1 18 3 3 2 16 1 7
21. The Matrix group stores statistics for an interchange between interfaces at different addresses This group s control parameters such as the interface that starts the interchange appear in the matrixControlTable When the Matrix group receives information from a good packet it places data in both the matrixSDTable and the matrixDSTable Filter Group The Filter group specifies what type of packets the DCM should capture Filter control parameters such as the minimum length of the packets to capture appear in the filterTable Associated with each filter is a channel a specific path along which data flows Control parameters in the channelTable define how and where the filtered packets flow Packet Capture Group The Packet Capture group enables the capture of packets that satisfy the Filter group control parameters For example you can specify the maximum number of octets from each packet that the group should store in the captureBufferTable To use the Packet Capture group you must set up the Filter group For More Information about RMON The following documents provide more detail e RMON MIB REC 1757 e The user guide for Optivity Design and Analysis network management software 6 10 Configuring AN and ANH Features Enabling the DCM Use the Configuration Manager to enable a newly installed N11 DCM option by creating the DCM software subsystem DCMMW 1 From the Configuration Manager window select Platform gt D
22. Use the Configuration Manager in local mode to create a configuration file for each AN ANH Refer to Configuring Routers for instructions Record the name of each configuration file and corresponding AN ANH for later reference When you name configuration files keep the following restrictions in mind Configuration files that you save on a BOOTP server do not have to be named config Configuration filenames must begin with an alphabetical character The remaining characters must be alphanumeric and may also include the underscore _ character You cannot use spaces Configuration filenames can consist of 1 to 15 characters including a dot We recommend that you limit filenames to eight characters to ensure that all operating systems Bay Networks supports can recognize the names Configuration filename extensions are optional and must follow a filename and a dot We recommend that you limit filename extensions to three characters BOOTP allows a maximum number of 49 characters in a path including slashes filename optional dot and filename extension If the BOOTP server and Site Manager do not reside on the same workstation transfer the configuration files to the BOOTP server 4 2 Configuring Network Booting Preparing an Image If you want the AN ANH to automatically boot a network image when starting up using EZ Install Netboot or Directed Netboot use the Site Manager Image Builder to configure the route
23. Window ccceceeeseeeeeteeeeeneeees 4 16 BOOTP Relay Agent Forwarding Table Window csceeeseeeeereees 4 17 BOOTP Addresses WINdON seiisissinisriesiincnnsis niin is ia 4 17 BOOTP Client Interface Table Window c cccccssecceceestteeeeeeesteeeeesenaes 4 20 BOOTP Client Interface Address Window Cr rer 4 20 Selecting the Repeater Hub Group Parameters Window c0ce 6 2 Group Paramete WOE sas chasiac Sus sass dadacnea vanities ntean ii anena aA 6 2 Selecting the Repeater Port Status Window cssceeeeeeeeteeeteeeees 6 4 8 Port ANH Port Status Window ansiniccutiicnaiiidiiianimnudans 6 5 12 Port ANH Port Status Window 4 E E A E 6 6 Creating the DCM Software Configuration from the Connguraion Mana ainiin iuei iandae aanse bhi aAA dA DER 6 11 Edi DOM Parameters WINdOw serisinin 6 12 Selecting the DCM Parameters Window cccceceessseseeeeeeeteeeseeees 6 19 Edit DCM Parameters WindOW cccccccessceeeeeenteeeeeeesaeeeseeeeaeeeeeseeaas 6 20 xi xii Figure 6 10 Figure B 1 Figure C 1 Figure C 2 Figure C 3 Figure C 4 Deleting DCM from the Configuration Manager Window sss 6 21 Starting the IP Interface Test cccisciscsssisiaccan ces sannencdcdansendceas iawentied aumentseiane B 14 Typical Single A NA Gonmmouranony cc ccistorcgescatcew vossiiedeatacsearncataideascciiniaes C 5 Connecting the ANH with Other Hubs 0 ce eecceeeeeeee
24. address and configuration file through an attached memory connection synchronous interface Next a remote UNIX or DOS based workstation that is configured as a Boot Protocol BOOTP server downloads a customized configuration file you save that configuration to Flash memory Requires a communications link over an HDLC or Frame Relay interface If EZ Install fails the router tries the Local Boot procedure continued 1 7 Connecting BayStack AN and ANH Systems to a Network Table 1 3 Summary of Boot Options continued Source for Boot Software Source for Option Image Config File Description and Requirements Netboot Network Network The AN ANH obtains all startup files from a remote UNIX or DOS based workstation that is configured as a BOOTP Synchronous Synchronous _ server Getting these files individually rather than getting or Ethernet or Ethernet the entire an exe file minimizes the cost of line usage and connection connection prevents saturation of the router s memory Requires a local an exe file a local console connection and a communications link over an HDLC Frame Relay or Ethernet interface If Netboot fails the router tries the Local Boot procedure Directed Network Network The AN ANH obtains all startup files from a remote UNIX or Netboot DOS based workstation that is configured as a Trivial File Synchronous Synchronous Transfer Protocol TFTP server Yo
25. address and subnet mask The AN ANH issues the request through all synchronous ports at about the same time even if cables are not connected to these ports Each port successively tries the following protocols until it receives a response e Bay Networks Standard PPP using HDLC high level datalink control encapsulation e Frame Relay Annex D e Frame Relay Local Management Interface LMI e Frame Relay Annex A The AN ANH makes two attempts for each protocol If it does not receive a response in approximately 4 minutes the AN ANH boots the default image and configuration file in its local file system as described in the next section Local Boot The first interface on the upstream router to receive the BOOTP request responds The upstream router calculates the IP address of the AN ANH s synchronous interface How the upstream router calculates the IP address depends on its protocol configuration See Step a if the upstream router circuit is running Bay Networks Standard or is a Frame Relay permanent virtual circuit PVC in direct access mode See Step b if it is a Frame Relay PVC in group access mode Hardware and Software Overview a A PVC in direct access mode or a Bay Networks Standard interface calculates the IP address by adding 1 to the IP address of the interface that received the request For example in Figure 1 1 the upstream router s interface address is 192 32 1 1 This means that the upstream router
26. available memory the RMON agent allocates the buffer size you requested The buffer can hold a maximum of 32 768 1024 20 or 31 packets NOTE The RMON agent allocates the full amount of memory you specify for the packet slice size to each packet even if the packet size is smaller than this amount For this reason Bay Networks recommends that you set the packet slice size to the smallest size possible The maximum packet size is 2 KB 6 29 Appendix A Troubleshooting Network Boot Problems Use the information in the following sections of this appendix to resolve problems directly related to startup and connectivity with remote routers e Solving Startup Problems e Identifying Remote Connectivity Problems e Resolving Connectivity Problems e Maintaining the Router Software Note For most troubleshooting information see Troubleshooting Routers Solving Startup Problems This section helps you isolate and solve the four most common router startup problems Refer to the appropriate section e Router Fails to Get IP Address e Router Fails to Netboot e Router Fails to Perform Directed Netboot e Router Netboots but Fails to Load Applications A 1 Connecting BayStack AN and ANH Systems to a Network Router Fails to Get IP Address If a message at the router console indicates that the router failed to get an IP address from the upstream router or if the upstream router is failing to receive BOOTP requests or respond to t
27. have more than 20 PVCs on the interface where EZ Install is occurring the EZ Install process may fail To ensure that the process does not fail configure no more than 20 PVCs for a Frame Relay interface If the AN ANH will have small routing or forwarding tables you can increase performance by reducing local memory and allocating more global memory for buffers If the AN ANH will have large tables for example more than 500 servers you might want to increase the local memory allocation If you use TFTP to transfer the software image file to upgrade or restore the router s file system be sure to specify the AN ANH image an exe Bay Networks supports BOOTP service on UNIX workstations but not PCs If you want to use Netboot and you are using a PC as your Site Manager workstation transfer the files you want to Netboot from the PC to a UNIX workstation and configure the workstation as a BOOTP server You cannot use EZ Install or Netboot directly from a Token Ring or FDDI interface You need Version 8 10 or higher to perform Directed Netboot If you have a LAN protocol analyzer available you may want to use it to troubleshoot BOOTP server communication errors Appendix A provides guidelines for using Packet Capture and an analyzer to isolate these errors Versions prior to 7 80 do not include the Technician Interface Packet Capture utility The 12 port ANH polls the internal repeater module for operation status it does not po
28. in the following order until it finds the correct type for the router s connection to the network 1 Bay Networks HDLC encapsulation also referred to as Bay Networks Standard Point to Point with external clocking 2 Frame Relay Annex D 3 Frame Relay LMI 4 Frame Relay Annex A continued 5 4 Configuring an Access Node as a Network Boot Client Table 5 2 ifconfig Command Settings for a Synchronous Interface continued Setting Description Frame Relay Settings fr Configures the router s synchronous port as a Frame Relay connection With this setting use one of the following options to specify a DLCMI setting annexd annexa or Imi annexd When one of these options is used with the fr setting it specifies a annexa DLCMI setting Use the same setting as the network to which the Imi router s Frame Relay interface is connected The default setting for Frame Relay is annexd Internal Clocking Setting int_clk Sets the synchronous port to internal clocking at 1 25 MB s If you do not specify this setting the router defaults to external clocking IP Connector Setting lt interface gt Specifies the IP connector you are configuring Use the format com lt port no gt IP Address Settings lt P address gt Specifies the IP address of the interface you set with lt interface gt Provide this address in dotted decimal notation lt subnet mask gt Specifies the IP
29. in the path between the AN ANH and the BOOTP server See Chapter 4 You ensure that there is a network connection from a synchronous or Ethernet interface on the AN ANH to the upstream router Note Jf the AN ANH will connect to the upstream router using a Frame Relay circuit be sure the upstream router is running Router Software Version 7 71 or higher gt The person at the AN ANH site establishes a Technician Interface session or you establish a session via modem See the hardware Installing and Starting guide for the AN or ANH The person at the AN ANH console uses the bconfig and ifconfig commands to configure a synchronous or Ethernet interface See Chapter 5 and the hardware Installing and Starting guide for the AN or ANH You install the netboot exe file in the BOOTP server s file system and make sure the image and application files reside in the same directory See Chapter 3 2 7 Connecting BayStack AN and ANH Systems to a Network 8 The person at the AN ANH site boots the router See the hardware Installing and Starting guide for the AN or ANH After the router boots it gets the software image and configuration file from the BOOTP server If the configuration file meets your network requirements the router starts bridging and routing traffic You can use the Site Manager Statistics Manager and Events Manager tools to verify that the router is routing traffic according to the configuration y
30. in this section only if you are using an HP 9000 as the Site Manager workstation To add a TFTP user for the HP 9000 enter a line with the following syntax in your etc passwd file We recommend that you use root as the TFTP home directory tftp lt user_id gt lt group_no gt bin false For example tftp 510 20 bin false Note We recommend that you not use the System Administration Manager SAM utility as an alternative to entering the commands above Setting Up Static Routes to Next Hop Routers If your workstation requires static routes use this section to specify a path to the network by e Editing the inetd conf file e Verifying the routes e Loading the changes into memory You must set up a static route for each path between the routers and the BOOTP server s next hop router You may want to specify a static route in a multihop environment or in an environment using routing protocols such as RIP where minor routing update delays may extend the time it takes to Netboot 3 10 Setting Up a UNIX Boot Server Editing the inetd conf File Add the following line to the inetd conf file to set up a static route route add lt destination gt lt gateway gt lt hops gt lt destination gt is the IP address of the AN ANH or its network lt gateway gt is the IP address of the network destination to which packets are to be addressed lt hops gt is the number of hops to the network destination
31. mask of the interface you set with lt interface gt Provide this address in dotted decimal notation lt next hop Specifies the IP address of the next hop router Provide this address address gt in dotted decimal notation Specify this address only if there are intermediate routers between the router and the BOOTP server Enabling and Disabling Interfaces with ifconfig To enable or disable an AN ANH interface for the network boot process use the following command formats ifconfig disable lt interface gt ifconfig enable lt nterface gt Table 5 4 describes the ifconfig command arguments for enabling and disabling interfaces for network booting Table 5 4 ifconfig Settings to Enable and Disable Netboot Interfaces Setting Description lt interface gt Specifies the IP connector you are enabling or disabling for network booting Use the format xevr lt port no gt or com lt port no gt 5 6 Configuring an Access Node as a Network Boot Client ifconfig Command Examples 1 Configure the current interface for the default Netboot procedure ifconfig d Specify the IP address and subnet mask of the first Ethernet Netboot interface ifconfig xcvr1 21 3 5 62 255 255 255 255 Specify the IP address and subnet mask of the second Ethernet Netboot interface ifconfig xcvr2 21 3 5 61 255 255 255 255 Configure the IP address and Frame Relay DLCMI of the third synchronous Netboot interf
32. number associated with the synchronous interface Enter connector number 1 1 COM1 2 COM2 3 COM3 Enter clock source number 2 1 Internal 2 External Enter circuit name S The AN recommends a circuit Press the Return name for the COM interface you key select for example S11 for COM1 and S12 for COM2 continued Connecting BayStack AN and ANH Systems to a Network Global Information Worksheet continued Step Requested Information Options Your Response 3 Enter IP address in dotted decimal Enter the IP address for the COM notation interface Enter the subnetwork mask in dotted Enter the subnetwork mask for decimal notation the COM interface IP address Is the router connected to y es Press the Return the same local area network n o key as the Site Manager workstation y n n Enter routing protocol 1 RIP Complete the number 1 2 OSPF worksheet for the 3 Static Route to Site Manager protocol you select Enter wide area protocol 1 Bay Networks Point to Point Complete the number 1 Protocol Proprietary worksheet for the 2 Frame Relay protocol you 3 Point to Point Protocol PPP select Standard 4 Switched Multimegabit Data Service SMDS Do you wish to set y es SNMP community management n o y n n Setting up SNMP community management is optional 4 TFTP default volume 1 The AN automatically assigns None the TFTP default volum
33. responses as well as some connector and interface settings you should consider e Enter the following command to display the router driver get wfLinkModules 15 0 The following response indicates that the AN ANH driver is configured to run in Slot 1 the only AN ANH slot wfLinkModules wfANLoad 0 2147483648 The decimal number 2147483648 represents Slot 1 If the setting is not 2147483648 enter the following command to correct it set wfLinkModules 15 0 2147483648 commit e To display the drivers that are configured to run enter the following command get wfDrivers 0 A combination of the following settings should appear within the list of drivers according to your AN or ANH configuration wfDrivers wfQsccSyncLoad 0 2147483648 COM ports EnetLoad 0 2147483648 Ethernet ports nonrepeating wfDrivers wfQsccl wfDrivers wfRptrLoad 0 2147483648 Ethernet repeater ports ANH only wfDrivers wfTMS380Load 0 2147483648 Token Ring ports A 6 Troubleshooting Network Boot Problems Use the set command to correct any settings that are incorrect For example if the router has a Token Ring port and the wfDrivers wfTMS380Load 0 setting is not 2147483648 enter the following command to correct it set wfDrivers wfTMS380Load 0 2147483648 commit If the router is Netbooting with a synchronous connector enter the following command to display the information about the connector where lt connector g
34. router shows a valid IP address that is configured on the IP router 7 Make sure the input IP address is correct A 2 Troubleshooting Network Boot Problems 8 If you are using EZ Install over a Frame Relay permanent virtual circuit PVC in group access mode make sure the upstream router s BOOTP client interface table is configured properly Router Fails to Netboot If the router fails to receive the configuration file or image using a network boot option first e Make sure that all cables between the router and the BOOTP server are firmly connected e Ifusing the ifconfig command be sure to specify the boot image krnl_an exe not an exe Then refer to the instructions in the following sections until you find and correct the problem e Upstream Router Not Receiving BOOTP Requests e Router Not Sending BOOTP Responses e BOOTP Server Not Sending BOOTP Responses If you have not isolated the problem to a specific interface retrieve the number of BOOTP packets forwarded and dropped from all routers between the router and the BOOTP server Refer to Displaying the Number of Packets Forwarded and Dropped later in this appendix Contact your local Bay Networks Technical Response Center if you perform the instructions in these sections and cannot find and correct the problem Upstream Router Not Receiving BOOTP Requests If the upstream router is not receiving BOOTP request messages do the following 1 Execute
35. subnet mask of the interface you set with lt interface gt Provide this address in dotted decimal notation lt next hop address gt Specifies the IP address of the next hop router Provide this address in dotted decimal notation Specify this address only if there are intermediate routers between the router and the BOOTP server Configuring an Ethernet Interface for Network Booting To configure an AN ANH Ethernet interface for network booting use the following command format ifconfig d lt interface gt lt IP address gt lt subnet mask gt lt next hop address gt Table 5 3 describes the ifconfig command arguments for configuring the router s Ethernet interface 5 5 Connecting BayStack AN and ANH Systems to a Network Table 5 3 ifconfig Command Settings for an Ethernet Interface Setting Description Default Setting d Resets the router s IP interface settings to the default values Resetting an Ethernet interface makes it inactive in the network booting process The output of the getcfg command shows the default as None IP Connector Setting lt interface gt Specifies the IP connector you are configuring Use the format xevr lt port no gt IP Address Settings lt P address gt Specifies the IP address of the interface you set with lt interface gt Provide this address in dotted decimal notation lt subnet mask gt Specifies the IP subnet
36. the ISDN network e A second Ethernet interface not supported in Token Ring ANs e An N11 Ethernet Data Collection Module DCM for gathering RMON Statistics not supported in Token Ring ANs Software Version 9 00 or higher and Site Manager Software Version 3 00 Note When using an NII DCM in the BayStack AN the AN requires Router gt or higher See Table 1 1 for a summary of AN hardware and the corresponding Site Manager module name for creating configuration files Table 1 1 BayStack AN Configurations Base AN Interface Configuration Upgrade Components Site Manager Module Name 1 Ethernet XCVR1 and 2 synchronous COM1 and COM2 Order Nos AE1001006 AE1001007 AE1001008 none E 2S 1 ISDN BRI replaces COM2 E 2S BRI 1 ISDN BRI with Floating B channel E 2S BRI 1 Ethernet DCM E 2S N11 DCM 1 third synchronous interface E 3S 1 second Ethernet interface 2E 2S 1 third synchronous interface and 1 Ethernet DCM E 3S N11 DCM 1 ISDN BRI with Floating B channel and 1 Ethernet DCM E 2S BRI N11 DCM 1 second Ethernet interface and 1 Ethernet DCM 2E 2S N11 DCM continued 1 2 Table 1 1 Hardware and Software Overview BayStack AN Configurations continued Base AN Interface Configuration Upgrade Components Site Manager Module Name 1 Token Ring none T 2S TOKEN1 and 2 synchronous C
37. the startup option e Booting the Router for the First Time e Booting the Router Routinely Then refer to the section Completing a Startup Option for a summary of your steps Booting the Router for the First Time You coordinate the initial startup with a person at the AN ANH site who physically installs and cables the router and initiates the desired startup procedure The hardware installation manual Installing and Starting BayStack AN Routers or Installing and Starting 8 Port BayStack ANH Systems explains these tasks in detail 2 1 Connecting BayStack AN and ANH Systems to a Network EZ Install Netboot After you select the initial startup configuration and set up the network as described in this guide you instruct the person at the router site to begin the appropriate startup option Note As an alternative to another person performing the initial startup at the remote site you can perform these tasks using a modem connection You can use EZ Install for the initial startup if e There is acommunications link between the AN ANH and an upstream router over an HDLC or Frame Relay interface e A directory on a BOOTP server contains a customized configuration file for the AN ANH EZ Install is the default option for a new router It is the easiest option for the person at the AN ANH site to perform because the network automatically supplies the IP address and configuration file You ca
38. they need to solve problems For instance the DCM can identify the hosts on a network that generate the most traffic or errors Refer to RMON Implementation Notes later in this chapter for issues you should consider when using an N11 DCM for RMON The RMON Groups The RMON agent runs on the DCM and comprises a set of MIB groups RFC 1757 defines the function and organization of these groups Bay Networks implements the following groups in its RMON agent e Ethernet Statistics e History Control e Ethernet History e Host e HostTopN e Matrix e Filter e Packet Capture 6 8 Configuring AN and ANH Features RMON groups contain control and data tables Control tables contain control parameters that specify which statistics you want to access You can view and change many entries in a control table Data tables contain statistics the agent obtains and usually you can only view entries in these tables Some of the groups work together to provide a particular RMON function For example the History Control group and the Ethernet History group together provide the history capability in the RMON agent for the DCM The following sections indicate the function of each group and the tables that each group defines Refer to RFC 1757 for the following information e A list of all the parameters that appear in a control table e The read write status of a control parameter e The default values for control parameters with r
39. upstream router and create a BOOTP client interface table in addition to a BOOTP relay agent forwarding table Note You do not need to create a BOOTP client interface table if the Frame Relay PVC is configured to operate in direct access mode or if the circuit is configured to operate with the Bay Networks Standard HDLC encapsulation protocol The BOOTP client interface table allows you to specify and pair the IP address of the AN ANH with the DLCI of the Frame Relay group access PVC Note f you are using EZ Install over Frame Relay to boot an AN you can have up to 20 PVCs for a single Frame Relay interface on the upstream router If you have more than 20 PVCs on the interface where EZ Install is occurring the EZ Install process may fail To ensure that the process does not fail configure no more than 20 PVCs for a Frame Relay interface For more information about the DLCI and Frame Relay refer to Configuring Frame Relay Services To create the BOOTP client interface table begin at the BOOTP Relay Agent Interface Table window refer to Figure 4 6 and proceed as follows 1 Click on Client I F The BOOTP Client Interface Table window appears Figure 4 9 4 19 Connecting BayStack AN and ANH Systems to a Network Ej BOOTP Client Interface Table f EE Done Add Delete Figure 4 9 BOOTP Client Interface Table Window 2 Click on Add The BOOTP Client Interface Address window appears Fig BOOTP Client Interf
40. when you terminate the third party RMON application it does not remove its History configuration using memory and processing power indefinitely You can release these resources only by using another application such as the SNMP tool or network management station or by resetting the DCM If you use too many resources for an RMON task the DCM can run out of memory for other RMON tasks and performs more slowly 6 23 Connecting BayStack AN and ANH Systems to a Network RMON Memory Use The total amount of RMON memory depends on the DRAM in the DCM Table 6 1 Table 6 1 DRAM and RMON Memory Size Installed DRAM MB RMON Memory in Bytes 2 162 578 4 2 077 330 8 5 222 034 16 12 561 042 NOTE Jf the RMON memory pool is full or if the RMON agent reaches an implementation limit the agent responds to an SNMP set command on an RMON control table entry with an SNMP GEN ERROR The following sections describes how much memory you need to e Configure an RMON group for example to configure the Matrix group or to configure Filter and Packet Capture groups e Store the data for an RMON group for example to store the packets a DCM captures In the following sections the word configuration means the set of control tables for a group For example a Matrix configuration includes only the matrixControlTable Note that you can create more than one configuration for some RMON groups For example
41. 12 Separates menu and option names in instructions Example Protocols gt AppleTalk identifies the AppleTalk option in the Protocols menu Indicates text that you need to enter and command names in text Example Use the dinfo command Indicate optional elements You can choose none one or all of the options Indicates variable values in command syntax descriptions new terms file and directory names and book titles Indicate the title of a chapter or section within a book Indicates data that appears on the screen Example set Bay Networks Trap Monitor Filters xix Connecting BayStack AN and ANH Systems to a Network ellipsis points vertical line I Horizontal and vertical lt ellipsis points indicate omitted information Indicates that you enter only one of the parts of the command The vertical line separates choices Do not type the vertical line when entering the command Example If the command syntax is show at routes nets you enter either show at routes or show at nets but not both Ordering Bay Networks Publications Acronyms To purchase additional copies of this document or other Bay Networks publications order by part number from Bay Networks Press at the following numbers You may also request a free catalog of Bay Networks Press product publications Phone FAX U S Canada FAX International AN ANH ANSI ARP ASN AUI BOFL BOOTP BOOTPD BRI CHAP DCE
42. 2 3 Recommend ONS ariana a a een Ter erree nme Seamer eared ret 2 3 Boch The Router FOUNDRY sionismin AE 2 3 ESSE jsutien rain aiiieei aman i meee dee 2 3 WPS Te IGT srianan ae leaned a ieee 2 4 LOCA OO anan etek giao Ge nlan rian E 2 5 PG Oo MMS MOANONS sscii cea coc eui cies tuna endear anas 2 5 Completing a Startup Option averai PREE E E E PET T E E 2 6 ELN e E 2 6 TE ao REAA E AA AY IAAI NEA NPA Y PAIE AANE NA AYORE NTP AEA 2 7 Directed GTO OO ace i ccsag here ccsleccesncaietas a e ai 2 8 Local BOGE meee ree re ee tere reerrt per ere rer ere er eretr Ere TNR 2 9 Chapter 3 Setting Up a UNIX Boot Server Seung Upa BOOTP SEYVET aarian aN N ENEN 3 1 Copying the BOOTPD Program on Sun Workstations sissunersisrinuurissrinrnsir iuan 3 2 petn UPBOOQIP SOCK ANS mantenesi a ober eetalad Wank iaddeen eae 3 2 Send UP BOOIP D tO RON Reopen reopen reer re eer conn etry Perr e rn Peereerttrerere re errr nr rrr erty 3 3 Setting Up BOOTPD to Respond to Routers ere EEEE E E 3 3 Ediungthe WOOT HAG FIG iieiea a ARRE 3 4 Verifying Consistent BOOTP Service ce cccccceceeceeeeeeeeseeeseaeeseeeeeeeeseeeeeeneees 3 8 Seer UPa MPU GIN sascciaascatisantacagieriekeduasdic a a AE 3 8 Providing TFIPD Access tothe Root Directory sadiwcscauinaaduetinesianad 3 8 Restricting TFTPD Access to a Specified Directory ccccesceeeseeeeeereeeeeeeeeeeetaees 3 9 Aoi TET Usei ior an HP BODO siiin 3 10 Setting Up Static Routes to
43. A 1 Router Falls to Gel IP POSS aronsson PEET A 2 Upstream Router Not Receiving BOOTP Requests s a a A 2 Upstream Router Not Sending BOOTP Responses cccccsccceeessteeeeeesnaes A 2 PROUTSE rae O NDOO niunia A 3 Upstream Router Not Receiving BOOTP Requests s A 3 Router Not Sending BOOTP Responses ssimisioiisiirsniiurersi iunea naniii A 4 BOOTP Server Not Sending BOOTP RESpongeS ssrrcresriniisrnroinenrnass A 4 Router Fails to Perform Directed Netboot senisssiinrunoiniinosdrnra A 5 Router Neiboots but Fails to Load Applications cesiececsiccsi osscesaaccismesiececsiomeaconsiens A 5 viii Identifying Remote Connectivity Problems cccesceceeseeeeeceeeeeeeeeeeeaeeseeneeeseaeeeeeneeeens A 7 Displaying Messages from the AN ANH Console ccccecceeeseeeeeeteeeteteeeeeneeeees A 7 Displaying Statistics and Error Messages ticccsecsisircncseccstesineeveuetdintaenueieans A 8 Guidelines for Using Packet Game ucsigensiiinonianaiaaan a A 8 Guidelines for Using a LAN Protocol Analyzer sirni aaia E E T A 9 Resovii Connecty Proble seirinin anaa a Ea A 9 PS VI Parameter Senge issu cass crsdausunh tare snneincsad paces hian ii ioi ad nA ins A 10 Pebugaing the COP Sarver acc oes tata acatedadsgied sad sami aesagaunraaiad aie bia leoe eS A 11 Vening the BOOTP Server Sep unuia anarian EAEAN ik A 12 Displaying the BOOTP Servers IP Routes 2 ccccceceeeseeeeeeeeeeeaeeeteeeeetaeeseeneees A 13 Displaying the N
44. BOOTP response Figure 1 3 Getting the Pathnames of the Kernel and Configuration Files The first server interface that processes the BOOTP response acts as the TFTP client in the remaining steps Connecting BayStack AN and ANH Systems to a Network 3 The AN ANH stops sending BOOTP requests 4 The AN ANH sends a TFTP request for the configuration file 5 The BOOTP server uses TFTP to transfer the configuration file Figure 1 4 AN ANH Configuration file lt _ Corporate backbone Upstream router BOOTP server Key TFTP request TFTP transfer Figure 1 4 Getting the Configuration File 6 The AN ANH sends a TFTP request for the image kernel file 7 The BOOTP server uses TFTP to transfer the image kernel file Figure 1 5 Local Boot Hardware and Software Overview AN ANH Kernel Corporate backbone ners D o TFTP request Key TFTP response Figure 1 5 Getting the Kernel 8 The AN ANH boots the kernel 9 The AN ANH uses TFTP to get application and string files as it needs them 10 The router begins bridging and routing network traffic in accordance with the configuration file The AN ANH can continue to request files even after it begins bridging and routing traffic If a failure occurs in Steps 1 through 8 the router attempts to boot locally When the AN
45. CM gt Create DCM Figure 6 6 obscreens an an cfg ecb Used Unused Description Connectors 8pt EHub 2S N11 DCM COM2 COMI Figure 6 6 Creating the DCM Software Configuration from the Configuration Manager The Edit DCM Parameters window appears Figure 6 7 Connecting BayStack AN and ANH Systems to a Network Cancel OK Values Help Enable Disable ENABLE Image Name Boot Option Image Save Mode Configuration Mode LOCAL Write Configuration Info NOWRITE RMON Max Host 500 RMON Default Host ENABLE RMON Default Matrix ENABLE Figure 6 7 Edit DCM Parameters Window 2 To accept the default configuration click on OK Or to customize the configuration continue with Step 3 3 Edit the parameters you want to change Use the descriptions that follow as guidelines 4 When you are finished click on OK Caution Configuration changes are effective only after you reboot the DCM board To do this use the Edit DCM Parameters window to disable and then re enable DCM 6 12 Configuring AN and ANH Features DCM Global Parameter Descriptions Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Enable Disable ENABLE ENABLE DISABLE Enables or disables DCMMW the DCM software subsystem and therefore the DCM board To enable the DCM board select ENABLE To disable t
46. Connecting BayStack AN and ANH Systems to a Network Router Software Version 10 0 Site Manager Software Version 4 0 Part No 112953 Rev A January 1996 a Bay Networks Bay Networks 4401 Great America Parkway 8 Federal Street Santa Clara CA 95054 Billerica MA 01821 Copyright 1988 1996 Bay Networks Inc All rights reserved Printed in the USA January 1996 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 Users must take full responsibility for their applications of any products specified in this document The information in this document is proprietary to Bay Networks Inc The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license A summary of the Software License is included in this document Restricted Rights Legend Use duplication or disclosure by the United States Government is subject to restrictions as set forth in subparagraph c 1 Gi of the Rights in Technical Data and Computer Software clause at DFARS 252 227 7013 Notice for All Other Executive Agencies Notwithstanding any other license agreement that may pertain to or accompany the delivery of this computer software the rights of the United States Government regard
47. D access 3 9 an exe 1 6 A 3 C 2 analyzing packets on a router A 8 on the BOOTP server A 9 ANH 12 port disabling 6 6 port status 6 6 status C 2 thirteenth port 6 6 8 port AUI interface 6 5 DCM option 6 7 ninth port 6 5 port status 6 5 AUI connections C 5 compliance rules C 4 Index configuring in a network C 3 to C 9 multiple C 6 single C 4 enabling ports on 6 4 repeater ports autopartitioning C 7 enabling 6 4 managing 6 1 resetting and testing 6 1 to 6 3 application files 1 6 generating 4 3 applications troubleshooting A 5 AUI connections 1 3 ANH C 5 coaxial backbone C 9 disabling SQE test function C 6 examples C 7 to C 9 automated addressing See IP address backbone coaxial C 9 fiber optic C 8 base record DCM 6 22 basic rate interface BRI 1 4 Bay Networks CompuServe forum xvii customer support xvii Home Page on World Wide Web xviii InfoFACTS service xviii publications ordering xxi Index 1 Technical Response Center xix Bay Networks Proprietary PPP protocol worksheet for B 8 Bay Networks Standard protocol 4 19 5 4 bconfig command examples 5 3 format 5 2 bf boot file tag in bootptab file 3 6 boot DCM board 6 18 failure 1 6 file tag 3 6 getcfg command display A 10 process 1 9 size tag 3 6 while writing to a file A 16 Boot Config From Network parameter 4 6 Boot Config Pathname parameter 4 7 Boot Image From Netw
48. DCM DLCI 1 800 845 9523 1 800 582 8000 1 916 939 1010 Access Node Access Node Hub American National Standards Institute Address Resolution Protocol Access Stack Node attachment unit interface Breath of Life Bootstrap Protocol Boot Protocol Daemon Basic Rate Interface Challenge Handshake Authentication Protocol data communications equipment Data Collection Module data link connection identifier XX DLCMI DTE FTP HDLC TEEE IP IPX ISDN LMI LQR MAC MAU MIB MTU NBMA NMM OSPF PAP PPP PVC RARP RFC RIP RMON SAM SMDS SMIT SNMP TCP IP Telnet TFTP TFTPD UDP UTP About This Guide data link control management interface data terminal equipment File Transfer Protocol high level data link control Institute of Electrical and Electronic Engineers Internet Protocol Internet Packet Exchange Integrated Services Digital Network Local Management Interface Link Quality Reporting media access control media access unit Management Information Base Maximum Transmission Unit Non Broadcast Multi Access network management module Open Shortest Path First Password Authentication Protocol Point to Point Protocol permanent virtual circuit Reverse Address Resolution Protocol Request for Comments Routing Information Protocol remote monitoring System Administration Manager Switched Multimegabit Data Services System Management Interface Tool Simple Network Management Protocol Transmission C
49. E The RMON agent allows you to create only one Host configuration Be sure to set the RMON Default Host parameter according to the expectations of the RMON network management application The Host configuration requires 148 bytes The Host data requires 105 bytes of memory per host address the DCM detects on a segment You specify the maximum number of host addresses that appear in the Host configuration by setting the RMON Max Host parameter when you enable a DCM If there is not enough memory for the number of hosts you request the RMON agent sets the RMON Max Host parameter to the highest possible value The number of addresses can range from 100 to 8 128 depending on the DCM memory configuration Table 6 2 shows recommended values for this parameter Table 6 2 Maximum Number of Hosts Installed DRAM MB Maximum Number of Hosts 2 4 2 048 5 8 4 096 9 16 8 128 You calculate the total memory in bytes you need for the host data as follows 105 Value of the RMON Max Host parameter 6 26 Configuring AN and ANH Features HostTopN Group Matrix Group To save memory and increase performance there is no default configuration for the HostTopN group You must create HostTopN configurations through your RMON network management application You can create as many HostTopN configurations as memory permits up to the RMON limit of 65 535 configurations NOTE Before you create a HostTopN configuration you mu
50. Ethernet segment e Stores the information according to the RMON MIB specification in compliance with RFC 1757 To communicate with the RMON agent software on the DCM board the ANH requires a software subsystem called DCM middleware DCMMW This software subsystem enables and configures an installed DCM board Using Site Manager you use the DCMMW to e Enable and initially configure the DCM e Modify the DCM configuration e Boot the DCM e Disable the DCM To set up other RMON configurations and to view RMON statistics use Optivity Design and Analysis software or a third party RMON network management application 6 7 Connecting BayStack AN and ANH Systems to a Network About Remote Network Monitoring RMON RFC 1757 is an extension of SNMP It specifies a standard MIB that defines both parameters for recording statistics and the actual statistics themselves The purposes of RMON include e Monitoring network performance You can configure the DCM to continuously perform diagnostics and monitor network performance If a network failure occurs the DCM can store statistical information about the failure The management stations can use this information to investigate the cause of the failure e Detecting and reporting problems You can configure the DCM to recognize and continuously check for error conditions e Collecting information for problem solving You can configure the DCM to give management stations information
51. Files Manager 4 5 Connecting BayStack AN and ANH Systems to a Network Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Boot Config From Network Enable Enable Disable Enables or disables retrieval of the configuration file from a BOOTP server the next time the router starts up Set to Disable if you have already saved the configuration file in the router s memory to the router s file system and you want to boot using this configuration file This setting reduces the time it takes to boot the router and eliminates using network resources to obtain the configuration file Set to Enable if you want the router to obtain the configuration file from a BOOTP server and you have already set up the network to support BOOTP service 1 3 6 1 4 1 18 3 3 2 10 1 2 Boot Server Address None A valid IP address of a TFTP server When one or both of the parameters Boot Image From Network and Boot Config From Network are set to Enable this parameter specifies the TFTP server from which the router will obtain the boot image and boot configuration files Use this parameter only when configuring Directed Netboot Enter the valid IP address of the TFTP server in dotted decimal notation 1 3 6 1 4 1 18 3 3 2 10 1 3 4 6 Parameter Default Options Function Instructions MIB Object ID Configuring Network B
52. N and ANH Information 0 ccccccccessseceeeeeeeeeeeeeaaeeeeeeeaeeeeenecnaeeeeeeeaaas xvi Bay Networks Customer SUPPOTU avaniris rnanan aan iaia iaiia auaa xvii COMPUS ENE miiran o ened cerned ences xvii MOFAG T S apunaan ANN xviii World Wide Web c E A EET PEE E E T Gerania xviii Howie GerRel ai a e a Ean xix RS TIMID INITEN AT stan Sd cy rad EA ETAN E ETNI ETE TOAT NT EET A XiX Ordering Bay Networks Publications i sciicscssetscpentataliedientddecriatadieceanlaradenolataloraienatuaies ACTON gee Peep eee eR Pere ee rare Terre PLC ANR XX Chapter 1 Hardware and Software Overview PCOS Node TRANS siiin a a aR 1 1 ee e EEE I EIN T ANEA E TA AEA A AN E NT A eadecs 1 1 ANH MOda saina a 1 3 Access Node SONWITE cic Gsu ieee cuentas S N A 1 5 Sotware Management Tole vases aan hansee ca nanihacannee Mearidanadatig ea is saan 1 5 WL FTIR oenn 1 6 Boot Orci ONS hurar Aa NAE CAA 1 6 TEBE G FO ana baealouedesiadsaninlactaniaduaeeraaraelieale 1 9 CARD gn elo sonn E esae Ont pecan Gre reek ene irerer cme rres 1 9 GND o IP ARGES anne mn peer aa ate ere eener nm crete rer ere tren rrereny try 1 9 Getting Kernel Image and Configuration Files ccccccseeseeeeeteeeeeeeeee 1 13 bocal BOGT ori A RE 1 15 Containing ihe Minal PMG ECE sirsiran adaini daaa aaia 1 16 Chapter 2 Selecting the Boot Configuration Boing The Router forthe Fot TMG earra a a S 2 1 EL i oa E S 2 2 hie ia e a E EA P E E E E E 2 2 Local BOGI ernis an RRN
53. OM1 1 ISDN BRI replaces COM2 T 2S BRI and COM2 1 ISDN BRI with Floating B channel T 2S BRI 1 third synchronous interface T 3S Order Nos AE1101002 AE1101003 AE1101004 1 Ethernet XCVR1 none E T 2S 1 Token Ring TOKEN1 and 2 1 ISDN BRI replaces COM2 E T 2S BRI synchronous COM1 1 third synchronous interface E T 3S and COM2 1 ISDN BRI with Floating B channel E 7 2S BRI Order Nos 1 Ethernet DCM E T 2S N11 DCM AE1101006 1 ISDN BRI with Floating B channel E T 2S BRI N11 DCM AE1101007 and 1 Ethernet DCM AE1101008 1 third synchronous interface and E T 3S N11 DCM 1 Ethernet DCM ANH Models The ANH is available in 12 and 8 Ethernet hub repeater port configurations The repeater interfaces include 10BaseT shielded or unshielded twisted pair UTP ports with RJ 45 modular connectors The 8 port ANH also supports a 15 pin Attachment Unit Interface AUT connection to the Ethernet repeater Note The Ethernet repeater ports operate as a single interface Software configuration parameters for example the port IP address apply to all ports Both the 12 and 8 port ANH models include two synchronous interfaces with 44 pin connectors COM1 and COM2 These ports provide simultaneous and independent support for SDLC X 21 EIA232 EIA449 422 or V 35 Connecting BayStack AN and ANH Systems to a Network With optional upgrades installed the BayStack ANH also supports e An ISDN basic rate interface BRD providing direct co
54. Statistics Manager Quick Get tool or the Technician Interface get command to display the number of BOOTP and TFTP packets forwarded and dropped for each interface in the path between the AN ANH and the BOOTP server Use the Events Manager tool or the Technician Interface log command to display the events associated with the interface and the BOOTP and TFTP protocols Refer to Managing Routers for instructions on using the Statistics Manager s Quick Get tool and the Events Manager That guide also describes each event displayed in the log Refer to Using Technician Interface Software for instructions on using the get and log commands Guidelines for Using Packet Capture Use the Packet Capture utility to view incoming or outgoing BOOTP or TFTP packets and isolate errors to a specific router interface This utility is available through the Technician Interface on routers running Version 7 80 or higher Refer to Using Technician Interface Software for instructions on how to use Packet Capture Refer to Configuring SNMP BOOTP DHCP and RARP Services for a description of BOOTP packets Note The instructions that follow assume that Version 7 80 or higher is running on all routers in the path between the AN ANH and the BOOTP server Use Packet Capture as follows 1 Test the BOOTP server s next hop router in the path to the AN ANH 2 Test the upstream router s interface to the AN ANH 3 Test the upstream router s interface to the n
55. a ID of the router s neighbor Note The backbone area ID is always 0 0 0 0 continued B 5 Connecting BayStack AN and ANH Systems to a Network OSPF Worksheet continued Requested Information Options Your Response Enable Simple Password y es authentication y n n n o Note If you answer y es the router requests a password Password Enter OSPF MTU size selection 1 1 Default 2 Ethernet size Bay Networks Series 5 compatible 3 User defined MTU Enter OSPF interface type selection 1 1 Broadcast 2 NBMA 3 Point to Point 4 Point to Multipoint 5 Point to Multipoint STD Note When using a wide area protocol other than Bay Networks Proprietary PPP we suggest selecting NBMA Enter decimal value in seconds for Hello Interval 10 Note This value must match all other interfaces in the OSPF area for connection to take place The AN suggests the following intervals Broadcast 10 seconds Point to Point 15 seconds NBMA 20 seconds Point to MultiPoint 10 seconds Enter decimal value in seconds for Router Dead Interval 40 Note This value must match all other interfaces in the OSPF area for connection to take place The AN suggests the following intervals Broadcast 40 seconds Point to Point 60 seconds NBMA 80 seconds Point to MultiPoint STD 40 seconds continued OSPF Workshe
56. a Network Boot Client Working with a Person at the AN ANH Site c cccccsceeseeeeeeeeeeseeneeeeeaaeseeneeeseeaeeeeaaeeeeea 5 1 Configuring the Router Boot Source anane PEE PE na T E Reon Orin aN FONA uniin aor ENTANA 5 2 beanna Command Er9MPIES sisinio eaa aa A aanak 5 3 Conigunng the Weiboot niera seciisaneie ween iTi 5 3 Configuring an IP Synchronous Interface for Network Booting cccceeeeeeees 5 4 Configuring an Ethernet Interface for Network Booting E E a DD Enabling and Disabling Interfaces with GONT cites c ccsccccsscciasesssccnenseconicenseneensens 5 6 PREY Command AG aauina aoaaa ie cae 5 7 HUO DON O ena B f Chapter 6 Configuring AN and ANH Features Managing ANH Repeater Ports P E meted PERT PEE ET SRNE arl Testing and Resetting Repeater PONE sasciicctexcinicctesciicacetainineceascsiieststsardacmaceeiiantes 6 1 Repeater Port Group Parameter DeSCriptiOnS sisrisiiiuusssiaisnuannianenunnissniunanianiaana 6 3 Enabling and Disabling ANH Repeater Ports c cccssseeeeseeeeeeeeeeeeeeeteaeeeeeneeeeaes 6 4 Gontiguring an NT Data Collection Module ccs suisierrsueadiceiiasaeniuieas Gans 6 7 foou te NTI DC N Meemmeeamer esuwnrte ect recor Sr ntres ter ureter ery rrrracer pens tern eerrrces retraces errr 6 7 vii About Remote Network Monitoring RMON cccceeeeeeceeee cesses eeeeeeeseaaeeneeeeess 6 8 Tie RMON OFORE nts terns aiena cst anion ca dinieenncuts Rad alanstuo vind c
57. ace ifconfig com3 21 3 5 62 fr annexa What to Do Next You can now boot the AN ANH over the network assuming that you already Configured a UNIX workstation to support network booting as described in Chapter 3 Prepared configuration and boot image files and placed them in the appropriate locations for your boot configuration as described in Chapter 4 Whenever you boot the AN ANH it should start routing traffic according to the configuration file it obtains from the BOOTP server You use the Site Manager Statistics Manager to view traffic statistics and the Event Log to determine whether the AN ANH is routing traffic Refer to Managing Routers for instructions on using the Statistics Manager and Events Manager tools If the AN ANH does not begin routing traffic after booting refer to Appendix A of this guide 5 7 Chapter 6 Configuring AN and ANH Features This chapter describes how to configure special features specific to the AN and ANH It explains how to e Manage ANH repeater ports e Configure and manage a Data Collection Module DCM option Managing ANH Repeater Ports You manage ANH repeater ports using Site Manager software From Site Manager the ANH repeater ports operate as a single interface XCVR1 Software configuration parameters such as the port IP address apply to all repeater ports Testing and Resetting Repeater Ports Use the following procedure to reset and test ANH repeater ports 1 Fro
58. ace Address Cancel OK Help DLCI Number Figure 4 10 BOOTP Client Interface Address Window 3 Enter the AN ANH s IP address and its associated DLCI number For help refer to the parameter descriptions that follow this procedure 4 Click on OK 4 20 5 Configuring Network Booting The BOOTP Client Interface Table window now lists the client IP interface and the DLCI number you added Click on Done to exit the window BOOTP Client Interface Parameters Parameter Default Options Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID IP Address None Any valid IP address Specifies the IP address of the AN ANH that is using EZ Install This parameter applies only to a Frame Relay group access PVC connection Enter the IP address in dotted decimal notation of the AN ANH interface 1 3 6 1 4 1 18 3 5 3 8 1 1 1 3 DLCI Number None 16 to 1007 Specifies the identification number of the upstream router s PVC to the AN ANH The Frame Relay network uses the DLCI number to direct data flow from the AN ANH to the upstream router Enter the number in decimal format Use the DLCI number assigned by your Frame Relay service provider 1 3 6 1 4 1 18 3 5 3 8 1 1 1 2 4 21 Chapter 5 Configuring an Access Node as a Network Boot Client To enable an AN or ANH for Netboot or Directed Netboot you configure one or more router in
59. al e Loading the changes into memory Note A daemon is an unattended process that is one that runs in the background An application typically calls up a daemon to perform a standard routine or service in this case TFTP When you set up the TFTPD server on a UNIX workstation you can allow TFTP to access the root directory and any subdirectory or restrict its access to a specified directory or pathname Allowing the router to access the root directory and any subdirectory is the simpler procedure Specifying a pathname provides security but it requires linking TFTPD Providing TFTPD Access to the Root Directory To provide TFTPD access to files in the root directory and to all subdirectories verify or insert the appropriate line for your operating system in the etc inetd conf file Find the sample line for your operating system in Table 3 3 3 8 Setting Up a UNIX Boot Server Table 3 3 Providing TFTPD Access to Root and All Subdirectories Operating System OS Sample Line to Insert in etc inetd conf Directory SunOS tftp dgram udp wait root usr etc in tftpd in tftpd s Solaris tftp dgram udp wait root usr sbin in tftpd in tftpd s HP UX tftp dgram udp wait root etc tftp tftp AIX Use the System Management Interface Tool SMIT to configure TFTP For instructions refer to the IBM guides on TCP IP daemons and the TFTP protocol Restricting TFTPD Access to a Specified Directory
60. anagement counters defined in the RFC 1516 MIB nor does it affect the status of the ports It does disrupt traffic flow Accept the default NO_RESET or select RESET 1 3 6 1 2 1 22 1 1 4 Selftest NO_SELFTEST NO_SELFTEST SELFTEST Causes the router to perform an agent specific test on itself This test does not disrupt traffic flow Accept the default NO_SELFTEST or select SELFTEST 1 3 6 1 2 1 22 1 1 5 6 3 Connecting BayStack AN and ANH Systems to a Network Enabling and Disabling ANH Repeater Ports Use the following procedure to enable or disable the repeater ports on an ANH 1 From the Site Manager window which appears at Site Manager startup select Tools gt Configuration Manager gt Dynamic The Configuration Manager window appears displaying the real time router hardware and software configuration 2 From the Configuration Manager window select Platform Setup Repeater Port Status Figure 6 3 Configuration M SNMP Ag File N Mi fa MIB Vers Boco o Used BEER Description Connectors 8pt EHub 2S7 N11 DCM Figure 6 3 Selecting the Repeater Port Status Window The Port Status window appears allowing you to enable or disable the ports on the router Figure 6 4 shows the port status window for the 8 port ANH Figure 6 5 shows the port status window for the 12 port ANH 6 4 Configuring AN and ANH Features Figure 6 4 8 Port ANH Port Status Window Note The ninth port is
61. and the BOOTP responses it receives vme rfc1048 The sample bootptab file in Figure 3 1 enables two ANs named AN Boston and AN Chicago to boot across the network Use the basic format shown in Figure 3 1 to set up your own bootptab file 3 6 Setting Up a UNIX Boot Server This file contains the default specification for the boot image file to be used by all ANs general contains information that is common to all ANs that need to boot via BOOTP You can use any word in place of general general sh se SE hd specifies that S HOME builder_dir rel900 an is the directory on the workstation where the boot files are located By default the Image Builder writes its files to this directory If you are using a router software version later than 8 00 add the associated three digits to the end of the rel directory name If you moved the files to another directory specify that directory hd SHOME builder_dir rel1812 an Sh OSE OSE OSE OSE OSE SE se bf specifies that the name of the boot image kernel file is krnl_an exe bf krnl_an exe bs indicates the size of the boot file If you specify auto as the size the BOOTP server calculates the size of the file for each BOOTP request bs auto sho SE vm indicates that the BOOTP server should always reply in a manner compliant with RFC 1048 You must enter rfcl048 for this tag so that the AN can understand the BOOTP
62. arameter name tag Follow each tag with an equal sign and a value A pound sign at the beginning of a line indicates a comment A backslash at the end of a line indicates continuation of the line Note Make sure you enter a backslash not a slash at the end of every line that does not conclude a definition 3 4 Setting Up a UNIX Boot Server Keep the following in mind when editing bootptab e The lt hostname gt definition can contain a maximum of 79 characters e The first character must be alphabetic e All characters must be alphanumeric e You can use a dot to separate characters but the character immediately following the dot must be alphabetic e The hostname definition cannot contain an underscore Table 3 1 lists the tags for router host names Table 3 2 lists the tags for boot image names Table 3 1 _ BOOTPD Tags for a Router Host Name Required or Tag Optional Value Example ip Required IP address the host IP address ip 192 32 5 2 of the router sm Optional Subnet mask the host subnet sm 255 255 255 0 mask of the router T129 Required Pathname of the router T129 usr cfg an_Bost cfg configuration file The maximum path length is 49 characters T130 Required Size of the router configuration file T130 0x0004 in 512 byte blocks The setting of this tag determines how much memory the router allocates for the file Set this tag to 0x0004 tc Optiona
63. artups Note You can boot an AN ANH over the network for some procedures and locally for others provided you set up the network to support Netboot Using Netboot for routine startups allows you to e Manage software image and configuration files from a remote location by storing them on the BOOTP server This option greatly simplifies the management of a number of routers by allowing you to concentrate on keeping the startup files up to date in a single central location the BOOTP server 2 3 Connecting BayStack AN and ANH Systems to a Network e Minimize the need to maintain the router s local file system When the router gets files from a BOOTP server it stores the files in memory not in its file system reducing the need for frequent file system compactions Refer to Using Technician Interface Software or Managing Routers and BNX Platforms to learn about compacting a file system e Restore a corrupted file system The AN ANH file system resides on an installed flash card With Netboot enabled the router can still boot over the network if the local files become corrupted When the AN ANH reboots due to a reset or power loss it automatically boots the configuration file and software image over the network if it cannot find intact files locally e Get application and string files from the BOOTP server as the AN ANH needs them Getting these files individually rather than getting the entire an exe file minimi
64. assigning an IP address to an interface Use the Technician Interface ifconfig command to manually configure a synchronous or Ethernet interface for Netboot or Directed Netboot Configure the upstream router to support automated addressing for EZ Install Chapter 4 describes how to configure the upstream router to support EZ Install by creating the BOOTP client interface table The Boot Process section in Chapter 1 describes how the router automatically obtains an IP address during the EZ Install process The following sections describe each use of the ifconfig command 5 3 Connecting BayStack AN and ANH Systems to a Network Configuring an IP Synchronous Interface for Network Booting Configure a synchronous interface to the IP network using the following interface configuration command ifconfig synchronous options lt interface gt lt IP address gt lt subnet mask gt lt next hop address gt The synchronous options variable indicates some combination of the following settings d fr annexd Imi annexa int_clk Note Insert a space to separate each command option from the next Table 5 2 describes the ifconfig command arguments for configuring an AN ANH synchronous interface Table 5 2 ifconfig Command Settings for a Synchronous Interface Setting Description Default Setting d Resets the router s IP interface settings to the default values This setting tries four WAN configurations
65. aves the new information to its Flash memory Caution The Technician Interface does not verify that the value you enter for a parameter is valid Entering an invalid value can corrupt your configuration 6 22 Configuring AN and ANH Features RMON Implementation Notes Read the following sections to learn about RMON memory use and interoperability issues you should consider when using RMON network management applications with the DCM These sections assume that you have a good understanding of each RMON group and do not refer to the low level details of the MIB such as RMON MIB objects Refer to About Remote Network Monitoring RMON earlier in this chapter and RFC 1757 for information about each RMON group RMON Interoperability Issues Some network management applications automatically set up their own configurations for an RMON group without checking to see if the RMON agent already has a default configuration In addition when you terminate those applications they may not remove the configurations they set up for the RMON agent These features can result in the RMON agent using excessive amounts of memory and processing power Example When you enable a DCM the RMON agent automatically creates a History configuration Suppose you then start a third party RMON History application which creates its own History configuration for the agent The RMON agent stores the data in two places wasting memory In addition
66. calculates 192 32 1 2 as the booting router s IP interface AN ANH router BOOTP request BOOTP response with IP address 192 32 1 2 Upstream router IP address 192 32 1 1 Figure 1 1 Getting an IP Address from a Bay Networks Standard Circuit or a Frame Relay PVC in Direct Access Mode Note f the IP address plus 1 equals a broadcast address the upstream router calculates the IP address by subtracting 1 For example if its interface is 7 255 255 254 the IP interface for the booting router is 7 255 255 253 b A PVC in group access mode references its BOOTP client interface table to find an associated IP address for the booting router Connecting BayStack AN and ANH Systems to a Network Note The BOOTP client interface table contains a data link connection identifier DLCI and IP address pair for each PVC You use Site Manager to create this table when you follow the instructions for setting up routing paths in Chapter 4 For example in Figure 1 2 an AN router sends BOOTP requests for its IP address The upstream router receives the request on PVC 31 The upstream router determines the DLCI refers to DLCI 31 in the BOOTP client interface table finds the IP address and sends a BOOTP response containing the IP address back to PVC 31 AN ANH Booting router 2 Booting router 3 PVC 32 PVC 31 PVC 33 Frame Relay Circ
67. ce 12Pt EHub 3S AE1101015 COM1 and 1 second Ethernet interface 12Pt EHub E 2S AE1101016 COM2 1 ISDN BRI with Floating B channel 12Pt EHub 2S BRI 1 4 Hardware and Software Overview Access Node Software Read this section for summary information about the AN ANH router software It describes e Tools available for configuring and managing an AN ANH e Kernel and application files e Boot configuration options AN and ANH models support all major LAN and WAN protocols standard IBM transport and dialup services A choice of protocol suites IP Access Suite Remote Office Suite or Corporate Suite provides site specific software configurations at remote AN and ANH installations As for all Bay Networks routers the Access Node family provides extensive MIB variable support including e Standard MIB II e Bay Networks proprietary MIB e Managed Hub RFC 1516 MIB for ANH models e Remote Monitoring RMON RFC 1757 for ANH models with a DCM option Software Management Tools You configure and manage an AN or ANH using e The Technician Interface a terminal based command line interface that operates in router memory You run Technician Interface commands and scripts for SNMP based MIB access from an attached console or from a remote console via modem e The Diagnostics Monitor a firmware diagnostics agent with a command line interface You use the Diagnostics Monitor to configure the router s boot configu
68. chnician Interface Software and Managing Routers When Technician Interface commands require you to specify a volume always specify Volume 1 for an AN ANH Upgrading the Software Image You can upgrade an AN ANH s software image krnl_an exe using one or both of the following options e Use Netboot to start the AN ANH This option upgrades the image only in the AN ANH s RAM e Use TFTP to transfer the image to the AN ANH s local file system then use Local Boot to start the AN ANH This option upgrades the image in both the AN ANH s local file system and in memory Caution f you use TFTP to transfer an upgraded image to an AN ANH Flash card and an interruption in the file transfer occurs for example if the AN ANH resets reboots or loses power the AN ANH s local file system becomes corrupted and it cannot boot locally until the file system is restored Connecting BayStack AN and ANH Systems to a Network Restoring a Local File System If the local file system becomes corrupted you must restore it by upgrading the software image If for any reason the AN ANH resets reboots or loses power while restoring or compacting its Flash card file system it automatically Netboots the configuration file and software image Note that you must already have the network set up for Netboot to succeed After the AN ANH successfully Netboots you can use TFTP to restore the software image and configuration file on the l
69. configure a UNIX workstation as a BOOTP server by e Setting up BOOTP sockets e Configuring BOOTPD the BOOTP daemon 3 1 Connecting BayStack AN and ANH Systems to a Network Note A daemon is an unattended process that is one that runs in the background An application typically calls up a daemon to perform a standard routine or service in this case BOOTP On Sun workstations you must first copy the BOOTPD program to the appropriate directory Copying the BOOTPD Program on Sun Workstations Depending on the operating system you use Bay Networks may or may not ship BOOTPD with the Site Manager package The AIX and HP UX operating systems already have BOOTPD SunOS and Solaris do not so Site Manager automatically installs BOOTPD on Sun workstations running SunOS and Solaris Copy the bootpd file to the etc directory as follows 1 Log in to the UNIX workstation as root 2 Enter the following command cp usr wf bin bootpd etc Setting Up BOOTP Sockets A socket is a UNIX mechanism for creating virtual connections between operating system and network processes For each socket the etc services file must include a user datagram protocol UDP descriptor that provides process to process addressing information Set up the send and receive sockets for the BOOTP process as follows 1 Log in to the UNIX workstation as root 2 Use a text editor to insert the following two lines into the efc services file bootps 67 udp bo
70. d BNX Platforms Reconfiguring AN ANH netboot Chapter 5 in this guide interfaces Considerations for setting up an AN or Appendix C in this guide ANH Resolving problems with the network Appendix A in this guide boot process Troubleshooting all other problems Troubleshooting Routers Bay Networks Customer Support Bay Networks provides live telephone technical support to our distributors resellers and service contracted customers from two U S and three international support centers If you have purchased your Bay Networks product from a distributor or authorized reseller contact the technical support staff of that distributor or reseller for assistance with installation configuration troubleshooting or integration issues Customers also have the option of purchasing direct support from Bay Networks through a variety of service programs The programs include priority access telephone support on site engineering assistance software subscription hardware replacement and other programs designed to protect your investment To purchase any of these support programs including PhonePlus for 24 hour telephone technical support call 1 800 2LANWAN Outside the U S and Canada call 408 764 1000 You can also receive information on support programs from your local Bay Networks field sales office or purchase Bay Networks support directly from your reseller Bay Networks provides several methods of receiving suppo
71. d in Figure 4 5 Booting routers Enable BOOTP on these interfaces BOOTP server Corporate backbone Figure 4 5 Enabling BOOTP in a Sample Network 4 14 Configuring Network Booting Enable BOOTP relay on an interface as follows 1 2 3 4 5 Click on the connector in the Configuration Manager window Select Edit Circuit in the Edit Connector window Select Protocols gt Add in the Circuit Definition window Select BOOTP in the Select Protocols window and click on OK Select File gt Exit to exit the Circuit Definition window Creating BOOTP Relay Agent Forwarding Tables You must create a BOOTP relay agent forwarding table for every router passing BOOTP traffic between the router and the Site Manager workstation The BOOTP relay agent forwarding table allows you to specify the IP interface that receives the incoming BOOTP request packets and the associated IP interface that forwards them You can add multiple pairs of incoming and outgoing interfaces to support connections to multiple routers in your network To create the BOOTP relay agent forwarding table begin at the Configuration Manager window and complete the following steps 1 Select Protocols gt IP gt BOOTP gt Relay Agent Interface Table in the Configuration Manager window The BOOTP Relay Agent Interface Table window appears Figure 4 6 This window lists all IP interfaces on the router 4
72. d use acknowledge that such portions of the software were developed by the University of California Berkeley The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED AS IS AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE In addition the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure that may incorporate by reference certain limitations and notices imposed by third parties Bay Networks Software License Note This is Bay Networks basic license document In the absence of a software license agreement specifying varying terms this license or the license included with the particular product shall govern licensee s use of Bay Networks software This Software License shall govern the licensing of all software provided to licensee by Bay Networks Software Bay Networks will provide licensee with Software in machine readable form and related documentation Documentation The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights Bay Networks will not grant any Software license whatsoever
73. e Read this guide if you are responsible for connecting a Bay Networks BayStack Access Node AN or Access Node Hub ANH router to a managed network Connecting BayStack AN and ANH Systems to a Network offers An overview of AN and ANH hardware and software Chapter 1 A description of network booting Chapter 2 Instructions for setting up a UNIX workstation as a BOOTP server Chapter 3 Instructions for configuring Site Manager to support network booting Chapter 4 Instructions for configuring the AN or ANH for network booting Chapter 5 Instructions for managing ANH repeater ports Chapter 6 Instructions for configuring an N11 Data Collection Module DCM for RMON statistics gathering Chapter 6 Troubleshooting guidelines and procedures Appendix A Worksheets for completing the Quick Start procedure Appendix B Implementation hints and notes Appendix C Written for system and network managers this guide assumes that you have a working knowledge of Ethernet and IEEE 802 3 networks and their physical layer components Site Manager A text editor on a UNIX workstation XV Connecting BayStack AN and ANH Systems to a Network Before You Begin Before using this guide you or a person at the router site must install the AN or ANH hardware and network connections as described in one of the following guides e Installing and Starting BayStack AN Routers e Installing and Starting 8 Port BayStack ANH S
74. e to 1 5 Do you want to enable y es TELNET y n n n o Enabling TELNET is optional 6 FTP default volume 1 The AN automatically assigns the FTP default volume to 1 7 Do you wish to save this configuration y es Press the Return to a file y n y n o key Enter filename startup cfg We recommend using the default filename Press the Return key Router Protocol Worksheets Local Boot The Quick Start Procedure This section contains requested information and possible options relating to the routing protocol choices on the Global Worksheet RIP Worksheet Requested Information Options Your Response Should RIP listen to the default route y es y n n n o Note RIP listens to a specific network or subnet route where Site Manager is located Answering y es to this request forces RIP to also listen to the default route 0 0 0 0 This is useful when no specific route is available in the RIP updates that the router receives OSPF Worksheet Requested Information Options Your Response Enter the OSPF router ID in dotted decimal notation the router provides the IP address of the COM port Enter an IP address to uniquely identify the router in the OSPF domain We suggest using the default IP address provided Enter the OSPF area ID in dotted decimal notation 0 0 0 0 Enter the area ID This ID must match the are
75. ead write status e A list of all the objects that appear in a data table Ethernet Statistics Group The Ethernet Statistics group records data that the DCM measures on network interfaces The DCM creates one entry for each Ethernet interface it monitors on a device and places the entry in the EtherStatsTable The EtherStatsTable also contains control parameters for this group History Control Group and Ethernet History Group The History Control and Ethernet History groups work together to control and record the periodic statistical sampling of data from varous types of networks The historyControlTable and etherHistoryTable comprise the two groups Host Group The Host group identifies hosts on the network by recording the source and destination MAC addresses in good packets and places the information in the hostTable This group also records the time it discovered a host on the network in the hostTimeTable The hostControlTable specifies control parameters and contains information about the monitoring process 6 9 Connecting BayStack AN and ANH Systems to a Network HostTopN Group The HostTopN group ranks hosts according to a statistic type For example you might want to rank the hosts by the number of errors they generate Control parameters for this group appear in the hostTopNControlTable and data this group generates appears in the hostTopNTable To use the HostTopN group you must set up the Host group Matrix Group
76. eceive end fiber link can be longer than 400 meters m Network Path Containing Four Repeaters In the longest path containing four repeaters e No more than three links are maximum length coaxial segments e No fiber link is longer than 500 m or if one or more is longer the total of all fiber links does not exceed 2500 m 2740 m if all are 10Base FB Configuring a Single ANH The basic ANH configuration consists of one ANH one local management console and as many as nine 10Base T devices in a standalone local area network configuration You can directly connect as many as eight 10Base T Ethernet stations into a local Ethernet segment using a single 8 port ANH C 4 Implementation Notes Note You can add a ninth Ethernet station to the AUI port using a 10Base T transceiver The section Configuring an AUI Port describes other options for using the AUI port Figure C 1 shows an example of a single ANH network configuration UTP distribution cables connect Ethernet stations that have either an installed 10Base T network interface card NIC or an AUI NIC plus an external 10Base T transceiver ANH MDI X MDI 5 6 7 8 Partition Lit on T2s 4 567 onooooooo LX J Link UTP cables Access Node Hub 10Base T NIC connector
77. ecifying location of 5 2 transferring C 2 upgrading A 15 implementation notes 6 23 C 2 incoming interface specifying 4 15 to 4 18 inetd conf file 3 3 loading changes 3 11 setting up static routes 3 11 troubleshooting A 4 InfoFACTS service xviii initial startup options 2 1 Input IP Address parameter 4 18 interface connections AUI port 1 1 1 3 Ethernet 1 1 Ethernet repeater ports 1 3 synchronous 1 1 Token Ring 1 1 UTP 1 3 Index 4 interfaces BOOTP parameters 4 18 incoming and outgoing 4 15 to 4 18 interoperability issues for RMON 6 23 to 6 29 IP address 1 9 to 1 13 assigning manually 2 7 DLCTI 4 19 to 4 21 failure A 2 getting automatically 1 10 to 1 13 input parameter 4 18 manual assignment 5 3 options for getting 5 3 EZ Install 1 9 Local Boot 1 8 1 15 2 3 output parameter 4 18 tag 3 5 IP interface Ethernet address settings 5 6 connector setting 5 6 synchronous connector setting 5 5 default settings 5 4 IP routes changing 3 10 displaying A 13 ip tag in bootptab 3 5 ISDN BRI 1 4 K kernel file See krnl_an exe 1 6 krnl_an exe 1 6 generating 4 3 specifying instead of an exe A 3 upgrading A 15 L LAN protocol analyzer A 8 A 9 line usage minimizing bandwidth 2 5 cost 2 4 link module B 3 linking ANHs C 6 to C 9 linking BOOTPD and TFTPD 3 9 LMI Frame Relay 5 4 Local Boot configuring B 1 definition 1 6 initial startup
78. eeteeeeeesnnteeeeeeees C 7 Connecting Two ANH Systems Using 10Base FL Transceivers C 8 Connecting ANH Systems through a Coaxial Backbone eceee C 9 Table 1 1 Table 1 2 Table 1 3 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 5 1 Table 5 2 Table 5 3 Table 5 4 Table 6 1 Table 6 2 Table 6 3 Table A 1 Table B 1 Table C 1 Tables BayStack AN Coniguratione saisan a i 1 2 BayStack ANH Configurations juss cniccarn nasser iusaaiianannnmnaeein 1 4 Summaiy Or EG Ol OION E siaina aara ank 1 7 BOOTPD Tags for a Router Host Nam nsincneninnsesinrsniannnno 3 5 BOOGIFU lage or A Bool Image Name icisaisenssniusaeioiakie aiii 3 6 Providing TFTPD Access to Root and All Subdirectories 0ce 3 9 Restricting TFTPD Access to One Directory eeceeeeeeeeeeeeeesereeateereeneens 3 9 bconfig Command Settings ceeeeeeee E E E E 5 2 ifconfig Command Settings for a Synchronous Interface 0 ceeee 5 4 ifconfig Command Settings for an Ethernet Interface cseeee 5 6 ifconfig Settings to Enable and Disable Netboot Interfaces 06 5 6 DRAM and RMON Memory SIZE aici iecasiecitatacdimauedvincde 6 24 Maximum Number of Hosts 0 ceeeeee er S 6 26 Derault Size oF CADW BUNGI serrr a 6 28 BOOTP We eS iaaiaee A 12 COS Sta TS OMIT arssinat eta B 13 IEEE 802 5 Maximum Segment LINKS casiscisatiecdenciiindaateteas C 4 xiii Audience About This Guid
79. er refer to Modifying Software Images for Routers If you use a different workstation as a BOOTP server transfer all of the files in the directory that contains the kernel file to the new workstation 4 3 Connecting BayStack AN and ANH Systems to a Network Enabling Netboot or Directed Netboot By default the router obtains its software image from its local file system and its configuration file from a BOOTP server Display and change these settings as follows 1 Select Protocols gt Global Protocols gt Net Boot gt Global from the Configuration Manager window The Edit Netboot Global Parameters window appears Figure 4 1 Edit NETBOOT Global Parameters Boot Image From Network ENABLE Boot Config From Network DISABLE Boot Server Address Boot Image Pathname Boot Config Pathname Figure 4 1 Edit Netboot Global Parameters Window 2 To enable Netboot set one or both of the first two parameters to Enable 3 To enable Directed Netboot set one or both of the first two parameters to Enable and configure the last three parameters For guidelines see the descriptions of the parameters that follow this procedure 4 After editing the parameters click on OK 4 4 Configuring Network Booting Note Of the five parameter fields shown in Figure 4 1 the first two Boot Image From Network and Boot Config From Network apply to both Netboot and Directed Netboot The last three parameters are for Direc
80. erms buckets The second configuration provides long term history by sampling statistics every 30 minutes and holding up to 50 buckets Through your RMON network management application you can create as many History configurations as memory permits up to the RMON limit of 65 535 configurations You can also set the number of buckets a particular History configuration uses to as many as available memory allows If you request more buckets than memory allows the agent allocates enough buckets to fill available memory You need 504 bytes of memory for each History configuration 252 bytes each for the short term and long term History configurations The History data requires 52 bytes of memory per bucket You calculate the total memory in bytes you need to store the data as follows Number of buckets 52 2 History configurations This calculation shows that you need approximately 5 1 KB for the default setting of 50 buckets 6 25 Connecting BayStack AN and ANH Systems to a Network Host Group When you enable the DCM the default setting Enabled for the RMON Default Host parameter creates a Host configuration To prevent creation of a Host configuration set the RMON Default Host parameter to Disabled before you enable the DCM as described in the Activating DCM section Some RMON network management applications expect the DCM to set up a Host configuration while others set up their own configurations NOT
81. ernet connectors are as follows None the default setting The IP address with subnet mask See Chapter 5 for instructions on using the ifconfig and bconfig commands to change the parameter settings Debugging the BOOTP Server Debug the BOOTP server as follows 1 Enter the following command at the UNIX command line bootpd d d amp The bootpd debugger tool reads the etc bootptab file and generates the etc bootpd dmp file The etc bootpd dmp file contains the portion of the etc bootptab file that the bootpd debugger could read successfully The debugger displays messages such as the following 1 12914 hostname etc gt reading etc bootptab read 19 entries from etc bootptab dumped 19 entries to etc bootpd dump Compare the bootptab file to the bootpd dmp file If the bootpd dmp file is truncated or is otherwise different from the bootptab file BOOTPD may have encountered a syntax error Find the inconsistency in the two files Compare the inconsistency in the bootptab file to the sample bootptab file in Chapter 3 refer to Figure 3 1 and correct the error If you cannot find an inconsistency boot the AN ANH and view the bootpd debugger messages to determine the cause of the error The sample messages in Table A 1 show the sequence of messages when a BOOTP exchange is successful Connecting BayStack AN and ANH Systems to a Network Table A 1 BOOTP Messages Message Explanation ho
82. ese instructions to add a Netboot interface 1 Select Protocols gt Global Protocols gt Net Boot gt Interfaces from the Configuration Manager window The Netboot Interfaces window appears Figure 4 2 psp TNT tere Ari Dejate Apply plum ia Help ap j Connecter IP Adirens Subnet Mask Hewi Hinam Protocol Mask State Figure 4 2 Netboot Interfaces Window The scroll box is empty unless this router has existing Netboot interfaces configured 2 Click on Add The Netboot Interface window appears Figure 4 3 4 8 Configuring Network Booting Figure 4 3 AN ANH Netboot Interface Window 3 Specify the interface s slot number and connector For guidelines see the parameter descriptions that follow this procedure 4 Click on OK The Netboot Interfaces window now shows the configured interface Figure 4 4 4 9 Connecting BayStack AN and ANH Systems to a Network l Connector LY RI i ral A Comector IF Adirens Sulmet Maske Hewi Him Protocol Hasi State Figure 4 4 Netboot Interfaces Window 5 Highlight the interface in the scroll box and edit its parameters For guidelines see the parameter descriptions that follow this procedure 6 Click on Apply 7 Add any additional Netboot interfaces you want to configure Repeat Steps 2 through 6 Note If you configure more than one interface to Netboot the first interface to receive a reply from the BOOTP server will use Netbo
83. et continued Local Boot The Quick Start Procedure Requested Information Options Your Response Enter decimal value for Router Priority 1 For Broadcast NBMA or Point to MultiPoint Enter a router priority value The lower the value above zero the higher the priority Note If you set the router priority to zero 0 the router is not eligible to become the designated router on this particular network Enter decimal value in seconds for Poll Interval 20 For NBMA only Enter the largest number of seconds allowed between Hello packets the router sends to an inactive NBMA neighbor The router suggests a 20 second interval Enter IP address of neighbor in dotted decimal notation or enter q to quit For NBMA only Enter addresses for all NBMA neighbors you want the router to communicate with Enter q and press the Return key when you finish entering addresses Enter IP address of neighbor in dotted decimal notation For PPP only Enter addresses for the PPP neighbor you want the router to communicate with Static Route to Site Manager Worksheet Requested Information Options Your Information Destination Network 0 0 0 0 Enter the gateway address of the destination network An address of 0 0 0 0 specifies the default route continued B 7 Connecting BayStack AN and ANH Systems to a Network Static Route
84. ext hop router A 8 Troubleshooting Network Boot Problems Test the interfaces that receive and forward the BOOTP and TFTP packets of the router in the middle of the path Continue testing each router in the path until you isolate the problem interface Guidelines for Using a LAN Protocol Analyzer Refer to the following guidelines when you use a LAN protocol analyzer If Netboot is failing connect the analyzer to the BOOTP server interface to determine whether it is receiving and responding to Netboot and TFTP requests To read the ASCII translation view the BOOTP reply packets for the configuration file pathname in hexadecimal mode Note The LAN protocol analyzer does not decode all of the vendor tag fields If the BOOTP server is not receiving the requests make sure the upstream router is receiving and forwarding them If it is receiving make sure each router interface between the upstream router and the BOOTP server is receiving and forwarding them If the BOOTP server is receiving requests but failing to respond refer to Router Fails to Netboot earlier in this appendix Resolving Connectivity Problems This section describes how to Display the router s Netboot parameter settings Debug the BOOTP server Verify the BOOTP server s setup Display the BOOTP server s IP routes Display the number of BOOTP packets forwarded and dropped A 9 Connecting BayStack AN and ANH Systems to a Network
85. figuration file The script begins to test the configuration on the new IP interface Figure B 1 B 13 Connecting BayStack AN and ANH Systems to a Network IP IP IP IP IP NOTE this happens 192s T92 192 192 1 925 32 32 32 00 00 00 32 32 000 000 000 00 00 000 000 Testing local IP interface ping IP 19232002000 r9 ping i ping ping ping ping is is is is is This test attempts to ping alive alive alive alive alive the Site Manager workstation If routing has not yet converged to ping the Site Manager workstation may fail you may either enter a new IP address or quit and wait a short period of time and try again from the TI command line Type q lt return gt to cancel this test 16 16 16 16 T6 an attempt Enter IP address of Site Manager workstation Figure B 1 8 To continue the IP configuration test enter the IP address for the Site Manager workstation To cancel the test enter q 9 When the ANH Technician Interface prompt reappears type logout and press the Return key to exit the Technician Interface Once the AN ANH creates and tests the configuration it starts using the configuration information you entered Refer to Configuring Routers to configure the router using Site Manager Starting the IP Interface Test Hints Appendix C Implementation Notes This appendix contains implementation hi
86. for misspellings or other errors Compare it to the sample file shown in Chapter 3 refer to Figure 3 1 Displaying the BOOTP Server s IP Routes Enter the following command at the UNIX command line of the BOOTP server to display the IP address of the next hop to a netbooting router netstat rn grep i n lt P_address gt lt P_adadress gt is the IP address of the netbooting router s network is the vertical bar key the UNIX pipe command For example enter netstat rn grep i n 192 32 155 to display the IP address of the next hop to the network address 192 32 155 Connecting BayStack AN and ANH Systems to a Network If the BOOTP server is receiving RIP advertisements of the netbooting router s network a message such as the following appears 121 192 32 155 0 192 32 13 53 UG 0 0 leo The number 121 is the number of the entry in the workstation s static routing table The number 192 32 155 0 is the IP address of the destination network The number 192 32 13 53 is the address of the next hop router If the next hop router is unavailable or wrong refer to Setting Up Static Routes to Next Hop Routers in Chapter 3 Displaying the Number of Packets Forwarded and Dropped This section describes how to display the number of BOOTP packets forwarded and dropped by a router Perform this procedure for each router between the router and the BOOTP server You can use either the Quick Get function of the Statistic
87. g guide for the AN or ANH The router starts bridging and routing traffic You can use the Site Manager Statistics Manager and Events Manager tools to verify that the router is routing traffic according to the configuration you want See Managing Routers and BNX Platforms 2 9 Chapter 3 Setting Up a UNIX Boot Server To support network booting you need to set up a UNIX workstation on the network to run Boot Protocol BOOTP and Trivial File Transfer Protocol TFTP This chapter describes what you need to do at a UNIX workstation to prepare for booting an AN ANH over the network When a router boots over the network it gets its startup files from a UNIX server When the AN ANH uses EZ Install or Netboot the server supplies configuration file and or software image file pathnames using BOOTP The AN ANH then retrieves the files using Trivial File Transfer Protocol TFTP When the AN ANH uses Directed Netboot it already knows the pathnames of the files it needs and retrieves the files directly from the server using TFTP To Configure This Boot Method Complete These Sections EZ Install Setting Up a BOOTP Server and Setting Up a TFTP Server Netboot Setting Up a BOOTP Server and Setting Up a TFTP Server Directed Netboot Setting Up a TFTP Server Setting Up a BOOTP Server To support EZ Install or Netboot an AN ANH needs a network connection to a BOOTP server You
88. group 6 9 6 25 Ethernet Statistics group 6 9 6 25 Events Manager tool A 8 executable exe files See application files EZ Install 1 10 to 1 15 configuring 3 1 4 1 initial startup option 2 6 maximum PVCs C 2 requirements 1 7 summary 1 7 troubleshooting A 2 to A 5 Index 3 F failure BOOTP A 2 A 3 FDDI interface limitation C 2 fiber optic backbone C 8 files corrupted A 15 naming restrictions 4 2 transferring See TFTP Filter group 6 10 6 28 Flash memory EZ Install boot image source 1 7 Local Boot image source 1 8 format command A 15 forwarding table See BOOTP Frame Relay direct access PVC 1 9 group access PVC example 1 11 setting up 4 19 to 4 21 settings 5 5 worksheet B 9 frames displaying A 14 G gateway 4 14 get command A 8 getcfg command 5 6 A 2 A 10 getting help from a Bay Networks Technical Response Center xix through CompuServe xvii through InfoFACTS service xviii through World Wide Web xviii group access See Frame Relay H hd home directory tag in bootptab 3 6 HDLC encapsulation 5 4 History Control group 6 9 6 25 home directory tag 3 6 Host group 6 9 6 26 HostTopN group 6 10 6 27 HP 9000 See HP UX HP UX adding a TFTP user 3 10 BOOTPD 3 2 TFTPD access 3 9 ifconfig command 5 3 Image Builder default directory 4 3 image software corrupted A 15 generating 4 3 getting from a BOOTP server 1 13 to 1 15 preparing 4 3 sp
89. han it does to Netboot one In most configurations however the difference between the two options is only a few seconds Minimize line usage Getting files from a BOOTP server during Netboot adds traffic to your network during the booting process Recommendations Bay Networks recommends that you Set up the network to support Netboot even if you plan to use the Local Boot option for the initial configuration and for subsequent restarts Maintain the software image an exe on the local file system at all times in case you want to use Local Boot for either of these routers 2 5 Connecting BayStack AN and ANH Systems to a Network Completing a Startup Option EZ Install This section lists the steps required to complete EZ Install Netboot Directed Netboot Local Boot You can use Netboot for some procedures and Local Boot for others provided you set up the network to support Netboot Note To boot an AN ANH over the network all other routers in the path to the BOOTP server must be running Router Software Version 7 60 or higher Completing the EZ Install option requires the following steps 1 You use the Configuration Manager in local mode to create a complete configuration file for the AN ANH See Chapter 4 and Configuring Routers You set up a UNIX workstation on the network to support BOOTP See Chapter 3 You create a BOOTP relay interface table on the upstream router to support automated address
90. he AN or ANH The router boots from a local software image and downloads the configuration file from a TFTP server The router starts bridging and routing traffic You can use the Site Manager Statistics Manager and Events Manager tools to verify that the router is routing traffic according to the configuration you want See Managing Routers and BNX Platforms Completing the Local Boot option requires the following steps 1 De You complete the Quick Start worksheets See Appendix B Either a person at the remote site using a local console connection or you using a modem connection establish a Technician Interface session See Chapter 5 and the hardware Installing and Starting guide for the AN or ANH If you are not at the AN ANH console you provide the person at the remote router site with the information necessary to complete the Quick Start worksheets in the installation manual See Appendix B The person at the AN ANH console runs the Quick Start configuration script install bat using the information provided in the worksheets you completed in Step 1 See Appendix B and the hardware Installing and Starting guide for the AN or ANH The Quick Start script records the responses in a configuration file See Appendix B and the hardware Installing and Starting guide for the AN or ANH no action required The person at the AN ANH console reboots the AN ANH See Chapter 5 and the hardware Installing and Startin
91. he DCM board select DISABLE Use this parameter to reboot the DCM board by enabling then disabling DCMMW 1 3 6 1 4 1 18 3 3 2 16 1 2 Image Name None but you must specify an image name when the Boot Option parameter is set to DOWNLOAD An ASCII text string no more than 255 characters Specifies the pathname of a DCM boot image in the ANH file system The image name must be a fully qualified filename including both volume and filename Enter the volume and filename for the image you want the DCM board to boot using the form lt volume_number filename gt for example 1 dcm_image 1 3 6 1 4 1 18 3 3 2 16 1 3 6 13 Connecting BayStack AN and ANH Systems to a Network Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Boot Option LOCAL LOCAL DOWNLOAD Specifies whether the DCM board uses the image in its own Flash memory for booting or an image copied from the ANH file system to DCM shared memory DRAM Select LOCAL to specify the image file in DCM local Flash memory as the DCM boot image Select DOWNLOAD to specify an image file on the ANH Flash memory as the DCM boot image When the DCM board boots in DOWNLOAD mode DCMMW software moves a copy of the image to DCM shared memory You specify the downloaded image with the Image Name parameter 1 3 6 1 4 1 18 3 3 2 16 1 4 Image Save Mode SAVE SAVE NO
92. he complete pathname of the remote software image or configuration file pathname gt d Reverts to the default values for the software image or configuration file and nullifies any previously specified IP address and pathname for the file thus disabling Directed Netboot 5 2 Configuring an Access Node as a Network Boot Client bconfig Command Examples 1 Configure the default Netboot procedure use a local image file and look for the configuration file over the network using BOOTP bconfig d image or bconfig image local bconfig d config or bconfig config network Use Netboot for both the boot image and configuration file bconfig image network bconfig config network Use a local configuration file and Directed Netboot for the boot image file bconfig image network 21 3 5 62 usr mykernel exe bconfig config local Use a local boot image file and Directed Netboot for the configuration file bconfig image local bconfig config network 21 3 5 62 usr anstartup config Use Directed Netboot for both the boot image and configuration file bconfig image network 21 3 5 62 usr mykernel exe bconfig config network 21 3 5 62 usr anstartup config Configuring the Netboot Interface A router interface cannot communicate in an IP network without an IP address Because an AN ANH netboots over one of its synchronous or Ethernet links the Netboot interface must have a valid IP address You have two options for
93. hem make sure the network cable between the router s synchronous port and the upstream router is firmly connected Then refer to the instructions in one of the following sections until you find and correct the problem e Upstream Router Not Receiving BOOTP Requests e Upstream Router Not Sending BOOTP Responses Contact the Bay Networks Technical Response Center if you follow the instructions in these sections and cannot find and correct the problem Upstream Router Not Receiving BOOTP Requests If the upstream router is not receiving BOOTP request messages use the getcfg command to display the router parameters and the bconfig and ifconfig commands to correct them if necessary Refer to Displaying Parameter Settings and Debugging the BOOTP Server later in this appendix if you need instructions Upstream Router Not Sending BOOTP Responses If the upstream router is receiving BOOTP request messages but failing to send BOOTP responses use Site Manager to do the following 1 Make sure the upstream router s interface to the AN ANH is enabled 2 Make sure BOOTP is enabled on the circuit connecting the AN ANH to the upstream router Make sure the upstream router s link modules and drivers are loaded Make sure the upstream router s IP protocol is enabled Make sure the upstream router s BOOTP protocol is enabled A a PF amp Make sure the BOOTP relay agent forwarding table associated with the upstream
94. iate 6 8 For More linter mehr About RMON scicaceceansctertenericrtrassccsgeevenladateeenieenciieess 6 10 Prabno me DG ruoriin a E AA 6 11 DOM Global Parameter DOScr PWONS sissiriiiirsnnasisver ienaa 6 13 Managing the DCM Usma Ste Managgi lt iczcccsccciiesteecasgectssnesaqcceranccienieedeniaceaducanesn 6 17 ee e e ELE e ssa tastes ad A ATE E A E AE A T T 6 17 EUV DOM cunka a 6 18 Bowo DONI iori nn ee reper ene A R 6 18 Changing DCM Configuration Parameters cccececeeceeeeeeeeeeeeseeeeeeeeetees 6 19 Deleting the DCM Software SubSy Ste ccccccecisaccsiccerssnncensnnriecrestsscoeteenemnvaness 6 21 Managing the DCM Board Using the Technician Interface csceceesseeeeeeeees 6 22 Changing DOM Configuration Parameters siccccsecicatcccaiieenecdedsssietedadonsiecndaacs 6 22 RMON Impiementatorn NOIES sirrcna a a E 6 23 RMON Interoperability ISS0eS rsrs iirinn anni ieaie 6 23 RMON Memory USE srrenssninerenia E 6 24 Interoperability Issues and Memory Use for RMON Groups sssi 6 24 Statistics GrOUP 2ecevesecle sas exiesancpecsectabesenessenccylastadscnes cuts c elasabisddeasuhseesheestinnd eanes 6 25 History Group ireira ete Ane dei ee tent da 6 25 POSE GFO ariora eet NA 6 26 HostIopN GroUp decesa a ea AE REN 6 27 Matrix Gro Up iirrainn a eee ed 6 27 Fiter gmd Capture COUPS isa see aaa cies aanraai a hAON 6 28 Appendix A Troubleshooting Network Boot Problems Song tartip FOUNENNS sanina E iauititss Casrecavd cate eada ametatiavaded
95. in the network Note Before the router can get files over the network you must also set up a UNIX server on the network as described in Chapter 3 The following sections of this chapter explain how to complete the tasks required for configuring EZ Install Netboot or Directed Netboot To Configure This Boot Method Complete These Sections EZ Install Preparing Configuration and Image Files EZ Install over Frame Relay group access PVC Preparing Configuration and Image Files and Creating the BOOTP Client Interface Table Netboot Enabling Netboot or Directed Netboot Configuring a Netboot or Directed Netboot Interface and Setting Up Routing Paths for Netboot Directed Netboot Interface Enabling Netboot or Directed Netboot and Configuring a Netboot or Directed Netboot Note The steps in this chapter assume that the Site Manager software is running on a network workstation Connecting BayStack AN and ANH Systems to a Network Preparing Configuration and Image Files Unless the AN ANH will use the default generic configuration file and software image that ships on its local Flash memory card you must create A unique configuration file for each remote router A uniform software image that all routers in your network can use Creating Configuration Files Prepare network configuration files as follows 1
96. ing C 1 Index 2 configuration file cont preparing 4 2 restrictions 4 2 T130 size tag 3 5 configuring Directed Netboot 3 1 5 1 EZ Install 3 1 4 1 interface 5 2 Local Boot B 1 Netboot 3 1 5 1 network C 3 to C 9 connecting multiple ANHs C 6 to C 9 Connector IP Address parameter 4 11 Connector Next Hop parameter 4 12 Connector parameter 4 11 Connector Protocol Mask parameter 4 12 Connector State parameter 4 13 Connector Subnet Mask parameter 4 12 console port 1 1 cost of line usage 1 8 2 4 customer support See getting help D daemon BOOTP 3 2 TFTP 3 8 DCM about 6 7 configuring 6 19 6 22 disabling 6 18 installing 6 11 parameters 6 13 reboot 6 12 6 18 DCMMW DCM middleware 6 7 debugging the BOOTP server A 11 default IP interface settings Ethernet 5 6 synchronous 5 4 deleting files A 15 dialup access A 7 direct access See Frame Relay Directed Netboot bconfig command 5 3 configuring boot client 5 1 interfaces for 4 1 server location 5 2 UNIX server 3 1 ifconfig command 5 7 requirements for 1 8 DLCI and IP address pair 4 19 to 4 21 example 1 12 DLCI Number parameter 4 21 DLCMI settings 5 5 driver displaying MIB entry for A 6 drivers B 3 E erasing files A 15 error messages displaying A 7 Ethernet compliance C 3 displaying MIB entry A 7 interface connections 1 1 repeater ports 1 3 6 1 segment lengths C 4 Ethernet History
97. ing and configure all routers between the BOOTP server and the booting router as BOOTP relay agents See Chapter 3 You ensure that there is a network connection from a synchronous interface on the AN ANH to the upstream router Note Ifthe AN ANH will connect to the upstream router using a Frame Relay circuit be sure the upstream router is running Router Software Version 7 80 or higher 5 A person at the AN ANH site installs and boots the router See the hardware Installing and Starting guide for the AN or ANH 2 6 Netboot 6 Selecting the Boot Configuration The AN ANH gets a software image from its local file system an IP address from the upstream router and the customized configuration file from the BOOTP server Described in Chapter 1 no action required If the configuration file meets your network requirements the AN ANH starts bridging and routing traffic You can use the Site Manager Statistics Manager and Events Manager tools to verify that the router is routing traffic according to the configuration you want See Managing Routers and BNX Platforms Completing the Netboot option requires the following steps 1 You use the Configuration Manager in local mode to create a complete configuration file for the AN ANH See Chapter 4 and Configuring Routers You set up a UNIX workstation on the network to support BOOTP See Chapter 3 You use Site Manager to enable BOOTP on each router interface
98. ing its use reproduction and disclosure are as set forth in the Commercial Computer Software Restricted Rights clause at FAR 52 227 19 Trademarks of Bay Networks Inc ACE AFN BCN BLN BN CN FRE LN Optivity SynOptics SynOptics Communications Wellfleet and the Wellfleet logo are registered trademarks and AN ANH ASN BaySIS BayStack BCNX BLNX BNX EZ Internetwork EZ LAN FN PathMan PhonePlus PPX Quick2Config RouterMan SPEX Bay Networks Bay Networks Press the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks Inc Third Party Trademarks All other trademarks and registered trademarks are the property of their respective owners Statement of Conditions In the interest of improving internal design operational function and or reliability Bay Networks Inc reserves the right to make changes to the products described in this document without notice Bay Networks Inc does not assume any liability that may occur due to the use or application of the product s or circuit layout s described herein Portions of the code in this software product are Copyright 1988 Regents of the University of California All rights reserved Redistribution and use in source and binary forms of such portions are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation advertising materials and other materials related to such distribution an
99. ion Instructions MIB Object ID Configuring Network Booting Connector State Enable Enable Disable Enables or disables Netboot on this interface When this parameter is set to Enable any settings already entered in the other four parameter boxes in the Netboot Interfaces window appear and are noted by Site Manager so that Netboot occurs If the setting is Disable Site Manager disregards the other parameters and the router cannot Netboot If you do not want Site Manager to use the settings on the Netboot Interfaces window set this parameter to Disable If you want Site Manager to use any of the other four parameters in the Netboot Interfaces window refer to Figure 4 2 you must set this parameter to Enable 1 3 6 1 4 1 18 3 3 2 10 3 1 1 4 13 Connecting BayStack AN and ANH Systems to a Network Setting Up Routing Paths for Netboot You set up the routing paths between the BOOTP server and the routers by e Enabling each router interface in the paths to the routers e Creating a BOOTP relay agent forwarding table for each router in the path e Creating a BOOTP client interface table for the upstream router when the AN ANH is on a Frame Relay PVC in group access mode Enabling Router Interfaces You must enable BOOTP relay also called BOOTP pass through or gateway on all interfaces in the paths between the AN ANH routers and the BOOTP server For example you would enable BOOTP relay on the interfaces indicate
100. ions If the AN ANH Netboots a software image successfully but displays an error message indicating that it cannot load specific applications it is failing to retrieve files from the TFTP server that provided the software image These files are necessary to perform functions such as running the protocols specified in the configuration file or displaying the log Do the following 1 Make sure that after booting you have at least one interface configured through which the file server that supplied the kernel image can be reached This is necessary for a router that has obtained its image over the network to load application or string files Make sure that all the application and string files files with exe and str filename extensions reside in the same directory as the kernel image A 5 Connecting BayStack AN and ANH Systems to a Network Check that you have TFTP on the router To determine this display the router s loadmap screen message If tftp exe is missing load it onto the router Use Site Manager to make sure that IP is enabled and TFTP is created in the AN ANH s configuration file Refer to Verifying the BOOTP Server Setup later in this appendix Use Technician Interface commands to verify or correct the status of the synchronous or Ethernet connectors used for network booting Refer to Using Technician Interface Software for instructions Following are some examples of AN ANH commands and their
101. is interface Does the Remote Peer have PAP authentication enabled y n n Note If you answer y es the router requests the PAP ID and password for the remote interface Enable the LQR Link Quality y es Reporting Protocol y n n n o Note Link Quality Monitoring on a Bay Networks Series 5 router is not compatible with this feature continued Local Boot The Quick Start Procedure PPP Standard Worksheet continued Requested Information Options Your Information Enable use of the Remote Peer y es router s LQR Timer y n y n o For LQR Protocol only Note If the LQR timer is enabled the remote peer router maintains its own LQR timer for this interface When the LQR timer is disabled the AN is responsible for maintaining the timer for this interface Number of seconds 1 120 3 For LQR Protocol only Enter the maximum number of seconds between the transmission of LQR packets Enter inbound success rate percentage 1 100 90 Enter the minimal acceptable success rate percentage of packets transmitted by the peer router and received on this interface over the last 5 LQR reporting periods Enter outbound success rate percentage 1 100 90 Enter the minimal acceptable success rate percentage of packets transmitted by this interface and received by the peer router over the last 5 LQR reporting periods Co
102. l Table continuation pointer to a tc general definition in another location in the same file for additional information The information this tag points to is common to all routers that need to boot using BOOTP If information in a definition for a specific router is inconsistent with the definition this tag points to BOOTPD uses the information for the specific router 3 5 Connecting BayStack AN and ANH Systems to a Network Table 3 2 BOOTPD Tags for a Boot Image Name Tag Required or Optional Value Example hd Required Home directory the directory on the workstation containing the boot files By default the Image Builder writes its files to the directory specified in the example The rel number is the version number of the current router software release If you change the default or move the files to another directory specify that directory hd HOME builder_dir rel 812 an bf Required Boot file the name of the boot image bf krnl_an exe bs Required Boot size the size of the boot file in 512 octet blocks If you specify auto as the size the BOOTP server calculates the size of the file for each BOOTP request bs auto vm Required Vendor magic cookie selector the BOOTP server should always reply in a manner compliant with RFC 1048 You must enter rfc1048 for this tag so that the router can underst
103. ll individual Ethernet repeater ports for connection link status Therefore the 12 port ANH is aware of the connection between the base board and repeater module but is not aware of any connection between the repeater module and the Ethernet network If the repeater module interface state reports an operational status the 12 port ANH may continue to transmit information through the repeater module even though a physical Ethernet connection does not exist You can issue a boot command from the Diagnostic Monitor prompt and specify a local boot by using 1 as the volume name C 2 Implementation Notes e When at the diagnostic prompt you cannot view the contents of Flash memory Be extremely careful to remember the name of the configuration file when doing a named boot from the Diagnostic Monitor prompt Network Configuration Options This section describes several options for configuring an ANH in a network It provides general requirements and recommendations for network configurations using the ANH as well as examples of valid configurations The basic configuration uses a standalone ANH in a departmental network see the section Configuring a Single ANH To accommodate more stations you can connect daisy chain multiple ANH systems see the section Configuring Multiple Hubs Note The examples and illustrations in this section show the 8 port ANH but they apply to any Bay Networks ANH system Ensuring Etherne
104. lly 1 Powers on 2 Determines its IP address 3 Obtains a software kernel file and or configuration file by communicating with a configured BOOTP server on the IP network 4 Reboots using the newly transferred image Gets application and string files over the network as it needs them 6 Begins bridging and routing network traffic in accordance with the configuration file The following sections describe in more detail the key steps in this process obtaining an IP address and downloading the image and configuration files Getting an IP Address The AN or ANH gets its IP address from a central site upstream router Note The upstream router must have a circuit running Bay Networks Standard Point to Point Protocol PPP using HDLC or a Frame Relay permanent virtual circuit PVC Connecting BayStack AN and ANH Systems to a Network Obtaining the IP Address Manually Netboot and Directed Netboot For Netboot and Directed Netboot you configure the IP address manually Chapter 4 describes how to use Site Manager to configure Netboot interfaces Chapter 5 describes how to configure the netboot interfaces using the Technician Interface Obtaining the IP Address Automatically EZ Install During the EZ Install process the router obtains its address automatically as described below l 2 When you power on the AN ANH it runs a set of diagnostic tests The AN ANH sends a BOOTP request to the upstream router for an IP
105. m the Site Manager window which appears at Site Manager startup select Tools gt Configuration Manager gt Dynamic The Configuration Manager window appears displaying the real time router hardware and software configuration 2 From the Configuration Manager window select Platform gt Setup Repeater gt Group Parameters Figure 6 1 6 1 Connecting BayStack AN and ANH Systems to a Network eee Used Unused Description Connectors _ CONSOLE 8pt EHub 25 N11 DCM COM2 COM1 Figure 6 1 Selecting the Repeater Hub Group Parameters Window The Group Parameters window appears Figure 6 2 allowing you to reset the ANH or issue the self test command Renek Sel ftest Figure 6 2 Group Parameters Window 3 Edit the parameters you want to change using the parameter descriptions that follow as guidelines 4 When you are finished click on OK 6 2 Configuring AN and ANH Features The Configuration Manager executes the action or actions you indicated in the Group Parameters window and closes the window Repeater Port Group Parameter Descriptions Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Reset NO_RESET NO_RESET RESET Resets the repeater The Configuration Manager tests each repeater port and records to a log file whether a port passed diagnostics The reset does not affect the m
106. matically generates the kernel image and application files when you open the software image file By default the Image Builder stores these files in the HOME builder_dir rel lt rel gt an directory where lt rel gt is the current router software release for the AN ANH Troubleshooting Network Boot Problems For example Version 2 12 of the Site Manager s Image Builder tool stores the Version 8 12 files in the SHOME builder_dir rel812 an directory 2 Make sure that the AN ANH extracts the kernel image and all of the application and string files from the same software image If these files are from different software versions the AN ANH may fail to boot or operate properly 3 Make sure that the bootptab file is in the etc directory 4 Make sure that the bootptab file contains the following entries general hd SHOME builder_dir rel812 an bf krnl_an exe bs auto vm rfcl1048 Note that SHOME builder_dir rel812 an is the default location of the kernel and all application and string files 5 Make sure that the bootptab file contains a definition for the particular AN ANH that is failing to Netboot 6 Make sure that the configuration filename and path are correct in the bootptab file For example the following bootptab line indicates that the configuration file named AN_Bost cfg is in the rte3 cfg directory path T129 rte3 cfg AN_Bost cfg 7 Read the bootptab file carefully
107. n use Netboot if e The AN ANH has a communications link to an upstream router over an Ethernet HDLC or Frame Relay interface e You establish a local console or modem connection with the AN ANH e A directory ona BOOTP server contains the software image file krnl_an exe and a network configuration file customized for the AN ANH e You configure an IP address for the AN ANH boot interface Netboot takes longer than EZ Install but minimizes the cost of line usage and the saturation of the router s memory 2 2 Local Boot Selecting the Boot Configuration You can use Local Boot if the AN ANH has the an exe image on its local file system When you use Local Boot as the initial boot option the router boots a default generic configuration file You must then complete the Quick Start installation script to customize the default configuration file and save it locally Refer to the information about the Quick Start procedure and associated worksheets in Appendix B Recommendations Even if you choose EZ Install we strongly recommend that you connect a modem or a console to the router With a console connection you can issue commands to the router and display messages This is very useful if you have network problems after installing the router Booting the Router Routinely Netboot This section compares the Netboot Directed Netboot and Local Boot options to help you choose a boot configuration for routine st
108. nded from time to time shall apply for interoperability purposes Licensee must notify Bay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance Notwithstanding any foregoing terms to the contrary if licensee licenses the Bay Networks product Site Manager licensee may duplicate and install the Site Manager product as specified in the Documentation This right is granted solely as necessary for use of Site Manager on hardware installed with licensee s network This license will automatically terminate upon improper handling of Software such as by disclosure or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty 30 days after the receipt of written notice from Bay Networks Upon termination of this license licensee shall discontinue all use of the Software and return the Software and Documentation including all copies to Bay Networks Licensee s obligations under this license shall survive expiration or termination of this license Bay Networks Inc 4401 Great America Parkway Santa Clara CA 95054 8 Federal Street Billerica MA 01821 Contents About This Guide o e E oc EEE E E NEA are cer est wee E EE RE ort rier art ervencke yer Ne rrr E are rrr crete e XV Beire VOU BoJ crana RA E E A E E E S xvi Where to Find A
109. nnecting BayStack AN and ANH Systems to a Network SMDS Worksheet Requested Information Options Your Information Enter 10 digit individual address Enter the individual address assigned to you by your SMDS service provider Enter 10 digit group address Enter the group address assigned to you by your SMDS service provider Enter 10 digit arp address Enter the Address Resolution Protocol ARP address assigned to you by your SMDS service provider Running the Quick Start Script You run the Quick Start script as part of the Local Boot process Begin Local Boot as follows 1 At the Technician Interface 1ogin prompt type Manager and press the Return key to log in Be sure to have the completed worksheets with you Type bconfig config local and press the Return key to configure the router to use the local config file when booting For information about the bconfig command see Configuring the Router Boot Source in Chapter 5 Reboot the AN ANH type boot and press the Return key The Technician Interface login prompt appears Log in to the AN ANH Technician Interface The Technician Interface mounts the local file system and displays a prompt indicating the present working directory Type run install bat and press the return key to begin the Quick Start procedure B 12 Local Boot The Quick Start Procedure 6 Follow the script online using your worksheets for responses
110. nnecting to a Series 5 router that uses DCE DTE addressing use the SAME local address value Frame Relay Worksheet Requested Information Options Your Information Enter Management type 3 1 DLCMI None 2 Rev 1 LMI 3 ANSI T1 617D 4 CCITT Annex A 5 LMI Switch 6 Annex D Switch 7 Annex A Switch Enter addressing type 4 1 ADDR Q 921 2 ADDR Q 922 MARCH 90 3 ADDR Q 922 NOVEMBER 90 4 ADDR Q 922 Enter address field length 2 Two Bytes 3 Three Bytes 4 Four Bytes Enter DLC number 30 Enter the Permanent Virtual Channel PVC number For DLCMI None LMI Switch Annex D Switch and Annex A Switch only Note The valid range for the DLCI number is between 16 and 1007 B 9 Connecting BayStack AN and ANH Systems to a Network PPP Standard Worksheet Requested Information Options Your Information Enter Remote IP address in dotted decimal notation Enter the IP address of the peer connection Do you wish to turn on the PPP echo y es function y n n n o Enable PAP Password Authentication y es Protocol y n n n o Note If you answer y es the router requests a PAP ID and password for this interface If you answer n o the router asks whether you want to enable CHAP Enable CHAP Challenge Handshake Authentication Protocol y n n Note If you answer y es the router requests a CHAP secret for th
111. nnection to the ISDN network as opposed to connecting via a terminal adapter On some ANH models the ISDN BRI disables the COM2 port e A third synchronous interface e A second nonrepeating Ethernet interface e An N11 Ethernet Data Collection Module DCM for gathering RMON statistics 8 port ANH only the 12 port ANH does not support the DCM Note When using an NII DCM the ANH requires Router Software Version 9 00 or higher and Site Manager Software Version 3 00 or higher See Table 1 2 for a summary of ANH hardware and the corresponding Site Manager module names for creating configuration files Table 1 2 BayStack ANH Configurations Base Interface Model Configuration Added Components Site Manager Name 8 port ANH 1 Ethernet none 8pt EHub 2S repeater Order Nos XCVA1 and 1 Ethernet DCM 8pt EHub 2S N11 DCM AE1101010 2 synchronous 1 third synchronous interface COM3 8pt EHub 3S AE1101011 COM1 and 4 second Ethernet interface XCVR2 8pt EHub E 2S AE1101012 COM2 1 ISDN BRI with Floating B channel 8pt EHub 2S BRI 1 third synchronous interface and 8pt EHub 3S N11 DCM 1 Ethernet DCM 1 second Ethernet interface and 8pt EHub E 2S N11 DCM 1 Ethernet DCM 1 ISDN BRI 1 Ethernet DCM 8pt EHub 2S BRI N11 DCM 12 port ANH 1 Ethernet none 12Pt EHub 2S repeater Order Nos XCVA1 and 1 ISDN BRI replaces COM2 12Pt EHub 2S BRI AE1101014 2 synchronous 1 third synchronous interfa
112. nng an AUI POr cacomcuscoseniiimccniannnadesiaaitianotatieniieert C 7 Connecting the AUI Port to a Fiber Optic Backbone cceeeeeeeeseeeeeeeees C 8 Connecting the AUI Port to a Coaxial Backbone ccecccceeesteeeeeesstteeeeeeees C 9 Index Figure 1 1 Figure 1 2 Figure 1 3 Figure 1 4 Figure 1 5 Figure 1 6 Figure 3 1 Figure 4 1 Figure 4 2 Figure 4 3 Figure 4 4 Figure 4 5 Figure 4 6 Figure 4 7 Figure 4 8 Figure 4 9 Figure 4 10 Figure 6 1 Figure 6 2 Figure 6 3 Figure 6 4 Figure 6 5 Figure 6 6 Figure 6 7 Figure 6 8 Figure 6 9 Figures Getting an IP Address from a Bay Networks Standard Circuit or a Frame Relay PVC in Direct Access Mode ccceeees 1 14 Getting an Address from a PVC in Group Access Mode e0 1 12 Getting the Pathnames of the Kernel and Configuration Files 1 13 Getting Te Coniguraton FNS icsse 1 14 Ge PUI CI UTNE Karnal carinii RA ARR 1 15 Establishing an IP Network Interface eR EE eased 1 16 Sampie DOCTOIAD FIE siani aa aina 3 7 Edit Netboot Global Parameters Window sssessssssssseessesssessssessressrerssnns 4 4 INGIDOGE Interiacos Window ceainarii iiae nS 4 8 AN ANH Netboot Interface Window cccccccsccccessseeeeeeesssteeeeeseseeeeeess 4 9 Netboot linteriaces Window secrrnusriiadasii aaia 4 10 Enabling BOOTP if a Sample NEWOrK ssciiiniciesrccissenssinrns 4 14 BOOTP Relay Agent Interface Table
113. nts a few important notes you could have missed earlier in this guide and guidelines for planning ANH network configurations This section contains a few hints for setting up an AN or ANH We recommend that you first install an AN ANH in the same site as your BOOTP server Site Manager workstation and intermediate Bay Networks routers to test the software image configuration file and routing path This test provides you with the startup and troubleshooting experience you need to perform these tasks on routers at remote sites After you perform the test move the test router to the remote location you want modify the configuration file for that router and set up the new paths After you build and test the remote router configuration file make copies of it on the Site Manager workstation Then modify the copies for each AN ANH in your network rather than starting over To avoid mix ups make sure the filename you assign to each configuration file is unique and meaningful for each router It may be easier to isolate BOOTP and TFTP configuration errors on the network if you upgrade all Bay Networks routers in the paths between the routers and the BOOTP server to Version 7 80 or higher before you set up the paths C 1 Connecting BayStack AN and ANH Systems to a Network Notes If you are using EZ Install over Frame Relay to boot an AN ANH you can have up to 20 PVCs for a single Frame Relay interface on the upstream router If you
114. nvolved with a synchronous configuration When you configure a LAN interface base your decisions on the information provided with each install bat prompt B 1 Connecting BayStack AN and ANH Systems to a Network Using the Quick Start Worksheets This appendix includes a series of worksheets to help you organize the network information you need for your specific configuration and answer Quick Start prompts The worksheets contain the options for each prompt and provide space for you to record the options you select If you are not configuring the AN ANH yourself fill out the worksheets for a person at the AN ANH site and relay the worksheet information Written for a person at the router site the manuals Installing and Starting AN Routers and Installing and Starting 8 Port ANH Systems include identical Quick Start worksheets and include instructions for completing the Quick Start procedure Prepare for Quick Start as follows 1 Fill out the Global Information Worksheet completely This worksheet lists options common to all synchronous interface configurations 2 After you record your protocol selections on the Global Information Worksheet fill out one Router Protocol worksheet This worksheet lists specific options for RIP OSPF or Static Route configurations For example if you select RIP as your routing protocol you need only fill out the worksheet pertaining to RIP 3 Fill out one Wide Area Protocol worksheet This w
115. ocal file system Caution Compacting the file system on a Flash card can take up to 15 minutes When you compact a router s file system always let compaction complete before you reset the router A 16 Appendix B Local Boot The Quick Start Procedure If you have read Chapter 2 and want to use the Local Boot process to start an AN or ANH for the first time use the information and worksheets in this appendix to gather the network information required to complete the Quick Start procedure Note The worksheets in this appendix apply only to AN and ANH models See Quick Starting Routers for all other Bay Networks routers The last section in this appendix Running the Quick Start Script provides information about the Quick Start procedure What Is Quick Start The Quick Start procedure is the initial configuration that starts a locally booted router running on the network The procedure enables Internet Protocol IP so that the router can connect to Site Manager Quick Starting the router consists of running the install bat script and entering information at the Quick Start prompts The router automatically selects options for some prompts and you can accept default values for many of the other prompts Note The install bat script allows for many possible configurations Since typical remote access uses a synchronous interface over a wide area connection the following Quick Start worksheets provide only the options i
116. on demand service This automated system contains libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products The system can return a fax copy to the caller or to a third party within minutes of being accessed World Wide Web The World Wide Web WWW is a global information system for file distribution and online document viewing via the Internet You need a direct connection to the Internet and a Web Browser such as Mosaic or Netscape xviii About This Guide Bay Networks maintains a WWW Home Page that you can access at http www baynetworks com One of the menu items on the Home Page is the Customer Support Web Server which offers technical documents software agents and an E mail capability for communicating with our technical support engineers How to Get Help For additional information or advice contact the Bay Networks Technical Response Center in your area United States Valbonne France Sydney Australia Tokyo Japan Conventions angle brackets lt gt arrow character gt bold text brackets italic text quotation marks screen text 1 800 2LAN WAN 33 92 966 968 61 2 903 5800 81 3 328 005 Indicate that you choose the text to enter based on the description inside the brackets Do not type the brackets when entering the command Example if command syntax is ping lt ip_address gt you enter ping 192 32 10
117. ontrol Protocol Internet Protocol Telecommunication Network Trivial File Transfer Protocol Trivial File Transfer Protocol Daemon User Datagram Protocol unshielded twisted pair xxi Chapter 1 Hardware and Software Overview The Bay Networks BayStack Access Node family of routers connects multiprotocol workgroups to corporate backbone networks This chapter includes the following information about the Access Node e Hardware connections e Software support e Boot configuration options e Boot process Access Node Hardware AN Models Bay Networks offers a series of Access Node products including Access Node Hub ANH systems AN and ANH models provide a variety of Ethernet Token Ring and synchronous network interfaces Each also includes a service port labeled CONSOLE with DB 9 connector for local or remote access Tables 1 2 and 1 2 summarize the AN and ANH base and optional hardware and provide corresponding module names for creating Site Manager configuration files The AN is available in the following basic configurations e One Ethernet AUI and two synchronous interfaces e One Token Ring media access unit MAU and two synchronous interfaces e One Ethernet one Token Ring and two synchronous interfaces Connecting BayStack AN and ANH Systems to a Network As optional upgrades the AN also supports e A third synchronous interface e AnISDN BRI interface for direct without terminal adapter connection to
118. ooting Boot Image Pathname None A valid image file pathname When the parameter Boot Image From Network is set to Enable this parameter specifies the absolute pathname of the boot image file on the TFTP server Use this parameter only when configuring Directed Netboot Make sure the file you specify is the valid image file on the TFTP server 1 3 6 1 4 1 18 3 3 2 10 1 4 path to the active image on the remote server When you boot an AN ANH Note When you netboot a router the active image parameter shows the full gt locally the name of the active image wfHwEntry wfHwActiveImageName appears in the form lt volume gt lt image name gt Parameter Default Options Function Instructions MIB Object ID Boot Config Pathname None A valid configuration file pathname When the parameter Boot Config From Network is set to Enable this parameter specifies the absolute pathname of the boot configuration file on the TFTP server Use this parameter only when configuring Directed Netboot Make sure the file you specify is the valid configuration file on the TFTP server 1 3 6 1 4 1 18 3 3 2 10 1 5 4 7 Connecting BayStack AN and ANH Systems to a Network Configuring a Netboot or Directed Netboot Interface When you enable Netboot or Directed Netboot you must configure at least one AN ANH circuit as a Netboot interface If you are using EZ Install you do not need to configure Netboot interfaces Follow th
119. option 2 9 starting B 12 summary 1 8 local file system mounting B 12 log command A 8 Matrix group 6 10 6 27 memory allocation hints C 2 preventing saturation 1 8 2 4 memory use for RMON 6 23 to 6 29 MIB router support 1 5 minimizing cost of line usage 1 8 2 4 modem port 1 1 N N11 DCM option See DCM naming configuration files 4 2 Netboot 1 13 to 1 15 adding an interface for 4 8 to 4 13 configuring 3 1 5 1 configuring interfaces for 4 1 5 2 definition 1 6 ifconfig command 5 2 requirements for 1 8 summary 1 8 Netboot cont troubleshooting A 3 to A 5 Index 5 Netboot Global parameters Boot Config From Network 4 6 Boot Config Pathname 4 7 Boot Image From Network 4 5 Boot Image Pathname 4 7 Boot Server Address 4 6 editing 4 4 to 4 7 Netboot Interface parameters Connector 4 11 Connector IP Address 4 11 Connector Next Hop 4 12 Connector Protocol Mask 4 12 Connector State 4 13 Connector Subnet Mask 4 12 Slot Number 4 11 netstat command 3 11 A 13 network analyzer A 9 next hop router configuring 4 19 not receiving BOOTP requests A 2 A 3 not sending BOOTP responses A 2 A 4 O operating systems 3 2 options for getting startup files application files 1 6 Directed Netboot 1 8 EZ Install 1 7 Local Boot 1 8 Netboot 1 8 string files 1 6 options for getting the IP address Directed Netboot 1 10 EZ Install 1 10 Local Boot 1 15 2 3 Netboot 1
120. or ANH boots locally it reads the kernel file application files and string files that are embedded within a local software image file an exe When you use Local Boot as the initial boot option you boot a default generic configuration file You must then complete the Quick Start installation script to customize the default configuration file Connecting BayStack AN and ANH Systems to a Network To run the Quick Start script you must establish an IP network interface between the AN ANH and a Site Manager management workstation Figure 1 6 To make this connection you use a Technician Interface command IP address 192 32 10 12 Corporate IP network Site Manager workstation ASCII console or PC AN or ANH router Console port Ethernet port IP address 192 32 156 7 Subnet mask 255 255 255 0 Figure 1 6 Establishing an IP Network Interface Configuring the Initial IP Interface Appendix B briefly describes the Quick Start procedure provides worksheets for preparing to run the procedure for an AN ANH and explains how to begin the Quick Start script Chapter 2 Selecting the Boot Configuration This chapter provides information to help you select the boot method for both the initial startup of the AN ANH and for day to day startup operations Note To learn about the boot process and startup options see Chapter 1 First refer to one of the following sections for help selecting
121. ork parameter 4 5 Boot Image Pathname parameter 4 7 Boot Server Address parameter 4 6 BOOTP 3 1 to 3 12 analyzing packets on a router A 8 client interface table 1 12 4 19 to 4 21 example 1 9 to 1 14 failure of A 2 pass through enabling 4 14 relay agent forwarding table 4 15 to 4 18 relay enabling 4 14 Site Manager support C 2 socket 3 2 testing C 1 BOOTP server analyzing packets A 9 debugging A 11 displaying IP routes A 13 location of files 4 2 not receiving BOOTP requests A 4 responses failure of A 2 router software version C 1 troubleshooting A 4 A 12 BOOTP addresses window 4 17 BOOTPD copying 3 2 debugger tool A 11 linking to TFTPD 3 9 send and receive sockets 3 2 bootpd dmp file A 11 bootptab file 3 3 to 3 7 debugging A 11 symbols in 3 5 syntax 3 4 troubleshooting A 12 broadcast address 1 11 bs boot size tag in bootptab 3 6 C clocking synchronous interface 5 4 COM ports See synchronous interfaces commands bconfig 5 2 to 5 3 A 2 for Local Boot B 12 boot Local Boot B 12 getcfg A 2 A 10 ifconfig 5 4 to 5 7 run install bat B 12 compacting files A 16 comparing startup options initial boot 2 1 routine boot 2 3 compliance Ethernet C 3 CompuServe Bay Networks forum on xvii config file using local B 12 configuration file 4 2 corrupted A 15 creating 4 2 customized 1 8 1 15 2 3 getting from a BOOTP server 1 13 to 1 15 hint for creat
122. orksheet lists specific options for Bay Networks proprietary Point to Point Protocol PPP Frame Relay Standard PPP and Switched Multimegabit Data Service SMDS configurations For example if you select Frame Relay as your wide area protocol you need only fill out the Frame Relay worksheet 4 Run install bat as described Running the Quick Start Script later in this chapter Or a remote site operator runs the install bat script as described in the hardware Installing and Starting guide 5 Once the ANH has an initial connection to the network use the guide Configuring Routers to configure the AN ANH using Site Manager B 2 Local Boot The Quick Start Procedure Global Information Worksheet This section contains the prompts and possible options relating to all AN synchronous configurations Write your selection in the Your Response column Global Information Worksheet Step Requested Information Options Your Response 1 Specify the slot number where the Link Because the AN is not a Link None Module resides Module the router bypasses this step and automatically accepts a default slot of 1 2 Specify the Link Module and network The AN automatically provides a interface information for the initial IP representative letter code connection to Site Manager depending on the type of AN you have The network interface options are Ethernet Token Ring Synchronous Select the
123. ot to reach the router 8 Click on Done to exit the Netboot Interfaces window 4 10 Configuring Network Booting Netboot Interface Parameters Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Slot Number 1 1 Specifies the physical slot in which the hardware module is installed Be sure that number 1 appears in the Slot Number box ANs and ANHs have only one slot Not Applicable Connector None COMI COM2 COM3 XCVR1 XCVR2 Identifies the connector configured as a Netboot interface Enter the connector name for the Netboot interface Enter COM1 COM2 or COM3 if you want to use Netboot over a synchronous interface Enter XCVR1 or XCVR2 if you want to use Netboot over an Ethernet interface Note that COM3 and XCVR2 are valid only with an installed interface upgrade Not Applicable Connector IP Address None Any valid IP address Specifies the IP address of this interface Enter the IP address of this interface in dotted decimal notation 1 3 6 1 4 1 18 3 3 2 10 3 1 4 Connecting BayStack AN and ANH Systems to a Network Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Options
124. otp server bootpc 68 udp bootp client 3 2 Setting Up a UNIX Boot Server Setting Up BOOTPD to Run Configure your workstation to run the BOOTPD program when it receives a BOOTP request packet as follows 1 2 As root use a text editor to open the etc inetd conf file Make sure that no other line in the file begins with bootps If there is such a line your workstation is already configured as a BOOTP server Comment out this line by entering a pound sign at the beginning of the line so that the server will use the BOOTPD program that you specify in the next step Insert the following line anywhere in the file to configure your workstation as a BOOTP server bootps dgram udp wait root etc bootpd bootpd Save and exit the file Setting Up BOOTPD to Respond to Routers When the operating system receives a BOOTP packet it starts up BOOTPD The BOOTPD software matches the source IP address of the packet to an IP address in its BOOTP table bootptab file to determine the pathnames to configuration and boot image files Note The bootptab file can include the same boot image pathname for all booting routers or a different boot image for each IP address Entries in bootptab also include optional parameter tags Bay Networks supplies a sample bootptab file that Site Manager installs automatically in the usr wf config directory Use a copy of this sample file if you do not already have a bootptab file
125. ou can determine the appropriate syntax for these commands and provide the person at the router site with the exact command lines to use Configuring the Router Boot Source To use Netboot you use the bconfig command to specify that the AN ANH configuration file or software image resides on the network To use Directed Netboot you use the bconfig command to specify the IP address of the server and the full pathname to the software image and configuration file bconfig Command Format To configure an interface for Netboot use the following format for the bconfig command bconfig d image config network To configure an interface for Directed Netboot use the following format bconfig image config network lt TFTP host gt lt TFTP pathname gt You must use the bconfig command twice once to specify the location of the software image and again to specify the location of the configuration file Refer to Table 5 1 for a complete description of the beonfig command Table 5 1 bconfig Command Settings Option Description image Indicates the router s software image config Indicates the router s configuration file network Indicates that the specified file image or configuration resides on a remote file system lt TFTP host gt Specifies the IP address of the TFTP server If both the software image and configuration file are on the network both files must reside on the same host lt TFTP Specifies t
126. ou want See Managing Routers and BNX Platforms Directed Netboot Completing the Directed Netboot option requires the following steps 1 You use the Configuration Manager in local mode to create a complete configuration file for the router See Chapter 4 and Configuring Routers You set up the network to support TFTP See Chapter 3 You ensure that there is a network connection from a synchronous or Ethernet interface on the AN ANH to the upstream router Note Ifthe AN ANH will connect to the upstream router using a Frame Relay circuit be sure the upstream router is running Router Software Version 8 00 or higher 4 The person at the AN ANH site establishes a Technician Interface session or you establish a session via modem See the hardware Installing and Starting guide for the AN or ANH The person at the AN ANH console issues bconfig and ifconfig commands to configure a synchronous or Ethernet interface for Directed Netboot See Chapter 5 if you are using a remote Technician Interface session or if at the router site the hardware Installing and Starting guide for the AN or ANH You install the netboot exe file in the BOOTP server s file system and make sure the image and application files reside in the specified directory See Chapter 3 2 8 Local Boot de Selecting the Boot Configuration The person at the router site boots the router See the hardware Installing and Starting guide for t
127. outers if you need instructions BOOTP Server Not Sending BOOTP Responses If the BOOTP server is receiving BOOTP requests but failing to respond to them do the following 1 Follow the instructions in the section Displaying the BOOTP Server s IP Routes later in this appendix Follow the instructions in the section Debugging the BOOTP Server later in this appendix Make sure that the etc inetd conf file contains no more than one bootps entry A 4 5 Troubleshooting Network Boot Problems If there is more than one entry comment out the invalid entry The valid entry should be bootps dgram udp wait root etc bootpd bootpd Make sure that the tftp dgram entry in the etc inetd conf file is correct for your system Refer to Setting Up a TFTP Server in Chapter 3 Refer to Verifying the BOOTP Server Setup later in this appendix Router Fails to Perform Directed Netboot If the AN ANH fails to perform Directed Netboot do the following 1 3 Make sure that the interface that connects the AN ANH to the TFTP file server is configured with an IP address Make sure that all necessary files are in fact residing on the TFTP file server Make sure the boot file is krn _an exe not an exe Contact your local Bay Networks Technical Response Center if you perform the instructions in these sections but still cannot find and correct the problem Router Netboots but Fails to Load Applicat
128. r to obtain its image from the network rather than locally To use Image Builder perform these steps 1 On the Site Manager workstation open the software image file in the Image Builder Keep the following in mind e Be sure to select the correct image an exe If you select an image for another router type you cannot generate the correct files e If you configure the router to obtain its image from the network it cannot Netboot the image until the kernel image is available on the BOOTP server e Make sure that you extract the kernel image and all of the application exe files and string str files in the router directory The files must be from the same software image file whose components were created from the same version of software If these files are from different software versions the router may fail to boot or may not operate properly Refer to Modifying Software Images for Routers for more instructions After you open the image file the Image Builder automatically generates the kernel image application files and AN ANH string files By default the Image Builder stores these files in SHOME builder_dir rel lt rel gt an where lt re l gt is the current router software release for the router For example Version 2 12 of the Site Manager Image Builder tool stores Version 8 12 files for an AN or ANH in the HOMEZ builder_dir rel812 an directory For additional instructions on how to use the Image Build
129. ration e Site Manager software a platform independent SNMP based router management and configuration application with a graphical user interface You run Site Manager at a workstation that is connected along with the router to an IP network Connecting BayStack AN and ANH Systems to a Network e Optivity Internetwork a comprehensive SNMP based network management application for administering and troubleshooting large complex networks The Optivity Internetwork package includes Site Manager PathMan and RouterMan software Router Software Before it can operate the AN and ANH hardware must boot a software image The software image is a group of executable files that operate the protocols the network requires The AN ANH software image called an exe comprises the following executable startup files e lt A krnil_an exe file that contains the operating system kernel e Application files executable files needed to perform the functions specified in the configuration file All application files have exe filename extensions For example the router needs an ipx exe executable file to run IPX e String files compressed ASCII files needed when you use the Technician Interface to display the event log or Management Information Base MIB object names Groups of string files remain in compressed format within the an exe file until needed To bridge and route traffic the AN ANH also needs a configuration file tha
130. resulting software available for use by any third party Neither title nor ownership to Software passes to licensee Licensee shall not provide or otherwise make available any Software in whole or in part in any form to any third party Third parties do not include consultants subcontractors or agents of licensee who have licensee s permission to use the Software at licensee s facility and who have agreed in writing to use the Software only in accordance with the restrictions of this license Third party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee Licensee shall not remove or obscure any copyright patent trademark trade secret or similar intellectual property or restricted rights notice within or affixed to any Software and shall reproduce and affix such notice on any backup copy of Software or copies of software resulting from modification or combination performed by licensee as permitted by this license Bay Networks Inc 4401 Great America Parkway Santa Clara CA 95054 8 Federal Street Billerica MA 01821 Bay Networks Software License continued 10 11 12 Licensee shall not reverse assemble reverse compile or in any way reverse engineer the Software Note For licensees in the European Community the Software Directive dated 14 May 1991 as may be ame
131. ring Quick Start B 14 TRIP adding an HP 9000 user 3 10 default volume B 4 example 1 14 1 15 interruption A 15 transferring image C 2 TFTPD linking to BOOTPD 3 9 setting up 3 8 to 3 12 tg variable in bootptab file 3 4 Timeout Secs parameter 4 16 Token Ring interfaces 1 1 limitation C 2 troubleshooting A 1 to A 14 U UDP 3 2 underscore symbol in bootptab file 3 5 UNIX workstation 3 1 unshielded twisted pair 1 3 upgrading image A 15 upstream router 1 9 4 19 not receiving BOOTP requests A 2 A 3 not sending BOOTP responses A 2 A 4 UTP interface 1 3 V vendor magic field 3 6 A 12 versions of software 2 6 2 7 4 3 C 2 vm vendor magic tag in bootptab 3 6 volume specifying A 15 W wfBootpRelayIntfEntry A 14 wfCSMACDEntry A 7 wfDrivers A 6 wfSyncEntry A 7 World Wide Web Bay Networks Home Page on xviii Index 8
132. rt and information on a nonpriority basis through the following automated systems CompuServe Bay Networks maintains an active forum on CompuServe All you need to join us online is a computer a modem and a CompuServe account We also recommend using the CompuServe Information Manager software available from CompuServe xvii Connecting BayStack AN and ANH Systems to a Network InfoFACTS The Bay Networks forum contains libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products Software agents and patches are available and the message boards are monitored by technical staff and can be a source for problem solving and shared experiences Customers and resellers holding Bay Networks service contracts can visit the special libraries to acquire advanced levels of support documentation and software To open an account and receive a local dial up number call CompuServe at 1 800 524 3388 and ask for Representative No 591 e Inthe United Kingdom call Freephone 0800 289378 e In Germany call 0130 37 32 e In Europe except for the United Kingdom and Germany call 44 272 760681 e Outside the U S Canada and Europe call 614 529 1349 and ask for Representative No 591 or consult your listings for an office near you Once you are online you can reach our forum by typing the command GO BAYNETWORKS at any prompt InfoFACTS is the Bay Networks free 24 hour fax
133. s Manager tool or the Technician Interface get command to retrieve this information Refer to Managing Routers for additional information about Quick Get Quick Get Instructions 1 Select the following path wfApplication wfInternet wfBootpGroup wfBootpRelayAgentGroup wfBootpRelayIntfTable 2 To display the number of packets forwarded select wfBootpRelayIntfRequests 3 To display the number of packets dropped select wfBootpRelayInt fHopsDrops Technician Interface Instructions Enter the following command to display information that may help you determine if and why a device is dropping packets where lt P_address gt is the address of the interface receiving the packets get wfBootpRelaylntfEntry lt P_address gt A 14 Troubleshooting Network Boot Problems Maintaining the Router Software The AN ANH file system resides on the Flash memory card This part of the router is not user serviceable You use Technician Interface commands to maintain the local file system on the AN ANH Flash card See Using Technician Interface Software and Using Technician Interface Scripts for information Caution Be very careful when you use the format command with the router This command erases all files on the local Flash card and the router will not be able to local boot an image or configuration file until you replace the files You can avoid this situation by partitioning the Flash card media See Using Te
134. st create a Host configuration Each HostTopN configuration requires 164 bytes The HostTopN data requires 10 bytes of memory per host address the DCM detects on a segment You calculate the total memory in bytes you need for the HostTopN data as follows 10 Value for the RMON Max Host parameter Refer to the previous section for information on setting the RMON Max Host parameter When you enable the DCM the default setting Enabled for the RMON Default Matrix parameter causes the DCM to set up a Matrix configuration To prevent creation of a Matrix configuration set the RMON Default Matrix parameter to Disabled before you enable the DCM as described in the Activating DCM section Some RMON network management applications expect the DCM to set up a Matrix configuration while others set up their own configurations NOTE The RMON agent allows you to create only one Matrix configuration Be sure to set the RMON Default Matrix parameter according to the expectations of the RMON network management application The Matrix configuration requires 212 bytes The Matrix data requires approximately 178 bytes of memory per source destination pair the DCM detects on a segment 6 27 Connecting BayStack AN and ANH Systems to a Network Filter and Capture Groups Caution The memory you need for a Filter Capture configuration and for storing captured packets can easily exhaust all the available memory on a DCM partic
135. stname etc gt request from IP addr 192 16 24 12 The UNIX hostname the path etc of the bootptab file and the IP address of the AN ANH found 192 16 24 12 AN Boston The IP address 192 16 24 12 mapped to the hostname AN Boston in the bootptab file boot file2 SHOME builder_dir rel812 an krnl_an exe The pathname of the kernel file as specified in the bootptab file couldn t access SHOME builder_dir rel812 an krnl_an exe AN Boston Disregard this message The BOOTP server tries to access the host both by its name and by its IP address The couldn t access message means that the server tried to access a host named AN Boston but failed because the AN is not named The attempt to access the AN by its IP address succeeds as you can infer from the last message vendor magic field is 99 130 83 99 Disregard this message sending RFC1048 style reply The BOOTP server is sending a BOOTP response in compliance with RFC 1048 Verifying the BOOTP Server Setup Refer to these instructions if the BOOTP server is receiving BOOTP requests but failing to respond or failing to forward the kernel configuration application or string files Verify the BOOTP server setup as follows 1 Make sure that the kernel image and all of the application exe files are in the same directory You can place these files in any directory you want The Image Builder auto
136. t is the connector number get wfSyncEntry 1 lt connector gt Make sure that external clocking is set If the router is Netbooting with an Ethernet connector enter the following command to display the information about the connector where lt connector gt is the connector number get wfCSMACDEntry 1 lt connector gt Identifying Remote Connectivity Problems The sections that follow provide guidelines for isolating a router addressing problem or a Netboot problem Refer to the appropriate section Displaying Messages from the AN ANH Console Displaying Statistics and Error Messages Guidelines for Using Packet Capture Guidelines for Using a LAN Protocol Analyzer Displaying Messages from the AN ANH Console If you cannot connect to the AN ANH using Site Manager we recommend that you connect the AN ANH to a modem or console If you cable the AN ANH to a modem you can dial in and connect to the AN ANH remotely This setup provides the same capabilities as an on site console connection Modem communications however are slower A 7 Connecting BayStack AN and ANH Systems to a Network Viewing an AN ANH error message and entering commands through a modem connection may simplify troubleshooting if you are not at the AN ANH site As an alternative you can ask the person at the AN ANH site to read the console messages to you and then you can enter the commands you want Displaying Statistics and Error Messages Use the
137. t Network Compliance Before configuring any network hardware use the following rules to assess your network for compliance with Ethernet operating standards Using these rules allows you to avoid performing the detailed calculations specified in the IEEE 802 3 specifications The network is compliant when it meets all of the following requirements e No path through the network contains more than five repeaters e No more than 1024 stations are connected not counting repeaters e The entire Ethernet network consists of only IEEE 802 3 components using only AUI 10Base T FOIRL 10Base F 10Base 5 or 10Base 2 cables e Fiber optic link attenuation limits are met Refer to the attenuation specifications for the fiber optic cable connectors and transceiver or device transmitter receiver ports that you are using e No link is longer than the IEEE 802 3 maximums given in Table C 1 C 3 Connecting BayStack AN and ANH Systems to a Network Table C 1 IEEE 802 3 Maximum Segment Links Segment Type Maximum Segment Length m 10Base 5 coaxial 500 10Base 2 coaxial 185 10Base T 100 10Base FB 2000 10Base FL 2000 FOIRL 1000 AUI drop 50 2 m allowance 48 m excess Network paths composed of three or four repeaters must also comply with the following additional restrictions Network Path Containing Three Repeaters In the longest path containing three repeaters no transmit end or r
138. t is tailored to your network A configuration file is a binary system file that contains hardware and software configuration data The default configuration file is named config Boot Configuration Options This section summarizes your options for getting the AN ANH software image file and configuration files An AN ANH boots using one of four configured startup options The differences among the four AN ANH startup options are based on whether the router retrieves boot and configuration files over the network or from local memory Getting a software image or configuration file over the network is called Netbooting Getting a file from the file system stored in local Flash memory is called Local booting 1 6 Hardware and Software Overview To initially start up the AN or ANH you use one of these boot configuration options e EZ Install the default e Netboot e Local Boot To start up the AN ANH after the initial configuration you use one of these options e Netboot e Directed Netboot Local Boot Table 1 3 summarizes the four startup options The next section The Boot Process describes how each option works Table 1 3 Summary of Boot Options Source for Boot Software Source for Option Image Config File Description and Requirements EZ Install Local Network The default option The AN ANH boots from a software image in local memory then transmits a request for its IP Flash Synchronous
139. ted Netboot only Netboot and Directed Netboot Parameters Parameter Boot Image From Network Default Disable Options Enable Disable Function Enables or disables retrieval of the software image from the BOOTP server the next time the router starts up Instructions Set to Disable if you want to boot using the image in the router s local file system This setting reduces the time it takes to boot the router and eliminates using network resources to obtain the image Set to Enable if You want the router to obtain the image from a BOOTP server and you have already set up the network to support BOOTP service You are upgrading the image on a number of routers The routers can then boot using a single image on the BOOTP server You must ensure that the directory name in the bootptab file matches the location of the upgraded image before you boot the routers MIB Object ID 1 3 6 1 4 1 18 3 3 2 10 1 1 Note As an alternative to enabling the Boot Image From Network parameter you can use the Router Files Manager to transfer an upgraded image to the AN ANEH To do this delete the old software image file compact the file system and copy the upgraded image file to the AN ANH Use the Router Files Manager to confirm that the upgraded image on the router is the same size as that on the Site Manager workstation This verifies that the file transfer was successful Refer to Managing Routers for more information on the Router
140. terface You can use Technician Interface commands to e Enable disable and reboot the DCM board enable disable dcmmw scripts e Display or modify DCMMW configuration parameters set get commands e Download a new DCM software image demload script Caution Avoid running scripts that continually issue Technician Interface commands while you are running another RMON network management application This combination can cause the SNMP agent to fill the system buffers with RMON data leading to a system restart For more information about using the Technician Interface to access the DCM MIB objects refer to Using Technician Interface Software and Using Technician Interface Scripts Changing DCM Configuration Parameters Modifying DCM or RMON parameters by issuing set and commit commands with the MIB object ID is equivalent to modifying parameters using Site Manager To change DCM configuration parameters be sure to set the value of wfDCMmw wfDCMmwCfgMode 0 to DCMMW_CFG_LOAD_SHMEM before changing other object values After you change any DCM object values always reboot by enabling then disabling the DCM board to initialize the change For example issue the following commands to change the maximum Host configuration set wfDCMmw wfDCMmwRMONMaxHost 0 1200 commit disable dcmmw base enable dcmmw base To use a configuration change in subsequent boots be sure the wfDCMmwWriteConfigInfo parameter is set to DCMMW_CFG_WRITE so the DCM s
141. terfaces for network booting You can do this using a Site Manager remote connection as described in Chapter 4 or at the AN ANH local console using Technician Interface commands This chapter describes how to use the e ifconfig command to configure the AN ANH s initial IP interface to the network bconfig command to specify the location and name of a software image and configuration file To Configure This Boot Method Complete These Sections Netboot or Directed Netboot over a Configuring the Router Boot Source and synchronous interface Configuring an IP Synchronous Interface for Network Booting Netboot or Directed Netboot over an Configuring the Router Boot Source and Ethernet interface Configuring an Ethernet Interface for Network Booting Working with a Person at the AN ANH Site Written for a person at the AN ANH site the guides Installing and Starting BayStack AN Routers and Installing and Starting 8 Port BayStack ANH Systems provide instructions for setting up the router for each of the boot options These instructions assume that a network administrator provides the person at the AN ANH site with the appropriate ifconfig and bconfig commands 5 1 Connecting BayStack AN and ANH Systems to a Network This chapter provides instructions for using the ifconfig and bconfig commands to configure Netboot and Directed Netboot If you are not configuring the AN ANH yourself y
142. the AUI interface from the 8 port ANH router to the repeater To disable the connection disable the Ethernet circuit on port nine 6 5 Connecting BayStack AN and ANH Systems to a Network Port Status Figure 6 5 12 Port ANH Port Status Window Note The thirteenth port is the Ethernet connection from the router base board to the repeater module You disable the repeater by disabling Port 13 3 To change the status of a port click on Enabled or Disabled to the right of the port number 4 When you are finished click on OK to exit the window and save your changes 6 6 Configuring AN and ANH Features Configuring an N11 Data Collection Module This section describes how to configure the N11 Data Collection Module DCM as an Ethernet remote monitoring RMON device It provides e Overviews of the N11 DCM and RMON e Instructions for enabling the N11 DCM e Instructions for managing the N11 DCM using Site Manager e Instructions for managing the N11 DCM using the Technician Interface e RMON implementation notes for operating the N11 DCM Note This section applies only if you have an optional N11 Ethernet Data Collection Module DCM installed in a BayStack AN or 8 port ANH About the N11 DCM The N11 DCM physically connects to the AN or ANH base board It contains a Flash memory SIMM for its own boot image and configuration file The DCM runs RMON agent software that e Gathers statistics by monitoring packets on an
143. the Technician Interface getcfg or ifconfig command to display the router parameters and the bconfig command to correct them if necessary Refer to Displaying Parameter Settings and Debugging the BOOTP Server later in this appendix if you need instructions A 3 Connecting BayStack AN and ANH Systems to a Network Make sure that you enter the proper command at the router console to configure the AN ANH s initial IP interface Refer to Configuring the Netboot Interface in Chapter 5 if you need instructions Make sure that the AN ANH s synchronous port configured for EZ Install is cabled to the upstream router or that the port configured for Netboot synchronous or Ethernet is cabled properly Router Not Sending BOOTP Responses If a router is receiving BOOTP request messages but failing to return BOOTP responses do the following 1 Use Site Manager to make sure the BOOTP relay agent forwarding table associated with the router shows an IP address that is configured on the IP router Make sure that the input IP address is correct If the Hops count is lower than the router s position in the path increase it Refer to Creating the BOOTP Client Interface Table in Chapter 4 if you need instructions Use the Configuration Manager to make sure that BOOTP and IP are enabled on the incoming and outgoing interfaces Make sure that the link modules and drivers are enabled Refer to Configuring R
144. to Site Manager Worksheet continued Requested Information Options Your Information Destination Network Mask 0 0 0 0 Enter the subnetwork mask of the destination network A mask of 0 0 0 0 specifies the default route Next Hop Address Enter a next hop address All static routes require a next hop address in the same subnet as the initial IP interface Wide Area Protocol Worksheets This section contains requested information and possible options relating to wide area protocol choices on the Global Worksheet Bay Networks Proprietary PPP Worksheet Requested Information Options Your Information Enter BOFL Breath of Life timer Enter the maximum amount of value 1 60 5 time that can elapse between the successful transmission of BOFL messages Enter Local Address 1 DCE Selection 3 2 DTE 3 EXPLICIT Note Reverse local and remote address values when configuring the device at the other end of the circuit Exception When connecting to a Series 5 router that uses DCE DTE addressing use the SAME local address value continued Local Boot The Quick Start Procedure Bay Networks Proprietary PPP Worksheet continued Requested Information Options Your Information Enter Remote Address 1 DCE Selection 3 2 DTE 3 EXPLICIT Note Reverse local and remote address values when configuring the device at the other end of the circuit Exception When co
145. to its prompts Refer to the list of Quick Start commands in Table B 1 Table B 1 Quick Start Commands To Do the Following Action Details Accept a default value Press Return Your console displays default values in brackets for example E11 Repeat a step for example if you make a mistake Press Control c Press n When prompted Terminate script y n press the n key You return to the beginning of the step so you can re enter the information Stop the Quick Start installation procedure Press Control c Press y When prompted Terminate script y n press the y key The Quick Start procedure is terminated and you return to the Technician Interface prompt To restart the Quick Start procedure you must reboot the router by entering boot and pressing the Return key The ANH progresses through the Quick Start script as follows a The Quick Start script begins prompting for the initial Global Worksheet information s 0 e p rh The script prompts for specific protocol information The script requests a wide area protocol selection The script prompts for specific protocol information The script prompts for the rest of the Global Worksheet information After you enter all of the Global Worksheet protocol information the Quick Start script displays a Configuration Summary and prompts you to save the configuration to a file 7 Name and save the con
146. u specify the IP address or Ethernet or Ethernet of the TFTP server and the pathname of the startup files connection connection before booting Requires a local console connection and a communications link over an HDLC Frame Relay or Ethernet interface If Directed Netboot cannot retrieve the appropriate files the router attempts normal Netboot If this fails the router tries Local Boot Local Local Local The AN ANH boots using a software router image and Boot configuration file stored in local memory Flash Flash memory memory During the initial startup the AN ANH uses a generic startup configuration file You customize the default configuration file by assigning an IP address to an interface and running an installation script this is called the Quick Start procedure Quick Start requires a local console and an active IP network connection 1 8 Hardware and Software Overview The Boot Process An AN ANH boots using its configured startup option The default configuration for anew AN or ANH is EZ Jnstall If an initial boot attempt fails the router attempts to boot once using a different option If both boot attempts fail you must troubleshoot the problem and reboot the router as described in Appendix A The following sections describe the boot process for network and local boot options Network Boot When booting over the network using EZ Install Netboot or Directed Netboot the AN or ANH essentia
147. uit containing PVC 31 32 33 for virtual connections to the three routers Key BOOTP Client Interface Table BOOTP request Bee 2 baie DLCI 33 192 32 1 4 lt BOOTP response Upstream router Figure 1 2 Getting an Address from a PVC in Group Access Mode 5 The upstream router sends the IP address and subnet mask to the AN in a BOOTP response message 6 The AN ANH assigns the IP address and subnet mask to any synchronous interface that receives a BOOTP response Hardware and Software Overview 7 The AN ANH stores these addresses along with the address of the next hop router in random access memory RAM If both synchronous interfaces receive BOOTP responses the AN ANH assigns the respective IP addresses to each interface Getting Kernel Image and Configuration Files With a known IP address the AN ANH can get image and configuration files 1 The AN ANH sends a BOOTP request for the pathnames of a configuration file and image kernel The router issues the request simultaneously through all synchronous and Ethernet interfaces that have IP addresses It issues this request periodically for about 3 minutes regardless of whether a cable is connected 2 A BOOTP server responds to the router s request with the directory pathnames Figure 1 3 AN ANH BOOTP Upstream router Pathnames server CL Corporate backbone gt Key BOOTP request lt
148. ularly if the filters are not selective You must create Filter and Capture configurations through your RMON network management application You can create as many filters and capture buffers as memory permits up to the RMON limit of 65 535 configurations Memory requirements vary greatly according to the size and number of the filters and the size of the capture buffer In most cases you need 3 to 5 KB of memory for the Filter and Packet Capture configuration The size of the capture buffer determines the amount of memory you need for the data You can request the largest buffer size available by specifying a buffer size of 1 through your RMON network management application When you specify 1 for the capture buffer size the agent attempts to allocate a default buffer depending on the DRAM in the DCM Table 6 3 Table 6 3 Default Size for Capture Buffer Installed DRAM MB Default Buffer Size KB 2 32 4 64 8 256 16 512 You can also request a larger buffer size up to 15 MB In any case if there is not enough memory currently available to satisfy the request the agent will provide a buffer that uses all available memory You can determine the maximum number of packets that an agent can capture in a buffer as follows buffer size packet slice size 20 bytes 6 28 Configuring AN and ANH Features Example You specify a buffer size of 32 KB and a packet slice size of 1 KB After checking the
149. umber of Packets Forwarded and Dropped csseeeeeeeeees A 14 CU Get Nemucone ss accede concdeatavenncraersanicxieainancraeis tener RAAN A 14 Technician Interface Meru CHONS secsi r A 14 Manitaiting Ihe FAouter SONWSIe acacia wanda decent aanucians A 15 Upgrading the Sofware MAGS uriuriia dp anermnaneatiend A 15 Restoring a Local File System PAET A EET EE EET E A 16 Appendix B Local Boot The Quick Start Procedure Via le Guk SIAN aironi P E E OE EE E E T slew vabunies B 1 Using the Quick Start Works WS rossiia iaaii iai ia B 2 Global Information WoOrkKSN OT ascsnur iiinn ae B 3 Router Protocol Worksheets epai AERE PENE T ET Sonena B 5 Wide Area Protocol Worksheets ssesicnisosniannisnareniitieiandri n i ANa B 8 Running Me QULk Stat SODE riiuisiraraieasiadiigaa siandiena aAa AETA B 12 Appendix C Implementation Notes r E E A tes hee E O E EA E T E C 1 NOTOS caccrnsuvencitas oia r E T AE T eyi ei r E T C 2 Network Gonngoratiomn ES arisini a OE SEN EN C 3 Ensuring Ethernet Network Compliance 0 cccceceeeeeeeeeeeeeeeaeeeeeneeesaeeseeneeeees C 3 Network Path Containing Three Repeaters cccccceeeeeeeeeeteeeeeesenaeeeeeeees C 4 Network Path Containing Four Repeaters cccccccsseceseeeeeeceeeeeeeeseteeeeneees C 4 Configuring a Single ANH re swai IVARI ere sdb medetna antares aaa 0 4 Contar MAU MINS HUDS gacsriecutd as scasecatessoeeiecad a ae C 6 Gonfigur
150. ures Parameter RMON Default Matrix Default Enable Options Enable Disable Function Relates to the RMON Matrix group Specifies whether or not to create the RMON Matrix Control Table at every boot Some RMON network management applications expect the DCM to set up a matrix configuration Others enable and disable their own configurations during normal operations Note that the DCM allows only one instance of the matrix control table Instructions Select Enable to create the RMON Matrix Control Table at the next and MIB Object ID every subsequent reboot Select Disable to disable default creation of the RMON Matrix Control Table at boot time 1 3 6 1 4 1 18 3 3 2 16 1 10 Managing the DCM Using Site Manager You use Optivity Design and Analysis software or a third party RMON network management application to set up RMON configurations and to view statistics To manage the installed DCM you can use Site Manager to Activating DCM 1 Change the DCMMW configuration Enable or disable a default RMON Max Host Default Host and Default Matrix configuration Activate temporarily disable and boot the DCM board Deactive the DCM by disabling the DCMMW software subsystem From the Configuration Manager window select Platform gt DCM Global refer to Figure 6 8 The Edit DCM Parameters window appears refer to Figure 6 7 Set the Enable Disable parameter to ENABLE Click on OK to exit the Edit DCM Parameters window
151. utomatically goes off line after 32 consecutive collisions C 7 Connecting BayStack AN and ANH Systems to a Network Connecting the AUI Port to a Fiber Optic Backbone To connect an AN or ANH to a fiber optic backbone you must first connect an IEEE 802 3 10Base FL or 10Base FB transceiver to the AUI port Figure C 3 shows an example network with two 8 port ANH systems connected via a fiber optic backbone An AUI cable connects each ANH to a transceiver that has the SQE test function disabled A fiber optic cable connects the two transceivers A Bay Networks Access Node Hub Power Console Boot Run DCM AUI Part AUI B k 1 2 2 4 2 8 Partition m Sa MDI XMDI aggoonnaa E EE DL 88838888 AUI cable UTP cables to Ethernet stations T R Fiber optic cable IEEE 802 3 10Base FL transceiver R T AUI cable a Bay Networks Access Node Hub 5 6 F 8 Partition WE nHoaooooo0 T2see SETS oOooooooo Link MDX UTP cables to Ethernet stations Figure C 3 Connecting Two ANH Systems Using 10Base FL Transceivers
152. ystems Where to Find AN and ANH Information Use this guide in conjunction with other Bay Networks documentation to set up and manage AN and ANH systems Refer to the following when looking for specific information For Information on This Look Here Installing BayStack AN hardware Installing and Starting BayStack AN Routers Installing 8 port BayStack ANH hardware Installing and Starting 8 Port BayStack ANH Systems Learning about AN and ANH software and the four startup boot options Chapter 1 in this guide Choosing the startup option for an AN or ANH Chapter 2 in this guide Setting up a UNIX workstation as a BOOTP server to support a network boot option Chapter 3 in this guide Configuring Site Manager to support a network boot option Chapter 4 in this guide What to do at the AN ANH site to support a network boot option Chapter 5 in this guide Configuring a Data Collection Module Chapter 6 in this guide Preparing for the Quick Start local boot procedure Appendix B in this guide Completing any of the four startup options at the AN ANH site Installing and Starting BayStack AN Routers or Installing and Starting 8 Port BayStack ANH Systems continued xvi About This Guide For Information on This Look Here Configuring and managing an AN or Configuring Routers and Managing Routers ANH after it is connected to the network an
153. zes the cost of line usage and prevents saturation of the router s memory A disadvantage to Netboot is that it requires the most time to boot the router Directed Netboot Directed Netboot requires a preconfigured communications link to a TFTP server that contains the AN ANH boot image and a customized configuration file Compared with Netboot Directed Netboot e Creates less network traffic e Is generally faster Directed Netboot is usually reserved for starting the router after the initial startup because you need to know the exact location of the software image and configuration files During Directed Netboot the AN ANH transfers files from a TFTP server directly bypassing negotiation with a BOOTP server for the IP address and pathname to the software files 2 4 Local Boot Selecting the Boot Configuration When you choose the Local Boot option for routine startups the router reads the IP addresses from the local configuration file and assigns them to the appropriate interfaces Local booting the software image and or configuration file for routine startups allows you to Minimize the time it takes to boot routers Typically local booting an image takes 2 to 3 minutes Netbooting an image takes a little longer For example over a low speed WAN or after configuring the router to run numerous protocols Netbooting an image can take up to 15 or 20 minutes It also takes less time to local boot a configuration file t

Download Pdf Manuals

image

Related Search

Related Contents

Laboratory Balances  StarTech.com USB to 3.4mm power cable - Type H barrel - 3 ft  Samsung GT-I9305 Εγχειρίδιο χρήσης  Boldair Surodorant  Page 1 Page 2 2 ) 被軸漿の操作手順 の ー )一のの標準血漿の代わ り  OM, EZ17, EZ21, 2007-02  Série - Welcome to Emerson Process Management Documentation    user manual electrical parallel gripper gpe ba-100069  ［浦和南公民館］基準表（PDF形式：44KB）  

Copyright © All rights reserved.
Failed to retrieve file