6. Select the correct SNIB2.

You can identify which SNIB2 you need by its MAC address (id=). The MAC address for each SNIB2 is printed on a white label located on the left side of the SNIB2’s daughterboard. This label contains both a barcode and a six-digit number. This number is the second half of the MAC address.

7. Select the Get Configuration From Device button.
A list of variables specific to this SNIB2 appear in the ‘Variable Name’ window.
The three options used for SNIB2 configuration are: Device_IP_Address, Device_Port, and Device_Hostname, as shown in the following example:

8. From the ‘Variable Name’ pick list, select Device_IP_Address.
A screen like this appears:

9. In the ‘Value’ field, enter the IP address you require for this SNIB2.
A screen like this appears:

Consult your IT or Security Administrator for the proper address.

10. From the ‘Variable Name’ pick list, select Device_Port.

11. In the ‘Value’ field, enter a port address for this SNIB2.
All network ports possess an address used to identify the SNIB2’s physical port address. The default Velocity port is 10001.

12. From the ‘Variable Name’ pick list, select Device_Hostname.

13. In the ‘Value’ field, enter a name for this SNIB2.

14. Click the Send Configuration to Device button to send the information to the SNIB2.

15. Click the Search for SNIB2 button again to verify that the SNIB2 has correctly received the information.

Make sure to write down the address, port, and host name you assigned for each SNIB2.
These values are required when you configure the SNIB2 in Velocity.

After the installer has assigned the remote master SNIB2 an IP address and port, use Velocity on the host PC to identify it to the system. To do this:1.

1. Create a new XNET port, as specified in Steps 1–5 of “Configuring a Master SNIB2 in a Different Subnet”.

2. the The ‘Name’ field, enter the name you assigned to the SNIB2 using the SNIB2 Configuration Utility (Device_Hostname).

3. In the ‘IP Address’ field, enter the IP address you assigned to this device using the SNIB2 Configuration Utility (Device_IP_Address).

4. In the ‘Port’ field, enter the port number you assigned to this device using the utility (Device_Port). The default value is 10001.

5. Make sure the ‘Enable this Port’ box is checked.

6. Click OK.
This enables Velocity to find and monitor the remote SNIB2.

Resetting SNIB2 Encryption Keys

After Velocity creates the encryption keys required for secure Host-to-SNIB2 communication, it continues to use those keys. If for some reason you need to change these keys, there are several ways to do it.

Set SW2-1 to:	Procedures/Results
	Cycle power on controller. SNIB2 retains encryption keys. Controller retains setups. Press the blue Reset button on the controller until it resets. SNIB2 retains encryption keys. Controller loses setups. Download SNIB2 firmware through Velocity. SNIB2 retains encryption keys. Controller retains setups.
	Cycle power on controller. SNIB2 resets encryption keys. Controller retains setups. Press the blue Reset button on the controller until it resets. SNIB2 resets encryption keys. Controller loses setups. Download SNIB2 firmware through Velocity. SNIB2 resets encryption keys. Controller retains setups.
OFF or ON	Download CCM/CCMx firmware through Velocity. SNIB2 retains encryption keys. Controller retains setups.

After you have reset the encryption key to its default value (set SW2-1 to ON, recycle controller power, then reset SW2-1 to OFF), you must assign a new key so that Velocity and the master SNIB2 can talk to each other. To do this:1.

1. From the Velocity Administrator system tree, click and expand the DIGI*TRAC
   Configuration system folder until the master SNIB2 port you require appears.

1. Right-click on the SNIB2 port and select Properties.

The Port Properties dialog appears. The master SNIB2 Properties should look like
this:

3. Check the ‘Reset encryption’ box, and click OK.
This resets and syncs the encryption key at host SNIB2.

Resetting the SNIB2 to its Factory Default Values

Starting with version 6.42 of the SNIB2 firmware, a SNIB2 board can be reset to the factory default values for its encryption keys and network settings. To reset a SNIB2 board to have an IP address based on its unique MAC address, perform the following steps:1.

