AdvanceStack Hub Agent Release History ====================================== AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.02.03 Description: Initial version. Date of Release: ~ 1/30/95 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.02.08 Description: Beta release Purpose of Release: Beta release for Tech Marketing On-line Date of Release: ~ 5/12/95 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) ================================= ENHANCEMENTS (since last release) ================================= ASCII console: New commands have been added to the ASCII console command set. Most of these commands were previously part of the extended command set. Help on the commands can be displayed with the HE (HElp) command. In addition three new commands have been added to support management of slave hubs chained through the out-of-band connectors. The command CH (CHain) will display information about chained hubs. The HU (HUb) command will indicate which hub is currently being accessed for management. The HU command with an entry number argument will access that hub for management. At that point commands entered at the console will affect the new hub. The AU (AUxiliary) command will allow connection to the auxiliary function module such as a router 210. Tolerance for some incorrect 802.3 packets: It was observed that some PC drivers occasionally send 802.3 packets with incorrectly calculated length fields. Specifically this was seen with networks running Novell's IPX protocol. The effect was that incorrectly formed SNMP management packets sent to the hub agent were discarded, causing the hub to appear "red" in the map. Now the agent will accept such packets. ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.03.01 Description: PCO that includes support for "B" versions of 24-port and 48-port hubs (which have RPS connectors). Also, officially released telnet & slave trap features. Purpose of Release: PCO Date of Release: ~ 8/1/95 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) J2601B (AdvanceStack 10BaseT Hub-24 with RPS connector) J2602B (AdvanceStack 10BaseT Hub-48 with RPS connector) ================================= ENHANCEMENTS (since last release) ================================= Telnet: It is now possible to telnet into a managed hub and use the ASCII console commands. Although only one active console session is supported (whether serial or telnet) the console will inform the user if a prior sesson is active and will offer a choice to continue. In addition, password authentication will remain enforced in telnet if a password has been set. Telnet capability is enabled by default, but can be disabled through a configuration option in the IP (IPconfig) command. The hub must be rebooted for this to take effect. ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.03.02 Description: Special LED version for Australian Telecom Purpose of Release: Marketing requested special LED version for Australian Telecom Date of Release: 9/15/95 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) J2601B (AdvanceStack 10BaseT Hub-24 with RPS connector) J2602B (AdvanceStack 10BaseT Hub-48 with RPS connector) ============================== BUG FIXES (since last release) ============================== Fixed Potential mbuf deadlock (PR NMT614): A network hang condition could occur under certain circumstances. This bug exists on the Summer 95 release and has been corrected. Fixed Potential Communication Error with Stack Manager: This was a problem only experienced with early development for another product, but recognized as a potential problem here. However, the problem has never been seen with this product. ================================= ENHANCEMENTS (since last release) ================================= Feature: Added LED option: An option is added to the LEDs behavior to make a port's LED blink at the slow rate when Linkbeat is detected and the port is off. This will allow an administrator to detect a hub port that is disabled but connected to an active end node. This feature is disabled by default and can be enabled by an undocumented LI (LInkbeat) command. All other LED behavior is unchanged, including a port's behavior when the feature is not enabled. To turn on the feature, issue the following ASCII command: LI LED ON To turn off the feature, issue the following ASCII command: LI LED OFF Resetting the hub to factory defaults also turns off this feature. When disabled port linkbeat detection is enabled, a line will be displayed at the bottom of the status display screen: Linkbeat detection of disabled ports led display enabled. This feature will have a few quirks. The configuration for disabled port linkbeat detection will be stored on the management card, thus if the card is moved from one hub to another, the configuration will be reset, just like IP addresses and security configuration. It will not stay with the hub. This feature will not exist on hubs without a SNMP management card. When backup links are enabled, the backup link port will blink when the primary port is active. This feature is not supported on the xcvr port when a twisted- pair xcvr is plugged in. As with faults that cause a slow blink, security violations that cause a fast blink will override the linkbeat detection slow blink. ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.03.04 Description: Bug fixes and enhancements Purpose of Release: Online Support requested fix for land.c virus, and support for "subnet zero" and the "all ones subnet" IP addresses. Date of Release: 3/20/98 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) J2601B (AdvanceStack 10BaseT Hub-24 with RPS connector) J2602B (AdvanceStack 10BaseT Hub-48 with RPS connector) ============================== BUG FIXES (since last release) ============================== NMT776: Intruder Address in STatus display is incorrect - Console display of intruder address is random garbage. NMT2785: Agent network communication hang - Under rare conditions with IPX traffic to agent, the agent can experience a memory leak. The result is a failure of network communications to/from the hub. NMT2786: Giant pings can hang agent network communication - If agent is subjected to giant IP packets, usually pings, the agent can leak memory, resulting in a failure of network communications to/from the hub. NMT3276: Reboot - The denial-of-service attack known as "Land Attack" (source code "land.c" or "moreland.c"), causes the hub to reboot. This attack involves a TCP SYN packet with the destination IP address equal to the source IP address. ================================= ENHANCEMENTS (since last release) ================================= Feature: Added CIDR support (Enhancement requests NMT3317 & NMT3382). Allows the hub to be assigned an address in the "all zeros subnet" and in the "all ones subnet". Also supported is the ability to set the subnet mask to a supernet value (CIDR). This is a subnet mask that is shorter than the class default mask. ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.03.05 Description: Bug fix Purpose of Release: Resolve the bug documented below Date of Release: 8/7/98 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) J2601B (AdvanceStack 10BaseT Hub-24 with RPS connector) J2602B (AdvanceStack 10BaseT Hub-48 with RPS connector) ============================== BUG FIXES (since last release) ============================== NMT3403: An invalid IPX RIP packet caused the hub agent to "hang". The symptom is a failure to respond to ping or telnet, although the hub continues to repeat network traffic. The invalid packet has an IPX header with the correct number of bytes, but the "length" field gives a different (wrong) value. ----------------------------------------------------------------------- AdvanceStack Agent Firmware Release Note ---------------------------------------- Product Name: J2603A and J2603B Ethernet SNMP modules Version: A.03.06 Description: Bug fix Purpose of Release: Resolve the bug documented below Date of Release: 10/26/98 Hubs supported: J2600A (AdvanceStack 10BaseT Hub-12) J2601A (AdvanceStack 10BaseT Hub-24) J2602A (AdvanceStack 10BaseT Hub-48) J2601B (AdvanceStack 10BaseT Hub-24 with RPS connector) J2602B (AdvanceStack 10BaseT Hub-48 with RPS connector) ============================== BUG FIXES (since last release) ============================== NMT3420: IPX stack did not function properly, related to the previous NMT3403.