August 25, 2007

Customers that may benefit from this SNIB2 release have one or more of these:

• Windows "Vista" computers on the same LAN as unconfigured SNIB2s.
• Large, globalized installations with high traffic: more than 40,000 globalized events per hour. Multiply the number of access grant transactions per hour times the number of controllers on that SNIB2 port to determine the global traffic load. For example, 1200 access grants per hour times 35 controllers = 1200x35 = 42,000 globalized events per hour.
• The need to set an IP address before physically moving it to another controller.
• More than 31 addresses at 9600 bps.
• RS-232 connection, directly from Velocity to SNIB2 or over a leased-line or NET*MUX4 connection. (Not dial-up.)
• XBox upstream of a SNIB2

Defects fixed:

• Spurious "Duplicate IP Address" errors on Windows Vista computer on the same network as an unconfigured SNIB2

• No SNIB2 will ever report as "IP Address 0.0.0.0", even temporarily. An unconfigured SNIB2 will power up with a default IP address of 10.X.Y.Z where X, Y, Z are taken from the MAC address. For example, if the sticker on the SNIB2 says "CB0825", then the default IP address will be 10.203.8.37. (203 decimal = "CB" hex, etc.)

• We do not recommend stopping and starting the services during peak traffic times. When there are many events flowing though the system, it is difficult to get all of the controllers online - RP 267
• Large installations should reset the default value of the SNet host timeout (located in the Communications tab of the Controller Properties window in Velocity) from the default value of 10 seconds to a number higher than the number of controllers on the loop - RP 250, 256