1. Set all four DIP switches in Switch Bank 2 to ON, and set all eight DIP switches in Switch Bank 3 to OFF.

1. Cycle power to the controller containing this SNIB2 board.

1. Watch the status LEDs on the SNIB2 board, to ensure that they display the Lamp Test start up pattern, and then display the following SNIB2/CCM Synchronization pattern:

4. Turn off power to the controller.
You can then reconfigure the SNIB2 board as needed, using its DIP switches and Velocity.

Controller and SNIB2 LED Diagnostics

The SNIB2 has three pairs of LEDs that show you how the SNIB2 is communicating with the Velocity Server.

Special Light Patterns: Start Up

This consists of the following light patterns during start up.

First comes the Lamp Test.

Power-up might include the first two patterns. If you’ve just reflashed the SNIB2, the sequence starts with the ones in the box.

This pattern is followed by:

This is the SNIB2/CCM Synchronization. This pattern repeats until the CCM and SNIB2 are synchronized. This light pattern should not persist longer than four minutes if there are no memory expansion boards on the controller.

Normal Operation

This table illustrates the various light patterns displayed during normal operation for both the master and subordinate SNIB2s:

For more about the status LEDs, especially for the patterns displayed during a firmware reflash or during data trouble, refer to the SNIB2 Troubleshooting Guide included with the SNIB2.

The SNIB2 also causes certain changes to the way the controller LEDs display as shown
below:

LED Configuration	Meaning
	The NET green LED is on; the NET red LED blinks intermittently depending on the amount of data being received from the host. This indicates the SNIB2 is working properly. The exact NET LED behavior depends on the controller version.
	Neither NET LED is blinking or only the NET green LED is on. In either case, the master SNIB2 is not communicating with the host. Check both your Ethernet connection and your Velocity port configuration.

Installing and Configuring the SNIB3

This section includes installation and configuration instructions for the SNIB3.

Because the SNIB3 board is sensitive to discharges of static electricity, you must observe the normal anti-static precautions (of using grounded wrist straps and anti-static devices) when handling the board.

Providing Surge Protection for a Master SNIB3

The current version of the SNIB3 board (which has a serial number of the form SNIB3- nnnnn) includes protection against extreme power surges, such as those caused by nearby lightning strikes, which might damage the Ethernet port. This surge protection is provided on a small printed circuit board which is mounted on the underside of the communications daughterboard. The presence of the surge protection is indicated by a jumper wire on the lower back of the SNIB3’s main board:

If a SNIB3 board does not have this jumper wire, then it is the initial version (sold only to a few US federal government agencies) which did not include surge protection. When using the initial version of the SNIB3 board (which has a serial number of the form SNIB3-S-nnnnn), surge protection must be provided for the master SNIB3 in each chain of connected controllers, using the Sankosha Guardian Net LAN-CAT5e-P+ surge protection device.

The specifications for this device are shown in the following table:

To be effective, this surge protection device (hereafter referred to as the “Guardian Net SPD”) must be properly installed so it is securely grounded to the controller’s metal enclosure. If this was not already done by Identiv, you can do it by performing the following steps.1.

