Troubleshooting - Metasys - LIT-12013055 - Gateway/Router - Cisco Switch - 12.0

Cisco IE 2000 and IE 4010 Ethernet Switches for Metasys Networks Installation Instructions and Troubleshooting Guide

Product name
Cisco Switch
Document type
Troubleshooting Guide
Document number
Revision date

Use a copy of the Installation Sheet to assist you in troubleshooting. For more information, see Configuration files. If the contents do not seem obvious, sketch out a network diagram like the one drawn for the Example network section. You can mark physical connections, VLAN/subnet boundaries, static IP addresses, points where security features are applied, the paths over which you can ping devices, and so on.

Use the following actions to troubleshoot the Cisco IE 2000 switch:

  • For general failures, check the LED indicators.
  • If the switch indicates that it is not configured, check the SD card slot for the SD card. Verify the SD card contains a configuration file named config.text (case sensitive), and an operating system. The operating system is a large .bin file. For further information, see Table 1, Table 2, and Table 1.
  • Inspect the cables and connectors for damage or loose connections.
  • If the switch is a remote device, verify the device is powered on and operating correctly.
  • If the switch does not boot on, the switch may need to be replaced.

To reset a switch to the factory default setting, refer to

Table 1. Troubleshooting problems and solutions
Problem Solution
The LEDs on the port for the controller chain is unlit. Look at the installation sheet and verify that the switch port is configured for a chain. Make sure that the one end of the chain is plugged into the switch. Make sure that at least the first of the controllers is powered and connected. Attempt a discovery or ping to force traffic on the network. Make sure that the controllers’ ETH1 and ETH2 LEDs are blinking green, which indicates active communication.
The LEDs on the switch indicate that the ring is open.

Closed: one ring port blinking green, one port solid green.

Open: both ring ports blinking green.

Make sure that the two ends of the ring are plugged into two ring ports of the same ring. Verify port numbers on the installation sheet. For best practice use different color coded Ethernet cables for the different rings. Make sure that the cables are connected all the way around the ring. Make sure that all the controllers are powered. Make sure that the controllers’ ETH1 and ETH2 LEDs are blinking green. Blinking green indicates active communication. If a controller is connected on a port, the LED always shows an indication of traffic. Even if the controller is not sending anything, traffic is generated by the ring manager, which sends test messages into the ring ports.

The MRP manager may not be configured on the switch. On the switch’s command line interface, enter: show license. The expected status of the manager is License State: Active, In Use. The expected status of the client is License State: Active, Not in Use, EULA not accepted. If the manager is present but not accepted, enter the command: license right-to-use activate mrp-manager acceptEULA. However, the ordering system is set up to order the license with the switch.

The network engine cannot discover any controllers.

Verify that the BACnet port used in the switch Access Control Lists (ACLs) matches that specified in the wizard, is configured in the network engine , and is configured in the IP controllers. For example, all ports can be 47808, which is the standard port, or all can be a non-standard port, for example 47818, but all port settings must use the same value.

Note: The switch ACLs always allow 47808 because it is used when commissioning a new IP controller. However, the switch ACLs may additionally allow a non-standard BACnet port value.

Verify that the network engines IP address and network mask match the values that were specified in wizard input and installation sheet. For example, if the network mask is, then an input, or a similar number, is incorrect. Ping the network engines to verify that the address matches the Installation Sheet.

If the network engine is on a network segment containing many other third party BACnet/IP devices, the network engine may not be able to process the high number of broadcast replies. To determine the number of broadcast replies, use the Wireshark application to capture traffic on the network engine port.

I see IP controllers with IP addresses which do not match the subnets listed in the Installation Sheet. You may be able to discover the controllers at a 169.254 address, but not ping them at the expected address, for example a 172.x.x.x address. This means that the controllers' generated a self-assigned addresses, instead of obtaining them through DHCP. If the switch is running, wait five minutes. The controllers may renew their lease and obtain accurate IP addresses. To force another round of DHCP requests, cycle power to the controllers. If the controllers are configured to use static addresses, configure the controllers to use DHCP.
My laptop cannot see anything.

Verify that your laptop is connected to the maintenance port specified in the installation sheet. Verify that the laptop is configured for DHCP. Verify your laptop is assigned the laptop address specified for the switch in the Installation Sheet, and not a self-assigned address, for example one starting with 169.254. Verify that the LED on the switch port blinks green when you do something.

If you connect a different laptop to the switch maintenance port shortly after disconnecting the previous one, wait 10 minutes for the previous DHCP lease to expire.

I cannot access the switch. Check the installation sheet and verify that you specified the IP address of the switch's management interface in your ssh session. Use the switch console log on. the switch console uses a serial connection instead of an Ethernet connection.
The network engine cannot discover all of the controllers. To verify that all of the controllers have received DHCP addresses, in the switch’s command line interface, enter the following commands: show ip dhcp snooping bind, which shows the number of IP address leased.
I cannot move off the switch to reach other devices on the network.

You are not expected not have access to the full network, but you are expected to be able to access some other parts. To see neighboring switches, in the switch’s command line interface, enter the following command : show cdp neighbor. Draw a map showing how the switches are interconnected. Add information about the Metasys devices. Additionally, refer to the installation sheet saved to the SD cards. If IND is installed and configured to manage the BAS network, you can also refer to the Network Topology view in IND.

The switch is powered but does not perform any switching.

The switch may have an old version of the operating system, which is missing an important feature. From the switch’s command line interface, enter the following command: show version. The required version for an IE 2000 is 15.2(6)E1 or newer. The required version for an IE 41010 is 15.2(4)EC2 or newer. It is possible that a newer release may contain a bug. If you suspect that the operating system is the cause of the problem, ask the Field Support Center for the latest IOS version that has been tested with Metasys .

Look at the log files on the switch. From the switch’s command line interface, enter the following command: show log. Retention of the log data depends on the size of the buffer that is allocated. If it is too small, set up a syslog server on a computer with a large amount of free of disk space. You can use the wizard to redirect logging to a syslog server.

The switch my not have loaded the config.text file from the SD card. Connect a laptop to the local maintenance port of the switch specified in the IP Network Wizard Installation Sheet. Configure the laptop to obtain its IP address via Dynamic Host Configuration Protocol (DHCP). Verify that the laptop is assigned the laptop IP address corresponding to the switch as specified in the Installation Sheet, indicating that the switch has the correct config.text file loaded.

Learn how to use the switch’s debug facility. The command is debug [debug options], and to get a list of the options, enter debug ?.

Something is wrong on the aggregation switch. We use the Rapid Spanning Tree Protocol (RSTP) to create a redundant path between the access switches and the aggregation switch. From the switch’s command line interface, enter this command: show spanning-tree to see everything, or show spanning-tree vlan number to limit the scope to a particular VLAN, for example the BAS VLAN listed in the Installation Sheet. The expected response from the command is This bridge is the root, with a priority value of 8000 or lower.
The switch has intermittent problems. It may be helpful to install network monitoring software, for example Cisco's Industrial Network Director (IND). IND has capabilities that include mapping the physical connections between switches, reporting network statistics, and logging switch errors. IND runs on a network server and collects switch information using protocols including SNMP.