GIGAswitch/IP Version 2.0.1-D Release Notes
Problems Fixed

This section describes problems fixed in the GIGAswitch/IP Software Version 2.0.1-D.

<

	More than 32 addresses on a directly attached local net sometimes caused transient failures in the relay of bootp reply messages.
	"No Enabled VIFs" message displayed when there were fewer than two VIFs enabled.
The fix lowers the log message severity from LOG_WARNING to LOG_INFO. The message will still be logged when run with a debug level of 2 or greater.
	IPX RIP decode printed inaccurate routes.
The IPX RIP decode ignored the length of the captured packet from BPF. It attempted to print out all possible fields of a RIP update.
	Browser crashed when large log file was loaded.
	Switch control leaked control NIC VC labels on multicast traffic.
	MAC address changes were not reflected in the database for the IPX address.
Changed an interface card but used the same config file. The changes in the MAC address did not get reflected in the Config Tool database for IPX address. It still had the MAC address of the interface card that was replaced.
	xpand dumped core in send_commit_response() when template name was NULL.
	Formatting on interface with an IPX address IPKTS, IERRS, OPKTS, OERRS, and COLL was misaligned.
	10 Mb/s Ethernet with a gateway had a poor performance compared to a back-to-back configuration.
Problem due to "capture-effect" on Ethernet. Turning on the capture-effect avoidance bit in the 21140 on both host and gateway returns normal performance to system.
The software is identical in 1.3 and 2.0. Now the software says 2.0, not 1.3.
	SNMP rsRuleTable was not instrumented.
Added SNMP instrumentation of rsRuleTable. Added rsRuleName object to rule table.
	Dropping very small packets sometimes resulted in loss of large packets.
	IPSRD quit immediately after upgrading to first DIGITAL GIGAswitch/IP software build with LINK0 modification.
	IPSRD quit with large numbers (>30) of interfaces running distance vector routing protocols.
	Added fixes so that default traffic gets the appropriate rate shaping when coming from an IFMP-C client.
	Label leak occurred in some cases when default entries were added for IFMP-C.
	Default speed was set to 100 instead of a 10 after a full install through some types of NICs.
Setting the speed to 100 causes the collision light on the switch to come on. This causes problems for other hosts connected to the switch.
	A gateway with IFMP and PVC enabled stopped forwarding data after a flow was established.
A gateway with two new NICs stops forward traffic after a flow has been established. This happened when a PVC and an IFMP were used on the same gateway.
	Shared lib for partner customization of switch view.
1. Partitioned the switch code into two parts, one for current support of sv, the other for partner customer support including table view routines. 2. The new module is a shlib libsv_partner.so.1.0. 3. There is also a README.sv for history of switch view.
	/etc/overpw did not work (Did not think it was in single user mode).

---

---