1. Make sure the controller shows its CCM/CCMx firmware version as 7.5.37 or later.
   (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

1. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

1. If this controller still has a SNIB or SNIB2 board installed, remove it.

4. Install the SNIB3 board using the last connection on the EBIC5 ribbon cable, so it is the topmost board on this controller’s stack of expansion boards.

5. Connect one end of the green ground wire to the underside of the Guardian Net SPD (using its ground screw), and connect the other end of the green ground wire to one of the controller’s mounting screws.

• For a small controller cabinet (used for an M2, M16, MSP, Mx-2, Mx-4, or Mx-8), see Figure 1-76.

• For a large controller cabinet (used for an M8 or M64), see Figure 1-77.

Figure 1-76: Installing a Guardian Net SPD for a SNIB3 in a Small Controller Cabinet

6. Connect one end of the included Cat5 STP Ethernet cable to the Ethernet connector 1 RJ-45 jack on the SNIB3 board, and connect the other end of the cable to the RJ-45 jack marked EQUIP of the Guardian Net SPD.

7. Peel the protective covering off one side of the adhesive-backed Velcro strip, and press the exposed adhesive firmly against the appropriate side of the Guardian Net SPD, as shown in either Figure 1-76 or Figure 1-77.

8. Peel the protective covering off the other side of the adhesive-backed Velcro strip, and press the exposed adhesive firmly against either the:

• inner top side of a small controller cabinet, or the

• inner left side of a large controller cabinet.

9. Route the incoming Cat5 Ethernet cable through a knockout hole in the controller's cabinet and connect it to the RJ-45 jack marked LINE of the Guardian Net SPD.

Figure 1-77: Installing a Guardian Net SPD for a SNIB3 in a Large Controller Cabinet

10. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

11. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

Installing the SNIB3 in a Controller without a SNIB or a SNIB2

The SNIB3 can be used with most DIGI*TRAC or Mx series controllers, except for the Mx-1 (which has a compact plastic case without room for any expansion boards). If you want to use a SNIB3 with an Mx controller that has a SNIB2 daughterboard, be sure to see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.

To install the SNIB3 in a controller which does not already have a SNIB or a SNIB2, perform the following steps:1.

1. Make sure each controller in the sequence shows its CCM/CCMx firmware version as 7.5.37 or later. (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

1. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

1. Run a network cable to the controller. Make sure that:

• The network cable is in good condition and is Cat 5 at a minimum; otherwise, run new cable.

• The network cable is properly connected to the Velocity host through a hub or switch.

4. Set the DIP switches on the SNIB3 to its appropriate address and other parameters.
For details, see “Setting the DIP Switches on a SNIB3”.

5. If necessary, run RS-485 cable downstream from the master or slave SNIB3.
For details, see “RS-485 Cabling for SNIB3s”.

6. Connect the necessary cables and wires to the controller and the SNIB3, including:

• The EBIC5 ribbon cable between the SNIB3 and the controller

• The network cable into the SNIB3’s RJ-45 Ethernet 1 port

• Any RS-485 wires connecting to a downstream controller

7. Mount the SNIB3 on the expansion board standoffs and secure the screws.
For details, see “Mounting and Connecting Expansion Boards to the Controller”. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

98. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

Replacing a Controller’s SNIB or SNIB2 by a SNIB3

SNIB3s can communicate with SNIB2s, but they cannot communicate with original SNIBs. Any SNIBs existing on your security system must be replaced with SNIB2s or SNIB3s to use the faster speeds and greater encryption available with SNIB3s.

If you have an M1N controller (which has built-in SNIB functionality and does not support any expansion boards), you must replace it with a different model of controller.

If you want to use a SNIB3 with an Mx controller that has a SNIB2 daughterboard, be sure to see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.

To replace a controller’s existing SNIB or SNIB2 board by a SNIB3, perform the following steps:1.

1. Make sure the controller shows its CCM/CCMx firmware version as 7.5.37 or later.
   (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

1. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

1. Disconnect the cables and wires attached to the existing SNIB or SNIB2 board, including:

• The EBIC5 ribbon cable between the controller and the SNIB or SNIB2

• The network cable into the SNIB2’s RJ-45 Ethernet port

• Any RS-485 wires connecting to a downstream controller

4. Unscrew the expansion board standoff screws, and remove the existing SNIB or SNIB2 board.

5. If necessary, run a network cable to the controller. Make sure that:

• The network cable is in good condition and is Cat 5 at a minimum; otherwise, run
  new cable.

• The network cable is properly connected to the Velocity host through a hub or
  switch.

6. If necessary, run RS-485 cable downstream from the master or slave SNIB3.
For details, see “RS-485 Cabling for SNIB3s”. Note that in an RS-485 array that includes a SNIB3, the master must be a SNIB3.

7. Set the DIP switches on the SNIB3 to its appropriate address and other parameters.
For details, see “Setting the DIP Switches on a SNIB3”.

8. Connect the necessary cables and wires to the controller and the SNIB3, including:

• The EBIC5 ribbon cable between the SNIB3 and the controller

• The network cable into the SNIB3’s RJ-45 Ethernet 1 port

• Any RS-485 wires connecting to a downstream controller

9. Mount the SNIB3 on the expansion board standoffs and secure the screws.
For details, see “Mounting and Connecting Expansion Boards to the Controller”.

10. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

11. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

SNIB3 Network Configuration Options

Be aware that the SNIB3 is backwards compatible with the SNIB2, but not with the original SNIB. Each connected DIGITRAC or Mx controller must have its own SNIB2 or SNIB3 board installed. (The Mx-1 and Mx-1-ME controllers provide built-in SNIB3 functionality.)

The SNIB3 provides both an RS-485 port and a 10/100/1000BaseT RJ-45 Ethernet port, which enables you to choose the security network configuration that is most appropriate for your situation:

• If you are using only SNIB3 boards in all of your controllers, you can use either the XNET2 or the XNET3 protocol, and the downstream controllers in your security network can either be connected directly using the RJ-45 Ethernet port, or be connected to a master SNIB3 using the RS-485 port. (These options are shown in Figure 1-27, “Example Network Configurations Using Only SNIB3 Boards”).

• If you are using SNIB2 boards in some of your controllers, you cannot use the XNET3 protocol, and those controllers must be downstream slaves to a master SNIB3, connected using the RS-485 port. (This option is shown in Figure 1-28, “Example Network Configuration Using SNIB2 and SNIB3 Boards”).

• The SNIB3 also supports connections to the NET*MUX4, as explained in “Using NET*MUX4s with SNIB3s”.

Using Ethernet

The SNIB3’s RJ-45 Ethernet port provides high-speed TCP/IP communication over an Ethernet network between the Velocity host computer and the controller, using either IPv4 or IPv6. With multiple controllers, each one can have an independent communication path with a unique IP address, as shown in Figure 1-78:

Figure 1-78: Multiple Controllers Connected Directly to an Ethernet Network

After an Ethernet connection has been established between the Velocity host and the SNIB3, Velocity views the SNIB3 as an XNET3 port. By default, the host communicates with the Ethernet-connected SNIB3 using AES 256-bit encrypted XNET3. However, before the Velocity server can communicate over Ethernet with a SNIB3, the SNIB3 must be configured through Velocity, as explained in “Configuring a SNIB3”.

Using Serial RS-485

The SNIB3’s RS-485 port provides support for downstream serial connectivity, where the master of each chain must be a SNIB3 which is connected to the Velocity host using Ethernet. This master SNIB3 must be assigned the same address as the XBox port.

Velocity views the master SNIB3 as both a controller and an XBox residing on an XNET port. (Subsequent multidropped controllers in the sequence do not appear as XBox controllers.)

• If every controller has a SNIB3, the XNET3 protocol can be used.

• If any downstream controller has a SNIB2, the XNET2 protocol must be used, and the top speed is limited to 38,400 bps.

The SNIB3’s RS-485 connector enables wire runs of up to 4000 feet (1220 meters). Higher baud rates are more dependent on the number of twists per foot, so capacitance specifications must be strictly followed: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf .

An example of connecting downstream slave controllers using serial RS-485 is shown in Figure 1-79:

Figure 1-79: Downstream Slave Controllers Connected Using Serial RS-485

RS-485 Cabling for SNIB3s

As noted in Figure 1-79, the RS-485 cable linking the first (master) controller to the second (slave) controller in a multidropped RS-485 series must cross over the RX± and TX± wires. The cable for each subsequent slave controller is wired straight through. The details of this wiring is shown in Figure 1-80:

Figure 1-80: Wiring for RS-485 Chains

For an RS-485 chain, the maximum total cable run (from the master SNIB3 to the last downstream SNIB2 or SNIB3) is 4,000 feet (1,220 m). Higher baud rates are more dependent on the number of twists per foot, so capacitance specifications must be strictly followed: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf.

In general, communications become less robust as baud rates increase, wire gauge decreases, and distances increase. For this reason, it may not be possible to implement the higher baud rates supported by the SNIB3 if you have long wire runs or small wire gauges.

Using NET*MUX4s with SNIB3s

Like the SNIB2, the SNIB3 can be used with NET*MUX4s to enable a host PC running Velocity to program, monitor, and control up to 63 controllers on a port. This type of network configuration is shown in Figure 1-81:

Figure 1-81: Example Network Using NET*MUX4s with SNIB3s

Note that:

• The master SNIB3 is connected to the Velocity host using Ethernet.

• All of the cables leading into and out of a NET*MUX4 are crossovers, where the RX± and TX± wires must be swapped.

• Only two levels of NET*MUX4s are supported.

• Each connected controller must have its own SNIB3 board installed.
  The NET*MUX4 has a single RS-485 input and four RS-485 outputs to which a series of controllers or additional NET*MUX4s can be wired. However, the baud rate is limited to only 9600 bps.

Setting the DIP Switches on a SNIB3

Switch Bank 1 (SW1)

The SNIB3 includes three DIP switch banks. The first bank (SW1) and second bank (SW2) have four DIP switches each. The third bank (SW3) has eight DIP switches.

SNIB3s can be used throughout an RS-485 multidrop run; however, you must specify whether a specific SNIB3 is connected to a controller that is at the beginning, middle, or end of a run.

To do this, set S1-S4 on switch bank SW1 to either all ON or all OFF in this way:

Switch Bank 2 (SW2)

The second switch bank at SW2 has four switches, where S1 configures encryption properties and S4 configures the SNIB3’s location in the multidrop run. (S2 and S3 are used to reset a SNIB3 to its factory default settings.)

Switch Bank 3 (SW3)

Switch bank SW3 is used to specify the SNIB3 speed (S1-S2) and the SNIB3 address (S3-S8). The DIP switch settings for the speed are:

This controls the baud rate for the RS-485 multi-drop line. 57,600 and 115,200 bps are only available if your RS-485 cables are made from Cat5/Cat6 data grade wire. These speeds are not recommended for installations using:

• 18-gauge to 22-gauge shielded twisted-pair cable

• NET*MUX4s

Baud rates only apply to the RS-485 ports for SNIB2s and SNIB3s. The SNIB3’s Ethernet port is used for host-to-controller connections and runs at 10/100/1G BaseT speeds. All SNIB2s and SNIB3s in an RS-485 multi-drop sequence must be set to the same speed.

The remaining DIP switches (S3-S8) on SW3 set the SNIB3’s address, just like for the SNIB2:

Table 1-22: SNIB3 DIP Switch Address Settings

Configuring a SNIB3

The location of a SNIB3 on your network relative to the Velocity host will determine the method you must use for configuring that SNIB3:

• If the SNIB3 is on the same subnet, then you will configure it using Velocity. See “Using Velocity to Configure a SNIB3 on the Same Subnet”.

• If the SNIB3 is on a different subnet, then you will configure it using the SNIB Configuration Tool. See “Configuring a SNIB3 on a Different Subnet”.

Overview of Network Subnets

Each SNIB3 that is connected to the network using Ethernet (instead of being a downstream controller in a serial RS-485 chain) must be assigned a unique IP address so it can communicate with the Velocity host. The method for doing that depends on the location of that SNIB3 on your network relative to the Velocity host. The determining factor is whether they are both on the same subnet.

What is a subnet? Put simply, a subnet is any group of PCs and other devices, such as printers and scanners, connected by network cable to a network server, router, or hub. Anything behind the router/hub is considered part of the subnet. Anything beyond this router/hub is not part of the subnet. This concept is illustrated in Figure 1-82.

Figure 1-82: Example of Network Subnets

In Figure 1-82, the SNIB3 and its attached controller labeled 1 are located in the same subnet as the host PC (Subnet A). This SNIB3 can therefore be configured using Velocity;however, the SNIB3 and controller labeled 2 are located behind a different router, in a different subnet (Subnet B), and must be configured using the SNIB Configuration Tool.

Any number of computers and devices can be behind a hub or router, but for reasons of security and speed, a company network often incorporates many network servers, hubs, and routers. It is fairly common to find that each department within a company has its own server connected to its own hub and/or router. Routers and hubs not only find the quickest way to ferry packets of information between two points, but also can serve as a rudimentary firewall against potential intrusion.

Using Velocity to Configure a SNIB3 on the Same Subnet

If a SNIB3 is on the same subnet as the Velocity host, then you will configure it using Velocity. (If the SNIB3 is on a different subnet, then you will configure it using the SNIB Configuration Tool, as explained in “Configuring a SNIB3 on a Different Subnet”).
To configure a SNIB3 which is on the same network subnet as the Velocity host:1.

1. If you have not yet done so, install the SNIB3 board in the controller. For details, see either:

• “Installing the SNIB3 in a Controller without a SNIB or a SNIB2”,
  or

• “Replacing a Controller’s SNIB or SNIB2 by a SNIB3”.

2. If you have not yet done so, connect the controller to the network. For guidance, see “SNIB3 Network Configuration Options”.

3. In Velocity’s Administration window, double-click the Add New XNET Port item.

The resulting Port Properties dialog varies according to whether your network is using IPv4 or IPv6 addressing. For IPv4 addressing:

For IPv6 addressing:

4. On the Port Properties dialog:
a. If necessary, for the ‘Network Type’ select either the IPv4 or the IPv6 option.
b. For the ‘Protocol’, select either the XNET2 or XNET3 option.
c. Click the Search button.

The results depend on the options you specified for the Network Type and the Protocol. Here is an example for an IPv4 network using the XNET2 protocol:

Here is an example for an IPv6 network using the XNET3 protocol:

Note that although the SNIB2 and the SNIB3 support dynamic IP addressing using the Dynamic Host Configuration Protocol (DHCP) for both IPv4 and IPv6, Identiv strongly recommends using static or reserved IP addresses. For this reason, all SNIB2s and SNIB3s that have the value of Yes in the DHCP Enabled column should be changed to have assigned fixed IP addresses before they are added to the Velocity
network.

5. To change the settings for one of the displayed ports, perform these steps:
a. Double-click on an entry in the Searching dialog’s results table.

b. In the resulting SNIB Configuration dialog, make the necessary changes.

For example:

• If you need to change the Port number from the default value of 10001, then make sure to stay within the range from 1024 to 32767. Outside of this range, SNIB3 cannot communicate with the Velocity host.

• If you plan to assign a fixed address to this port, then clear the check box for the ‘DHCP Enabled (ignored for SNIB2)’ option.

c. When you are finished, click OK to close this dialog.

6. Back in the Searching dialog, click on the appropriate row to select the desired SNIB3 board, and click OK.

Velocity starts communicating with the specified SNIB3, and its port appears in the Ports folder within the Administration window.

Configuring a SNIB3 on a Different Subnet

If a SNIB3 is on a different subnet than the Velocity host, you will configure it using the SNIB Configuration Tool. (If the SNIB3 is on the same subnet, then you will configure it using Velocity, as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”).

To configure a SNIB3 which is on a different network subnet than the Velocity host:

1.If you have not yet done so, install the SNIB3 board in the controller. For details, see either:

• “Installing the SNIB3 in a Controller without a SNIB or a SNIB2”,

or

• “Replacing a Controller’s SNIB or SNIB2 by a SNIB3”.

2. If you have not yet done so, connect the controller to the network. For guidance, see “SNIB3 Network Configuration Options”.

3. If you have not yet done so, download the SNIB Configuration Tool to a PC which you will use to configure the SNIB3:

On that PC, download the SNIBConfigTool.exe file from the Identiv website. (Use your Web browser to go to theidentiv.com/support page, click the Support: Hirsch Products link, click the SNIB3 - Documents and Downloads link, and click on the link to download the SNIB Configuration Tool.)

4. Connect that PC to the same network subnet as the SNIB3 being configured.

5. Locate and double-click the SNIBConfigTool.exe file.

6. On the resulting SNIB Hunt and Configure window:

a. Select one of these options:

• All Devices in network, to search for all SNIB2s or SNIB3s on this network subnet. (If a SNIB2 or SNIB3 is currently logged on, this utility will not detect it.)

• Specific Device in network, to search for a specific SNIB2 or SNIB3 on this network subnet. If you select this option, enter a search term such as an IP address in the text field which appears after this option. (This option works for both IPv4 and IPv6.)

b. Click the Search button.
c. From the resulting list of previously-undetected SNIB2s or SNIB3s displayed in the Devices list, double-click on the entry for the desired SNIB3, so its information appears in the subsequent fields on this window.

Note that the Device_IP_Address, Device_Subnet_Mask, and Device_Default_Gateway fields are specific to IPv4. The Device_IPv6_Multicast_Address, Device_IPv6_Address, Device_IPv6_Prefix_Len, and Device_IPv6_Gateway fields are specific to IPv6.

Info
You can identify a SNIB3 by its MAC address (id=), which is printed on a white label attached to its RJ45 Ethernet connector. This label includes both a barcode (in QR code format) and the full MAC address (in small print).

d. Enter the values required for this SNIB3 in the relevant fields. For example:

• In the Device_Hostname field, enter the SNIB3 name that the Velocity host will use to identify this SNIB3.

• In the Device_Port field, enter the network port number for this SNIB3. If you need to change this from the default value of 10001, then make sure to stay within the range from 1024 to 32767. Outside of this range, SNIB3 cannot communicate with the Velocity host.

• Enter the necessary IP address in either the Device_IP_Address field (for IPv4) or in the Device_IPv6_Address field (for IPv6).

• If you follow our recommendation to use static or reserved IP addresses, then clear the check box for the Enable DHCP Mode option.

e. Click the Send to Device button, to send the updated values to this SNIB3.
f. Click the Search button again, to verify that the SNIB3 has correctly received the updated information.
g. Record this SNIB3’s device hostname, port number, and IP address.
You will need this information to finish configuring the SNIB3 in Velocity.
h. When you are finished, click the Close button.

Info

If you have a lot of SNIB3s to configure remotely, you should use a portable computer which has the SNIB Configuration Tool installed. This should enable the installer to do the job more rapidly. But make sure you are onsite when you do this, because a SNIB3 does not retain its IP address for more than 5 minutes after being unplugged from a controller. (If you were planning to program several SNIB3s using one controller then move them to other controllers at a remote site, you probably won’t have time before the IP address in each SNIB3 is lost.)

After you have used the SNIB Configuration Tool to assign the device hostname, port number, and IP address to a remote SNIB3, you must use Velocity to assign that SNIB3 to a new port.

To assign a remote SNIB3 to a new port on Velocity:1.

1. In Velocity’s Administration window, double-click the Add New XNET Port item.

The resulting Port Properties dialog varies according to whether your network is using IPv4 or IPv6 addressing. For IPv4 addressing:

For IPv6 addressing:

2. On the Port Properties dialog:
a. If necessary, for the ‘Network Type’ select either the IPv4 or the IPv6 option.
b. For the ‘Protocol’, select either the XNET2 or XNET3 option.
c. In the ‘Name’ field, enter the value you assigned as the Device_Hostname (when using the SNIB Configuration Tool).

d. In the ‘IP address’ field, enter the value you assigned as either the Device_IP_Address or the Device_IPv6_Address (when using the SNIB Configuration Tool).
e. In the ‘IP Port’ field, enter the value you assigned as the Device_Port (when using the SNIB Configuration Tool).
f. Make sure the ‘Enable this Port’ option is checked.
g. Click OK.

Velocity should then be able to find and monitor this remote SNIB3.

Resetting SNIB3 Encryption Keys

---

After Velocity creates the encryption keys required for secure Host-to-SNIB3 communication, it continues to use those keys. If for some reason you need to change these keys, there are several ways to do it.

Set SW2-1 to:	Procedures/Results
	Cycle power on controller. SNIB3 retains encryption keys. Controller retains setups. Press the blue Reset button on the controller until it resets. SNIB3 retains encryption keys. Controller loses setups. Download SNIB3 firmware through Velocity. SNIB3 retains encryption keys. Controller retains setups.
	Cycle power on controller. SNIB3 resets encryption keys. Controller retains setups. Press the blue Reset button on the controller until it resets. SNIB3 resets encryption keys. Controller loses setups. Download SNIB3 firmware through Velocity. SNIB3 resets encryption keys. Controller retains setups.

After you have reset the SNIB3’s encryption key to its default value (by setting SW2-1 to ON, recycling controller power, then resetting SW2-1 to OFF), you must perform the following steps to assign a new key:1.

1. In the Velocity Administration system tree, expand the DIGI*TRAC Configuration system folder until the master SNIB3 port you require appears.

2.

1. Right-click on that SNIB3 port, and select Properties from the pop-up menu.

3.

1. On the resulting Port Properties dialog, check the box for the ‘Reset encryption’ option, and then click OK.

This resets the encryption key at the Velocity host.

Resetting a SNIB3 to its Factory Default Values

---

A SNIB3 board can be reset to the factory default values for its encryption keys and network settings. To reset a SNIB3 board to have an IP address based on its unique MAC address, perform the following steps:1.

1. Set all four DIP switches in Switch Bank 2 to ON, and set all eight DIP switches in Switch Bank 3 to OFF.

2.

1. Cycle power to the controller containing this SNIB3 board.

3.

1. Watch the status LEDs on the SNIB3 board, to ensure that they display the Lamp Test start up pattern, and then display the following SNIB2/CCM Synchronization pattern:

4. Turn off power to the controller.
You can then reconfigure the SNIB3 board as needed, using its DIP switches and Velocity.

Controller and SNIB3 LED Diagnostics

---

The SNIB3 has three pairs of LEDs that show you how the SNIB3 is communicating with the Velocity Server.

Special Light Patterns at Startup

---

At startup, the following pattern may be observed:

This indicates the SNIB3/CCM Synchronization. This pattern repeats until the CCM and SNIB3 are synchronized. This light pattern should not persist longer than four minutes if there are no memory expansion boards on the controller.

Light Patterns for Normal Operations

---

This table illustrates the various light patterns displayed during normal operation for SNIB3s:

Like the SNIB2, the SNIB3 also causes certain changes to the way the controller LEDs display, as shown below:

LED Configuration	Meaning
	The NET green LED is on; the NET red LED blinks intermittently depending on the amount of data being received from the host. This indicates the SNIB3 is working properly. The exact NET LED behavior depends on the controller version.
	Neither NET LED is blinking, or only the NET green LED is on. In either case, the master SNIB3 is not communicating with the host. Check both your Ethernet connection and your Velocity port configuration.

For more information, see “Troubleshooting the Controller Using Status LEDs”.