Preface RUGGEDCOM ROS v4.
RUGGEDCOM ROS User Guide Copyright © 2014 Siemens Canada Ltd. 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.
RUGGEDCOM ROS User Guide Table of Contents Table of Contents Preface ................................................................................................................ xi Conventions ....................................................................................................................................... xi Alerts ......................................................................................................................................... xi CLI Command Syntax ....
Table of Contents RUGGEDCOM ROS User Guide 1.7.3.7 PSStatusCmd ....................................................................................................... 21 1.7.3.8 TruthValues .......................................................................................................... 22 1.8 Certificate and Key Requirements ............................................................................................... 22 Chapter 2 Using ROS ....................................................
RUGGEDCOM ROS User Guide Table of Contents 3.5.1 Viewing Local Logs ......................................................................................................... 51 3.5.2 Clearing Local Logs ......................................................................................................... 51 3.5.3 Configuring the Local System Log .................................................................................... 52 3.5.4 Managing Remote Logging ........................................
Table of Contents RUGGEDCOM ROS User Guide 3.10.2.2 Adding an RMON Alarm ...................................................................................... 88 3.10.2.3 Deleting an RMON Alarm .................................................................................... 90 3.10.3 Managing RMON Events ................................................................................................ 91 3.10.3.1 Viewing a List of RMON Events ...........................................................
RUGGEDCOM ROS User Guide Table of Contents 5.2.1.2 Native VLAN ....................................................................................................... 121 5.2.1.3 The Management VLAN ...................................................................................... 122 5.2.1.4 Edge and Trunk Port Types ................................................................................. 122 5.2.1.5 Ingress and Egress Rules ..................................................................
Table of Contents RUGGEDCOM ROS User Guide 5.4.5 Configuring DSCP to CoS Mapping ................................................................................ 158 5.5 Managing MAC Addresses ........................................................................................................ 159 5.5.1 Viewing a List of MAC Addresses ................................................................................... 159 5.5.2 Configuring MAC Address Learning Options ..................................
RUGGEDCOM ROS User Guide Table of Contents 5.9.3 Viewing a Summary of Multicast Groups ......................................................................... 193 5.9.4 Configuring IGMP .......................................................................................................... 193 5.9.5 Configuring GMRP Globally ............................................................................................ 195 5.9.6 Configuring GMRP for Specific Ethernet Ports ..............................
Table of Contents x RUGGEDCOM ROS User Guide
RUGGEDCOM ROS User Guide Preface Preface This guide describes v4.1 of ROS (Rugged Operating System) running on the RUGGEDCOM RS8000. It contains instructions and guidelines on how to use the software, as well as some general theory. It is intended for use by network technical support personnel who are familiar with the operation of networks. It is also recommended for us by network and system planners, system programmers, and line technicians.
RUGGEDCOM ROS User Guide Preface CLI Command Syntax The syntax of commands used in a Command Line Interface (CLI) is described according to the following conventions: Example Description command Commands are in bold. command parameter Parameters are in plain text. command parameter1 parameter2 Parameters are listed in the order they must be entered. command parameter1 parameter2 Parameters in italics must be replaced with a user-defined value.
RUGGEDCOM ROS User Guide Preface Accessing Documentation The latest Hardware Installation Guides and Software User Guides for most RUGGEDCOM products are available online at www.siemens.com/ruggedcom. For any questions about the documentation or for assistance finding a specific document, contact a Siemens sales representative.
RUGGEDCOM ROS User Guide Customer Support Preface xiv
RUGGEDCOM ROS Chapter 1 User Guide Introduction Introduction This chapter provides a basic overview of the ROS software. It describes the following topics: • Section 1.1, “Overview” • Section 1.2, “Security Recommendations and Considerations” • Section 1.3, “Port Numbering Scheme” • Section 1.4, “Available Services by Port” • Section 1.5, “SNMP Management Interface Base (MIB) Support” • Section 1.6, “SNMP Traps” • Section 1.7, “ModBus Management Support” • Section 1.
Chapter 1 RUGGEDCOM ROS Introduction User Guide Section 1.2 Security Recommendations and Considerations The following describes important security-related recommendations and suggestions that should be considered before implementing the RS8000 on any network: • Section 1.2.1, “Security Recommendations” • Section 1.2.2, “Key Files” Section 1.2.
RUGGEDCOM ROS Chapter 1 User Guide Introduction • Configuration files are provided in the CSV (comma separated values) format for ease of use. Make sure configuration files are properly protected when they exist outside of the device. For instance, encrypt the files, store them in a secure place, and do not transfer them via insecure communication channels. • Management of the configuration file, certificates and keys is the responsibility of the device owner.
Chapter 1 RUGGEDCOM ROS Introduction User Guide Section 1.2.2.1 SSL Certificates ROS supports SSL certificates that conform to the following specifications: • X.509 v3 digital certificate format • PEM format • RSA key pair, 512 to 2048 bits The RSA key pair used in the default certificate and in those generated by ROS uses a public key of 1024 bits in length. NOTE RSA keys smaller than 1024 bits in length are not recommended. Support is only included here for compatibility with legacy equipment.
RUGGEDCOM ROS Chapter 1 User Guide -out Introduction ros_ssl.crt # Concatenate Cert and Key into a single file suitable for upload to ROS: # Note that cert must precede the RSA key: cat ros_ssl.crt ros_ssl.key > ssl.crt For information on creating SSL certificates for use with ROS in a Microsoft Windows environment, refer to the following Siemens application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows.
Chapter 1 RUGGEDCOM ROS Introduction User Guide The DSA key pair used in the default key pair and in those generated by ROS uses a public key of 1024 bits in length. NOTE DSA keys smaller than 1024 bits in length are not recommended, and support is only included here for compatibility with legacy equipment. NOTE DSA key generation times increase depending on the key length. 1024 bit RSA keys may take several minutes to generate, whereas 2048 bit keys may take significantly longer.
RUGGEDCOM ROS Chapter 1 User Guide Introduction Section 1.3 Port Numbering Scheme For quick identification, each port on an RS8000/RS8000A/RS8000H/RS8000T device is assigned a number. All port numbers are silk-screened on the device. Figure 1: RS8000/RS8000A/RS8000H/RS8000T Port Numbering (Typical) Use these numbers to configure applicable features on select ports. Section 1.4 Available Services by Port The following table lists the services available under ROS.
Chapter 1 RUGGEDCOM ROS Introduction 8 User Guide Services Port Number Port Open Port Default Access Authorized RSH TCP/512 Open (configurable) Closed Yes Only available through two management interfaces. TFTP UDP/69 Open (configurable) Closed No Only available through two management interfaces. SFTP TCP/22 Open Open Yes Only available through two management interfaces. SNMP UDP/161 Open (configurable) Closed Yes Only available through two management interfaces.
RUGGEDCOM ROS Chapter 1 User Guide Introduction Section 1.5 SNMP Management Interface Base (MIB) Support ROS supports a variety of standard MIBs, proprietary RUGGEDCOM MIBs and Agent Capabilities MIBs, all for SNMP (Simple Network Management Protocol). • Section 1.5.1, “Supported Standard MIBs” • Section 1.5.2, “Supported Proprietary RUGGEDCOM MIBs” • Section 1.5.3, “Supported Agent Capabilities” Section 1.5.
Chapter 1 RUGGEDCOM ROS Introduction User Guide Standard MIB Name Title RFC 4363 Q-BRIDGE-MIB Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions Section 1.5.2 Supported Proprietary RUGGEDCOM MIBs ROS supports the following proprietary RUGGEDCOM MIBs: File Name MIB Name Description ruggedcom.mib RUGGEDCOM-MIB RUGGEDCOM enterprise SMI ruggedcomtraps.mib RUGGEDCOM-TRAPS-MIB RUGGEDCOM traps definition rcsysinfo.
RUGGEDCOM ROS Chapter 1 User Guide Introduction File Name MIB Name Supported MIB rcipmibAC.mib RC-IP-MIB-AC IP-MIB rclldpmibAC.mib RC-LLDP-MIB-AC LLDP-MIB rclagmibAC.mib RC-LAG-MIB-AC IEEE8023-LAG-MIB rcrstpmibAC.mib RC_RSTP-MIB-AC RSTP-MIB rcrcdot11AC.mib RC-RUGGEDCOM-DOT11-MIB-AC RUGGEDCOM-DOT11- MIB rcrcpoeAC.mib RC-RUGGEDCOM-POE-MIB-AC RUGGEDCOM-POE-MIB rcrcrstpmibAC.mib RC-RUGGEDCOM-STP-AC-MIB RUGGEDCOM-STP-MIB rcrcsysinfomibAC.
Chapter 1 RUGGEDCOM ROS Introduction User Guide Trap MIB weakPasswordTrap defaultKeysTrap Generic traps carry information about events in their severity and description objects. They are sent at the same time an alarm is generated for the device. The following are examples of RUGGEDCOM generic traps: NOTE Information about generic traps can be retrieved using the CLI command alarms. For more information about the alarms command, refer to Section 2.6.1, “Available CLI Commands”.
RUGGEDCOM ROS Chapter 1 User Guide Introduction • Section 1.7.3, “ModBus Memory Formats” Section 1.7.1 ModBus Function Codes RUGGEDCOM devices support the following ModBus function codes for device management through ModBus: NOTE While RUGGEDCOM devices have a variable number of ports, not all registers and bits apply to all products. Registers that are not applicable to a particular device return a zero (0) value.
Chapter 1 RUGGEDCOM ROS Introduction User Guide Section 1.7.2 ModBus Memory Map The following details how ModBus process variable data is mapped.
RUGGEDCOM ROS Chapter 1 User Guide Introduction Ethernet Port Status The following data is mapped to the ethPortStats table: Address #Registers 03FE 2 Description (Reference Table in UI) Port Link Status R/W Format R PortCmd R/W Format Ethernet Statistics The following data is mapped to the rmonStats table: Address #Registers 0400 2 Port s1/p1 Statistics - Ethernet In Packets R Uinst32 0402 2 Port s1/p2 Statistics - Ethernet In Packets R Uinst32 0404 2 Port s1/p3 Statistics -
Chapter 1 RUGGEDCOM ROS Introduction 16 User Guide Address #Registers 0440 2 0442 Description (Reference Table in UI) R/W Format Port s1/p1 Statistics - Ethernet Out Packets R Uinst32 2 Port s1/p2 Statistics - Ethernet Out Packets R Uinst32 0444 2 Port s1/p3 Statistics - Ethernet Out Packets R Uinst32 0446 2 Port s1/p4 Statistics - Ethernet Out Packets R Uinst32 0448 2 Port s2/p1 Statistics - Ethernet Out Packets R Uinst32 044A 2 Port s2/p2 Statistics - Ethernet Out Pack
RUGGEDCOM ROS Chapter 1 User Guide Introduction Address #Registers 048C 2 048E R/W Format Port s2/p3 Statistics - Ethernet In Packets R Uinst32 2 Port s2/p4 Statistics - Ethernet In Packets R Uinst32 0490 2 Port s3/p1 Statistics - Ethernet In Packets R Uinst32 0492 2 Port s3/p2 Statistics - Ethernet In Packets R Uinst32 0494 2 Port s3/p3 Statistics - Ethernet In Packets R Uinst32 0496 2 Port s3/p4 Statistics - Ethernet In Packets R Uinst32 0498 2 Port s4/p1 Statistics
Chapter 1 RUGGEDCOM ROS Introduction User Guide Address #Registers 04D8 2 04DA Description (Reference Table in UI) R/W Format Port s4/p1 Statistics - Ethernet Out Packets R Uinst32 2 Port s4/p2 Statistics - Ethernet Out Packets R Uinst32 04DC 2 Port s4/p3 Statistics - Ethernet Out Packets R Uinst32 04DE 2 Port s4/p4 Statistics - Ethernet Out Packets R Uinst32 04E0 2 Port s5/p1 Statistics - Ethernet Out Packets R Uinst32 04E2 2 Port s5/p2 Statistics - Ethernet Out Packets
RUGGEDCOM ROS Chapter 1 User Guide Introduction Address #Registers Description (Reference Table in UI) R/W Format 06C6 2 Port 4 Statistics – Serial Out Packets R Uint32 Section 1.7.3 ModBus Memory Formats The following ModBus memory formats are supported by Siemens: • Section 1.7.3.1, “Text” • Section 1.7.3.2, “Cmd” • Section 1.7.3.3, “Uint16” • Section 1.7.3.4, “Uint32” • Section 1.7.3.5, “PortCmd” • Section 1.7.3.6, “Alarm” • Section 1.7.3.7, “PSStatusCmd” • Section 1.7.3.
Chapter 1 RUGGEDCOM ROS Introduction 0x10 User Guide 0x00 0x80 0x00 0x01 2 0xFF 0x00 • FF 00 for register 00 80 clears the system alarms • 00 00 does not clear any alarms The response may look like: 0x10 0x00 0x80 0x00 0x01 Section 1.7.3.3 Uint16 The Uint16 format describes a Standard ModBus 16 bit register. Section 1.7.3.4 Uint32 The Uint32 format describes Standard 2 ModBus 16 bit registers. The first register holds the most significant 16 bits of a 32 bit value.
RUGGEDCOM ROS Chapter 1 User Guide Introduction Performing Write Actions Using PortCmd To understand how data is written using PortCmd, consider a Write Multiple Register request to clear Ethernet port statistics: 0x10 0x00 0x83 0x00 0x01 2 0x55 0x76 0x00 0x50 A bit value of 1 clears Ethernet statistics on the corresponding port. A bit value of 0 does not clear the Ethernet statistics. 0x10 0x00 0x81 0x00 0x02 Section 1.7.3.6 Alarm The Alarm format is another form of text description.
Chapter 1 RUGGEDCOM ROS Introduction User Guide The lower byte of the register displays the power supply's status. In this example, both power supplies in the unit are functional. Section 1.7.3.
RUGGEDCOM ROS Chapter 1 User Guide Introduction If a default SSL certificate and SSL/SSH keys are in use, ROS immediately begins to generate a unique certificate and SSL/SSH keys for the device in the background. This process takes approximately 5 minutes to complete (depending on how busy the device is at the time) following the startup of the device.
Chapter 1 Introduction RUGGEDCOM ROS User Guide X5TnRcMraJ0RuuGK+chqQJW5k3zQmZa/BS6q9U7wYwIAx8JSxxpwfPfl/t09VwKG rtSJIMpLRoDq3qEwEVyR4kDUo4LFQDsljtiyhcz1n6kd6gqsd5Xu1vdh4wIVANXb SBi97GmZ6/9f4UCvIIBtXLEjAoGAAfmhkcCCEnRJitUTiCE+MurxdFUr3mFs/d31 4cUDaLStQEhYYmx5dbFdQuapl4Y32B7lZQkohi5q1T1iUAa40/nUnJx1hFvblkYT 8DLwxcuDAaiu0VqsaPtJ+baL2dYNp96tFisj/475PEEWBGbP6GSe5kKa1Zdgwuie 9LyPb+ACgYBv856v5tb9UVG5+tX5Crfv/Nd8FFlSSFKmVWW3yzguhHajg2LQg8UU sm1/zPSwYQ0SbQ9aOAJnpLc2HUkK0lji/0oKVI7y9MMc4B+bGu4W4OnryP7oFpnp YYHt5
RUGGEDCOM ROS Chapter 2 User Guide Using ROS Using ROS This chapter describes how to use the ROS interface. It describes the following tasks: • Section 2.1, “Connecting to ROS” • Section 2.2, “Logging In” • Section 2.3, “Logging Out” • Section 2.4, “Using the Web Interface” • Section 2.5, “Using the Console Interface” • Section 2.6, “Using the Command Line Interface” • Section 2.7, “Selecting Ports in ROS” • Section 2.8, “Managing the Flash File System” • Section 2.9, “Accessing BIST Mode” Section 2.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide • Flow Control: Off • Terminal ID: VT100 • Stop Bit: 1 3. Connect to the device. Once the connection is established, the login form appears. For more information about logging in to the device, refer to Section 2.2, “Logging In”. Section 2.1.2 Connecting via the Network ROS can be accessed over the network either through a Web browser, terminal or a workstation running terminal emulation software.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS 1. Select the service (i.e. Telnet, RSH or SSH). 2. Enter the IP address for the port that is connected to the network. 3. Connect to the device. Once the connection is established, the login form appears. For more information about logging in to the device, refer to Section 2.2, “Logging In”. Section 2.2 Logging In To log in to the device, do the following: 1. Connect to the device either directly or through a Web browser.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide CAUTION! To prevent unauthorized access to the device, make sure to change the default guest, operator, and admin passwords before commissioning the device. For more information about changing passwords, refer to Section 4.3, “Configuring Passwords”. 2. In the User Name field, type the username for an account setup on the device. 3. In the Password field, typ the password for the account. 4. Click Enter or click Submit (Web interface only). Section 2.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS 1 2 3 Figure 5: Web Interface Layout (Example) 1. Top Frame 2. Side Frame 3. Main Frame Frame Description Top The top frame displays the system name for the device. Side The side frame contains a logout option and a collapsible list of links that open various screens in the main frame. For information about logging out of ROS, refer to Section 2.3, “Logging Out”.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide 3 1 2 4 Figure 6: Elements of a Typical Screen (Example) 1. Title 2. Parameters and/or Data 3. Access Level or Alarm Notification 4. Controls Section 2.5 Using the Console Interface The Console interface is a Graphical User Interface (GUI) organized as a series of menus. It is primarily accessible through a serial console connection, but can also be accessed through IP services, such as a Telnet, RSH (Remote Shell), or SSH (Secure Shell) session.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS 4 5 1 2 3 Figure 7: Console Interface (Example) 1. System Identification 2. Menus 3. Command Bar 4. Menu Name 5. Alarms Indicator NOTE They system identifier is user configurable. For more information about setting the system name, refer to Section 4.1, “Configuring the System Information”.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide NOTE Before exiting a screen, ROS will automatically prompt the user to save any changes that have not been committed. Ctrl + I Inserts a new record. Ctrl + L Deletes a record. Ctrl + S Opens the CLI interface. Ctrl + X Terminates the current session. This command is only available from the main menu. Ctrl + Z Displays important information about the current screen or selected parameter. Section 2.
RUGGEDCOM ROS Chapter 2 User Guide Command Using ROS Description • port is a comma separated list of port numbers (e.g. 1,3-5,7) clrstpstats Clears all spanning tree statistics. cls Clears the screen. dir Prints the directory listing. exit Terminates the session. factory Enables factory mode, which includes several factory-level commands used for testing and troubleshooting. Only available to admin users.
Chapter 2 RUGGEDCOM ROS Using ROS Command User Guide Description pinged is not on the same network as the device pinging the other device, the default gateway must be programmed. purgemac Purges the MAC Addrtess table. reset Perform a hard reset of the switch. resetport {all | ports} Resets one or more Ethernet ports, which may be useful for forcing re-negotiation of speed and duplex, or in situations where the link partner has latched into an inappropriate state.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS Command Description Optional and/or required parameters include: • • • • dest is the remote TFTP server's IP address cmd is either put (upload) or get (download) fsource is the source filename fdest is the destination filename trace Starts event tracing. Run trace ? for more help. type filename Displays the contents of a text file.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide • option is the option to use during the trace Example: >trace transport allon TRANSPORT: Logging is enabled 4. Start the trace by typing: trace Section 2.6.3 Executing Commands Remotely via RSH The Remote Shell (RSH) facility can be used from a workstation to cause the product to act upon commands as if they were entered at the CLI prompt.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS The following sections describe in more detail how to use SQL commands: • Section 2.6.4.1, “Finding the Correct Table” • Section 2.6.4.2, “Retrieving Information” • Section 2.6.4.3, “Changing Values in a Table” • Section 2.6.4.4, “Resetting a Table” • Section 2.6.4.5, “Using RSH and SQL” Section 2.6.4.1 Finding the Correct Table Many SQL commands operate upon specific tables in the database, and require the table name to be specified.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide Retrieving Information About a Parameter from a Table Use the following command to retrieve information about a specific parameter from a table: NOTE The parameter name must be the same as it is displayed in the menu system, unless the name contains spaces (e.g. ip address). Spaces must be replaced with underscores (e.g. ip_address) or the parameter name must be wrapped in double quotes (e.g. "ip address").
RUGGEDCOM ROS Chapter 2 User Guide Port Name 1 Port 1 2 Port 2 3 Port 3 4 Port 4 Using ROS 1 2 3 4 ifName Media 1000T 1000T 1000T 1000T State Enabled On Enabled On Enabled On Enabled On AutoN Speed Dupx FlowCtrl LFI Alarm Auto Auto Off Off on Auto Auto Off Off On Auto Auto Off Off On Auto Auto Off Off On 4 records selected Section 2.6.4.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide 10.0.1.1 10.0.1.2 C:\> for /F %i in (devices) do rsh %i -l admin,admin sql select from ipAddrtable C:\>rsh 10.0.1.1 -l admin,admin sql select from ipAddrtable IP Address 192.168.0.31 Subnet 255.255.255.0 IfIndex 1001 IfStats 274409096 IfTime 2218 IfName vlan1 1 records selected C:\>rsh 10.0.1.2 -l admin,admin sql select from ipAddrtable 0 records selected C:\ Section 2.
RUGGEDCOM ROS Chapter 2 User Guide Using ROS 1. Log in to the device as an admin user and access the CLI shell. For more information about accessing the CLI shell, refer to Section 2.6, “Using the Command Line Interface”. 2. Type flashfiles. A list of files currently in Flash memory is displayed, along with their locations and the amount of memory they consume.
Chapter 2 RUGGEDCOM ROS Using ROS User Guide Section 2.8.3 Defragmenting the Flash File System The flash memory is defragmented automatically whenever there is not enough memory available for a binary upgrade. However, fragmentation can occur whenever a new file is uploaded to the unit. Fragmentation causes sectors of available memory to become separated by ones allocated to files.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Device Management This chapter describes how to configure and manage the device and its components, such as module interfaces, logs and files. It describes the following tasks: NOTE For information about how to configure the device to work with a network, refer to Chapter 5, Setup and Configuration. • Section 3.1, “Viewing Product Information” • Section 3.2, “Viewing CPU Diagnostics” • Section 3.3, “Restoring Factory Defaults” • Section 3.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 5 6 7 8 9 Figure 8: Product Information Form (Example) 1. MAC Address Box 2. Order Code Box 3. Classification Box 7. Required Boot Box 8. Hardware ID Box 9. Reload Button 4. Serial Number Box 5. Boot Version Box 6. Main Version Box This screen displays the following information: Parameter Description MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF Shows the unique MAC address of the device.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Shows the type, part number, and revision level of the hardware. Section 3.2 Viewing CPU Diagnostics To view CPU diagnostic information useful for troubleshooting hardware and software performance, navigate to Diagnostics » View CPU Diagnostics. The CPU Diagnostics form appears. 1 2 3 4 5 6 7 8 9 11 Figure 9: CPU Diagnostics Form 1. Running Time Box 2. Total Powered Time Box 3. CPU Usage Box 4. RAM Total Box Box 7.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description The size of RAM that have never been used during the system runtime. Synopsis: -32768 to 32767 C Temperature The temperature on CPU board. Synopsis: 0 to 4294967295 Free Rx Bufs Free Rx Buffers. Synopsis: 0 to 4294967295 Free Tx Bufs Free Tx Buffers. Section 3.3 Restoring Factory Defaults The device can be completely or partially restored to its original factory default settings.
RUGGEDCOM ROS Chapter 3 User Guide Device Management NOTE If the VLAN ID for the Management IP interface is not 1, setting Defaults Choice to Selected will automatically set it to 1. Parameter Description Defaults Choice Synopsis: { None, Selected, All } Setting some records like IP Interfaces management interface, default gateway, SNMP settings to default value would cause switch not to be accessible with management applications.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.4.1 Uploading/Downloading Files Using XMODEM To updload or download a file using XMODEM, do the following: NOTE This method requires a host computer that has terminal emulation or Telnet software installed and the ability to perform XMODEM transfers. NOTE Xmodem transfers can only be performed through the serial console, which is authenticated during login. 1. Establish a direct connection between the device and the host computer.
RUGGEDCOM ROS Chapter 3 User Guide Device Management IMPORTANT! TFTP does not define an authentication scheme. Any use of the TFTP client or server is considered highly insecure. NOTE This method requires a TFTP server that is accessible over the network. 1. Identify the IP address of the computer running the TFTP server. 2. Establish a direct connection between the device and a host computer. For more information, refer to Section 2.1.1, “Connecting Directly”. 3.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1. Establish a direct connection between the device and the host computer. For more information, refer to Section 2.1.1, “Connecting Directly”. 2. Initialize the TFTP server on the host computer and launch the TFTP transfer. The server will indicate when the transfer is complete. The following is an example of a successful TFTP server exchange: C:\>tftp -i 10.1.0.1 put C:\files\ROD-CF52_Main_v3.7.0.bin main.
RUGGEDCOM ROS Chapter 3 User Guide Device Management The following sections describe how to configure and manage logs: • Section 3.5.1, “Viewing Local Logs” • Section 3.5.2, “Clearing Local Logs” • Section 3.5.3, “Configuring the Local System Log” • Section 3.5.4, “Managing Remote Logging” Section 3.5.1 Viewing Local Logs The local crash and system logs can both be downloaded from the device and viewed in a text editor. For more information about downloading log files, refer to Section 3.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.5.3 Configuring the Local System Log To configure the severity level for the local system log, do the following: NOTE For maximum reliability, use remote logging. For more information, refer to Section 3.5.4, “Managing Remote Logging”. 1. Navigate to Administration » Configure Syslog » Configure Local Syslog. The Local Syslog form appears. 1 2 3 Figure 13: Local Syslog Form 1. Local Syslog Level 2. 2. Apply Button 3.
RUGGEDCOM ROS Chapter 3 User Guide Device Management • Section 3.5.4.3, “Adding a Remote Syslog Server” • Section 3.5.4.4, “Deleting a Remote Syslog Server” Section 3.5.4.1 Configuring the Remote Syslog Client To configure the remote syslog client, do the following: 1. Navigate to Administration » Configure Syslog » Configure Remote Syslog Client. The Remote Syslog Client form appears. 1 2 3 Figure 14: Remote Syslog Client Form 1. UDP Port 2. 2. Apply Button 3.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 15: Remote Syslog Server Table If remote syslog servers have not been configured, add the servers as needed. For more information, refer to Section 3.5.4.3, “Adding a Remote Syslog Server”. Section 3.5.4.3 Adding a Remote Syslog Server ROS supports up to 5 remote syslog servers (or collectors). Similar to the local system log, a remote system log server can be configured to log information at a specific severity level.
RUGGEDCOM ROS Chapter 3 User Guide Device Management 1 2 3 4 5 7 6 Figure 17: Remote Syslog Server Form 1. IP Address Box 3. 2. UDP Port Box 3. Facility Box 4. Severity Box 5. Apply Button 6. Delete Button 7. Reload Button Configure the following parameter(s) as required: Parameter Description IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Syslog server IP Address.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 18: Remote Syslog Server Table 2. Select the server from the table. The Remote Syslog Server form appears. 1 2 3 4 5 7 6 Figure 19: Remote Syslog Server Form 1. IP Address Box 3. 2. UDP Port Box 3. Facility Box 4. Severity Box 5. Apply Button 6. Delete Button 7. Reload Button Click Delete. Section 3.
RUGGEDCOM ROS Chapter 3 User Guide Device Management • Section 3.6.6, “Configuring an Ethernet Port” • Section 3.6.7, “Configuring Port Rate Limiting” • Section 3.6.8, “Configuring Port Mirroring” • Section 3.6.9, “Configuring Link Detection” • Section 3.6.10, “Detecting Cable Faults” • Section 3.6.11, “Resetting Ethernet Ports” Section 3.6.1 Controller Protection Through Link Fault Indication (LFI) Modern industrial controllers often feature backup Ethernet ports used in the event of a link failure.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Siemens offers an advanced Link-Fault-Indication (LFI) feature for the links that do not have a native link partner notification mechanism. With LFI enabled, the device bases the generation of a link integrity signal upon its reception of a link signal. In the example described previously, if switch A fails to receive a link signal from the controller, it will stop generating a link signal.
RUGGEDCOM ROS Chapter 3 User Guide Parameter Device Management Description The port's current duplex status. Section 3.6.3 Viewing Statistics for All Ethernet Ports To view statistics collected for all Ethernet ports, navigate to Ethernet Stats » View Ethernet Statistics. The Ethernet Statistics table appears.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.6.4 Viewing Statistics for Specific Ethernet Ports To view statistics collected for specific Ethernet ports, navigate to Ethernet Stats » View Ethernet Port Statistics. The Ethernet Port Statistics table appears. Figure 23: Ethernet Port Statistics Table This table displays the following information: Parameter Description Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description CRCAlignErrors Synopsis: 0 to 4294967295 The number of packets received which meet all the following conditions: • • • • OversizePkts Packet data length is between 64 and 1536 octets inclusive. Packet has invalid CRC. Collision Event has not been detected. Late Collision Event has not been detected. Synopsis: 0 to 4294967295 The number of packets received with data length greater than 1536 octets and valid CRC.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description The number of received and transmitted packets with size of 1024 to 1536 octets. This includes received and transmitted packets as well as dropped and local received packets. This does not include rejected received packets. Synopsis: 0 to 4294967295 DropEvents The number of received packets that are droped due to lack of receive buffers.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 25: Port Parameters Table 2. Select an Ethernet port. The Port Parameters form appears. 1 2 3 4 5 6 7 8 9 10 11 12 Figure 26: Port Parameters Form 1. Port Box 2. Name Box 3. Media Box 4. State Box 5. AutoN Box Box 10. Alarm Box 11. Apply Button 12. Reload Button 3. 6. Speed Box 7. Dupx Box 8. FlowCtrl Box 9.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description Media Synopsis: { 100TX, 10FL, 100FX, 1000X, 1000T, 802.11g, EoVDSL, 100TX Only, 10FL/100SX, 10GX } Default: 100TX 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. Also, when disabled link integrity signal is not sent so that the link/activity LED will never be lit.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description NOTE This feature must not be enabled at both ends of a fiber link. Synopsis: { On, Off } Default: On Alarm Disabling link state alarms will prevent alarms and LinkUp and LinkDown SNMP traps from being sent for that port.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 5 6 Figure 28: Port Rate Limiting Form 1. Port Box 3. 2. Ingress Limit Box 3. Ingress Frames List 4. Egress Limit Box 5. Apply Button 6. Reload Button Configure the following parameter(s) as required: Parameter Description Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch.
RUGGEDCOM ROS Chapter 3 User Guide Device Management will be discarded if the sum traffic exceeds the target port’s transmission rate. This problem reaches its extreme in the case where traffic on a 100 Mbps full-duplex port is mirrored onto a 10 Mbps half-duplex port. NOTE Invalid frames received on the source port will not be mirrored. These include CRC errors, oversize and undersize packets, fragments, jabbers, collisions, late collisions and dropped events.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description The port where a monitoring device should be connected. 3. Click Apply. Section 3.6.9 Configuring Link Detection To configure link detection, do the following: 1. Navigate to Ethernet Ports » Configure Link Detection. The Link Detection form appears. 1 2 4 3 Figure 30: Link Detection Form 1. Fast Link Detection Box 2. 2. Link Detection Time Box 3. Apply Button 4.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description disables FAST LINK DETECTION of a particular port, user can re-enable FAST LINK DETECTION on the port by clearing the alarm. • ON - In certain special cases where a prolonged excessive link state changes constitute a legitimate link operation, using this setting can prevent Port Guard from disabling FAST LINK DETECTION on the port in question.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 31: Cable Diagnostics Parameters Table This table displays the following information: Parameter Description Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch. State Synopsis: { Stopped, Started } Control the start/stop of the cable diagnostics on the selected port. If a port does not support cable diagnostics, State will be reported as N/A.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Pass /Fail /Total Synopsis: Any 19 characters This field summarizes the results of the cable diagnostics performed so far. Pass - number of times cable diagnostics successfully completed on the selected port. Fail - number of times cable diagnostics failed to complete on the selected port. Total - total number of times cable diagnostics have been attempted on the selected port.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 32: Cable Diagnostics Parameters Table 4. Select an Ethernet port. The Cable Diagnostics Parameters form appears. 1 2 3 4 5 6 7 8 9 10 11 Figure 33: Cable Diagnostics Parameters Form 1. Port Box 2. State Options 3. Runs Box 4. Calib. Box Fail /Total Box 10. Apply Button 11. Reload Button 5. Good Box 6. Open Box 7. Short Box 8. Imped Box 9. Pass / 5. Under Runs, enter the number of consecutive diagnostic tests to perform.
RUGGEDCOM ROS Chapter 3 User Guide 8. Device Management Click Apply. The state of the Ethernet port will automatically change to Stopped when the test is complete. For information about how to monitor the test and view the results, refer to Section 3.6.10.1, “Viewing Cable Diagnostics Results”. Section 3.6.10.3 Clearing Cable Diagnostics To clear the cable diagnostic results, do the following: 1. Navigate to Ethernet Ports » Clear Cable Diagnostics Statistics.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.6.11 Resetting Ethernet Ports At times, it may be necessary to reset a specific Ethernet port, such as when the link partner has latched into an inappropriate state. This is also useful for forcing a re-negotiation of the speed and duplex modes. To reset a specific Ethernet port(s), do the following: 1. Navigate to Ethernet Ports » Reset Port(s). The Reset Port(s) form appears. 1 2 Figure 35: Reset Port(s) Form 1. Ports 2.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Section 3.7.1 Viewing a List of IP Interfaces To view a list of IP interfaces configured on the device, navigate to Administration » Configure IP Interfaces » Configure IP Interfaces. The IP Interfaces table appears. Figure 36: IP Interfaces Table If IP interfaces have not been configured, add IP interfaces as needed. For more information, refer to Section 3.7.2, “Adding an IP Interface”. Section 3.7.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 5 6 7 9 8 Figure 38: IP Interfaces Form 1. Type Options 8. Delete Button 3. 2. ID Box 3. Mgmt Options 9. Reload Button 4. IP Address Type Box 5. IP Address Box 6. Subnet Box 7. Apply Button Configure the following parameter(s) as required: NOTE The IP address and mask configured for the management VLAN are not changed when resetting all configuration parameters to defaults and will be assigned a default VLAN ID of 1.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Subnet Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: 255.255.255.0 Specifies the IP subnet mask of this device. An IP subnet mask is a 32-bit number that is notated by using four numbers from 0 through 255, separated by periods. Typically, subnet mask numbers use either 0 or 255 as values (e.g. 255.255.255.0) but other numbers can appear. IMPORTANT! Each IP interface must have a unique network address.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 5 6 7 9 8 Figure 40: IP Interfaces Form 1. IP Address Type Box 3. 2. IP Address Box 3. Subnet Box 4. Apply Button 5. Delete Button 6. Reload Button Click Delete. Section 3.8 Managing IP Gateways ROS allows up to ten IP gateways to be configured. When both the Destination and Subnet parameters are blank, the gateway is considered to be a default gateway.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 41: IP Gateways Table If IP gateways have not been configured, add IP gateways as needed. For more information, refer to Section 3.8.2, “Adding an IP Gateway”. Section 3.8.2 Adding an IP Gateway To add an IP gateway, do the following: 1. Navigate to Administration » Configure IP Gateways. The IP Gateways table appears. 1 Figure 42: IP Gateways Table 1. InsertRecord 2. Click InsertRecord. The IP Gateways form appears.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 6 5 Figure 43: IP Gateways 1. Destination Box 3. 2. Subnet Box 3. Gateway Box 4. Apply Button 5. Delete Button 6. Reload Button Configure the following parameter(s) as required: Parameter Description Destination Synopsis: ###.###.###.### where ### ranges from 0 to 255 Specifies the IP address of destination network or host. For default gateway, both the destination and subnet are 0. Subnet Synopsis: ###.###.###.
RUGGEDCOM ROS Chapter 3 User Guide Device Management 1 2 3 4 6 5 Figure 45: IP Gateways Form 1. Destination Box 3. 2. Subnet Box 3. Gateway Box 4. Apply Button 5. Delete Button 6. Reload Button Click Delete. Section 3.9 Configuring IP Services To configure the IP services provided by the device, do the following: 1. Navigate to Administration » Configure IP Services. The IP Services form appears. 1 2 3 4 5 6 7 8 9 Figure 46: IP Services Form 1. Inactivity Timeout Box 2.
Chapter 3 RUGGEDCOM ROS Device Management Parameter User Guide Description 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 Web Server users maximum timeout value is limited to 30 minutes. Telnet Sessions Allowed Synopsis: 0 to 4 Default: 0 (controlled version) or 4 (non-controlled version) Limits the number of Telnet sessions. A value of zero prevents any Telnet access.
RUGGEDCOM ROS User Guide Chapter 3 Device Management Section 3.10.1 Managing RMON History Controls The history controls for Remote Monitoring take samples of the RMON-MIB history statistics of an Ethernet port at regular intervals. The following sections describe how to configure and manage RMON history controls: • Section 3.10.1.1, “Viewing a List of RMON History Controls” • Section 3.10.1.2, “Adding an RMON History Control” • Section 3.10.1.3, “Deleting an RMON History Control” Section 3.10.1.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 Figure 48: RMON History Controls Table 1. InsertRecord 2. Click InsertRecord. The RMON History Controls form appears. 1 2 3 4 5 6 7 10 8 9 Figure 49: RMON History Controls Form 1. Index Box 2. Port Box 3. Requested Buckets Box Button 8. Delete Button 9. Reload Button 3. 4. Granted Buckets Box 5. Interval Box 6. Owner Box 7.
RUGGEDCOM ROS Chapter 3 User Guide Parameter Device Management Description The number of buckets granted for this RMON collection history. This field is not editable. Interval Synopsis: 1 to 3600 Default: 1800 The number of seconds in over which the data is sampled for each bucket. The range is 1 to 3600. The default is 1800. Owner Synopsis: Any 127 characters Default: Monitor The owner of this record. It is suggested to start this string withword 'monitor'. 4. Click Apply. Section 3.10.1.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 1 2 3 4 5 6 7 10 8 9 Figure 51: RMON History Controls Form 1. Index Box 2. Port Box 3. Requested Buckets Box Button 8. Delete Button 9. Reload Button 3. 4. Granted Buckets Box 5. Interval Box 6. Owner Box 7. Apply Click Delete. Section 3.10.2 Managing RMON Alarms When Remote Monitoring (RMON) alarms are configured, ROS examines the state of a specific statistical variable.
RUGGEDCOM ROS User Guide Chapter 3 Device Management Figure 52: The Alarm Process There are two methods to evaluate a statistic in order to determine when to generate an event: delta and absolute. For most statistics, such as line errors, it is appropriate to generate an alarm when a rate is exceeded. The alarm defaults to the delta measurement method, which examines changes in a statistic at the end of each measurement period.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.10.2.2 Adding an RMON Alarm To add an RMON alarm, do the following: 1. Navigate to Ethernet Stats » Configure RMON Alarms. The RMON Alarms table appears. 1 Figure 54: RMON Alarms Table 1. InsertRecord 2. Click InsertRecord. The RMON Alarms form appears. 1 2 3 4 5 6 7 8 9 10 11 12 14 13 Figure 55: RMON Alarms Form 1. Index Box 2. Variable Box 3. Rising Thr Box 4. Falling Thr Box 5. Value Box 6. Type Options 7. Interval Box 8.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Index Synopsis: 1 to 65535 Default: 1 The index of this RMON Alarm record. Variable Synopsis: SNMP Object Identifier - up to 39 characters 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'.
Chapter 3 RUGGEDCOM ROS Device Management Parameter User Guide Description The index of the event that is used when a rising threshold is crossed. If there is no corresponding entryl 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 withword 'monitor'. 4. Click Apply. Section 3.10.2.
RUGGEDCOM ROS Chapter 3 User Guide Device Management 1 2 3 4 5 6 7 8 9 10 11 12 14 13 Figure 57: RMON Alarms Form 1. Index Box 2. Variable Box 3. Rising Thr Box 4. Falling Thr Box 5. Value Box 6. Type Options 7. Interval Box 8. Startup Alarm List 9. Rising Event Box 10. Falling Event Box 11. Owner Box 12. Apply Button 13. Delete Button 14. Reload Button 3. Click Delete. Section 3.10.3 Managing RMON Events Remote Monitoring (RMON) events define behavior profiles used in event logging.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.10.3.1 Viewing a List of RMON Events To view a list of RMON events, navigate to Ethernet Stats » Configure RMON Events. The RMON Events table appears. Figure 58: RMON Events Table If events have not been configured, add events as needed. For more information, refer to Section 3.10.3.2, “Adding an RMON Event”. Section 3.10.3.2 Adding an RMON Event To add an RMON alarm, do the following: 1.
RUGGEDCOM ROS Chapter 3 User Guide Device Management 1 2 3 4 5 6 7 9 8 Figure 60: RMON Events Form 1. Index Box 2. Type List 3. Community Box 4. Last Time Sent Box 8. Delete Button 9. View Button 10. Reload Button 3. 5. Description Box 6. Owner Box 7. Apply Button Configure the following parameter(s) as required: Parameter Description Index Synopsis: 1 to 65535 Default: 3 The index of this RMON Event record.
Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.10.3.3 Deleting an RMON Event To delete an RMON event, do the following: 1. Navigate to Ethernet Stats » Configure RMON Events. The RMON Events table appears. Figure 61: RMON Events Table 2. Select the event from the table. The RMON Events form appears. 1 2 3 4 5 6 7 9 8 Figure 62: RMON Events Form 1. Index Box 2. Type List 3. Community Box 4. Last Time Sent Box 8. Delete Button 9. View Button 10. Reload Button 3. 5.
RUGGEDCOM ROS Chapter 3 User Guide Device Management Section 3.11.1 Upgrading Firmware Upgrading ROS firmware, including the main, bootloader and FPGA firmware, may be necessary to take advantage of new features or bug fixes. Binary firmware images are available from Siemens . Visit www.siemens.com/ruggedcom to determine which versions/updates are available or contact Siemens Customer Support.
Chapter 3 RUGGEDCOM ROS Device Management User Guide 2. Log in to the device as an admin user. For more information, refer to Section 2.2, “Logging In”. 3. Make a local copy of the current configuration file. For more information, refer to Section 3.4, “Uploading/ Downloading Files”. IMPORTANT! Never downgrade the ROS software version beyond ROS v4.1 when encryption is enabled. Make sure the device has been restored to factory defaults before downgrading. 4.
RUGGEDCOM ROS User Guide Chapter 3 Device Management Section 3.13 Decommissioning the Device Before taking the device out of service, either permanently or for maintenance by a third-party, make sure the device has been fully decommissioned. This includes removing any sensitive, proprietary information. To decommission the device, do the following: 1. Disconnect all network cables from the device. 2. Connect to the device via the RS232 serial console port. For more information, refer to Section 2.1.
RUGGEDCOM ROS User Guide Decommissioning the Device Chapter 3 Device Management 98
RUGGEDCOM ROS Chapter 4 User Guide System Administration System Administration This chapter describes how to perform various administrative tasks related to device identification, user permissions, alarm configuration, certificates and keys, and more. It describes the following tasks: • Section 4.1, “Configuring the System Information” • Section 4.2, “Customizing the Login Screen” • Section 4.3, “Configuring Passwords” • Section 4.4, “Managing Alarms” • Section 4.
Chapter 4 RUGGEDCOM ROS System Administration User Guide Parameter Description Contact Synopsis: Any 49 characters The contact can be used to help identify the person responsible for managing the switch. You can enter name, phone number, email, etc. It is displayed in the login screen so that this person may be contacted should help be required. 3. Click Apply. Section 4.
RUGGEDCOM ROS Chapter 4 User Guide System Administration NOTE Users can also be verified through a RADIUS or TACACS+ server. When enabled for authentication and authorization, the RADIUS or TACACS+ server will be used in the absence of any local settings. For more information about configuring a RADIUS or TACACS+ server, refer to Section 4.6, “Managing an Authentication Server”.
Chapter 4 RUGGEDCOM ROS System Administration User Guide An alarm will generate if a weak password is configured. The weak password alarm can be disabled by the user. For more information about disabling alarms, refer to Section 4.4, “Managing Alarms”. 2.
RUGGEDCOM ROS Chapter 4 User Guide System Administration Parameter Description Related username is in field Admin Username; full read/write access to all settings and commands. Confirm Admin Password Synopsis: 15 character ASCII string Related username is in field Admin Username; full read/write access to all settings and commands. 3. Click Apply. Section 4.4 Managing Alarms Alarms indicate the occurrence of events of either importance or interest that are logged by the device.
Chapter 4 System Administration RUGGEDCOM ROS User Guide Figure 66: Alarms Table NOTE This list of alarms (configurable and non-configurable) is accessible through the Command Line Interface (CLI) using the alarms. For more information, refer to Section 2.6.1, “Available CLI Commands”. For information about modifying a pre-configured alarm, refer toSection 4.4.3, “Configuring an Alarm”. Section 4.4.
RUGGEDCOM ROS Chapter 4 User Guide System Administration Figure 67: Latched Alarms Table To clear the passive alarms from the list, do the following: 1. Navigate to Diagnostics » Clear Latched Alarms. The Clear Latched Alarms form appears. 1 Figure 68: Clear Latched Alarms Form 1. Confirm Button 2. Click Confirm. Section 4.4.3 Configuring an Alarm While all alarms are pre-configured on the device, some alarms can be modified to suit the application.
Chapter 4 System Administration RUGGEDCOM ROS User Guide Figure 69: Alarms Table 2. 106 Select an alarm. The Alarms form appears.
RUGGEDCOM ROS Chapter 4 User Guide System Administration 1 2 3 4 5 6 7 8 10 9 Figure 70: Alarms Form 1. Name Box 2. Level Box 3. Latch Box 4. Trap Box Button 9. Delete Button 10. Reload Button 3. 5. Log Box 6. LED & Relay Box 7. Refresh Time Box 8. Apply Configure the following parameter(s) as required: Parameter Description Name Synopsis: Any 34 characters Default: sys_alarm The alarm name, as obtained through the alarms CLI command.
Chapter 4 RUGGEDCOM ROS System Administration User Guide Parameter Description LED & Relay Synopsis: { On, Off } Default: Off Enables LED and fail-safe relay control for this alarm. If latching is not enabled, this field will remain disabled. Refresh Time Synopsis: 0 s to 60 s Default: 60 s Refreshing time for this alarm. 4. Click Apply. Section 4.4.
RUGGEDCOM ROS Chapter 4 User Guide System Administration Message Name Weak Password Configured Alarm SNMP Trap Syslog Yes Yes Yes Default Keys In Use ROS generates this alarm and logs a message in the syslog when default keys are in use. For more information about default keys, refer to Section 1.8, “Certificate and Key Requirements”. NOTE For Non-Controlled (NC) versions of ROS, this alarm is only generated when default SSL keys are in use.
Chapter 4 RUGGEDCOM ROS System Administration User Guide TACACS+ Response Invalid ROS generate this alarm and logs a message in the syslog when the response from the TACACS+ server is received with an invalid CRC. Message Name TACACS Response Invalid Alarm SNMP Trap Syslog Yes Yes Yes SNMP Authentication Failure ROS generates this alarm, sends an authentication failure trap, and logs a message in the syslog when an SNMP manager with incorrect credentials communicates with the SNMP agent in ROS.
RUGGEDCOM ROS Chapter 4 User Guide System Administration Message Name Alarm SNMP Trap Syslog 802.1X Port X Authentication Failure Yes Yes Yes 802.1X Port X Authorized Addr. XXX No No Yes Section 4.5 Managing the Configuration File The device configuration file for ROS is a single CSV (Comma-Separate Value) formatted ASCII text file, named config.csv. It can be downloaded from the device to view, compare against other configuration files, or store for backup purposes.
Chapter 4 RUGGEDCOM ROS System Administration 1. User Guide Navigate to Administration » Configure Data Storage. The Data Storage form appears. 1 2 3 4 5 Figure 71: Data Storage Form 1. Encryption Options 2. 2. Passphrase Box 3. Confirm Passphrase Box 4. Apply Button 5. Reload Button Configure the following parameter(s) as required: Parameter Description Encryption Synopsis: { On, Off } Enable/disable encryption of data in configuration file.
RUGGEDCOM ROS Chapter 4 User Guide System Administration ROS also has the ability to accept partial configuration updates. For example, to update only the parameters for Ethernet port 1 and leave all other parameters unchanged, transfer a file containing only the following lines to the device: # Port Parameters ethPortCfg Port,Name,Media,State,AutoN,Speed,Dupx,FlowCtrl,LFI,Alarm, 1,Port 1,100TX,Enabled,On,Auto,Auto,Off,Off,On, Section 4.
Chapter 4 RUGGEDCOM ROS System Administration User Guide Attribute Value Vendor-Specific Vendor-ID: 15004 Type: 1 Length: 11 String: RuggedCom A RADIUS server may also be used to authenticate access on ports with 802.1X security support.
RUGGEDCOM ROS Chapter 4 User Guide System Administration NOTE The RADIUS client uses the Password Authentication Protocol (PAP) to verify access. To configure access to either the primary or backup RADIUS servers, do the following: 1. Navigate to Administration » Configure Security Server » Configure RADIUS Server. The RADIUS Server table appears. Figure 72: RADIUS Server Table 2. Select either Primary or Backup from the table. The RADIUS Server form appears.
Chapter 4 RUGGEDCOM ROS System Administration User Guide Parameter Description Confirm Auth Key Synopsis: 31 character ASCII string The authentication key to be shared with server. 4. Click Apply. Section 4.6.
RUGGEDCOM ROS Chapter 4 User Guide System Administration 1 2 3 4 5 7 6 Figure 75: TACACS Plus Server Form 1. Server Box Button 3. 2. IP Address Box 3. Auth TCP Port Box 4. Auth Key Box 5. Confirm Key Box 6. Apply Button 7. Reload Configure the following parameter(s) as required: Parameter Description Server Synopsis: Any 8 characters Default: Primary This field tells whether this configuration is for a Primary or a Backup Server. IP Address Synopsis: ###.###.###.
Chapter 4 RUGGEDCOM ROS System Administration User Guide • 1 represents the guest access level To configure the privilege levels for each user type, do the following: 1. Navigate to Administration » Configure Security Server » Configure TacPlus Server » Configure TACPLUS Serv Privilege Config. The TACPLUS Serv Privilege Config form appears. 1 2 3 4 5 Figure 76: TACPLUS Serv Privilege Config Form 1. Server Box 2. 2. IP Address Box 3. Auth TCP Port Box 4. Apply Button 5.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Setup and Configuration This chapter describes how to setup and configure the device for use on a network using the various features available in ROS. It describes the following tasks: • Section 5.1, “Configuring the DHCP Relay Agent” • Section 5.2, “Managing Virtual LANs” • Section 5.3, “Managing Spanning Tree Protocol” • Section 5.4, “Managing Classes of Service” • Section 5.5, “Managing MAC Addresses” • Section 5.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 4 Figure 77: DHCP Relay Agent Form 1. DHCP Server Address Box 2. 2. DHCP Client Ports 3. Apply Button 4. Reload Button Configure the following parameter(s) as required: Parameter Description DHCP Server Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 Default: This parameter specifies the IP address of the DHCP server to which DHCP queries will be forwarded from this relay agent.
RUGGEDCOM ROS User Guide Chapter 5 Setup and Configuration VLANs can be learned through GVRP. For more information about GVRP, refer to Section 5.2.1.8, “GARP VLAN Registration Protocol (GVRP)” For more information about VLANs, refer to Section 5.2.1, “VLAN Concepts”. The following sections describe how to configure and manage VLANs: • Section 5.2.1, “VLAN Concepts” • Section 5.2.2, “Viewing a List of VLANs” • Section 5.2.3, “Enabling/Disabling VLAN-Aware Mode” • Section 5.2.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.2.1.3 The Management VLAN Management traffic, like all traffic on the network, must belong to a specific VLAN. The management VLAN is configurable and always defaults to VLAN 1. This VLAN is also the default native VLAN for all ports, thus allowing all ports the possibility of managing the product. Changing the management VLAN can be used to restrict management access to a specific set of users. Section 5.2.1.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration a Frame Received Frame dropped due to its tagged/untagged format a Untagged Priority Tagged (VID = 0) Tagged (Valid VID) No No No Does not depend on the ingress port's VLAN configuration parameters. Egress rules are applied as follows to all frames when they are transmitted by the switch.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.2.1.8 GARP VLAN Registration Protocol (GVRP) GARP VLAN Registration Protocol (GVRP) is a standard protocol built on GARP (Generic Attribute Registration Protocol) to automatically distribute VLAN configuration information in a network. Each switch in a network needs only to be configured with VLANs it requires locally. VLANs configured elsewhere in the network are learned through GVRP. A GVRP-aware end station (i.e.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Ports A1, B1 to B4, C1, D1, D2 and E1 are GVRP aware • Ports B1 to B4, D1 and D2 are set to advertise and learn • Ports A1, C1 and E1 are set to advertise only • Ports A2, C2 and E2 are edge ports • End node D is GVRP aware • End nodes A, E and C are GVRP unaware • Ports A2 and C2 are configured with PVID 7 • Port E2 is configured with PVID 20 • End node D is interested in VLAN 20, hence VLAN 20 is advertised by it towards switch D • D2 become
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide The use of creative bridge filtering and multiple VLANs can carve seemingly unified IP subnets into multiple regions policed by different security/access policies. Multi-VLAN hosts can assign different traffic types to different VLANs. 1 3 2 2 5 4 Figure 79: Multiple Overlapping VLANs 1. VLAN 2.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 199.85.245.1/25 3 199.85.245.128/26 4 199.85.245.192/26 5 2 Figure 80: Inter-VLAN Communications 1. Server, Router or Layer 3 Switch 2. Switch 3. VLAN 2 4. VLAN 3 5. VLAN 4 Section 5.2.2 Viewing a List of VLANs To view a list of all VLANs, whether they were created statically, implicitly or dynamically, navigate to Virtual LANs » View VLAN Summary. The VLAN Summary table appears.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 Figure 82: Global VLAN Parameters Form 1. VLAN-Aware Mode Options 2. 2. Apply Button 3. Reload Button Configure the following parameter(s) as required: Parameter Description VLAN-aware Synopsis: { No, Yes } Default: Yes Set either VLAN-aware or VLAN-unaware mode of operation. 3. Click Apply. Section 5.2.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 6 7 Figure 84: Port VLAN Parameters Form 1. Port(s) Box 3. 2. Type List 3. PVID Box 4. PVID Format Options 5. GVRP List 6. Apply Button 7. Reload Button Configure the following parameter(s) as required: Parameter Description 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).
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description • ADVERTISE ONLY - the port will declare all VLANs existing in the switch (configured or learned) but will not learn any VLANs. • ADVERTISE & LEARN - the port will declare all VLANs existing in the switch (configured or learned) and can dynamically learn VLANs. Only Trunk ports are GVRP-capable. 4. Click Apply. Section 5.2.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 Figure 86: Static VLANs Table 1. InsertRecord 2. Click InsertRecord. The Static VLANs form appears. 1 2 3 4 5 8 6 7 Figure 87: Static VLANs Form 1. VID Box 2. VLAN Name Box 8. Reload Button 3. 3. Forbidden Ports Box 4. IGMP Options 5. MSTI Box 6. Apply Button 7.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description The VLAN Identifier is used to identify the VLAN in tagged Ethernet frames according to IEEE 802.1Q. VLAN Name Synopsis: Any 19 characters 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 These are ports that are not allowed to be members of the VLAN.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 8 6 7 Figure 89: Static VLANs Form 1. VID Box 2. VLAN Name Box 8. Reload Button 3. 3. Forbidden Ports Box 4. IGMP Options 5. MSTI Box 6. Apply Button 7. Delete Button Click Delete. Section 5.3 Managing Spanning Tree Protocol The following sections describe how to configure and manage STP: • Section 5.3.1, “RSTP Operation” • Section 5.3.2, “RSTP Applications” • Section 5.3.3, “Configuring STP Globally” • Section 5.3.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide The Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) was a further evolution of the 802.1D Spanning Tree Protocol. It replaced the settling period with an active handshake between bridges that guarantees the rapid propagation of topology information throughout the network.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration the network. When it is determined that the port will play an active part in the network, the state will change to learning. 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.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide A port is a Backup Port when it receives a better message from the LAN segment it is connected to, originating from another port on the same bridge. The port is a backup for another port on the bridge and will become active if that port fails. The Backup Port does not participate in the network. Section 5.3.1.2 Edge Ports A port may be designated as an Edge Port if it is directly connected to an end station.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration bridge is used to select the root port. In all cases the lower ID, path cost or port ID is selected as the best. How Port Costs Are Generated Port costs can be generated either as a result of link auto-negotiation or manual configuration. When the link auto-negotiation method is used, the port cost is derived from the speed of the link. This method is useful when a well-connected network has been established.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide Section 5.3.1.6 eRSTP Siemens's enhanced Rapid Spanning Tree Protocol (eRSTP) improves the performance of RSTP in two ways: • Improves the fault recovery time performance (< 5 ms per hop) • Improves performance for large ring network topologies (up to 80 switches) eRSTP is also compatible with standard RSTP for interoperability with commercial switches.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.3.2 RSTP Applications The following sections describe various applications of RSTP: • Section 5.3.2.1, “RSTP in Structured Wiring Configurations” • Section 5.3.2.2, “RSTP in Ring Backbone Configurations” • Section 5.3.2.3, “RSTP Port Redundancy” Section 5.3.2.1 RSTP in Structured Wiring Configurations RSTP may be used to construct structured wiring systems where connectivity is maintained in the event of link failures.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide To design a structured wiring configuration, do the following: 1. Select the design parameters for the network. What are the requirements for robustness and network failover/recovery times? Are there any special requirements for diverse routing to a central host computer? Are there any special port redundancy requirements? 2. Identify required legacy support.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration A 1 B K I 3 3 1 3 3 L D 2 C 2 E 2 G 1 333 666 2 3 J F 1 555 2 H 3 1 444 Figure 92: Example - Ring Backbone Configuration To design a ring backbone configuration with RSTP, do the following: 1. Select the design parameters for the network. What are the requirements for robustness and network fail-over/recovery times? Typically, ring backbones are chosen to provide cost effective but robust network designs. 2.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide The strategy that should be used is to assign each bridge’s priority to correspond to its distance from the root bridge. If the root bridge is assigned the lowest priority of 0, the bridges on either side should use a priority of 4096 and the next bridges 8192 and so on. As there are 16 levels of bridge priority available, this method provides for up to 31 bridges in the ring. 6. Decide upon a port cost calculation strategy.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 6 7 8 9 10 Figure 94: Bridge RSTP Parameters Form 1. State Options 2. Version Support List 3. Bridge Priority List 4. Hello Time Box 5. Max Age Time Box Box 7. Forward Delay Box 8. Max Hops Box 9. Apply Button 10. Reload Button 2. 6. Transmit Count Configure the following parameter(s) as required: Parameter Description State Synopsis: { Disabled, Enabled } Default: Enabled Enable STP/RSTP for the bridge globally.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Transmit Count Synopsis: 3 to 100 or { Unlimited } Default: Unlimited Maximum number of BPDUs on each port that may be sent in one second. Larger values allow the network to recover from failed links/bridges more quickly. Forward Delay Synopsis: 4 to 30 s Default: 15 s The amount of time a bridge spends learning MAC addresses on a rising port before beginning to forward traffic.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 6 7 8 9 10 11 Figure 96: Port RSTP Parameters Form 1. Port(s) Box 2. Enabled Options 3. Priority List 4. STP Cost Box 5. RSTP Cost Box 6. Edge Port List List 8. Restricted Role Box 9. Restricted TCN Box 10. Apply Button 11. Reload Button 3. 7.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description the ability to preferentially select specific ports to carry traffic over others. Leave this field set to "auto" to use the standard RSTP port costs as negotiated (20,000 for 1Gbps, 200,000 for 100 Mbps links and 2,000,000 for 10 Mbps links). Edge Port Synopsis: { False, True, Auto } Default: Auto Edge ports are ports that do not participate in the Spanning Tree, but still send configuration messages.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 6 7 Figure 97: eRSTP Parameters Form 1. Max Network Diameter Options 2. BPDU Guart Timeout Box 3. Fast Root Failover List Options 5. Cost Style Options 6. Apply Button 7. Reload Button 2. 4. IEEE802.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description • In a single ring topology, this feature is not needed and should be disabled to avoid longer network recovery times due to extra RSTP processing. The Fast Root Failover algorithm must be supported by all switches in the network, including the root, to guarantee optimal performance. However, it is not uncommon to assign the root role to a switch from a vendor different from the rest of the switches in the network.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 98: Bridge RSTP Statistics Form This table displays the following information: Parameter Description 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.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description The actual Forward Delay time provided by the root bridge as learned in configuration messages. This time is used in designated bridges. Configured Max Age Synopsis: 0 to 65535 The configured Maximum Age time from the Bridge RSTP Parameters menu. Learned Max Age Synopsis: 0 to 65535 The actual Maximum Age time provided by the root bridge as learned in configuration messages. This time is used in designated bridges.
RUGGEDCOM ROS Chapter 5 User Guide Parameter Setup and Configuration Description • Forwarding - The port is forwarding traffic. 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.
Chapter 5 RUGGEDCOM ROS Setup and Configuration 1. User Guide Navigate to Spanning Tree » Clear Spanning Tree Statistics. The Clear Spanning Tree Statistics form appears. 1 Figure 100: Clear Spanning Tree Statistics Form 1. Confirm Button 2. Click Confirm. Section 5.4 Managing Classes of Service Classes of Service (CoS) provides the ability to expedite the transmission of certain frames and port traffic over others. The CoS of a frame can be set to Normal or Critical.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration After inspection, the frame is forwarded to the egress port for transmission. 2. Forwarding Phase Once the CoS of the frame is determined, the frame is forwarded to the egress port, where it is collected into one of the priority queues according to the assigned CoS. CoS weighting selects the degree of preferential treatment that is attached to different priority queues.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description • 6:1 - 6 Critical priority CoS frames and 1 Normal priority CoS frame • 1:0 - Normal priority CoS frames will be only transmitted after all Critical priority CoS frames have been transmitted 3. Click Apply. 4. If necessary, configure CoS mapping based on either the IEEE 802.1p priority or Differentiated Services (DS) field set in the IP header for each packet. For more information, refer to Section 5.4.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description 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). Default CoS Synopsis: { Normal, Crit } Default: Normal This parameter allows to prioritize frames received on this port that are not prioritized based on the frames contents (e.g.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 4 Figure 105: Priority to CoS Mapping Form 1. Priority Box 3. 2. CoS Options 3. Apply Button 4. Reload Button Configure the following parameter(s) as required: Parameter Description Priority Synopsis: 0 to 7 Default: 0 Value of the IEEE 802.1p priority. CoS Synopsis: { Normal, Crit } Default: Normal CoS assigned to received tagged frames with the specified IEEE 802.1p priority value. 4. Click Apply. Section 5.4.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 106: Access Priorities Table 2. Select a port. The Access Priorities form appears. 1 2 3 4 5 Figure 107: Access Priorities Form 1. Priority Box 3. 2. CoS Options 3. Apply Button 4.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description of Service upon receiving and is getting tagged upon transmission from the specified port. This parameter does not affect frames that were originally received tagged. 4. Click Apply. Section 5.4.5 Configuring DSCP to CoS Mapping Mapping CoS to the Differentiated Services (DS) field set in the IP header for each packet is done by defining Differentiated Services Code Points (DSCPs) in the CoS configuration.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description DSCP Synopsis: 0 to 63 Default: 0 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, Crit } Default: Normal Class of Service assigned to received frames with the specified DSCP. 4. Click Apply. 5. Configure the CoS parameters on select switched Ethernet ports as needed. For more information, refer to Section 5.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • Configure the address on the device as a static MAC address. For more information, refer to Section 5.5.3.2, “Adding a Static MAC Address”. Section 5.5.2 Configuring MAC Address Learning Options The MAC address learning options control how and when MAC addresses are removed automatically from the MAC address table. Individual addressees are removed when the aging timer is exceeded.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.5.3 Managing Static MAC Addresses Static MAC addresses must be configured when the device is only able to receive frames, not transmit them. They may also need to be configured if port security (if supported) must be enforced. Prioritized MAC addresses are configured when traffic to or from a specific device on a LAN segment is to be assigned a higher CoS priority than other devices on that LAN segment.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 Figure 113: Static MAC Addresses Table 1. InsertRecord 2. Click InsertRecord. The Static MAC Addresses form appears. 1 2 3 4 5 7 6 Figure 114: Static MAC Addresses Form 1. MAC Address Box 3. 2. VID Box 3. Port Box 4. CoS Options 5. Apply Button 6. Delete Button 7.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description Enter the port number upon which the device with this address is located. The security mode of the port being selected should not be '802.1X'. If the port should be auto-learned, set this parameter to 'Learn'. The option 'Learn' is applicable for Port Security in 'Static MAC' mode. Synopsis: { Normal, Crit } Default: Normal CoS Prioritizes traffic for the specified MAC address. 4. Click Apply. Section 5.5.3.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.5.4 Purging All Dynamic MAC Addresses To purge the dynamic MAC address list of all entries, do the following: 1. Navigate to MAC Address Tables » Purge MAC Address Table. The Purge MAC Address Table form appears. 1 Figure 117: Purge MAC Address Table Form 1. Confirm Button 2. Click Confirm. Section 5.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 5 6 7 Figure 118: Time and Date Form 1. Time 2. 2. Date 3. Time Zone 4. DST Offset 5. DST Rule 6. Apply Button 7. Reload Button Configure the following parameter(s) as required: Parameter Description Time Synopsis: HH:MM:SS This parameter allows for both the viewing and setting of the local time. Date Synopsis: MMM DD, YYYY This parameter allows for both the viewing and setting of the local date.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description DST ends on November's 1st Sunday at 2:00am. Section 5.6.2 Configuring NTP ROS may be configured to refer periodically to a specified NTP server to correct any accumulated drift in the onboard clock. ROS will also serve time via the Simple Network Time Protocol (SNTP) to hosts that request it. Two NTP servers (primary and backup) may be configured for the device.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description IP Address Synopsis: ###.###.###.### where ### ranges from 0 to 255 The Server IP Address. Synopsis: 1 to 1440 min Default: 60 min Update Period Determines how frequently the (S)NTP server is polled for a time update.If the server cannot be reached in three attempts that are made at one minute intervals an alarm is generated. 4. Click Apply. Section 5.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.7.1 Managing SNMP Users The following sections describe how to configure and manage SNMP users, refer to the following: • Section 5.7.1.1, “Viewing a List of SNMP Users” • Section 5.7.1.2, “Adding an SNMP User” • Section 5.7.1.3, “Deleting an SNMP User” Section 5.7.1.1 Viewing a List of SNMP Users To view a list of SNMP users configured on the device, navigate to Administration » Configure SNMP » Configure SNMP Users.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 Figure 122: SNMP Users Table 1. InsertRecord 2. Click InsertRecord. The SNMP Users form appears. 1 2 3 4 5 6 7 8 9 10 12 11 Figure 123: SNMP Users Form 1. Name Box 2. IP Address Box 3. v1/v2c Community Box 4. Auth Protocol Box 5. Priv Protocol Box 6. Auth Key Box 7. Confirm Auth Key Box 8. Priv Key Box 9. Confirm Priv Key Box 10. Apply Button 11. Delete Button 12.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • Must have at least one alphabetic character and one number. Special characters are permitted. • Must not have more than 3 continuously incrementing or decrementing numbers. For example, Sub123 and Sub19826 are permitted, but Sub12345 is not. An alarm will generate if a weak password is configured. The weak password alarm can be disabled by the user. For more information about disabling alarms, refer to Section 4.4, “Managing Alarms”. 3.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.7.1.3 Deleting an SNMP User To delete an SNMP user, do the following: 1. Navigate to Administration » Configure SNMP » Configure SNMP Users. The SNMP Users table appears. Figure 124: SNMP Users Table 2. Select the user from the table. The SNMP Users form appears. 1 2 3 4 5 6 7 8 9 10 12 11 Figure 125: SNMP Users Form 1. Name Box 2. IP Address Box 3. v1/v2c Community Box 4. Auth Protocol Box 5. Priv Protocol Box 6.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide Section 5.7.2 Managing Security-to-Group Mapping The following sections describe how to configure and manage security-to-group maps, refer to the following: • Section 5.7.2.1, “Viewing a List of Security-to-Group Maps” • Section 5.7.2.2, “Adding a Security-to-Group Map” • Section 5.7.2.3, “Deleting a Security-to-Group Map” Section 5.7.2.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 Figure 127: SNMP Security to Group Maps Table 1. InsertRecord 2. Click InsertRecord. The SNMP Security to Group Maps form appears. 1 2 3 4 6 5 Figure 128: SNMP Security to Group Maps Form 1. Security Model Box 3. 2. Name Box 3. Group Box 4. Apply Button 5. Delete Button 6.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.7.2.3 Deleting a Security-to-Group Map To delete a security-to-group map, do the following: 1. Navigate to Administration » Configure SNMP » Configure SNMP Security to Group Maps. The SNMP Security to Group Maps table appears. Figure 129: SNMP Security to Group Maps Table 2. Select the map from the table. The SNMP Security to Group Maps form appears. 1 2 3 4 6 5 Figure 130: SNMP Security to Group Maps Form 1.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.7.3.1 Viewing a List of SNMP Groups To view a list of SNMP groups configured on the device, navigate to Administration » Configure SNMP » Configure SNMP Access. The SNMP Access table appears. Figure 131: SNMP Access Table If SNMP groups have not been configured, add groups as needed. For more information, refer to Section 5.7.3.2, “Adding an SNMP Group”. Section 5.7.3.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 4 5 6 7 9 8 Figure 133: SNMP Access Form 1. Group Box 2. Security Model Box 3. Security Level Box 4. ReadViewName Box 6. NotifyViewName Box 7. Apply Button 8. Delete Button 9. Reload Button 3. 5. WriteViewName Box Configure the following parameter(s) as required: Parameter Description Group Synopsis: Any 32 characters The group name to which the security model and name belong.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.7.3.3 Deleting an SNMP Group To delete an SNMP group, do the following: 1. Navigate to Administration » Configure SNMP » Configure SNMP Access. The SNMP Access table appears. Figure 134: SNMP Access Table 2. Select the group from the table. The SNMP Access form appears. 1 2 3 4 5 6 7 9 8 Figure 135: SNMP Access Form 1. Group Box 2. Security Model Box 3. Security Level Box 4. ReadViewName Box 6. NotifyViewName Box 7.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide • Section 5.8.2, “Configuring LLDP Globally” • Section 5.8.3, “Configuring LLDP for an Ethernet Port” • Section 5.8.4, “Enabling/Disabling RCDP” • Section 5.8.5, “Viewing Global Statistics and Advertised System Information” • Section 5.8.6, “Viewing Statistics for LLDP Neighbors” • Section 5.8.7, “Viewing Statistics for LLDP Ports” Section 5.8.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration configuration tools to configure them. The behavior of IP-based mechanisms such as the web interface, SSH, telnet, or SNMP will all be undefined. Since RCDP operates at Layer 2, it can be used to reliably and unambiguously address multiple devices even though they may share the same IP configuration. Siemens 's RUGGEDCOM Explorer is a lightweight, standalone Windows application that supports RCDP.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 4 5 6 7 Figure 136: Global LLDP Parameters Form 1. State Options 2. 2. Tx Interval Box 3. Tx Hold Box 4. Reinit Delay Box 5. Tx Delay Box 6. Apply Button 7. Reload Button Configure the following parameter(s) as required: Parameter Description State Synopsis: { Disabled, Enabled } Default: Enabled Enables LLDP protocol.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.8.3 Configuring LLDP for an Ethernet Port To configure LLDP for a specific Ethernet Port, do the following: 1. Navigate to Network Discovery » Link Layer Discovery Protocol » Configure Port LLDP Parameters. The Port LLDP Parameters table appears. Figure 137: Port LLDP Parameters Table 2. Select a port. The Port LLDP Parameters form appears. 1 2 3 4 5 Figure 138: Port LLDP Parameters Form 1. Port Box 3. 2.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description rxOnly: the local LLDP agent can only receive LLDP frames. disabled: the local LLDP agent can neither transmit or receive LLDP frames. Notifications Synopsis: { Disabled, Enabled } Default: Disabled Disabling notifications will prevent sending notifications and generating alarms for particular port from the LLDP agent. 4. Click Apply. Section 5.8.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 Figure 139: RCDP Parameters Form 1. RCDP Discovery Options 2. Apply Button 3. Reload Button 2. Select Enabled to enable RCDP, or select Disabled to disable RCDP. 3. Click Apply. Section 5.8.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description A number of times an entry was deleted from LLDP Neighbor Information Table because the information timeliness interval has expired. Synopsis: 0 to 4294967295 Ageouts A counter of all TLVs discarded. Section 5.8.6 Viewing Statistics for LLDP Neighbors To view statistics for LLDP neighbors, navigate to Network Discovery » Link Layer Discovery Protocol » View LLDP Neighbor Information.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.8.7 Viewing Statistics for LLDP Ports To view statistics for LLDP ports, navigate to Network Discovery » Link Layer Discovery Protocol » View LLDP Statistics. The LLDP Statistics table appears. Figure 142: LLDP Statistics Table This table displays the following information: Parameter Description Port Synopsis: 1 to maximum port number The port number as seen on the front plate silkscreen of the switch.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide Section 5.9 Managing Multicast Filtering Multicast traffic can be filtered using either static multicast groups, IGMP (Internet Group Management Protocol) snooping, or GMRP (GARP Multicast Registration Protocol). The following sections describe how to configure and manage multicast filtering: • Section 5.9.1, “Multicast Filtering Concepts” • Section 5.9.1.2, “GMRP (GARP Multicast Registration Protocol)” • Section 5.9.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 M1 M2 2 3 4 3 4 5 4 4 Figure 143: Example – IGMP In Operation 1. Producer 2. Membership Queries 3. Membership Reports 4. Host 5. Multicast Router One producer IP host (P1) is generating two IP multicast streams, M1 and M2. There are four potential consumers of these streams, C1 through C4. The multicast router discovers which host wishes to subscribe to which stream by sending general membership queries to each segment.
Chapter 5 Setup and Configuration RUGGEDCOM ROS User Guide 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. NOTE A switch running in passive mode requires the presence of a multicast router or it will be unable to forward multicast streams at all if no multicast routers are present.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • 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. Combined Router and Switch IGMP Operation The following example illustrates the challenges faced with multiple routers, VLAN support and switching.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • 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 host C1 is the last member of the group on that port. If host C1 is the last (or only) member, the group will immediately be pruned from the port.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Service Requirement Attributes are used to change the receiving port's multicast filtering behavior to one of the following: • Forward All Multicast group traffic in the VLAN, or • Forward All Unknown Traffic (Multicast Groups) for which there are no members registered in the device in a VLAN If GMRP is disabled on the RS8000 , GMRP packets received will be forwarded like any other traffic.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Once GMRP-based registration has propagated through the network, multicast traffic from S1 and S2 can reach its destination as follows: • Source S1 transmits multicast traffic to Port D2 which is forwarded via Port D1, which has previously become a member of Multicast Group 1. • Switch B forwards the Group 1 multicast via Port B4 towards Switch E.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Make sure IGMP is properly configured on the device. For more information, refer to Section 5.9.4, “Configuring IGMP”. Section 5.9.3 Viewing a Summary of Multicast Groups To view a summary of all multicast groups, navigate to Multicast Filtering » View Multicast Group Summary. The Multicast Group Summary table appears.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 2 3 4 5 6 7 Figure 148: IGMP Parameters Form 1. Mode Options 2. Query Interval Box 6. Apply Button 7. Reload Button 3. 3. Router Ports Box 4. Router Forwarding Options 5.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.9.5 Configuring GMRP Globally To configure global settings for GMRP, do the following: 1. Navigate to Multicast Filtering » Configure Global GMRP Parameters. The Global GMRP Parameters form appears. 1 2 3 4 5 Figure 149: Global GMRP Parameters Form 1. GMRP Enable Options 2. 2. RSTP Flooding Options 3. Leave Timer Box 4. Apply Button 5.
Chapter 5 RUGGEDCOM ROS Setup and Configuration 2. User Guide Navigate to Multicast Filtering » Configure Port GMRP Parameters. The Port GMRP Parameters table appears. Figure 150: Port GMRP Parameters Table 3. Select an Ethernet port. The Port GMRP Parameters form appears. 1 2 3 4 Figure 151: Port GMRP Parameters Form 1. Port(s) Box 4. 2. GMRP List 3. Apply Button 4.
RUGGEDCOM ROS User Guide Chapter 5 Setup and Configuration Section 5.9.7 Managing Static Multicast Groups The following sections describe how to configure and manage a list of known static multicast groups on other devices: • Section 5.9.7.1, “Viewing a List of Static Multicast Groups” • Section 5.9.7.2, “Adding a Static Multicast Group” • Section 5.9.7.3, “Deleting a Static Multicast Group” Section 5.9.7.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide 1 Figure 153: Static Multicast Groups Table 1. InsertRecord 2. Click InsertRecord. The Static Multicast Groups form appears. 1 2 3 4 7 5 6 Figure 154: Static Multicast Groups Form 1. MAC Address Box 3. 2. VID Box 3. CoS List 4. Ports Box 5. Apply Button 6. Delete Button 7.
RUGGEDCOM ROS Chapter 5 User Guide 4. Setup and Configuration Click Apply. Section 5.9.7.3 Deleting a Static Multicast Group To delete a static multicast group, do the following: 1. Navigate to Multicast Filtering » Configure Static Multicast Groups. The Static Multicast Groups table appears. Figure 155: Static Multicast Groups Table 2. Select the group from the table. The Static Multicast Groups form appears. 1 2 3 4 7 5 6 Figure 156: Static Multicast Groups Form 1. MAC Address Box 3. 2.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide that received the frame can be shutdown permanently or for a specified period of time. An alarm will be raised indicating the detected unauthorized MAC address. Frames to unknown destination addresses are flooded through secure ports. The following sections describe how to configure and manage port security: • Section 5.10.1, “Port Security Concepts” • Section 5.10.2, “Viewing a List of Authorized MAC Addresses” • Section 5.10.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 1 2 3 4 Figure 157: IEEE 802.1x General Topology 1. Supplicant 2. Authenticator Switch 3. LAN 4. Authentication Server IMPORTANT! ROS supports both Protected Extensible Authentication Protocol (PEAP) and EAP-MD5. PEAP is more secure and is recommended if available in the supplicant. IEEE 802.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.10.1.4 Assigning VLANS with Tunnel Attributes ROS supports assigning a VLAN to the authorized port using tunnel attributes, as defined in RFC 3580 [http:// tools.ietf.org/html/rfc3580], when the Port Security mode is set to 802.1x or 802.1x/MAC-Auth. In some cases, it may be desirable to allow a port to be placed into a particular VLAN, based on the authentication result.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description Authorized MAC address learned by the switch. Synopsis: 0 to 65535 VID VLAN Identifier of the VLAN upon which the MAC address operates. If a MAC address is not listed, do the following: • Configure port security. For more information, refer to Section 5.10.3, “Configuring Port Security”. • Configure IEEE 802.1X. For more information, refer to Section 5.10.4, “Configuring IEEE 802.1X”. Section 5.10.
Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Security Synopsis: { Off, Static MAC, 802.1X, 802.1x/MAC-Auth } Default: Off Enables or disables the port's security feature. Two types of port access control are available: • Static MAC address-based. With this method, authorized MAC address(es) should be configured in the Static MAC Address table.
RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 161: 802.1X Parameters Table 2. Select an Ethernet port. The 802.1X Parameters form appears. 1 2 3 4 5 6 7 8 9 10 11 Figure 162: 802.1X Parameters Form 1. Port Box 2. tX Period Box 3. quietPeriod Box 4. reAuthEnabled Options 5. reAuthPeriod Box 7. suppTimeout Box 8. serverTimeout Box 9. maxReq Box 10. Apply Button 11. Reload Button 3. 6.
Chapter 5 RUGGEDCOM ROS Setup and Configuration Parameter User Guide Description Default: 60 s The period of time not to attempt to acquire a Supplicant after the authorization session failed. reAuthEnabled Synopsis: { No, Yes } Default: No Enables or disables periodic re-authentication. reAuthPeriod Synopsis: 60 to 86400 Default: 3600 s The time between periodic re-authentication of the Supplicant.
RUGGEDCOM ROS Chapter 6 User Guide Troubleshooting Troubleshooting This chapter describes troubleshooting steps for common issues that may be encountered when using ROS or designing a network. It describes the following tasks: IMPORTANT! For further assistance, contact a Customer Service representative. • Section 6.1, “General” • Section 6.2, “Ethernet Ports” • Section 6.3, “Spanning Tree” • Section 6.4, “VLANs” Section 6.1 General The following describes common problems.
Chapter 6 RUGGEDCOM ROS Troubleshooting User Guide Section 6.2 Ethernet Ports The following describes common problems related to Ethernet ports. Problem Solution A link seems fine when traffic levels are low, but fails as traffic rates increase OR a link can be pinged but has problems with FTP/ SQL/HTTP/etc. A possible cause of intermittent operation is that of a ‘duplex mismatch’.
RUGGEDCOM ROS Chapter 6 User Guide Problem Troubleshooting Solution Another possible explanation is that some links in the network run in half-duplex mode. RSTP uses a peer-to-peer protocol called Proposal-Agreement to ensure transitioning in the event of a link failure. This protocol requires full-duplex operation. When RSTP detects a non-full duplex port, it cannot rely on Proposal-Agreement protocol and must make the port transition the slow (i.e. STP) way.
Chapter 6 RUGGEDCOM ROS Troubleshooting User Guide Problem Solution VLANs are not needed on the network. Can they be turned off? Yes. Simply leave all ports set to type edge and leave the native VLAN set to 1. This is the default configuration for the switch. Two VLANs were created and a number of ports were made members of them. Now some of the devices in one VLAN need to send messages to devices in the other VLAN.
