DECNIS V2.3 DECNIS[TM] V2.3 Release Notes for MS-DOS[TM] 27-March-1994 Digital Equipment Corporation Maynard, Massachusetts _________________ While Digital believes the information in this publication is correct as of the date of publication, it is subject to change without notice. Possession, use, or copying of the software described in this docu- mentation is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. _________________ Copyright Digital Equipment Corporation 1994. All Rights Reserved. _________________ The following are trademarks of Digital Equipment Corporation: Bookreader DECwindows VAXcluster DDCMP DNA VAXELN DEC OpenVMS VMS DECbrouter Packetnet VT DECmcc PATHWORKS DECnet POLYCENTER DECNIS ULTRIX DECrouter VAX and the DIGITAL logo AppleTalk is a registered trademark of Apple Computer, Inc. IBM is a registered trademark of International Business Machines Cor- poration. MS-DOS is a registered trademark of Microsoft Corporation. NetWare is a registered trademark of Novell, Inc. OSF and OSF/1 are registered trademarks of the Open Software Founda- tion, Inc. Vitalink is a registered trademark of Vitalink Communications Corpo- ration. All other trademarks and registered trademarks are the property of their respective holders. The Digital implementation of OSPF is an adaptation of the OSPF im- plementation developed by the University of Maryland, College Park, Maryland. Copyright (c) 1989, 1990, 1991, 1992, University of Mary- land. ii Permission to use, copy and modify the software and its documentation is granted provided that this copyright notice and these terms shall appear in all copies of the software and its supporting documentation. The origin of this software may not be misrepresented, either by ex- plicit claim or by omission. The Software is provided "AS IS" and without any express or implied warranties, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. iii CONTENTS 1 Functionality Added for This Release..................... 1 2 Functionality Restrictions for This Release.............. 1 2.1 OSPF Network sizes supported.......................... 1 2.2 Serial Line Restrictions.............................. 2 2.3 IP Subnet Masks Longer than 28 Bits................... 2 2.4 Using HDLC Links...................................... 2 2.5 Setting values for T1 over LAPB X.25 links............ 2 2.6 Disabling X.25 security............................... 2 2.7 FDDI links sticking in the "Off-Ready" state.......... 3 2.8 BOOTP TSR (background) startup errors on systems with MS-DOS V6.2........................................... 3 2.9 Disabling MOP Load Requester & IP Load Requester...... 3 2.10 MOP cannot initiate loopback packets on DDCMP links.. 3 2.11 NetWare[TM] IPX Routing: Events...................... 4 2.12 AppleTalk[TM] Routing: Events........................ 4 2.13 CSMA-CD Events....................................... 4 2.14 Event Filtering...................................... 4 2.15 Disabled Netware IPX from Routing Circuits in the DECNIS configurator.................................. 4 3 General Information...................................... 4 3.1 ACTUAL SPEED Characteristic........................... 5 3.2 MAC Addresses......................................... 5 3.3 W618 and W614 Connector Cable......................... 5 3.4 MOP node name......................................... 5 3.5 NSP defaults may affect performance of Routing Convergence........................................... 5 3.6 Replacement of the "Metric" attribute for IP Destination Address Entity............................ 5 3.7 BOOTP/TFTP Loading from PATHWORKS V5.................. 6 3.8 Running NETSET after Pathworks, and Pathworks Stopnet. 6 3.9 Setting up the PWTCP.INI file in for Pathworks Version 5 use................................................. 7 3.10 Using NCP with Pathworks Version 5................... 7 3.11 Trouble shooting network problems using Pathworks.... 7 3.12 Pathworks V5.0 errors setting up MOP loading of a DECNIS............................................... 7 3.13 Using the BOOTP/TFTP server program to copy dump files................................................ 7 3.14 BOOTP operation with old Management Processor ROMs... 8 4 Interoperability Information............................. 8 4.1 DECNIS IPX interoperability with Novell NE2000T+ ethernet card......................................... 9 4.2 Designated Router election against DECbrouter 90...... 9 iii 4.3 Network "probe" of Vitalink[TM] Bridges............... 9 4.4 DECmcc - SNMP ARP entry table deletion................ 9 4.5 DECmcc - restrictions with objects defined as type FddiTime.............................................. 9 5 Configuration Information................................ 10 5.1 NCL script error with LLC2 on FDDI circuits........... 10 5.2 Misleading DECNIS configurator Error message.......... 10 5.3 DECNIS system time when loaded using BOOTP............ 11 5.4 Incorrect "MOP error" message......................... 11 6 NCL Problems............................................. 11 6.1 On-line HELP for NCL: HDLC LINK Entity................ 11 6.2 DELETE AND DISABLE Commands........................... 11 6.3 Displaying Ports...................................... 12 6.4 Using the 50-Way Loopback Connector................... 12 6.5 Loopback With Assistance.............................. 12 6.6 NCL Abbreviation of 'Protocol' Keyword................ 12 6.7 NCL errors "No buffer space available"................ 12 7 Documentation Information................................ 12 7.1 Configuring OSPF over X25-DA Circuits................. 12 7.2 LOOP MOP Command...................................... 13 7.3 On-line Problem Solving Guide......................... 13 7.4 Missing Information in DECNIS 500 Manual.............. 14 iv DECNIS[TM] V2.3 Release Notes for MS-DOS[TM] This document contains information not included elsewhere in the DEC Network Integration Server (DECNIS[TM]) documentation. This informa- tion includes information about using the DECNIS, software changes and /or documentation changes. This document is intended for use with Version V2.3 of the DECNIS. PLEASE READ THESE NOTES BEFORE INSTALLING OR USING THE SOFTWARE. 1 Functionality Added for This Release The following software functions are included in this release: 1. Management of DECNIS systems from IBM[TM] Compatible Personal Com- puters running MS-DOS[TM]. 2. OSPF Routing support. 3. Fast IPX routing support for the (F621 and L601/L602) LAN line cards. 4. SNMP Get and SET support for MIB-II, BRIDGE MIB, and FDDI MIB (RFC's 1213, 1493, and 1512 respectively) 5. Bridging operation over Frame Relay networks. 6. Inter-operation with DECbrouter 90 (and Cisco AGS+ router) systems over the CHDLC datalink. Common Trace Facility (CTF) also provides support for SNMP with the following routing trace filters: - "sntx" display SNMP packets transmitted - "snrx" display SNMP packets received 2 Functionality Restrictions for This Release The following section describes known restrictions with this software release. 2.1 OSPF Network sizes supported For this release, due to the processing overhead caused when large num- bers of routes change state in an OSPF network there are restrictions on the number of ROUTES that the DECNIS can support in an OSPF net- work. If running OSPF over a LAN circuit then Digital does not recommend the use of more than 1000 routes, ie. IP Maximum External Adjacencies and IP Maximum External Destinations should not be greater than 1000. If running OSPF over a WAN circuit, or running OSPF at the same time as other processor bound protocols (such as X.25 or IPX tunnel cir- cuits) then no more than 500 routes can be supported by the DECNIS. 1 If you need to extend the number of OSPF routes used beyond the above size then changing the following parameters will allow an OSPF only router to support more routes. NCL>SET {nodename} ROUTING CONTROL PROTOCOL {cproname} LOGICAL CIRCUIT {circuit} OSPF HELLO INTERVAL 20 NCL>SET {nodename} ROUTING CONTROL PROTOCOL {cproname} LOGICAL CIRCUIT {circuit} OSPF DEAD INTERVAL 80 Note: default values for these parameters are 10 and 40 respectively If you need to operate with larger OSPF networks then contact Digi- tal for details of maintenance fixes. 2.2 Serial Line Restrictions For this release, do not reconfigure the serial data-link on a run- ning system. If you need to change the data-link type (for example from HDLC to PPP), then you must change the configuration files and reboot the system. 2.3 IP Subnet Masks Longer than 28 Bits IP subnet masks longer than 28 bits are not supported. Such subnet masks cannot be configured on the DECNIS. If such a subnet mask is received in an IS-IS LSP, then the DECNIS will discard the LSP and all routes in the LSP will not be learnt. 2.4 Using HDLC Links Occasionally the DECNIS may not correctly bring up an adjacency over an HDLC circuit when the HDLC link is established. This situation can be recognised by noticing that the HDLC link is "Running" and one side has a Routing Circuit Adjacency in state "Initializing" but the other side has no Adjacency for that circuit at all. If this occurs, the HDLC link should be disabled and then re-enabled. 2.5 Setting values for T1 over LAPB X.25 links For operation of X.25 over LAPB links the values for the timer "T1" should not be set below the default values specified in the network profile, on either the DECNIS system (DTE) or the network system (DCE). Digital recommends that this value is not set below 2 second, values below 1 second may result in datalink disconnections if the DECNIS Man- agement processor is heavily overloaded. 2.6 Disabling X.25 security. When running the DECNIS configurator if the X.25 security option is disabled it should not subsequently be re-enabled. Doing so will cause information on outgoing security to be lost. 2 2.7 FDDI links sticking in the "Off-Ready" state If the following sequence of commands is supplied to the FDDI station LINK entity the link may remain in the "Off-Ready" state. NCL> disable node x fddi station f621-{n} link 1 NCL> disable node x fddi station f621-{n} phy port 1 NCL> disable node x fddi station f621-{n} phy port 2 NCL> enable node x fddi station f621-{n} link 1 NCL> enable node x fddi station f621-{n} phy port 1 NCL> enable node x fddi station f621-{n} phy port 2 NCL> disable node x fddi station f621-{n} link 1 NCL> enable node x fddi station f621-{n} link 1 (where x is the node name, and f621-{n} is the F621 FDDI card name) Should this happen issue the following commands to return the link to the "On-Ring Run" state. NCL> disable node x fddi station f621-{n} link 1 NCL> disable node x fddi station f621-{n} phy port 1 NCL> disable node x fddi station f621-{n} phy port 2 NCL> enable node x fddi station f621-{n} phy port 1 NCL> enable node x fddi station f621-{n} phy port 2 NCL> enable node x fddi station f621-{n} link 1 2.8 BOOTP TSR (background) startup errors on systems with MS-DOS V6.2 The scheduler used for background BOOTP operation (TSR mode) does not allow for operation against MSDOS V6.2 and will report a startup er- ror. To order to overcome this problem you need to to change the ver- sion number reported by this image by typing the following DOS com- mand: SETVER sch.exe 6.00 2.9 Disabling MOP Load Requester & IP Load Requester If MOP Load Requester or IP Load Requester is disabled for a partic- ular interface then this will also disable the receipt of boot or load requests over that interface even if the target load host is on an- other, enabled interface. 2.10 MOP cannot initiate loopback packets on DDCMP links Although MOP circuits can be set up for DDCMP links, the MOP LOOP di- rective will always fail with a datalink error. MOP LOOP directives (Phase IV via NCP or Phase V via NCL with DECnet/OSI) from the remote station will be responded to correctly. 3 2.11 NetWare[TM] IPX Routing: Events The following event is not logged by the NetWare[TM] IPX routing soft- ware: o State Change 2.12 AppleTalk[TM] Routing: Events The following event is not logged by the AppleTalk[TM] routing soft- ware: o State Change 2.13 CSMA-CD Events These are not generated for either station transmit or receive errors. 2.14 Event Filtering The following conditions apply to event filters for this release. 1. A node name must be included in the specific filter argument of Pass, Block or Ignore directives and in the Event argument of the TestEvent directive. However, the name is not checked or acted upon by the DECNIS. For example, in the following command, the node xyzzy is not checked or used by the DECNIS: NCL> PASS NODE decnis EVENT DISPATCHER OUTBOUND STREAM - stream-name SPECIFIC FILTER ( NODE xyzzy ROUTING CIRCUIT - csmacd-0, CIRCUIT CHANGE) 2. The "All Events" event group is not supported in the filtering com- mands. For example, the following will be rejected with an invalid argument value error: NCL> PASS NODE decnis EVENT DISPATCHER OUTBOUND STREAM - stream-name SPECIFIC FILTER (NODE xyzzy ROUTING CIRCUIT - csmacd-0, ALL) 2.15 Disabled Netware IPX from Routing Circuits in the DECNIS configurator In this release, once a Netware IPX routing circuit has been entered (in the lines and DTE section) it can not be disabled. Disabled IPX circuits will prevent a clean NCL script compilation and should be re- moved by deleting and re-adding the line. 3 General Information This section provides information about using DECNIS and the V2.3 soft- ware in your network. 4 3.1 ACTUAL SPEED Characteristic The value of the ACTUAL SPEED characteristic is only an estimate and at high speeds the value may be inaccurate. For example: a line run- ning at 2Mbps may report as running at 2.5Mbps. 3.2 MAC Addresses When transmitting frames on an 802.3 LAN (Ethernet), the DECNIS may use different source addresses for different protocols: o OSI, DECnet Phase IV or IP traffic: SA = Logical Address o All other frames: SA = Physical Address of NIC. where Logical Address is the Phase IV style Ethernet address of the system if Phase IV address is enabled on the particular routing cir- cuit; otherwise it is the Physical Address of the Network Interface Card. 3.3 W618 and W614 Connector Cable This cable must not be unplugged (at either end) when power is applied to the Network Interface Card. 3.4 MOP node name If you manually configure the file name for the load file in the MOP CLIENT profile it is important to use the correct syntax:- System Image = {:.Node::mom$system:nis023.sys} The leading colon is required for successful operation 3.5 NSP defaults may affect performance of Routing Convergence If you operate a large network you may experience problems in the per- formance of Routing Convergence, and possible loss of transport con- nections during topology changes in the network. This is due to in- appropriate NSP defaults when running Phase V routing. The following defaults are recommended: o Delay Factor = 5 o Delay Weight = 3 o Retransmit Factor = 10 3.6 Replacement of the "Metric" attribute for IP Destination Address Entity The "Metric" status attribute associated with the ROUTING IP DESTI- NATION ADDRESS entity is nolonger supported by the DECNIS software. Instead it uses the new "Path Metric" attribute which has the same mean- ing but allows the larger range of metric values required for OSPF. 5 3.7 BOOTP/TFTP Loading from PATHWORKS V5 There is a problem with PATHWORKS V5 which prevents the BOOTP/TFTP server from finding the PC's IP address entered during PATHWORKS configura- tion. BOOTP/TFTP needs this address to load a DECNIS. To work around this problem, run the DECROU NETSET utility before you start the BOOTP/TFTP server. NETSET enables you to enter the PC's IP address, and then sets up files recording the address. Follow these steps. 1. Stop PATHWORKS V5, by entering STOPNET. Note that after entering STOPNET, you may also need to enter the following command: SET DECNET= See Section 3.8 for details. 2. Run NETSET, as described in the manual, Router Configuration and Management from PCs, Section 3.4. 3. Exit from NETSET. 4. Start PATHWORKS V5 again, by running the PATHWORKS version of START- NET.BAT For example: C:\PW\STARTNET You must run NETSET once, before the first time you load the DECNIS using BOOTP/TFTP. After that, you only need to run NETSET if you change the PC's IP address. 3.8 Running NETSET after Pathworks, and Pathworks Stopnet The Pathworks V4.1 and V5 STOPNET procedures do not completely remove the pathworks configuration from the system. To correctly remove all components of pathworks the following steps are required: For Pathworks V4.1 Pathworks V4.1 does not remove all components from memory when the STOP- NET procedure is run. These components of pathworks must be unloaded before NETSET can be run. To overcome this problem it will be neces- sary to reboot the PC, after removing the commands in C:\AUTOEXEC.BAT and C:\CONFIG.SYS that start the PATHWORKS V4.1 software. For Pathworks V5 Although the Pathworks V5 procedure does correctly unload memory it does not remove the DECNET environment variable. This will result in the following error message when running the NETSET program, even af- ter running STOPNET. 6 ERROR : Network running (do stopnet first) To avoid this problem you need to enter the following command after shutting down Pathworks (V4.1) and before running NETSET. SET DECNET= 3.9 Setting up the PWTCP.INI file in for Pathworks Version 5 use. If your PC has been configured to run with Pathworks Version 5 you should modify the PWTCP.INI file, and increase the value of the " UDPMaxSock " parameter up to a minimum of 12. This allows TCP sockets as follows on your system. o one for BOOTP (all purposes) o one for TFTP requests o one per active file transfer (max 10) 3.10 Using NCP with Pathworks Version 5 If your PC has been configured to run with Pathworks Version 5 you should define network information using NCP.EXE (rather than NCPW.EXE) 3.11 Trouble shooting network problems using Pathworks NETSTAT and PING network trouble shooting utilities can be found in the Pathworks V5 product and are useful if suspected network problems are encountered on your system. 3.12 Pathworks V5.0 errors setting up MOP loading of a DECNIS If you use Pathworks MOP NCP to define network loading of a DECNIS and use the NCP command " DEFINE NODE node-name HARDWARE-ADDRESS ethernet- address " then NCP incorrectly generates an error message. This is for backward compatibility with applications that use the NCP V4.1 database, NCP V5.0 maintains both V4.1 and V5.0 databases. When you define a new V5.0 attribute for a node such as a management file attribute, the part of NCP that tries to update the V4.1 database will fail and issue an error message. Please Ignore This Message. 3.13 Using the BOOTP/TFTP server program to copy dump files The BOOTP/TFTP server can be used to transfer dump (or any other) files over a network. However the BOOTP/TFTP server image must be started with the "-P" switch in order to weaken the file protection on the sys- tem, and allow the TFTP client to specify the full file specification. The easiest way to do this is to run NETSET to generate the RBOOT.BAT and FBOOT.BAT files and then edit these files to add the -P qualifier. After the BOOTP/TFTP server has been started the TFTP client should be used in BINARY mode as follows: 7 $ TFTP {network_IP_address_of_system_running_BOOTP/TFTP_server} tftp> binary tftp> get C:\DECROU\CLIENTS\{DECNIS_client_name}\DUMP tftp> Where {network_IP_address_of_system_running_BOOTP/TFTP_server} and {DEC- NIS_client_name} (and C:\DECROU) are the values chosen for your sys- tem. 3.14 BOOTP operation with old Management Processor ROMs There is a problem with full dumps of the DECNIS taken by BOOTP/TFTP if the MPC has ROMs prior to V7-07. The dump slows down and has ex- cessive retransmissions after the first 8M-10M bytes. The BOOTP/TFTP server window shows all retransmissions and will display the follow- ing message: "Resend ACK on timeout" Every 4 seconds. (Note that a foreground dump takes an hour and a back- ground dump 2 or 3 hours on the PC even in normal circumstances.) The ROM version number can be found by using the following NCL com- mand. Any pre-1993 DECNIS will probably require upgrading if dumps are required and this problem is found. NCL> SHOW NODE node-name DEVICE UNIT MP8M-1 FIRMWARE IDENTIFIER Show Node DEC:.node-name Device Unit MP8M-1 at 1993-12-10-11:49:12.60000 + 00:00 I 28147497.67107 Status Firmware Identifier "0 2-3.6 V7-07 5.1" ~~~~~ Setting the DECNIS to only dump the management processor will in most circumstances provide a workaround. However upgraded ROMs will be nec- essary where dumps are required for all other cards in the system. The NCL command to limit the size of the dump file is: NCL> SET NODE node-name HARD DUMP CONTROL SYSTEM PROCESSOR DUMP To return to a full system dump issue the following command: NCL> SET NODE node-name HARD DUMP CONTROL FULL DUMP 4 Interoperability Information This section provides information about other products that interact with the DECNIS V2.3 software. 8 4.1 DECNIS IPX interoperability with Novell NE2000T+ ethernet card This release will not inter-work correctly with PC systems using the the Novell NE2000T+ card, or any other cards using drivers that re- quire IPX packets to be generated with an even number of bytes within 802.3 frames. This problem can be avoided by using alternative ethernet cards, or using ETHERNET_II IPX encapsulation formats. Contact Digital for details of maintenance fixes. 4.2 Designated Router election against DECbrouter 90 When the DECbrouter 90 (or Cisco routers) are configured to conduct DNA Phase IV to V conversion, the DECbrouter 90 (or Cisco routers) must have equal settings for both DNA IV & V router priorities. Failure to do so may result in a designated router not being elected if the DEC- NIS router priority is between the two values set in the DECbrouter 90. 4.3 Network "probe" of Vitalink[TM] Bridges In order to use Vitalink[TM] network "probe" features over VCP links the following ethernet types should be selected for forwarding. DVS -> Display Vitalink Systems Type 80-80 CON -> Connect Type 06-00 (XNS_IDP) 4.4 DECmcc - SNMP ARP entry table deletion It is not possible to to delete ARP cache entries using the address translation table of MIB II if using the DECmcc management agent. This is because DECmcc does not allow a zero length string to be entered. The workaround is to set the ipNetToMediaType object in the ipNetTo- MediaTable to 'invalid' for the entry which you wish to deleted. 4.5 DECmcc - restrictions with objects defined as type FddiTime DECmcc incorrectly handles the type Unsigned32 are encoded incorrectly in ASN.1 as the SNMP application type 'TimeTicks' rather than plain integer (0..2147483647). The consequence being that it is not be possible to set from DECmcc the following variables in the FDDI MIB (RFC1285). o snmpFddiMACTReq o snmpFddiPORTMACLoopTime 9 o snmpFddiPORTTBMax The following will not be setable from DECmcc in the BRIDGE MIB (RFC1286): o dot1dStpBridgeMaxAge o dot1dStpBridgeHelloTime o dot1dStpBridgeForwardDelay Note that if any other management station is used these variables will behave as expected. 5 Configuration Information This section provides information associated with installation and con- figuration of the DECNIS V2.3 software.. 5.1 NCL script error with LLC2 on FDDI circuits If you use the the DECNIS configurator to set up LLC2 operation over an FDDI circuit the NCL generated will be incorrect, due to the ad- dition of the wrong LAN type. To correctly compile the NCL script the main .NCL file must be edited to reset the LAN type back to FDDI, For example: Change: set llc2 sap sap-0 lan station csma-cd station f621-9-0 To: SET LLC2 SAP SAP-0 LAN STATION FDDI STATION F621-9-0 _________ 5.2 Misleading DECNIS configurator Error message If the DECNIS Router Configurator is accidentally run before the load HOST configurator, then following misleading message is displayed. FATAL ERROR: The host configurator data file listed below contains no suitable clients. Use nis_hcfg.exe to configure a suitable MOP client. Host configurator data file : C:\DECROU\NIS\nis_hcfg.dat The " C:\DECROU\NIS\nis_hcfg.dat " file will be generated by running the HOST configurator, from the main menu. Do not run the file C:\DECROU\NIS\NIS_ HCFG.EXE directly. 10 5.3 DECNIS system time when loaded using BOOTP If a DECNIS is configured and loaded using BOOTP (on PC or ULTRIX/OSF[TM] systems), the clock on the DECNIS will not be set. Once the system has loaded the system time needs to be set after initial load using the following command. NCL> UPDATE NODE {node-name} DTSS TIME yyyy-mmm-dd-hh:mm:ss +a:b Where "yyyy-mmm-dd-hh:mm:ss" is the current time and "a:b" is the dif- ferential time in Hours and Minutes 5.4 Incorrect "MOP error" message If an error occurs during the update of the BOOTP.TAB file in the HOST configurator the screen will incorrectly display a MOP error message (if the network is loaded/running) This message should be ignored. 6 NCL Problems This section describes provides information about possible problems with NCL. 6.1 On-line HELP for NCL: HDLC LINK Entity The PREFERRED CRC TYPE characteristic attribute of the HDLC LINK en- tity has the following three possible values: o 16 bit o 32 bit o EITHER The NCL HELP text incorrectly includes a hyphen in the first two val- ues. 6.2 DELETE AND DISABLE Commands The following directives are not supported: DELETE CSMA-CD DELETE CSMA-CD STATION DELETE MODEM CONNECT LINE DISABLE CSMA-CD STATION The following directive returns an incorrect error message: DISABLE ROUTING The error message returned is "No such entity". This should be "Di- rective not supported". 11 6.3 Displaying Ports If your DECNIS system has both L601 and L602 NICs, the NCL command: NCL> SHOW NODE name DEVICE ALL displays all the L602/L601 port 0 information, followed by the L602 port 1 information. 6.4 Using the 50-Way Loopback Connector You cannot use the STOPLOOP command on a MODEM CONNECT LINE, if the W622 or W614 Network Interface Card associated with that line has a 50-way loopback connector installed. Issuing the STOPLOOP command in this circumstance will have no effect. 6.5 Loopback With Assistance MOP loopback with assistance is not supported. 6.6 NCL Abbreviation of 'Protocol' Keyword When issuing NCL commands to a ROUTING CIRCUIT NETWORK PROTOCOL en- tity, you must not abbreviate the keyword PROTOCOL. 6.7 NCL errors "No buffer space available" The following error will be seen if the command "NCL> load node {node-name} device unit mp8m-1" is repeatedly used to reboot systems. Failed to get connection to remote entity No buffer space available Should this error occur then the network should be shutdown and restarted, using STOPNET and STARTNET 7 Documentation Information The following sections describe documentation changes. 7.1 Configuring OSPF over X25-DA Circuits To configure OSPF to run over an X25-DA circuit requires some addi- tional setup by the user which is not currently documented in the Man- agement Guide and is not performed by the Configurator. The follow- ing steps describe the actions necessary to configure an OSPF NBMA net- work over X25-DA circuits. 12 1. Use the Configurator to create an X.25-DA routing circuit, spec- ifying any security options you require and the DTE information. Note that the router must be configured as a ISIS L2 router in or- der to create an X.25-DA circuit (although you can still disable IP information from being propagated by the ISIS routing protocol if necessary). 2. Also in the Configurator, create an IP Reachable Address for ev- ery OSPF Neighbor which is accessible over the X.25-DA Routing cir- cuit. You must specify 255.255.255.255 as the mask for the reach- able address (i.e. a host mask) and the address of the Neighbor's interface. 3. In the NIS_name_EXTRA_SET.NCL file you must setup a subnet address and mask for the X.25-DA Routing Circuit (this is not done by the Configurator). The subnet address is the subnet of the OSPF NBMA network, i.e. SET ROUTING CIRCUIT x25-da-1 - SUBNET ADDRESS [ADDRESS=92.1.1.0, MASK=55.255.255.0 ] 4. Now create and setup the OSPF entities (CONTROL PROTOCOL, LOGICAL CIRCUIT and ADJACENCY) in the NIS_name_EXTRA_.NCL files as described in section 8.8.7 in the DECNIS Management Guide. Specifically you must create a manual adjacency for every OSPF Neighbor on the X.25- DA network e.g. CREATE ROUTING CONTROL PROTOCOL ospf-area-0 LOGICAL CIRCUIT rx25-da-1 - ADJACENCY node OSPF NEIGHBOR ADDRESS 192.1.1.5, OSPF PRIORITY 1 Note you should have an adjacency for every IP Reachable Address you created in the Configurator). 7.2 LOOP MOP Command The DECNIS Problem Solving manual describes using the following com- mand to test HDLC, DDCMP and LAPB circuits: NCL> LOOP MOP CIRCUIT circuit-name In this release, this command is not supported for DDCMP and LAPB cir- cuits, see Section 2.10. 7.3 On-line Problem Solving Guide Text versions of the Problem Solving Guide are provided in the doc- umentation directory; C:\DECROU\DOCS\PSG*.* 13 7.4 Missing Information in DECNIS 500 Manual The following information applies to the 7-segment display as described in the DECNIS 500 Installation and Service Manual. 7-Segment displays for DECNIS systems while loading/dumping: 0 No Load Circuits. The system cannot issue a load request since all the possible load circuits are either broken or have been disabled. 1 Load Request. The system is requesting a load from a specific load host. This would normally be the first display since the load is always tried from the last load host first. 2 Loading. The system has located a load host and is loading the image. This display remains until the load completes or is aborted. 3 Load Request Backoff. The system has backed off the load request to avoid congestion on any load hosts. The load request will be re-issued when the backoff timer expires (a few seconds). 4 Load Complete, flash update or decompression in progress. 5 Dump Request. The system is requesting a dump to a specific dump host. This would normally be the first display since the dump is always tried from the last load host first. 6 Dumping. The system has located a dump host and is dumping the sys- tem context. This display remains until the dump completes or is aborted. 7 Broadcast Load Request. The system is requesting a load on all cir- cuits (using the dump/load assistance multicast address on LAN cir- cuits). 8 not-used 9 Broadcast Dump Request. The system is looping around all the circuits sending a dump request on each in turn trying to locate a dump host (using the dump/load assistance multicast address on LAN circuits). 14