ECO NUMBER: NISFIX-12-031 ----------- PRODUCT: DEC Network Integration Server Software -------- UPDATED PRODUCT: DEC Network Integration Server Software 3.1 ---------------- APPRX BLCK SIZE: 125128 ---------------- DIGITAL Cover Letter for DEC Network Integration Server Software, ECO Kit #12, V3.1-12. ECO Kit V3.1-12 Description -------------------------- The DEC Network Integration Server Software Fix Notes contain a complete explanation of this release. Below is a brief description: o MOP loading over PPP circuit will not work on W614/8 card. MOP loading over PPP circuit will now work on W614/8 card. o Enable strict IP compliance for ICMP Echo Requests In previous releases, a DECNIS would respond to an ICMP Echo Request for any of its configured IP addresses, even if the cir- cuit was off. This was intentional, but in certain circumstances could cause problems. This feature is now configurable. The following command will force the DECNIS to ignore an ICMP Echo Request if the data link or the circuit is down, or the address is not in a subnet on the receiving circuit. NCL> SET ROUTING STRICT IP INTERFACE ADDRESSING = TRUE o DECNIS could crash on disabling static route In a previous release, a DECNIS running Routing Vector at L1 and L2, could crash when a static route was disabled. This has now been fixed. o DECNIS could transmit L1 LAN HELLOS at excessive rate In a previous release, under certain conditions the DECNIS could transmit L1 LAN HELLOS at excessive rate. This has now been fixed. o Connectivity could be lost In a previous release, the DECNIS could lose connectivity to arbitrary nodes, even though the circuits and the nodes were up. This has now been fixed. o New adjacencies might not form on static route creation Previously, if DECnet/OSI static route entries were created and deleted repeatedly, then the DECNIS might not form new adjacencies and start logging configuration error events. This had now been fixed. o Generated route costs could cycle to infinity. In a previous release, in certain network topologies where DECNIS routers were connected in parallel, the generated RIP metric could repeatedly cycle to infinity. This has now been fixed. o DECnis could crash clearing an X25 Relay Call In V3.1-9, sometimes the DECnis would crash when clearing down an X25 Relay call. This is now fixed. o DECNIS reports invalid NCL dictionary on the console In a previous release, a DECNIS could report invalid NCL dictio- nary on the console This has now been fixed. o DECNIS routers could dump on topology changes In a previous release, in exceptional circumstances, a DECNIS could crash during IP topology changes. This has now been fixed. o Configurable ARP cache size introduced A broadcast routing circuit of TYPE CSMA-CD FDDI or SMDS which is running IP will have an ARP cache. Previously on large net- works, this ARP cache could be filled, and subsequent ARP en- tries would then replace an existing entry. This could degrade network performance. To fix this problem, it is now possible to configure the size of a routing circuit's ARP cache. o Incorrectly set bridge ports still activate In previous releases, CHDLC bridge ports which are incorrectly set up (wrong SDU sizes) by the configurator would still acti- vate. A recent release prevented them activating if incorrectly set up. This behaviour has now been changed back so that CHDLC bridge ports which are incorrectly set up will activate. Installation Overview --------------------- Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL NISFIX-12-031 [location of the saveset] Refer to Chapter 1.1 of the update notes for post installation tasks. The update notes can be found in the save-set NISFIX-12-031.A or after the installation in the file SYS$HELP:NISFIX031.RELEASE_NOTES. Please note that after installing this update kit, you need to reboot all DECNIS servers which require updating with the latest DECNIS software. Copyright Digital Equipment Corporation 1997. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.