Rugged Operating System (ROS™) v3.5 User Guide For use with: RS400 Release 3.5.
Copyright COPYRIGHT © 2008 RuggedCom Inc. ALL RIGHTS RESERVED Dissemination or reproduction of this document, or evaluation and communication of its contents, is not authorized except where expressly permitted. Violations are liable for damages. All rights reserved, particularly for the purposes of patent application or trademark registration. This document contains proprietary information, which is protected by copyright. All rights are reserved.
Table Of Contents Table Of Contents Table Of Contents.....................................................................................................................................3 Table Of Figures .......................................................................................................................................9 Preface ...................................................................................................................................................
Table Of Contents 1.14 DHCP Relay Agent (N/A for RMC30)......................................................................................48 1.15 Syslog .....................................................................................................................................49 1.15.1 Configuring Local Syslog.................................................................................................49 1.15.2 Configuring Remote Syslog Client .................................................
Table Of Contents 3.2.8 Resetting Ports..............................................................................................................109 3.3 Troubleshooting ....................................................................................................................109 4 Ethernet Statistics .........................................................................................................................111 4.1 Viewing Ethernet Statistics........................................
Table Of Contents 6.1.7 Forbidden Ports List ......................................................................................................171 6.1.8 VLAN-aware and VLAN-unaware operation modes......................................................171 6.1.9 GVRP (Generic VLAN Registration Protocol) ...............................................................172 6.1.10 QinQ (not supported in RS400 and RS8000/RS1600 families).....................................173 6.2 VLAN Applications .............
Table Of Contents 11 PPP over Modem ......................................................................................................................221 11.1 PPP over Modem Operation .................................................................................................221 11.1.1 Remote Dial-in For Monitoring ......................................................................................221 11.1.2 Router Concentration ....................................................................
Table Of Contents 14.3.4 14.3.5 14.3.6 Changing Values in a Table ..........................................................................................257 Setting Default Values in a Table ..................................................................................257 Using RSH and SQL .....................................................................................................258 Appendix A - SNMP MIB Support .............................................................................
Table Of Figures Table Of Figures Figure 1: Main Menu With Screen Elements Identified...........................................................................16 Figure 2: Log in to The Device with a Web Browser..............................................................................19 Figure 3: Log in to The Device with a Web Browser (secure login banner)...........................................20 Figure 4: Main Menu via Web Server Interface ........................................................
Table Of Figures Figure 48: WIN and TIN Form.................................................................................................................77 Figure 49: MicroLok Form.......................................................................................................................79 Figure 50: DNP Form..............................................................................................................................80 Figure 51: Mirrored Bits Table ...........................
Table Of Figures Figure 99: Spanning Tree Menu ...........................................................................................................146 Figure 100: Bridge RSTP Parameters Form.........................................................................................147 Figure 101: Port RSTP Parameter Table..............................................................................................150 Figure 102: Port RSTP Parameter Form ..................................................
Table Of Figures Figure 150: Port LLDP Parameters Form .............................................................................................216 Figure 151: LLDP Global Remote Statistics Form ................................................................................217 Figure 152: LLDP Neighbor Information Table .....................................................................................218 Figure 153: LLDP Statistics Table ..............................................................
Preface Preface This manual contains instructions, examples, guidelines, and general theory on how to use the Rugged Operating System (ROS™) management software. Supported Platforms ROS™ has been designed to work on many RuggedCom product hardware platforms. This ensures consistency of the user experience when migrating from one product model to another.
Preface • • • • RS400 Installation Guide RuggedCom Fiber Guide RuggedCom Wireless Guide White paper: Rapid Spanning Tree in Industrial Networks Applicable Firmware Revision This guide is applicable to ROS™ software revision v3.5.x. Firmware/User Guide Version Numbering System ROS has a three-digit version numbering system of the form X.Y.Z where each digit is a number starting from zero. The 'X.Y' digits represent the functional version of ROS whereas the 'Z' digit represents firmware patches.
Administration 1 Administration The Administration menu covers the configuration of administrative parameters of both device and network (local services availability, security methods employed, system identification and functionality related to the IP network): • • • • • • • • • • • • IP Address, Subnet Mask and Gateway Address (static or dynamically obtainable) Management VLAN Management Connection Inactivity Timeout TFTP Server Permissions System Identification Passwords Time and Date SNTP to keep the t
Administration 1.1.2 The Structure of the User Interface The user interface is organized as a series of menus with an escape to a command line interface (CLI) shell. Each menu screen presents the switch name (as proved by the System Identification parameter), Menu Title, Access Level, Alarms indicator, Sub-Menus and Command Bar. Sub-menus are entered by selecting the desired menu with the arrow keys and pressing the enter key. Pressing the escape key ascends to the parent menu.
Administration Typing a new value after pressing enter always erases the old parameter value. The left and right cursor keys can be used to position the edit point without erasing the old parameter value. The up and down cursor keys can be used to cycle through the next higher and lower values for the parameter. After the parameter has been edited, press enter again to change other parameters. When all desired parameters have been modified, press A to apply changes.
Administration get – upload from the switch and download to PC put – upload from PC and download to PC 1.3 The ROS™ Web Server Interface 1.3.1 Using a Web Browser to Access the Web Interface A web browser uses a secure communications method called Secure Socket Layer (SSL) to encrypt traffic exchanged with its clients. Web server guarantees that communications with the client is kept private. If client requires access via unsecure http port, it will be rerouted to the secure port.
Administration Figure 2: Log in to The Device with a Web Browser Enter the “admin” user name and the appropriate password for the admin user, and then click on the “LogIn” button. The switch is shipped with a default administrator password of “admin”. Once successfully logged in, the user will be presented with the main menu. If the user wants to hide device information from the login screen, the ‘Login Banner’ option in the System Identification menu must be set to ‘secure’. RS400 19 ROS™ v3.
Administration Figure 3: Log in to The Device with a Web Browser (secure login banner) ROS™ v3.
Administration 1.3.2 The Structure of the Web Interface The user interface is organized as a series of linked web pages. The main menu provides the links and allows them to be expanded to display lower level pages for a particular configuration system. Figure 4: Main Menu via Web Server Interface Each web page presents the switch name (as proved by the System Identification parameter), Menu Title link and user’s access name or Alarms link if any alarms are reported.
Administration Figure 5: Parameters Form Example Some menus will require you to create or delete new records of information. 1.3.4 Updating Statistics Displays You may click the refresh button to update statistics displays. ROS™ v3.
Administration 1.4 Administration Menu The Administration menu provides ability to configure network and switch administration parameters. RS400 23 ROS™ v3.
Administration Figure 6: Administration Menu ROS™ v3.
Administration 1.5 IP Interfaces These parameters provide the ability to configure IP connection parameters such as address, network, and mask. The user can configure an IP Interface for each subnet (VLAN). One of the interfaces is configured as management interface. IP services: TFTP server, SNMP server, Telnet server, SSH server, RSH server, Web server, authentication using RADIUS server, DHCP client, BOOTP client, DHCP relay agent will be available only via management interface.
Administration Figure 8: IP Interfaces Form Note: The IP address and mask configured for management VLAN are not changed when resetting all configuration parameters to defaults and will be assigned to default VLAN ID of 1. Changes to the IP address take effect immediately. All IP connections in place at the time of an address change will be lost. Type Synopsis: { VLAN } Default: VLAN Specifies the type of the interface for which this IP interface is created.
Administration DYNAMIC is a common case of dynamically assigned IP address. It switches between BOOTP and DHCP until it gets the response from the relevant server. Must be static for non management interfaces IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: 192.168.0.1 Specifies the IP address of this device. An IP address is a 32-bit number that is notated by using four numbers from 0 through 255, separated by periods. Only a unicast IP address is allowed which ranges from 1.0.
Administration 1.6 IP Gateways These parameters provide the ability to configure gateways. A maximum of 10 gateways can be configured. When both the Destination and Subnet fields are both 0.0.0.0 (displayed as blank space), the gateway is a default gateway. Figure 9: IP Gateways Form Destination Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: 0.0.0.0 Specifies the IP address of the destination device.
Administration 1.7 IP Services These parameters provide the ability to configure properties for IP services provided by the device. Figure 10: IP Services Form Inactivity Timeout Synopsis: 1 to 60 or { Disabled } Default: 5 min Specifies when the console will timeout and display the login screen if there is no user activity. A value of zero disables timeouts for console and Telnet users. For Web Server users maximum timeout value is limited to 30 minutes.
Administration Server access. DISABLED - disables read and write access to TFTP Server GET ONLY - only allows to read files via TFTP Server ENABLED - allows to read and write files via TFTP Server ModBus Address Synopsis: 1 to 254 or { Disabled } Default: Disabled Determines the Modbus address to be used for Management through Modbus. SSH Sessions Allowed Synopsis: 1 to 4 Default: 4 Limits the number of SSH sessions.
Administration 1.8 System Identification The system identification is displayed in the sign-on screen and in the upper left hand corner of all ROS™ screens. Figure 11: System Identification Form System Name Synopsis: Any 19 characters Default: System Name The system name is displayed in all ROS menu screens.
Administration 1.9 Passwords These parameters provide the ability to configure parameters for authorized and authenticated access to the device services (HMI via Serial Console, Telnet, SSH, RSH, Web Server). The access to the switch can be authorized and authenticated via RADIUS server, or using locally configured passwords, that are always related to the username and access level. Note that access via Serial Console is always going to be authorized first using local settings.
Administration Guest Username Synopsis: 15 character ascii string Default: guest Related password is in field Guest Password; view only, cannot change settings or run any commands. Guest Password Synopsis: 15 character ascii string Default: guest Related username is in field Guest Username; view only, cannot change settings or run any commands.
Administration 1.10 Time and Date Device time, date and time zone can be set via this form. The device can also be configured to periodically contact an (S)NTP server to correct for drift in the onboard clock. Each RuggedCom unit can act as a unicast SNTP server and/or SNTP client. The SNTP server will respond to the unicast SNTP requests received from the units where it’s address is configured as NTP Server Address. Server itself can be synchronized by higher level NTP server.
Administration UTC+5:30 (Calcutta, New Delhi), UTC+5:45 (Kathmandu), UTC+6:00 (Almaty, Dhaka), UTC+6:30 (Rangoon), UTC+7:00 (Bangkok, Hanoi), UTC+8:00 (Beijing, Hong Kong) UTC+9:00 (Seoul, Tokyo), UTC+9:30 (Adelaide, Darwin), UTC+10:00 (Melbourne, Sydney), UTC+11:00 (Magadan, New Caledonia), UTC+12:00 (Auckland, Fiji) } Default: UTC-0:00 (Lisbon, London) This setting allows for the conversion of UTC (Universal Coordinated Time) to local time. NTP Server Address Synopsis: ###.###.###.
Administration 1.11 SNMP Management ROS supports Simple Network Management Protocol Version 3 (SNMPv3). This protocol provides secure access to devices by a combination of authentication and encrypting packets over the network.
Administration Figure 15: SNMP User Form Name Synopsis: Any 32 characters Default: initial The name of the user. This is the User-based Security Model dependent security ID IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: The IP address of the user's SNMP management station if it is configured to receive traps and notifications.
Administration Priv Key Synopsis: 31 character ascii string Default: The secret encryption key (password) that must be shared with SNMP client 1.11.2 SNMP Security to Group Maps Entries in this table map configuration of security model and security name (user) into a group name, which is used to define an access control policy. Up to 32 entries can be configured.
Administration Default: The user name which is mapped by this entry to the specified group name. Group Synopsis: Any 32 characters Default: The group name to which the security model and name belong. This name is used as index to SNMPv3 VACM Access Table. 1.11.3 SNMP Access These parameters provide the ability to configurate access rights for groups.
Administration Figure 19: SNMP Access Form Group Synopsis: Any 32 characters Default: The group name to which the security model and name belong. This name is used as index to SNMPv3 VACM Access Table. SecurityModel Synopsis: { snmpV1, snmpV2c, snmpV3 } Default: snmpV3 In order to gain the access rights allowed by this entry, configured security model must be in use.
Administration NotifyViewName Synopsis: { noView, V1Mib, allOfMib } Default: noView This parameter identifies the MIB tree(s) to which this entry authorizes access for notifications. If the value is noView, then no access for notifications is granted. RS400 41 ROS™ v3.
Administration 1.12 RADIUS RADIUS (Remote Authentication Dial In User Service) is used to provide centralized authentication and authorization for network access. ROS assigns a privilege level of Admin, Operator or Guest to a user who presents a valid username and password. The number of users who can access the ROS server is ordinarily dependent on the number of user records which can be configured on the server itself.
Administration The vendor specific attribute is used to determine the access level from the server, which may be configured at the RADIUS server with following information: • • • • Vendor ID: Ruggedcom Inc.
Administration 1.12.4 Radius Server Configuration Figure 20: RADIUS Server summary Figure 21: RADIUS Server Form Server Synopsis: Any 8 characters Default: Primary This field tells whether this configuration is for a Primary or a Backup Server IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 ROS™ v3.
Administration Default: The RADIUS server IP Address. Auth UDP Port Synopsis: 1 to 65535 Default: 1812 The authentication UDP Port on RADIUS server. Auth Key Synopsis: 31 character ascii string Default: The authentication key shared with RADIUS server. It is used to encrypt any passwords that are sent between the switch and RADIUS server. RS400 45 ROS™ v3.
Administration 1.13 TACACS+ TACACS+ (Terminal Access Controller Access-Control System Plus) is a TCP-based access control protocol that provides authentication, authorization and accounting services to routers, network access servers and other networked computing devices via one or more centralized servers. It is based on, but is not compatible with, the older TACACS protocol.
Administration Figure 23: TACACS+ Server Form Server Synopsis: Any 8 characters Default: Primary This field tells whether this configuration is for a Primary or a Backup Server IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: The TACACS+ server IP Address. Auth TCP Port Synopsis: 1 to 65535 Default: 49 The authentication TCP Port on TACACS+ server. Auth Key Synopsis: 31 character ascii string Default: The authentication key shared with TACACS+ server.
Administration 1.14 DHCP Relay Agent (N/A for RMC30) DHCP Relay Agent is a device that forwards DHCP packets between clients and servers when they are not on the same physical LAN segment or IP Subnet. The feature is enabled if DHCP Server IP address and set of access ports are configured. DHCP Option 82 provides a mechanism for assigning IP Address based on location of the client device is in the network. Information about client’s location can be sent along with the DHCP request to the server.
Administration DHCP Client Ports Synopsis: Any combination of numbers valid for this parameter Default: None This parameter specifies ports where DHCP clients are connected. Examples: All - all ports of the switch can have DHCP clients connected. 2,4-6,8 - ports 2,4,5,6 and 8 can have DHCP clients connected 1.15 Syslog The syslog provides users the ability to configure local syslog and remote syslog.
Administration Syslog severity level - {EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUGGING}. 1.15.2 Configuring Remote Syslog Client Figure 26: Remote Syslog Client Form UDP Port Synopsis: 1025 to 65535 or { 514 } Default: 514 The local UDP port through which client sends information to server(s). 1.15.3 Configuring Remote Syslog Server Figure 27: Remote Syslog Server Table ROS™ v3.
Administration Figure 28: Remote Syslog Server Form IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: Syslog server IP Address. UDP Port Synopsis: 1025 to 65535 or { 514 } Default: 514 The UDP port number on which remote server listens. Facility Synopsis: { USER, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCA L7 } Default: LOCAL7 Syslog facility name - { USER, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7 }.
Administration 1.16 Troubleshooting Problem One I have configured the IP address and a gateway. I am pinging the switch but it is not responding. I am sure the switch is receiving the ping because it’s port LEDs are flashing and the statistics menu shows the pings. What is going on? Is the switch being pinged through a router? If so, the switch gateway address must be configured. The following figure illustrates the problem.
Serial Protocols 2 Serial Protocols RuggedCom devices support following serial protocols: • • • • • • • Raw Socket serial encapsulation Preemptive Raw Socket TCPModbus (client and server modes) DNP 3 Microlok WIN and TIN Mirrored Bits 2.1 Serial Protocols Overview Baud rates on serial interfaces can be configured in range of 100 to 230400 bps. A “turnaround” time is supported to enforce minimum times between messages sent out the serial port.
Serial Protocols • • • • TCP accept one dynamic connection from different IP address Dynamic connection activity timer controlled XON/XOFF flow control for permanent connection ‘Packetization’ trigger based on a full packet, a specific character or upon a timeout for each connection 2.1.
Serial Protocols 2.2 Serial Protocols Operation 2.2.1 Serial Encapsulation Applications 2.2.1.1 Character Encapsulation (Raw Socket) Character encapsulation is used any time a stream of characters must be reliably transported across a network. The character streams can be created by any type of device. The baud rates supported at either server need not be the same. If configured, the server will obey XON/XOFF flow control from the end devices. Figure 30: Character Encapsulation 2.2.1.
Serial Protocols If RuggedServer™ is used at the host end, it will wait for a request from the host, encapsulate it in an IP Datagram and send it to the remote side. There, the remote RuggedServer™ will forward the original request to the RTU. When the RTU replies the RuggedServer™ will forward the encapsulated reply back to the host end. RuggedServer™ maintains configurable timers to help decide if replies and requests are complete.
Serial Protocols 2.2.1.4 Preemptive Raw Socket Figure 33: Permanent and Dynamic Master Connection Support Most SCADA protocols are master/slave and support only a single master device. Preemptive Raw Socket offers the ability to have a multiple masters communicate to RTUs/IEDs in protocol independent manner. For example, the SCADA master polling device is the normal background process collecting data from the RTUs/IEDs on permanent TCP connection.
Serial Protocols 2.2.1.5 Use of Port Redirectors Port redirectors are PC packages that emulate the existence of communications ports. The redirector software creates and makes available these “virtual” COM ports, providing access to the network via a TCP connection. When a software package uses one of the virtual COM ports, a TCP connection request is sent to a remote IP address and IP port that has been programmed into the redirector. Some redirectors also offer the ability to accept connection requests.
Serial Protocols 2.2.2 Modbus Server and Client Applications The Modbus Server and Client applications are used to transport Modus requests and responses across IP networks. The Modbus Client application accepts Modbus polls from a master and determines the IP address of the corresponding RTU. The client then encapsulates the message in TCP respecting TCPModbus protocol, and forwards the frame to a Server Gateway or native TCPModbus RTU.
Serial Protocols Client Gateway Master Server Gateway RTU Transmission time from Master to Client Gateway Network transmission time 1 1a 2 3a 3b 4 Queuing time 5 Transmission time from Server Gateway to RTU 6 RTU "think" and transmission times to Server Gateway 7 Network transmission time 9a 8 9b 9c 9d Transmission time from Client Gateway to Master Time-out / Retransmissions complete, Exception sent Figure 35: Sources of Delay and Error in an End-to-End Exchange In step 1 the master is
Serial Protocols an exception to the originator. If sending exceptions has not been enabled, the Server Gateway will not send any response. 2.2.2.2 A Worked Example A network is constructed with two Masters and 48 RTUs on four Server Gateways. Each of the Masters is connected to a Client Gateway with a 115.2 Kbps line. The RTUs are restricted to 9600 bps lines. The network is Ethernet based and introduces an on average 3 ms of latency.
Serial Protocols 2.2.3 DNP 3.0, Microlok, TIN and WIN Applications RuggedServer™ supports a variety of protocols that specify source and destination addresses. A destination address specifies which device should process the data, and the source address specifies which device sent the message. Having both destination and source addresses satisfies at least one requirement for peer-to-peer communication because the receiver knows where to direct response.
Serial Protocols 2.2.3.2 Address Learning Address Learning for TIN Address learning is implemented for the TIN protocol and learned entries are viewable in Dynamic Device Address Table. Address Learning for TIN Mode 1 When a message with unknown source address is received from the IP network, it is learned on the IP address and IP port. If a message with the same source address is received from another IP address and/or IP port, the address will be relearned.
Serial Protocols All learned addresses will be kept in the Device Address Table until they are active. They will also be saved in non volatile memory and recovered if device reboots, so learning process does not have to be repeated because of, for example, accidental power brakeage. Aging timer is reset whenever message is received or sent to the specified address. This concept makes DNP protocol configurable with the minimum number of parameters: IP port, learning IP interface and aging timer. 2.2.3.
Serial Protocols 2.2.4 Transport Protocols For supported protocols, with exception of Modbus, either UDP datagram or TCP connection packets can be used to transport protocol data over the IP network. The Modbus data can be transported only using TCP connection, following TCPModbus protocol. UDP supports all the addressing modes of IP – unicast, multicast and broadcast. Therefore, if address learning is enabled, UDP broadcasts will be sent across the network. 2.2.4.
Serial Protocols 2.2.5 Force Half Duplex Mode of Operation A “force half duplex” mode of operation allows use of extensions that create echo loops (as optical loop topology that utilizes the RMC20 repeat mode function). Figure 37: Optical loop topology Figure 37 illustrates the optical loop topology that utilizes the RMC20 repeat mode function. The repeat function will optically re-transmit any data received on the optical receiver, in addition to any connected serial devices.
Serial Protocols 2.3 Serial Protocol Configuration and Statistics The Serial Protocols menu is accessible from the main menu Figure 38: Serial Protocols Menu RS400 67 ROS™ v3.
Serial Protocols 2.3.1 Serial Ports Figure 39: Serial Ports Table Figure 40: Serial Ports Form ROS™ v3.
Serial Protocols Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Name Synopsis: Any 15 characters Default: Port 1 A descriptive name that may be used to identify the device conected on that port. Protocol Synopsis: { None, RawSocket, ModbusServer, ModbusClient, DNP, WIN, TIN, MicroLok, MirroredBits,PreemptRawSocket } Default: None The serial protocol supported on this serial port.
Serial Protocols Default: 0 ms The amount of delay (if any) to insert between the transmissions of individual messages out the serial port. DSCP Synopsis: 0 to 63 Default: 0 DSCP - Differentiated Services Code Point, to set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.2 Raw Socket Figure 41: Raw Socket Table ROS™ v3.
Serial Protocols Figure 42: Raw Socket Form Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Pack Char Synopsis: 0 to 255 or { Off } Default: Off The character that can be used to force forwarding of accumulated data to the network. If a packetization character is not configured, accumulated data will be forwarded based upon the packetization timeout parameter.
Serial Protocols Default: TCP The network transport used to transport protocol data over IP network. Call Dir Synopsis: { In, Out, Both } Default: In Whether to accept an incoming connection, to place an outgoing connection, or to place outgoing connection and wait for incoming (both directions). This parameter is applicable only for TCP transport. Max Conns Synopsis: 1 to 64 Default: 1 The maximum number of allowed incoming TCP connections.
Serial Protocols 2.3.3 Preemptive Raw Socket Figure 43: Preemptive Raw Socket Table Figure 44: Preemptive Raw Socket Form RS400 73 ROS™ v3.
Serial Protocols Port Synopsis: 1 to 4 Default: 1 The port number as seen on the front plate silkscreen of the switch. Pack Char Synopsis: 0 to 255 or { Off } Default: Off The character that can be used to force forwarding of accumulated data to the network. If a packetization character is not configured, accumulated data will be forwarded based upon the packetization timeout parameter. Pack Timer Synopsis: 3 to 1000 Default: 10 ms The delay from the last received character until when data is forwarded.
Serial Protocols Timeout Synopsis: 10 to 3600 Default: 10 s The time in seconds that is allowed to dynamic master to be idle before it's connection is closed. The protocolo listens to the socket open to dymamic master, and if no data are received within this time, conneciton will be closed. 2.3.4 Modbus Server Figure 45: Modbus Server Table Figure 46: Modbus Server Form Port Synopsis: 1 to maximum port number RS400 75 ROS™ v3.
Serial Protocols Default: 1 The port number as seen on the front plate silkscreen of the switch. Response Timer Synopsis: 50 to 10000 Default: 1000 ms The maximum allowable time to wait for the RTU to start to respond. Auxiliary TCP Port Synopsis: 1024 to 65535 or { Disabled } Default: Disabled TCP Modbus Server always listens on TCP port 502. It may be additionally configured to listen on this auxiliary port number, accepting calls on both.
Serial Protocols Forward Exceptions Synopsis: { Disabled, Enabled } Default: Enabled When the Master polls for an unconfigured RTU or the remote Modbus Server receives a poll for an RTU which is not configured or is timing out, it returns an exception message. Enabling this feature forwards these messages to the Master as exception codes 10 (no path) and 11 (no response). Disable this feature if your Master is confused by these codes and would prefer to time-out when a failure occurs.
Serial Protocols TIN Mode: Synopsis: 1 to 2 Default: 1 TIN Protocol running mode. TIN Transport: Synopsis: { TCP, UDP } Default: UDP The network transport used to transport protocol data over IP network. WIN Transport: Synopsis: { TCP, UDP } Default: UDP The network transport used to transport protocol data over IP network. TIN IP Port Synopsis: 1024 to 65535 Default: 51000 The local port number on which TIN protocol listens for TCP connections or UDP datagrams.
Serial Protocols WIN DSCP Synopsis: 0 to 63 Default: 0 DSCP - Differentiated Services Code Point, to set the DS byte in the IP header. DS byte setting is supported in the egress direction only. TIN DSCP Synopsis: 0 to 63 Default: 0 DSCP - Differentiated Services Code Point, to set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.
Serial Protocols Default: 0 DSCP - Differentiated Services Code Point, to set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.8 DNP Figure 50: DNP Form Transport Synopsis: { TCP, UDP } Default: TCP The network transport used to transport protocol data over IP network. IP Port Synopsis: 1024 to 65535 Default: 20000 A local port number on which protocol listens for UDP datagrams. Learning Synopsis: ###.###.###.
Serial Protocols Aging Timer Synopsis: 60 to 1000 Default: 300 s The time of communication inactivity after which a learned DNP address is removed from the device address table. Entries in Link Statistics Table with the aged address will be kept until statistics is cleared. Link Stats Synopsis: { Disabled, Enabled } Default: Enabled Enables links statistics collection for protocol. DSCP Synopsis: 0 to 63 Default: 0 DSCP - Differentiated Services Code Point, to set the DS byte in the IP header.
Serial Protocols Figure 52: Mirrored Bits Form Port Synopsis: 1 to 4 Default: 1 The port number as seen on the front plate silkscreen of the switch. Transport Synopsis: { TCP, UDP } Default: UDP The network transport used to transport protocol data over IP network. Loc Port Synopsis: 1024 to 65535 Default: 61001 The local IP port to use when listening for an incoming connection or UDP data. Rem Port Synopsis: 1 to 65535 Default: 61000 The remote TCP port to use when placing an outgoing connection.
Serial Protocols For both, outgoing and incoming connections enabled (client or server), this is remote IP address where to place an outgoing TCP connection request or from which to accept calls. Link Stats Synopsis: { Disabled, Enabled } Default: Enabled Enables links statistics collection for protocol. 2.3.10 Device Addresses Up to 1024 entries can be created in this table. Figure 53: Device Address Table RS400 83 ROS™ v3.
Serial Protocols Figure 54: Device Address Form Protocol Synopsis: { ModbusServer, ModbusClient, DNP, WIN, TIN, MicroLok } Default: ModbusServer The serial protocol supported on this serial port. Address Synopsis: Any 31 characters Default: The destination (source) device address. Could be local or remote. Local address is the address of the device connected to the serial port on this device, and serial port must be configured.
Serial Protocols Default: Unknown The serial port to which device is attached. If the device with this address is attached to the serial port of remote host, the value of this parameter is 'Unknown'. Name Synopsis: Any 16 characters Default: The addressed device name. 2.3.11 Dynamic Device Addresses This table provides ability to view TIN protocol’s device addresses from remote locations that were learned dynamically.
Serial Protocols Protocol Synopsis: { TIN } The serial protocol supported on this serial port. Address Synopsis: Any 31 characters The remote device address. Location Synopsis: ###.###.###.### where ### ranges from 0 to 255 The IP Address of the remote host. IP Port Synopsis: 1 to 65535 The remote port number through which remote device sent a UDP datagram or TCP connection is established. RSSI Synopsis: -128 to 0 or { N/A } The signal strength indicator received from wayside data radio.
Serial Protocols Figure 58: Links Statistics Form Protocol Synopsis: { None, RawSocket, ModbusServer, ModbusClient, DNP, WIN, TIN, MicroLok } The serial protocol supported by devices that create this link. Local Address Synopsis: Any 27 characters The address of the device connected to the serial port on this device. Remote Address Synopsis: Any 35 characters The address of the device connected to the remote host's serial port.
Serial Protocols Figure 59: Connection Statistics Table Remote IP Synopsis: ###.###.###.### where ### ranges from 0 to 255 The remote IP address of the connection. Remote Port Synopsis: 0 to 65535 The remote port number of the connection. Local Port Synopsis: 0 to 65535 The local port number of the connection. Rx Packets Synopsis: 0 to 4294967295 The number of received packets on the connection. Tx Packets Synopsis: 0 to 4294967295 The number of packets transmitted on the connection. 2.3.
Serial Protocols Figure 60: Serial Port Statistics Table Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch. Protocol Synopsis: Any 15 characters The serial protocol supported on this serial port. Rx Chars Synopsis: 0 to 4294967295 The number of received characters. Tx Chars Synopsis: 0 to 4294967295 The number of transmitted characters. Rx Packets Synopsis: 0 to 4294967295 The number of received packets.
Serial Protocols 2.3.15 Clearing Serial Port Statistics This command clears serial ports statistics and links statistics. Figure 61: Clear Serial Port Statistics Form This command clears statistics on one or more serial ports. Ports to clear statistics will be chosen checking out required boxes. 2.3.16 Resetting Serial Ports Figure 62: Reset Serial Port(s) Form Ports to reset will be chosen checking out required boxes. ROS™ v3.
Serial Protocols 2.4 Troubleshooting Problem One I configured a Serial IP to use TCP transport ( in or out connection request direction) but nothing seems to be happening. What is going on? Ensure that an Ethernet port link is up. The peer may not be requesting (accepting) connections. The Connection Statistics Table will display whether the connection is active or not. The peer may not be sending data.
Ethernet Ports 3 Ethernet Ports ROS™ Ethernet port control provides you with the following features: • • • • • • • Configuring port physical parameters Configuring link alarms/traps for the port Configuring port rate limiting Using Port Mirroring Viewing the status of ports Resetting all or some ports Using Link-Fault-Indication (LFI) 3.1 Controller Protection Through Link-Fault-Indication (LFI) Modern industrial controllers often feature backup Ethernet ports used in the event of a link failure.
Ethernet Ports 1. Auto-Negotiating links (100Base-TX,1000Base-T,1000Base-X) - auto-negotiation built-in feature (a special flag called Remote Fault Indication is set in the transmitted autonegotiation signal) 2. 100Base-FX links - Far–End-Fault-Indication (FEFI) is a standard feature defined by the IEEE 802.3 standard for this link type. The feature includes: a. Transmitting FEFI - transmitting modified link integrity signal in case a link failure is detected, i.e.
Ethernet Ports 3.2 Ethernet Ports Configuration and Status The Ethernet Ports menu is accessible from the main menu. Figure 64: Ethernet Ports Menu RS400 95 ROS™ v3.
Ethernet Ports 3.2.1 Port Parameters Figure 65: Port Parameters Table Figure 66: Port Parameters Form ROS™ v3.
Ethernet Ports Port Synopsis: 1 to maximum port number Default: 0 The port number as seen on the front plate silkscreen of the switch. Name Synopsis: Any 15 characters Default: Not installed A descriptive name that may be used to identify the device conected on that port. Media Synopsis: { 100TX, 10FL, 100FX, 1000X, 1000T } The type of the port media. State Synopsis: { Disabled, Enabled } Default: Enabled Disabling a port will prevent all frames from being sent and received on that port.
Ethernet Ports When the port is half-duplex it is accomplished using 'backpressure' where the switch simulates collisions causing the sending device to retry transmissions according to the Ethernet backoff algorithm. When the port is full-duplex it is accomplished using PAUSE frames which causes the sending device to stop transmitting for a certain period of time.
Ethernet Ports 3.2.2 Port Rate Limiting Figure 67: Port Rate Limiting Table Figure 68: Port Rate Limiting Form Port Synopsis: 1 to maximum port number RS400 99 ROS™ v3.
Ethernet Ports Default: 1 The port number as seen on the front plate silkscreen of the switch. Ingress Limit Synopsis: { Disabled, 128 Kbps, 256 Kbps, 512 Kbps, 1 Mbps, 2 Mbps, 4 Mbps, 8 Mbps } Default: 1 Mbps The rate at which received frames (of the type described by the ingress frames parameter) will start to be discarded by the switch. Ingress Frames Synopsis: { Broadcast, Multicast, All } Default: Broadcast This parameter specifies the types of frames to rate-limit on this port.
Ethernet Ports Figure 69: Port Mirroring Form Port Mirroring Synopsis: { Disabled, Enabled } Default: Disabled Enabling port mirroring causes all frames received and transmitted by the source port(s) to be transmitted out of the target port. Source Port Synopsis: 1 to maximum port number Default: 1 The port(s) being monitored. Target Port Synopsis: 1 to maximum port number Default: 1 The port where a monitoring device should be connected. RS400 101 ROS™ v3.
Ethernet Ports 3.2.4 Link Detection Options Figure 70: Link Detection Form Fast Link Detection Synopsis: { Off, On, On_withPortGuard } Default: On_withPortGuard This parameter provides system protection against a faulty end device generating an improper link integrity signal. When a faulty end device or a mismatched fiber port is connected to the unit, a large number of continuous link state changes can be reported in a short period of time.
Ethernet Ports OFF - Turning this parameter OFF will disable Fast Link Detection completely. The switch will need a longer time to detect a link failure. This will result in a longer network recovery time of up to 2s. This option should only be used if fast link failure detection is not needed. Note When Fast Link Detection is enabled, the system prevents link state change processing from consuming all available CPU resources.
Ethernet Ports Figure 73: PoE Parameters Form Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Admin Synopsis: { Disabled, Enabled } Default: Enabled This parameter allows to enable or disable supplying power by the port. Powered Synopsis: { No, Yes } Whether or not power is currently supplied by the port. Class Synopsis: 0 to 65535 PoE Class value that defines the minimum supplied power level. See IEEE 802.1af standard for details.
Ethernet Ports Current Synopsis: 0 to 65535 Supplied current level. 3.2.6 EoVDSL Parameters (when applicable) From the switching functionality point of view Ethernet-over-VDSL (EoVDSL) ports function the same way as 10/100Base-TX Ethernet ports. The VDSL interface is only used as a media to transfer regular Ethernet frames. However, the link throughput and the link establishment procedure are different.
Ethernet Ports Figure 74: Accessing EoVDSL Parameters Figure 75: EoVDSL Parameters Table ROS™ v3.
Ethernet Ports Figure 76: EoVDSL Parameters Form Port Synopsis: 1 to maximum port number Default: Depends on the particular product (3 for RS920L, 7 for RS930L, 9 for RS9XX, etc.) The port number as seen on the front plate silkscreen of the switch. Type Synopsis: { Univ, LR } The type of VDSL port. Supported types: Universal and Long Reach. Mode Synopsis: { Master, Slave } Default: Master Specify if the port should operate as a VDSL Master or Slave.
Ethernet Ports the given media. If this parameter is set to a fixed value, the system will only try to achieve the specified rate. NOTE: depending on the actual physical link, it may not be possible to achieve the configured fixed bit rate. In that case the system will fall back to some default low-rate link just to provide basic connectivity. Link Synopsis: { Down, Scan, Up } Status parameter - indicates if optimal VDSL link is established.
Ethernet Ports Name Synopsis: Any 15 characters A descriptive name that may be used to identify the device connected on that port. Link Synopsis: { ----, ----, Down, Up } The port's link status. Speed Synopsis: { ---, 10, 100, 1000 } The port's current speed. Duplex Synopsis: { ----, Half, Full } The port's current duplex status. 3.2.8 Resetting Ports This command performs a reset of the specified Ethernet ports.
Ethernet Statistics 4 Ethernet Statistics ROS™ Ethernet statistics provides you with the following abilities: • • • • • • • Viewing basic Ethernet statistics Viewing and clearing detailed Ethernet statistics Configuring RMON History control Viewing collected RMON History samples Configuring RMON Alarms Configuring RMON Events Viewing collected RMON Event logs The Ethernet Statistics menu is accessible from the main menu. Figure 78: Ethernet Port Statistics Menu RS400 111 ROS™ v3.
Ethernet Statistics 4.1 Viewing Ethernet Statistics This table provides basic Ethernet statistics information which is reset periodically, every few seconds. This traffic view is useful when the origin and destination of a traffic flow needs to be determined. Figure 79: Ethernet Statistics Table Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch. State Synopsis: { ----, Down, Up } The port link status.
Ethernet Statistics InPkts Synopsis: 0 to 4294967295 The number of received good packets (Unicast+Multicast+Broadcast) and dropped packets. OutPkts Synopsis: 0 to 4294967295 The number of transmitted good packets. ErrorPkts Synopsis: 0 to 4294967295 The number of any type of erroneous packet. RS400 113 ROS™ v3.
Ethernet Statistics 4.2 Viewing Ethernet Port Statistics Ethernet port statistics provide a detailed view of the traffic. This is useful when the exact source of error or traffic mix needs to be determined. Figure 80: Ethernet Port Statistics Table ROS™ v3.
Ethernet Statistics Figure 81: Ethernet Port Statistics Form Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch. RS400 115 ROS™ v3.
Ethernet Statistics InOctets Synopsis: 0 to 18446744073709551615 The number of octets in received good packets (Unicast+Multicast+Broadcast) and dropped packets. OutOctets Synopsis: 0 to 18446744073709551615 The number of octets on a transmitted good packets. InPkts Synopsis: 0 to 18446744073709551615 The number of received good packets (Unicast+Multicast+Broadcast) and dropped packets. OutPkts Synopsis: 0 to 18446744073709551615 The number of transmitted good packets.
Ethernet Statistics 4. Packet has invalid CRC. Jabbers Synopsis: 0 to 4294967295 The number of packets which meet all the following conditions: 1. Packet data length is greater that 1536 octets. 2. Packet has invalid CRC. Collisions Synopsis: 0 to 4294967295 The number of received packets for which Collision Event has been detected. LateCollisions Synopsis: 0 to 4294967295 The number of received packets for which Late Collision Event has been detected.
Ethernet Statistics OutMulticasts Synopsis: 0 to 18446744073709551615 The number of transmitted Multicast packets. This does not include Broadcast packets. OutBroadcasts Synopsis: 0 to 18446744073709551615 The number of transmitted Broadcast packets. UndersizePkts Synopsis: 0 to 18446744073709551615 The number of received packets which meet all the following conditions: 1. Packet data length is less than 64 octets. 2. Collision Event has not been detected. 3. Late Collision Event has not been detected. 4.
Ethernet Statistics 4.3 Clearing Ethernet Port Statistics Figure 82: Clear Ethernet Port Statistics Form This command clears Ethernet ports statistics for one or more Ethernet ports. Ports will be chosen by checking out required boxes. RS400 119 ROS™ v3.
Ethernet Statistics 4.4 Remote Monitoring (RMON) The RuggedSwitch™ Remote Monitor (RMON) package provides the following capabilities: • • The ability to collect and view historical statistics in order to review performance and operation of Ethernet ports. The ability to record a log entry and/or generate an SNMP trap when the rate of occurrence of a specified event is exceeded. 4.4.
Ethernet Statistics Figure 84: RMON History Controls Form Index Synopsis: 1 to 65535 Default: 1 The index of this RMON History Control record. Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Requested Buckets Synopsis: 1 to 4000 Default: 50 The maximum number of buckets requested for this RMON collection history group of statistics. The range is 1 to 4000. The default is 50.
Ethernet Statistics Owner Synopsis: Any 127 characters Default: Monitor The owner of this record. It is suggested to start this string with the word 'monitor'. 4.4.2 RMON History Samples History samples for a particular record in the RMON History Control Table are displayed by selecting a particular record and view option. The index of the record will be included in the resulting menu title of the sample screen. The table will present a series of samples.
Ethernet Statistics Figure 86: RMON History Samples Form Sample Synopsis: 0 to 4294967295 The sample number taken for this history record. StartTime Synopsis: DDDD days, HH:MM:SS The system elapsed time when started interval over which this sample was measured DropEvents Synopsis: 0 to 4294967295 The number of received packets that are dropped due to lack of receive buffers. InOctets Synopsis: 0 to 4294967295 RS400 123 ROS™ v3.
Ethernet Statistics The number of octets in good packets (Unicast+Multicast+Broadcast) and dropped packets received. InPkts Synopsis: 0 to 4294967295 The number of good packets (Unicast+Multicast+Broadcast) and dropped packets received. InBroadcasts Synopsis: 0 to 4294967295 The number of good Broadcast packets received. InMulticasts Synopsis: 0 to 4294967295 The number of good Multicast packets received.
Ethernet Statistics 2. Packet has invalid CRC. Collisions Synopsis: 0 to 4294967295 The number of received packets for which Collision Event has been detected. Utilization Synopsis: 0 to 4294967295 The best estimate of the mean physical layer network utilization on this interface during this sampling interval (hundredths of percent) 4.4.3 RMON Alarms RMON Alarms table configures the switch to examine the state of a specific statistic variable.
Ethernet Statistics Figure 87: The Alarm Process There are two methods to evaluate a statistic in order to determine when to generate an event; these are the delta and absolute methods. For most statistics (such as line errors) it is appropriate to alarm when a rate is exceeded. The alarm record defaults to the “delta” measurement method, which examines changes in a statistic at the end of each measurement period.
Ethernet Statistics Figure 89: RMON Alarms Form Index Synopsis: 1 to 65535 Default: 2 The index of this RMON Alarm record. Variable Synopsis: SNMP Object Identifier - up to 39 characters Default: ifOutOctets.2 The SNMP object identifier (OID) of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type INTEGER (INTEGER, Integer32,Counter32, Counter64, Gauge, or TimeTicks) may be sampled. A list of objects can be printed using shell command 'rmon'.
Ethernet Statistics Default: 11800 A threshold for the sampled variable. When the current sampled variable value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this record is created is greater than or equal to this threshold and the associated startup alarm is equal to 'rising'.
Ethernet Statistics corresponding entry in the Event Table, then no association exists. In particular, if this value is zero, no associated event will be generated. Owner Synopsis: Any 127 characters Default: Monitor The owner of this record. It is suggested to start this string with the word 'monitor'. 4.5 RMON Events The RMON Events Table stores profiles of behavior used in event logging. These profiles are used by RMON Alarm records to send traps and log events.
Ethernet Statistics Figure 91: RMON Events Form Index Synopsis: 1 to 65535 Default: 2 The index of this RMON Event record. Type Synopsis: { none, log, snmpTrap, logAndTrap } Default: logAndTrap The type of notification that the probe will make about this event. In the case of 'log', an entry is made in the RMON Log table for each event. In the case of snmp_trap, and SNMP trap is sent to one or more management stations.
Ethernet Statistics Owner Synopsis: Any 127 characters Default: Monitor The owner of this event record. It is suggested to start this string with the word 'monitor'. 4.6 RMON Event Log Event logs for a particular record in the RMON Events Table can be viewed by selecting a particular record and view option. The index of the record will be included in the resulting menu title of the logs screen. Figure 92: RMON Event Log Table RS400 131 ROS™ v3.
Ethernet Statistics Figure 93: RMON Event Log Form Log Synopsis: 0 to 4294967295 The index (log) taken for this log record. LogTime Synopsis: DDDD days, HH:MM:SS The system elapsed time when this log was created. LogDescription Synopsis: Any 49 characters The description of the event that activated this log entry. ROS™ v3.
Spanning Tree 5 Spanning Tree The RuggedSwitch™ family of Ethernet switches provide the latest in IEEE standard Spanning Tree functionality, including: • • • • • • • • • Industry standard support of Rapid Spanning Tree (802.1D-2004), which features a compatibility mode with legacy STP (802.1D-1998) Industry standard support of Multiple Spanning Trees (802.1s and 802.1Q-2003), which is interoperable with both RSTP and legacy STP.
Spanning Tree • RSTP offers edge port recognition, allowing ports at the edge of the network to forward frames immediately after activation while at the same time protecting them against loops. While providing much better performance than STP, IEEE 802.1w RSTP still required up to several seconds to restore network connectivity when a topology change occurred. A revised and highly optimized RSTP version was defined in the IEEE standard 802.1D-2004 edition. IEEE 802.
Spanning Tree The learning state is entered when the port is preparing to play an active part in the network. The port learns addresses in this state but does not participate in frame transfer. In a network of RSTP bridges the time spent in this state is usually quite short. RSTP bridges operating in STP compatibility mode will spend 6 to 40 seconds in this state. After “learning” the bridge will place the port in the forwarding state.
Spanning Tree the bridge and will become active if that port fails. The backup port does not participate in the network. 5.1.2 Edge Ports A port may be designated an edge port if it is directly connected to an end station. As such, it cannot create bridging loops in the network and can thus directly transition to forwarding, skipping the listening and learning stages. Edge ports that receive configuration messages immediately lose their edge port status and become normal spanning tree ports.
Spanning Tree when the designer is not too concerned with the resultant topology as long as connectivity is assured. Manual configuration is useful when the exact topology of the network must be predictable under all circumstances. The path cost can be used to establish the topology of the network exactly as the designer intends. STP vs. RSTP Costs The IEEE 802.1D-1998 specification limits port costs to values of 1 to 65536. It recommends that a path cost corresponding to the 1x109 / link speed be used.
Spanning Tree 5.2 MSTP Operation The Multiple Spanning Tree (MST) algorithm and protocol provide greater control and flexibility than RSTP and legacy STP. MSTP (Multiple Spanning Tree Protocol) is an extension of RSTP whereby multiple spanning trees may be maintained on the same bridged network. Data traffic is allocated to one or another spanning tree by mapping one or more VLANs onto it.
Spanning Tree Each MSTI has a topology that is independent of every other. Data traffic originating from the same source and bound to the same destination but on different VLANs on different MSTIs may therefore travel a different path across the network. IST An MST region always defines an IST (Internal Spanning Tree). The IST spans the entire MST region, and carries all data traffic that is not specifically allocated (by VLAN) to a specific MSTI. The IST is always computed and is defined to be MSTI zero.
Spanning Tree 5.2.2.2 Port Roles: Each port on an MST bridge may have more than one role depending on the number and topology of spanning tree instances defined on the port. CIST Port Roles • • • The Root Port provides the minimum cost path from the bridge to the CIST Root via the CIST Regional Root. If the bridge itself happens to be the CIST Regional Root, the Root Port is also the Master Port for all MSTIs (see below), and provides the minimum cost path to a CIST Root located outside the region.
Spanning Tree 5.2.3 Benefits of MSTP Despite the fact that MSTP is configured by default to arrive automatically at a spanning tree solution for each configured MSTI, advantages may be gained from influencing the topology of MSTIs in an MST region. The fact that the Bridge Priority and each port cost are configurable per MSTI (see sections 5.4.4 and 5.4.5) makes it possible to control the topology of each MSTI within a region.
Spanning Tree 5.2.4 Implementing MSTP on a Bridged Network It is recommended that the configuration of MSTP on a network proceed in the sequence outlined below. Naturally, it is also recommended that network analysis and planning inform the steps of configuring the VLAN and MSTP parameters in particular. Begin with a set of MSTP-capable Ethernet bridges, and MSTP disabled. For each bridge in the network: 1. Configure and enable RSTP (see sections 5.4.1 and 5.4.2).
Spanning Tree 5.3 RSTP Applications 5.3.1 RSTP in Structured Wiring Configurations RSTP allows you to construct structured wiring systems in which connectivity is maintained in the event of link failures. For example a single link failure of any of links A through N in Figure 96 would leave all the ports of bridges 555 through 888 connected to the network. Figure 96: Example of a Structured Wiring Configuration Design Considerations for RSTP in Structured Wiring Configurations 1.
Spanning Tree notifications in the network. Ports with half duplex/shared media restrictions require special attention in order to guarantee that they do not cause extended failover/recovery times. 4. Choose the root bridge and backup root bridge carefully. The root bridge should be selected to be at the concentration point of network traffic. Locate the backup root bridge adjacent to the root bridge.
Spanning Tree Design Considerations for RSTP in Ring Backbone Configurations 1. Select the design parameters for the network. What are the requirements for robustness and network failover/recovery times? Typically, ring backbones are chosen to provide cost effective but robust network designs. 2. Identify required legacy support and ports with half duplex/shared media restrictions. These bridges should not be used if network failover/recovery times are to be minimized. 3.
Spanning Tree 5.4 Spanning Tree Configuration The Spanning Tree menu is accessible from the main menu. Figure 99: Spanning Tree Menu ROS™ v3.
Spanning Tree 5.4.1 Bridge RSTP Parameters Figure 100: Bridge RSTP Parameters Form State Synopsis: { Disabled, Enabled } Default: Enabled Enable STP/RSTP/MSTP for the bridge globally. Note that for STP/RSTP/MSTP to be enabled on a particular port, it must be enabled both globally per port. Version Support Synopsis: { STP, RSTP, MSTP } Default: RSTP Selects the version of Spanning Tree Protocol to support: either STP, Rapid STP, or Multiple STP.
Spanning Tree Default: On Enable/disable RuggedCom proprietary eRSTP (enhanced RSTP) enhancements Bridge Priority Synopsis: { 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 4 9152, 53248, 57344, 61440 } Default: 32768 Bridge Priority provides a way to control the topology of the STP connected network. The desired Root and Designated bridges can be configured for a particular topology. The bridge with the lowest priority will become root.
Spanning Tree every switch that propagates the BPDU. If the maximum number of hops inside the region exceeds the configured maximum, BPDUs may be discarded due to their time-to-live information. Cost Style Synopsis: { STP (16 bit), RSTP (32 bit) } Default: STP (16 bit) This parameter selects the style of link costs to employ.
Spanning Tree 5.4.2 Port RSTP Parameters Figure 101: Port RSTP Parameter Table Figure 102: Port RSTP Parameter Form Port(s) Synopsis: Any combination of numbers valid for this parameter The port number as seen on the front plate silkscreen of the switch (or a list of ports, if aggregated in a port trunk). ROS™ v3.
Spanning Tree Enabled Synopsis: { Disabled, Enabled } Default: Enabled Enabling STP activates the STP or RSTP protocol for this port per the configuration in the STP Configuration menu. STP may be disabled for the port ONLY if the port does not attach to an STP enabled bridge in any way. Failure to meet this requirement WILL result in an undetectable traffic loop in the network. A better alternative to disabling the port is to leave STP enabled but to configure the port as an edge port.
Spanning Tree This protocol is automatically turned off in situations where multiple STP bridges communicate over a shared (non point-to-point) LAN. The bridge will automatically take point-to-point to be true when the link is found to be operating full duplex. The point-to-point parameter allows this behavior or overrides it, forcing point-to-point to be true or false. Force the parameter true when the port operates a point-to-point link but cannot run the link full duplex.
Spanning Tree 5.4.3 MST Region Identifier Figure 103: MST Region Identifier Table Name Synopsis: Any 32 characters Default: 00-0A-DC-00-41-74 Variable length text string. You must configure an identical region name on all switches you want to be in the same MST region. Revision Level Synopsis: 0 to 65535 Default: 0 Use this parameter, if you want to create a new region from a subset of switches in a current region, while maintaining the same region name.
Spanning Tree 5.4.4 Bridge MSTI Parameters Figure 104: Bridge MSTI Parameters Instance ID Synopsis: 0 to 16 Default: 1 The Instance ID refers to the MSTI (Multiple Spanning Tree Instance) ID. Specify an Instance ID and select GET in order to load the parameters of the page corresponding to the selected MSTI. Changes to parameters that are subsequently applied will apply to the selected Instance ID.
Spanning Tree 5.4.5 Port MSTI Parameters Figure 105: Port MSTI Parameter Table Figure 106: Port MSTI Parameter Form Instance ID Synopsis: 0 to 16 Default: 1 RS400 155 ROS™ v3.
Spanning Tree The Instance ID refers to the MSTI (Multiple Spanning Tree Instance) ID. Specify an Instance ID and select GET in order to load parameters corresponding to the selected MSTI. Changes to parameters that are subsequently applied will apply to the selected Instance ID. Note: Port Parameters for the IST (MSTI zero), are accessible via the Port RSTP Parameters menu (see section 5.4.2).
Spanning Tree 5.5 Spanning Tree Statistics 5.5.1 Bridge RSTP Statistics Figure 107: Bridge RSTP Statistics Form Bridge Status Synopsis: { , Designated Bridge, Not Designated For Any LAN, Root Bridge } Spanning Tree status of the bridge. The status may be root or designated. This field may show text saying not designated for any LAN if the bridge is not designated for any of its ports.
Spanning Tree Root Port Synopsis: 0 to 65535 or { } If the bridge is designated, this is the port that provides connectivity towards the root bridge of the network. Root Path Cost Synopsis: 0 to 4294967295 Total cost of the path to the root bridge, composed of the sum of the costs of each link in the path. If custom costs have not been configured. 1Gbps ports will contribute 4, 100 Mbps ports will contribute 19 and 10 Mbps ports will contribute a cost of 100 to this figure.
Spanning Tree 5.5.2 Port RSTP Statistics Figure 108: Port RSTP Statistics Table RS400 159 ROS™ v3.
Spanning Tree Figure 109: Bridge RSTP Parameters Form Port(s) Synopsis: Any combination of numbers valid for this parameter The port number as seen on the front plate silkscreen of the switch (or a list of ports, if aggregated in a port trunk). Status Synopsis: { Disabled, Listening, Learning, Forwarding, Blocking, Link Down, Discarding } Status of this port in Spanning Tree. This may be one of the following: Disabled - STP is disabled on this port.
Spanning Tree Role of this port in Spanning Tree. This may be one of the following: Designated - The port is designated for (i.e. carries traffic towards the root for) the LAN it is connected to. Root - The single port on the bridge, which provides connectivity towards the root bridge. Backup - The port is attached to a LAN that is serviced by another port on the bridge. It is not used but is standing by. Alternate - The port is attached to a bridge that provides connectivity to the root bridge.
Spanning Tree 5.5.3 Bridge MSTI Statistics Figure 110: Bridge MSTI Statistics Table Instance ID Synopsis: 0 to 16 Default: 1 The Instance ID refers to the MSTI (Multiple Spanning Tree Instance) ID. Specify an Instance ID and select GET in order to load parameters corresponding to the selected MSTI. Note: Bridge Statistics for the IST (MSTI zero), are accessible via the Bridge RSTP Statistics menu (see section 5.5.1).
Spanning Tree Root Port Synopsis: 0 to 65535 or { } If the bridge is designated, this is the port that provides connectivity towards the root bridge of the network. Root Path Cost Synopsis: 0 to 4294967295 Total cost of the path to the root bridge composed of the sum of the costs of each link in the path. If custom costs have not been configured. 1Gbps ports will contribute 4, 100 Mbps ports will contribute 19 and 10 Mbps ports will contribute a cost of 100 to this figure.
Spanning Tree Figure 112: Port MSTI Statistics Form Instance ID Synopsis: 1 to 16 Default: 1 The Instance ID refers to the MSTI (Multiple Spanning Tree Instance) ID. Specify an Instance ID and select GET in order to load parameters corresponding to the selected MSTI. Note: Port Statistics for the IST (MSTI zero), are accessible via the Port RSTP Statistics menu (see section 5.5.2).
Spanning Tree Role Synopsis: { , Root, Designated, Alternate, Backup, Master } Role of this port in Spanning Tree. This may be one of the following: Designated - The port is designated for (i.e. carries traffic towards the root for) the LAN it is connected to. Root - The single port on the bridge, which provides connectivity towards the root bridge. Backup - The port is attached to a LAN that is serviced by another port on the bridge. It is not used but is standing by.
Spanning Tree 5.6 Troubleshooting Problem One When I connect a new port the network locks up. The port status LEDs are flashing madly. Occasionally, the network seems to experience a lot of flooding. All the ports seem to experience significant traffic. The problem lasts a few seconds and then goes away. One of my switches displays a strange behavior where the root port hops back and forth between two switch ports and never settles down.
Spanning Tree Problem Three When I test your switch by deliberately breaking a link, it takes a long time before I can poll devices past the switch. I thought RSTP was supposed to be fast. What is happening? Is it possible that ports participating in the topology have been configured to STP mode or that the port’s point-to-point parameter is set false? STP and multipoint ports converge slowly after failures occur.
Spanning Tree If the controller fails around the time of a link outage then there is the remote possibility that frame disordering or duplication may be the cause of the problem. Try setting the root port of the failing controller’s bridge to STP. Problem Eight My network runs fine with your switch but I occasionally lose polls to my devices. Inspect network statistics to determine whether the root bridge is receiving TCNs around the time of observed frame loss.
VLANs 6 VLANs ROS™ provides the following VLAN features: • • • • • • • • • Support for up to 64 VLANs Support for up to 15 VLANs Configurable port native VLAN. Port modes of operation tailored to edge devices (such as a PC or IED) and to network switch interconnections. A default setting that ensures configuration-free connectivity in certain scenarios.
VLANs Changing the management VLAN can be used to restrict management access to a specific set of users. 6.1.5 Edge and Trunk Port Types Each port can be configured to take on a type of Edge or Trunk. Edge Type An Edge port attaches to a single end device (such as a PC or IED) and carries traffic on a single pre-configured VLAN, the native VLAN. Trunk Type Trunk ports are part of the network and carry traffic for all VLANs between switches.
VLANs Frame received This doesn’t depend on ingress port ‘s VLAN configuration parameters VLAN the frame associated with Frame dropped due to its tagged/untagged format Frame dropped, if associated with VLAN not configured (or learned) in the switch Frame dropped, if ingress port is not a member of the VLAN the frame associated with Untagged Priority Tagged (VID=0) Tagged (valid VID) PVID No PVID No VID in the tag No N/A N/A Yes N/A N/A No Egress Rules These are the VLAN egress rules, i.e.
VLANs To ensure the required operation in any possible application scenario and provide full compatibility with legacy (VLAN-unaware) devices RuggedSwitchTM can be configured to work in a VLAN-unaware mode. In that mode: • • Frames ingressing a VLAN-unaware switch are not associated with any VLAN Frames egressing a VLAN-unaware switch are sent out unmodified, i.e. in the same untagged, 802.1Q-tagged or priority-tagged format as they were received 6.1.
VLANs End Node D GVRP aware Port D2– GVRP aware Adv. & Learn Edge Switch D Port D1 – GVRP aware Adv. & Learn Port B3 – GVRP aware Adv. & Learn Port B1 – GVRP aware Adv. & Learn Core Switch B Port B2 – GVRP aware Adv. & Learn Port B4 – GVRP aware Adv. & Learn Port A1 –GVRP aware Adv. only Edge Switch A Port A2– Edge Port Port C1 – GVRP aware Adv. only Port E1 – GVRP aware Adv.
VLANs ingress edge port. This means that traffic from an individual customer is tagged with his unique VID and, thus, segregated from other customers’ traffic. Within the service provider network, switching is based on the VID in the outer tag. When double-tagged frames leave the service provider network they egress a QinQ-enabled port of another switch. The switch strips the outer tag while associating the frames with the VID extracted from it before stripping.
VLANs 6.2 VLAN Applications 6.2.1 Traffic Domain Isolation VLANs are most often used for their ability to restrict traffic flows between groups of devices. Unnecessary broadcast traffic can be restricted to the VLAN that requires it. Broadcast storms in one VLAN need not affect users in other VLANs. Hosts on one VLAN can be prevented from accidentally or deliberately assuming the IP address of a host on another VLAN.
VLANs 6.2.2 Administrative Convenience VLANs enable equipment moves to be handled by software reconfiguration instead the alternative, cable management. When a host’s physical location is changed, its connection point is often changed as well. With VLANs, the host’s VLAN membership and priority are simply copied to the new port. 6.2.3 Reduced Hardware Without VLANs, traffic domain isolation requires using separate bridges for separate networks. VLANs eliminate the need for separate bridges.
VLANs 6.3 VLAN Configuration The Virtual LANs menu is accessible from the main menu. Figure 117: Virtual LANs Menu 6.3.1 Global VLAN Parameters Figure 118: Global VLAN Parameters Form VLAN-aware Synopsis: { No, Yes } Default: Yes Set either VLAN-aware or VLAN-unaware mode of operation. RS400 177 ROS™ v3.
VLANs • NOTE: Do not attempt to change the “VLAN-aware” parameter of the managed switch by applying a configuration (.CSV) file update. Configuration file updates are used to apply “bulk changes” to the current configuration of a switch. Instead, a change to this individual parameter MUST first be applied separately from any other table (i.e. parameter) changes. In other words, configuration file updates should exclude the “VLAN-aware” parameter. 6.3.
VLANs The VLAN Identifier is used to identify the VLAN in tagged Ethernet frames according to IEEE 802.1Q. VLAN Name Synopsis: Any 19 characters Default: The VLAN name provides a description of the VLAN purpose (for example, Engineering VLAN). Forbidden Ports Synopsis: Any combination of numbers valid for this parameter Default: None These are ports that are disallowed to be members of the VLAN.
VLANs 6.3.3 Port VLAN Parameters Figure 121: Port VLAN Parameters Table Figure 122: Port VLAN Parameters Form ROS™ v3.
VLANs Port(s) Synopsis: Any combination of numbers valid for this parameter The port number as seen on the front plate silkscreen of the switch (or a list of ports, if aggregated in a port trunk). Type Synopsis: {Edge, Trunk} Default: Edge This parameter specifies how the port determines its membership in VLANs. There are few types of ports: EDGE - the port is only a member of one VLAN (its native VLAN specified by the 'PVID' parameter). TRUNK - the port is automatically a member of all configured VLANs.
VLANs 6.3.4 VLAN Summary There are actually 3 ways VLAN can be created in the switch: Explicit VLAN is explicitly configured in the Static VLANs list. Implicit VLAN ID is a parameter required for different feature configurations (e.g. Port VLAN Parameters, Static MAC Addresses, IP Interface Type and ID). When such a parameter is set to some VLAN ID value, appropriate VLAN is automatically created, if doesn’t exist yet. Dynamic VLAN learned through GVRP.
VLANs 6.4 Troubleshooting Problem One I don’t need VLANs at all. How do I turn them off? Simply leave all ports set to type “Edge” and leave the native VLAN set to 1. This is the default configuration for the switch. Problem Two I have added two VLANs 2 and 3. I made a number of ports members of these VLANS. Now I need some of the devices in one VLAN send messages to some devices in the other VLAN. If the devices need to communicate at the physical address layer, they must be members of the same VLAN.
Classes of Service 7 Classes of Service ROS™ CoS provides the following features: • Support for 4 Classes of Service • Ability to prioritize traffic by ingress port. • Ability to prioritize traffic by the priority field in 802.1Q tags. • Ability to prioritize traffic based on its source or destination MAC address. • Ability to prioritize traffic by the TOS field in the IP header. 7.
Classes of Service Received Frame MAC Address in Static MAC Address Table? No Y No Frame tagged ? IP Frame ? No Use Port Default CoS To CoS Queues of Egress Ports Y Y Use TOS DSCP ? No Y Use DSCP-toCoS Mapping Use CoS Configured for the MAC address Use Priority-toCoS Mapping Figure 124: Determining The CoS Of A Received Frame After inspection, the frame is the forwarded to the egress port for transmission. 7.1.
Classes of Service 7.2 CoS Configuration The Classes Of Service menu is accessible from the main menu. Figure 125: Classes Of Service Menu 7.2.1 Global CoS Parameters Figure 126: Global CoS Parameters Form CoS Weighting Synopsis: { 8:4:2:1, Strict } Default: 8:4:2:1 During traffic bursts, frames queued in the switch pending transmission on a port may have different CoS priorities. RS400 187 ROS™ v3.
Classes of Service This parameter specifies weighting algorithm for transmitting different priority CoS frames. Examples: 8:4:2:1 - 8 Critical, 4 High, 2 Medium and 1 Normal priority CoS frame Strict - lower priority CoS frames will be only transmitted after all higher priority CoS frames have been transmitted. 7.2.2 Port CoS Parameters Figure 127: Port CoS Parameter Table ROS™ v3.
Classes of Service Figure 128: Port CoS Parameter Form Port(s) Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch (or a list of ports, if aggregated in a port trunk). Default CoS Synopsis: { Normal, Medium, High, Crit } Default: Normal This parameter allows to prioritize frames received on this port that are not prioritized based on the frames contents (e.g. priority field in the VLAN tag, DiffServ field in the IP header, prioritized MAC address).
Classes of Service Figure 130: Priority to CoS Mapping Form Priority Synopsis: 0 to 7 Default: 0 This is a value of the IEEE 802.1p priority. CoS Synopsis: { Normal, Medium, High, Crit } Default: Normal This is a CoS assigned to received tagged frames with the specified IEEE 802.1p priority value. ROS™ v3.
Classes of Service 7.2.4 DSCP to CoS Mapping Figure 131: TOS DSCP to CoS Mapping Table Figure 132: TOS DSCP to CoS Mapping Form DSCP Synopsis: 0 to 63 Default: 0 RS400 191 ROS™ v3.
Classes of Service This is a Differentiated Services Code Point (DSCP) - a value of the 6 bit DiffServ field in the Type-Of-Service (TOS) field of the IP header. CoS Synopsis: { Normal, Medium, High, Crit } Default: Normal This is a Class of Service assigned to received frames with the specified DSCP. 7.2.5 CoS Access Priorities (RS8000 and RS1600 families only) Figure 133: CoS Access Priorities Table ROS™ v3.
Classes of Service Figure 134: CoS Access Priorities Form Port(s) Synopsis: Any combination of numbers valid for this parameter The port number as seen on the front plate silkscreen of the switch (or a list of ports, if aggregated in a port trunk). Normal Access Priority Synopsis: 0 to 7 Default: 0 When frames that were originally received untagged are transmitted from a tagged port the switch will insert 802.1Q VLAN tags.
Multicast Filtering 8 Multicast Filtering ROS™ accomplishes Multicast Filtering through the following ways: 1. Static Multicast Groups 2. Use of the Internet Group Management Protocol (IGMP) snooping. ROS™ Multicast Filtering provides you with the following features: • • • Support for up to 256 Multicast Groups (either static or dynamic). Ability to prioritize a Static Multicast Group via Class-of-Service Industry standard support of IGMP (RFC 1112, RFC 2236) versions 1 and 2 in active and passive roles.
Multicast Filtering P1 M1 M2 Membership Query Multicast Router Membership Query M1 Membership Report M2 Membership Report C1 C2 C3 C4 Figure 135: IGMP Operation Example 1 In this example the general membership query sent to the C1-C2 segment is answered by a membership report indicating the desire to subscribe to a stream M2. The router will forward the M2 stream onto the C1-C2 segment. In a similar fashion the router discovers that it must forward M1 onto segment C3-C4.
Multicast Filtering Passive Mode When such a switch is used in a network with a multicast router, it can be configured to run Passive IGMP. This mode prevents the switch from sending the queries that can confuse the router causing it to stop issuing IGMP queries.
Multicast Filtering If RSTP detects change in the network topology, IGMP will take some actions to avoid loss of multicast connectivity and reduce network convergence time: • • The switch will immediately issue IGMP queries (if in IGMP Active mode) to obtain potential new group membership information. The switch can be configured to flood multicast streams temporarily out of all ports that are not configured as RSTP Edge Ports. 8.1.
Multicast Filtering Processing Leaves When host C1 decides to leave a multicast group it will issue a leave request to the switch. The switch will poll the port to determine if C1 is the last member of the group on that port. If C1 is the last (or only) member, the group will immediately be pruned from the port. Should host C1 leave the multicast group without issuing a leave group message and then fail to respond to a general membership query, the switch will stop forwarding traffic after two queries.
Multicast Filtering 8.2 Multicast Filtering Configuration and Status The Multicast Filtering menu is available from the main menu. Figure 137: Multicast Filtering Menu 8.2.1 Configuring IGMP Parameters Note that the activation of IGMP on a per-VLAN basis is configured using Static VLANs. Figure 138: IGMP Parameters Form ROS™ v3.
Multicast Filtering Mode Synopsis: { Passive, Active } Default: Passive Specifies IGMP mode: PASSIVE - the switch passively snoops IGMP traffic and never sends IGMP queries ACTIVE - the switch generates IGMP queries, if no queries from a better candidate for being the querier are detected for a while. Query Interval Synopsis: 10 to 3600 Default: 60 s The time interval between IGMP queries generated by the switch. NOTE: This parameter also affects the Group Membership Interval (i.e.
Multicast Filtering 8.2.2 Configuring Static Multicast Groups Figure 139: Static Multicast Groups Table Figure 140: Static Multicast Group Form MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF Default: 00-00-00-00-00-00 Multicast group MAC address. VID Synopsis: 1 to 4094 Default: 1 VLAN Identifier of the VLAN upon which the multicast group operates. CoS ROS™ v3.
Multicast Filtering Synopsis: { Normal, Medium, High, Crit } Default: Normal Specifies what Class Of Service is assigned to the multicast group frames Ports Synopsis: Any combination of numbers valid for this parameter Default: None Ports to which the multicast group traffic is forwarded. 8.2.3 Viewing IP Multicast Groups Figure 141: IP Multicast Groups Table VID Synopsis: 0 to 65535 VLAN Identifier of the VLAN upon which the multicast group operates. IP Address Synopsis: ###.###.###.
Multicast Filtering 8.3 Troubleshooting Problem One When I start a multicast traffic feed it is always distributed to all members of the VLAN. Is IGMP enabled for the VLAN? Multicasts will be distributed to all members of the VLAN unless IGMP is enabled. Problem Two Computers on my switch receive the multicast traffic just fine, but I can’t get the stream through a connected router.
Multicast Filtering Problem Six I connect or disconnect some switch ports and multicast goes everywhere. Is IGMP broken? No, it may be a proper switch behavior. When the switch detects a change in the network topology through RSTP it acts to avoid loss of multicast traffic – if configured to do so, it starts forwarding all multicast traffic to all ports that are not RSTP Edge ports (because they may potentially link to routers).
MAC Address Tables 9 MAC Address Tables ROS™ MAC address table management provides you with the following features: • • • • Viewing learned MAC addresses Purging MAC Address Entries Configuring the switch MAC Address Aging time Configuring static MAC addresses The MAC Address Tables menu is accessible from the main menu. Figure 142: MAC Address Tables Menu RS400 207 ROS™ v3.
MAC Address Tables 9.1 Viewing MAC Addresses Figure 143: Address Table MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF MAC address learned by the switch. VID Synopsis: 0 to 65535 VLAN Identifier of the VLAN upon which the MAC address operates. Port Synopsis: 0 to 65535 or { Multi, Local } Port on which MAC address has been learned.
MAC Address Tables Specifies what Class Of Service is assigned to frames carrying this address as source or destination address 9.2 Configuring MAC Address Learning Options Figure 144: MAC Address Learning Options Form Aging Time Synopsis: 15 to 800 Default: 300 s This parameter configures the time a learned MAC address is held before being aged out.
MAC Address Tables Figure 145: Static MAC Address Table Figure 146: Static MAC Address Form MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF Default: 00-00-00-00-00-00 MAC address that is to be statically configured. VID Synopsis: 1 to 1000 Default: 1 VLAN Identifier of the VLAN upon which the MAC address operates. Port Synopsis: 1 to maximum port number ROS™ v3.
MAC Address Tables Default: 1 Enter the port number upon which the device with this address is located. If the port should be auto-learned, set this parameter to 'Learn' CoS Synopsis: { Normal, Medium, High, Crit } Default: Normal Set this parameter to prioritize the traffic for specified address. 9.4 Purging MAC Address Table This command removes all dynamic entries from the MAC address table. The only negative impact of this operation is that it causes flooding while addresses are relearned.
Network Discovery 10 Network Discovery Network Discovery is based on LLDP (Link Layer Discovery Protocol) as defined by the IEEE 802.1AB standard. This feature provides the ability to: • • • • Enable LLDP per device and per port View LLDP statistics View neighbor information Report LLDP data via SNMP 10.1 LLDP Operation The IEEE standard, 802.
Network Discovery 10.2 Network Discovery Menu The Network Discovery menu provides the ability to configure the switch, globally and per port, to exchange LLDP information with neighbors, and to view LLDP information and statistics. Figure 147: Network Discovery Menu ROS™ v3.
Network Discovery 10.2.1 Global LLDP Parameters Figure 148: Global LLDP Parameters Form State Synopsis: { Disabled, Enabled } Default: Enabled Enables LLDP protocol. Note that LLDP is enabled on a port when LLDP is enabled globally and along with enabling per port setting in Port LLDP Parameters menu. Tx Interval Synopsis: 5 to 32768 Default: 30 s The interval at which LLDP frames are transmitted on behalf of this LLDP agent.
Network Discovery changed. The recommended value 1 <= txDelay <= (0.25 * Tx Interval) is set according to the following formula: 10.2.2 Port LLDP Parameters Figure 149: Port LLDP Parameters Table Figure 150: Port LLDP Parameters Form ROS™ v3.
Network Discovery Port Synopsis: 1 to 9 Default: 1 The port number as seen on the front plate silkscreen of the switch. Admin Status Synopsis: { rxTx, txOnly, rxOnly, Disabled } Default: rxTx rxTx: the local LLDP agent can both transmit and receive LLDP frames through the port. txOnly: the local LLDP agent can only transmit LLDP frames. rxOnly: the local LLDP agent can only receive LLDP frames. disabled: the local LLDP agent can neither transmit nor receive LLDP frames.
Network Discovery Drops Synopsis: 0 to 4294967295 The number of times an entry was deleted from LLDP Neighbor Information Table because the information timeliness interval has expired. Ageouts Synopsis: 0 to 4294967295 The number of all TLVs discarded 10.2.4 LLDP Neighbor Information Figure 152: LLDP Neighbor Information Table Port Synopsis: 0 to 4294967295 The local port associated with this entry. ChassisId Synopsis: Any 19 characters Chassis Id information received from remote LLDP agent.
Network Discovery 10.2.5 LLDP Statistics Figure 153: LLDP Statistics Table Port Synopsis: 1 to 9 The port number as seen on the front plate silkscreen of the switch.
PPP over Modem 11 PPP over Modem ROS™ PPP over Modem provides you with the following features: • • • • • Configuring PPP network parameters Configuring PAP/CHAP authentication Configuring PPP clients Viewing the status of the PPP/Modem port Resetting the port 11.1 PPP over Modem Operation In RuggedCom device, internal modem with following features can be installed: • • • • Industrial grade V.90 modem offering connection speeds ranging from V.22bis (2400 bps), V.32bis (14.4 kbps), V.34 (33.6 kbps) to V.
PPP over Modem On the RuggedCom device : • • • • At least one username and password for PAP or CHAP to authenticate against.
PPP over Modem On the dial-in client: • • • • The telephone number to dial in order to reach the RuggedCom device The authentication protocol (PAP or CHAP) to use and a username and password that will be accepted by the device.
PPP over Modem • • • After the PPP link establishment phase is complete, the RuggedCom device sends a challenge message to the client. The client responds with an MD5 hashed value of the password. The RuggedCom device checks the response against its own calculation of the hashed password and clears the call if the values do not match. The client may also use CHAP to authenticate the server. This is known as two-way authentication.
PPP over Modem 11.2 PPP Configuration The PPP Configuration menu is accessible from the main menu. Figure 156: PPP Configuration Menu RS400 225 ROS™ v3.
PPP over Modem 11.2.1 Modem Settings Figure 157: PPP Modem Settings Form Country Code Synopsis: { Australia, Austria, Belgium, Brazil, China, Denmark, Finland, France, Germany, Gre ece, India, Ireland, Italy, Japan, Korea, Malaysia, Mexico, Netherlands, North America, Norway, Poland, Portugal, Singapore, South Africa, Spain, Sweden, Switzerland, Taiwan, United Kingdom } Default: North America The country that the product is being used in.
PPP over Modem 11.2.2 PPP Control Figure 158: PPP Control Form PPP Status Synopsis: { Disabled, Enabled } Default: Disabled Whether PPP is disabled or enabled. Local IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: 192.168.1.1 This parameter specifies the IP address of the local side of the PPP link. Note that local and remote PPP addresses must be on the same subnet and that this subnet must be different from the management network address. Remote IP Address Synopsis: ###.
PPP over Modem Server Name Synopsis: Any 15 characters Default: Server This string determines the server name and is used for CHAP and when authenticating ourselves to the caller using PAP. Outgoing PAP Password Synopsis: Any 15 characters Default: If the caller requests the server to authenticate itself, the server will reply with an id set to the Server name and this password. Leave this field blank if you do not require two-way authentication. Note: ROS™ v3.
PPP over Modem 11.2.3 PPP Users Up to 10 user/password combinations can be in this table. Figure 159: PPP Users Table Figure 160: PPP Users Form User Name Synopsis: Any 15 characters Default: The username used to validate the PPP connection RS400 229 ROS™ v3.
PPP over Modem Password Synopsis: Any 9 characters Default: The password associated with a specific username. Auth Type Synopsis: { CHAP Only, PAP Only, Both PAP/CHAP, No Authentication } Default: CHAP Only Determines whether the username/password applies to PAP, CHAP or both. Setting authentication to "none" should be used only when debugging new installs, and only temporarily. Remote Net Synopsis: ###.###.###.
PPP over Modem 11.2.4 PPP Statistics Figure 161: PPP Statistics Form Current Status Synopsis: { Disabled, Waiting for a call, Authenticating user, Call in progress, Stopping call, No Dialtone, Number Busy, No Answer } The current port status. Modem Speed Synopsis: 0 to 2147483647 bps or { Offline } The speed in bps that the modem connected at. Rx Packets Synopsis: 0 to 4294967295 The number of received packets on the connection.
PPP over Modem Tx LCP Packets Synopsis: 0 to 4294967295 The number of packets LCP transmitted on the connection. Authentication Synopsis: { ,None, PAP, PAP Failure, CHAP, CHAP Failure } The current authentication status. Connected User Synopsis: Any 15 characters The name of the currently connected user. ROS™ v3.
PPP over Modem 11.2.5 Clearing PPP Statistics Figure 162: Clear PPP Statistics Form 11.2.6 Resetting PPP Resetting PPP will immediately clear the modem call. Figure 163: Reset PPP Port Form RS400 233 ROS™ v3.
PPP over Modem 11.3 Troubleshooting Problem One My PC is calling the RuggedCom device but the call never connects. It is important to discriminate between the call connecting (i.e. the modem answering the call) and the PPP session connecting (i.e. successful link up and authentication). Problems with the latter are dealt with in the next problem description.
PPP over Modem If you are sure the client has installed the PPP link as default gateway, is the client otherwise connected to a LAN? If the client is connected to a LAN and the best route is to the LAN, the PPP link will not be used. The following figure illustrates this case. The client will always direct all packets bound for 10.0.0.10 down its Ethernet connection. This will occur regardless of the PPP gateway setting and possible lack of connectivity in the Ethernet cloud.
Diagnostics 12 Diagnostics ROS™ provides the following diagnostics features: • • • • • • Alarm System to view and clear alarms Viewing and clearing the system log Viewing CPU diagnostics Viewing the product information Loading the factory default configuration Resetting the device The Diagnostics menu is accessible from the main menu: Figure 165: Diagnostics Menu 12.1 Using the Alarm System Alarms are the occurrence of events of interest that are logged by the device.
Diagnostics 12.1.1 Active Alarms Active alarms are ongoing. They signify states of operation that are not in accordance with normal operation. Examples of active alarms include links that should be up but are not or error rates that are continuously exceeding a certain threshold. Active alarms are removed (cleared) either by solving the original cause of the alarm or by explicitly clearing the alarm itself. 12.1.2 Passive Alarms Passive alarms are historic in nature.
Diagnostics ERROR - Device has a recoverable problem that does not seriously affect operation WARNING - Possibly serious problem affecting overall system operation NOTIFY - Condition detected that is not expected or not allowed INFO - Event which is a part of normal operation, e.g. warm start, user login etc. DEBUG - Intended for factory troubleshooting only Time Synopsis: MMM DD HH:MM Time of first occurrence of the alarm.
Diagnostics CPU Usage Synopsis: 0 to 100 The percentage of available CPU cycles used for device operation as measured over the last second. RAM Total Synopsis: 0 to 4294967295 The total number of bytes of RAM in the system. RAM Available Synopsis: 0 to 4294967295 The total number of bytes of RAM still available. Temperature Synopsis: -32768 to 32767 C The temperature on CPU board. ROS™ v3.
Diagnostics 12.3 Viewing and Clearing the System Log The system log records various events including reboots, user sign-ins, alarms and configuration saves. Figure 168: Viewing the System Log The system log will continue to accumulate information until becomes full. There is enough room in the file to accumulate logs for months or years under normal operation. Clear System Log option will clear the system log. Clearing the log is recommended after a firmware upgrade. RS400 241 ROS™ v3.
Diagnostics 12.4 Viewing Product Information Figure 169: Product Information Form MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF Shows the unique MAC address of the device Order Code Synopsis: Any 31 characters Shows the order code of the device. Serial Number Synopsis: Any 31 characters Shows the serial number of the device. Boot Version Synopsis: Any 47 characters Shows the version and the build date of the boot loader software.
Diagnostics RS900 (v2, 40-00-0066), RS900 (v2, 40-00-0067) } Shows the type, part number, and revision level of the hardware 12.5 Loading Factory Default Configuration The Load Factory Default Configuration option will reset all configuration parameters to factory default values with the exception of parameters that affect basic connectivity and SNMP management.
Diagnostics Figure 171: Reset Device Dialog ROS™ v3.
Using the CLI Shell 13 Using the CLI Shell ROS™ Command Line Interface (CLI) support allows: • • • Executing commands from CLI Shell Executing commands remotely using RSH Entering and leaving the CLI Shell Note: Different commands may be available to users at different login session security levels (guest, operator or administrator). 13.1 Entering and Leaving the Shell You may enter the Command Line Interface (CLI) shell from all the menus by pressing S.
Using the CLI Shell Please note that this chapter describes only the most useful of the above commands. 13.2.1 Getting Help for a Command Help related to the usage of a particular command may be obtained by entering “help command name ” at the shell prompt. >help type Displays the contents of a text file. Enter 'dir' for a directory listing of files. TYPE filename Figure 173: Displaying help for a command 13.2.2 Viewing Files RuggedCom devices maintain a number of volatile and nonvolatile files.
Using the CLI Shell Viewing and Clearing Log Files The crashlog.txt and syslog.txt files contain historical information about events that have occurred. The crashlog.txt file will contain debugging information related to problems that might have resulted in unplanned restarts of the device or which may effect the device operation. A file size of 0 bytes indicates that no untoward events have occurred. The syslog.
Using the CLI Shell trace ? Supported commands: noclear Starts the log without clearing it first alloff Disables all trace subsystems from tracing allon Enables all flags in all trace subsystems stp Traces STP operations link Displays switch fabric statistics mac Displays MAC Events forward Forwards trace messages to an IP:UDP address igmp Displays IGMP Snooping events gvrp Displays GVRP events webs Traces Web Server connections dhcpra Traces DHCP Relay Agent 802.1X Traces 802.
Using the CLI Shell Starting Trace To start trace enter “trace”. All historical trace messages may be displayed using “trace noclear”. Since this may include many messages, it may be more desirable to use the “trace clear” command instead. This command will automatically clear the trace buffer as it starts the trace.
Using the CLI Shell command_string = combination username,password is to be used. E.g. admin,secret where admin is the username and secret is the password The command to execute The access level selected must support the given command. Any output from the command will be returned to the workstation submitting the command. Commands that start interactive dialogs (such as trace) cannot be used. 13.2.7 Resetting the Device The CLI command “reset” can be used to reset the device. ROS™ v3.
Upgrading Firmware and Managing Configurations 14 Upgrading Firmware and Managing Configurations ROS™ provides the following features for management of system firmware and configuration: • • • Upgrading firmware using the XModem protocol and Trivial File Transfer Protocol (TFTP) Capturing and restoring the device configuration using XModem and TFTP Using SQL commands to view/change configuration 14.
Upgrading Firmware and Managing Configurations Start sending the file. After the file transfer is finished device will provide an indication that it was properly upgraded. The device must be reset in order for the new software to take effect. If you want to reset the device immediately enter “reset”. The device will begin its reboot within a few seconds. 14.1.
Upgrading Firmware and Managing Configurations 14.1.3 Upgrading Firmware Using ROS™ TFTP Client Identify the IP address of the host providing the TFTP server capability. Ensure that the firmware revision to be downloaded (e.g. ROS-CF52_Main_v3.0.0.bin) is present there. Telnet to the device or connect to its console port. Enter the CLI shell and run command “tftp host_addr get main.bin ROS-CF52_Main_v3.0.0.bin”. Check the status of the download by running the version command.
Upgrading Firmware and Managing Configurations 14.2 Capturing Configurations ROS™ provides a means to capture the configuration of the device in an ASCII formatted text file. The same file can be downloaded to the device at a later date in order to restore the device to its previous configuration. Different versions of configuration file can be compared using an ASCII text difference tool, in order to pinpoint configuration changes. 14.2.
Upgrading Firmware and Managing Configurations 14.
Upgrading Firmware and Managing Configurations >sql info tables Table Description ------------------------------------------------------------------------------alarms Alarms cpuDiags CPU Diagnostics ethPortCfg Port Parameters ethPortStats Ethernet Statistics ethPortStatus Port Status ipCfg IP Services Figure 182 Brief snippet of SQL command for finding the correct table name 14.3.3 Retrieving Information Retrieving a Table The SQL select subcommand is used to retrieve table information.
Upgrading Firmware and Managing Configurations results. As an example, suppose that it is desirable to identify all ports on the device operating in Auto Select mode.
Upgrading Firmware and Managing Configurations 14.3.6 Using RSH and SQL Combination of remote shell scripting and SQL commands offers a means to interrogate and maintain a large number of devices. Consistency of configuration across sites may be verified by this method. The following presents a simple example where the devices to interrogate are drawn from the file “Devices”. C:> type Devices 10.0.1.1 10.0.1.2 10.0.1.
Appendix A - SNMP MIB Support Appendix A - SNMP MIB Support Standard MIBs RFC RFC 1907 MODULE Name SNMPv2-MIB RFC 2863 IF-MIB RFC 2012 RFC 2013 RFC 2819 TCP-MIB UDP-MIB RMON-MIB RFC 4188 BRIDGE-MIB RFC 4318 RSTP-MIB LLDP MIB LLDP-MIB RFC 3414 RFC 3415 SNMP-USER-BASED-SM-MIB SNMP-VIEW-BASED-ACM-MIB RS400 259 Groups Supported SNMP Group SNMP Community Group SNMP Set Group System Group SNMP Basic Notifications Group General Information Group VHC Packet Group Counter Discontinuity Group Link Up
Appendix A - SNMP MIB Support RuggedCom proprietary MIBs Proprietary MIB RuggedSwitch MODULE Name RUGGEDCOM-SWITCH-MIB Groups Supported Defines Agent Capabilities for Ruggedcom Switches RuggedServer RUGGEDCOM-SERVER-MIB Defines Agent Capabilities for Ruggedcom Servers RuggedMC30 RUGGEDCOM-MC30-MIB Defines Agent Capabilities for RMC30 RuggedcomTraps RUGGEDCOM-TRAPS-MIB Generic Traps Group Power Supply Trap Group Notifications Group RcSysInfo RUGGEDCOM-SYS-INFO-MIB System Error Objects Group, S
Appendix B – SNMP Trap Summary Appendix B – SNMP Trap Summary The switch generates the standard traps summarized in the following table. • • • • • from IF-MIB: linkDown, linkUp from SNMPv2-MIB: authenticationFailure coldStart from BRIDGE-MIB: newRoot, topologyChage from RMON-MIB: risingAlarm, fallingAlarm from LLDP-MIB: lldpRemoteTablesChange The switch also generates the proprietary traps which are summarized in this document with their severity levels. These traps are described in the RC-TRAPS-MIB.
Appendix C – List of Objects Eligible for RMON Alarms Appendix C – List of Objects Eligible for RMON Alarms ifInOctets The total number of bytes received on the interface, including framing characters. ifInUcastPkts The number of packets, delivered by this sub-layer to a higher (sub-)layer, which, were not addressed to a multicast or broadcast address at this sub-layer. ifInDiscards The number of received packets that are droped due to lack of receive buffers.
Appendix C – List of Objects Eligible for RMON Alarms The total number of segments sent, including those on current connections but excluding those containing only retransmitted bytes. tcpRetransSegs The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted bytes. udpInDatagrams The total number of UDP datagrams received and delivered to UDP users.
Appendix C – List of Objects Eligible for RMON Alarms The number of good Broadcast packets received. etherStatsMulticastPkts The number of good Multicast packets received. etherStatsCRCAlignErrors The number of packets received which meet all the following conditions: 1. Packet data length is between 64 and 1536 bytes inclusive. 2. Packet has invalid CRC. 3. Collision Event has not been detected. 4. Late Collision Event has not been detected.
Appendix C – List of Objects Eligible for RMON Alarms The total number of received packets that where between 1024 and 1518 bytes long. dot1dBasePortDelayExceededDiscards The number of frames discarded by this port due to excessive transit delay through the bridge. dot1dBasePortMtuExceededDiscards The number of frames discarded by this port due to an excessive size. dot1dTpPortInFrames The number of frames that have been received by this port from its segment.
Appendix C – List of Objects Eligible for RMON Alarms The total number of packets transmitted that were directed to multicast address. This object is a 64-bit version of ifOutMulticastPkts. ifHCOutBroadcastPkts The total number of packets transmitted that were directed to the broadcast address. This object is a 64-bit version of ifOutBroadcastPkts. rcDeviceStsTemperature The temperature measured in the device. ROS™ v3.
Appendix E – ModBus Management Support and Memory Map Appendix E – ModBus Management Support and Memory Map ModBus management support in RuggedCom devices provides the user with a simple interface with basic status information. Support for this protocol simplifies the job of SCADA System integrators who can now easily use this feature to retrieve basic info from RuggedCom devices via a familiar protocol.
Appendix E – ModBus Management Support and Memory Map Note that, as RuggedCom devices have variable number of ports, not all registers and bits apply to all products. Registers that are not applicable to a given product return zero value. E.g. registers referring to serial ports are not applicable to RuggedSwitch products.
Appendix E – ModBus Management Support and Memory Map RS400 0414 0416 0418 041A 041C 041E Address 2 2 2 2 2 2 #Registers Port 11 Statistics - Ethernet In Packets Port 12 Statistics - Ethernet In Packets Port 13 Statistics - Ethernet In Packets Port 14 Statistics - Ethernet In Packets Port 15 Statistics - Ethernet In Packets Port 16 Statistics - Ethernet In Packets Description R R R R R R R/W Uint32 Uint32 Uint32 Uint32 Uint32 Uint32 Format 0420 0422 0424 0426 2 2 2 2 Port 17 Statistics - Ethernet I
Appendix E – ModBus Management Support and Memory Map 04A0 04A2 04A4 04A6 2 2 2 2 Port 17 Statistics - Ethernet In Octets Port 18 Statistics - Ethernet In Octets Port 19 Statistics - Ethernet In Octets Port 20 Statistics - Ethernet In Octets R R R R Uint32 Uint32 Uint32 Uint32 04C0 Address 2 #Registers Port 1 Statistics - Ethernet Out Octets Description R R/W Uint32 Format 04C2 04C4 04C6 04C8 04CA 04CC 04CE 04D0 04D2 04D4 04D6 04D8 04DA 04DC 04DE 04E0 04E2 04E4 04E6 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
Appendix E – ModBus Management Support and Memory Map Text Simple ASCII representation of the information related to the product. ASCII characters’ most significant byte of register comes first. E.g.
Appendix E – ModBus Management Support and Memory Map Read Data from device using PortCmd: E.g. A Modbus Request to read multiple registers from location – 0x03FE 0x04 0x03 0xFE 0x00 0x02 Response would depend on the device as on how many ports are available on the device E.g. If Max number of ports on RuggedCom device to which you are talking to is 20 Response may look like: 0x04 0x04 0xF2 0x76 0x00 0x05 In the above response Byte 3 and 4 refer to Register 1 i.
Index Values used for presenting power supply status have been derived from RuggedCom specific MIB for SNMP. Read Power Supply Status from device using PSStatusCmd: E.g. A Modbus Request to read multiple registers from location – 0x0043 0x04 0x00 0x43 0x00 0x01 Response may look like: 0x04 0x02 0x00 0x0A In the above response lower byte of the register shows status of power supplies. As per the response both power supplies in the unit are functional. Index Loss-of-Link Management .................
Index Bridge Parameters....................................147 Edge Ports ................................................136 MultiPoint Links.........................................136 Operation ..................................................133 Path Costs ................................................136 Point To Point Links..................................136 Port Costs .................................................136 Port Parameters........................................150 Port Redundancy .
Index Tagging .................................................... 169 Troubleshooting ....................................... 183 Trunk Type............................................... 170 RS400 WIN and TIN Configuration ............................77 Xmodem, Capturing Configuration ...............254 XModem, Upgrading Firmware With ............251 275 ROS™ v3.
