Table of Contents

Advertisement

Quick Links

RUGGEDCOM ROS
v4.3
User Guide
For RS900
07/2016
RC1275-EN-03
Preface
Introduction
Using ROS
Device Management
System Administration
Setup and Configuration
Troubleshooting
1
2
3
4
5
6

Advertisement

Table of Contents
loading

Summary of Contents for Siemens RUGGEDCOM ROS v4.3

  • Page 1 Preface Introduction Using ROS RUGGEDCOM ROS v4.3 Device Management System Administration Setup and Configuration User Guide Troubleshooting For RS900 07/2016 RC1275-EN-03...
  • Page 2: Security Information

    Siemens recommends strongly that you regularly check for product updates. For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered.
  • Page 3 RUGGEDCOM ROS User Guide Contacting Siemens Address Telephone E-mail ruggedcom.info.i-ia@siemens.com Siemens Canada Ltd Toll-free: 1 888 264 0006 Industry Sector Tel: +1 905 856 5288 www.siemens.com/ruggedcom 300 Applewood Crescent Fax: +1 905 856 1995 Concord, Ontario Canada, L4K 5C7...
  • Page 4 RUGGEDCOM ROS User Guide...
  • Page 5: Table Of Contents

    RUGGEDCOM ROS   User Guide Table of Contents Table of Contents Preface ......................xiii Conventions ............................xiii Related Documents ..........................xiv System Requirements ......................... xiv Accessing Documentation ........................xiv Training ............................. xv Customer Support ..........................xv Chapter 1 Introduction ..................... 1.1  Features and Benefits ........................
  • Page 6   RUGGEDCOM ROS Table of Contents User Guide 1.8.3.8  TruthValues ......................25 1.9  SSH and SSL Keys and Certificates ....................26 1.9.1  Certificate and Keys Life Cycle ................... 26 1.9.2  Certificate and Key Requirements ..................27 Chapter 2 Using ROS ....................... 2.1  Connecting to ROS ........................29 2.1.1  Connecting Directly ......................
  • Page 7 RUGGEDCOM ROS   User Guide Table of Contents 3.4  Uploading/Downloading Files ....................... 55 3.4.1  Uploading/Downloading Files Using XMODEM ..............56 3.4.2  Uploading/Downloading Files Using a TFTP Client ............... 57 3.4.3  Uploading/Downloading Files Using a TFTP Server .............. 58 3.4.4  Uploading/Downloading Files Using an SFTP Server ............58 3.5  Managing Logs ...........................
  • Page 8   RUGGEDCOM ROS Table of Contents User Guide 3.10.1  Managing RMON History Controls ................... 94 3.10.1.1  Viewing a List of RMON History Controls ............... 94 3.10.1.2  Adding an RMON History Control ................94 3.10.1.3  Deleting an RMON History Control ................ 96 3.10.2  Managing RMON Alarms ....................97 3.10.2.1  Viewing a List of RMON Alarms ................
  • Page 9 RUGGEDCOM ROS   User Guide Table of Contents 4.8.2.2  Configuring User Privileges .................. 131 Chapter 5 Setup and Configuration ................5.1  Managing Virtual LANs ......................133 5.1.1  VLAN Concepts ......................134 5.1.1.1  Tagged vs. Untagged Frames ................134 5.1.1.2  Native VLAN ......................134 5.1.1.3  The Management VLAN ..................135 5.1.1.4  Edge and Trunk Port Types ...................
  • Page 10   RUGGEDCOM ROS Table of Contents User Guide 5.2.3.4  Implementing MSTP on a Bridged Network ............162 5.2.4  Configuring STP Globally ....................163 5.2.5  Configuring STP for Specific Ethernet Ports ..............164 5.2.6  Configuring eRSTP ......................167 5.2.7  Viewing Global Statistics for STP ..................169 5.2.8  Viewing STP Statistics for Ethernet Ports ................
  • Page 11 RUGGEDCOM ROS   User Guide Table of Contents 5.6.2.3  Deleting a Security-to-Group Map ................. 205 5.6.3  Managing SNMP Groups ....................205 5.6.3.1  Viewing a List of SNMP Groups ................206 5.6.3.2  Adding an SNMP Group ..................206 5.6.3.3  Deleting an SNMP Group ..................208 5.7  Managing Network Discovery ....................209 5.7.1  Network Discovery Concepts ...................
  • Page 12   RUGGEDCOM ROS Table of Contents User Guide 5.10.1.1  Rules and Limitations ..................242 5.10.1.2  Link Aggregation and Layer 2 Features ..............242 5.10.1.3  Link Aggregation and Physical Layer Features ............243 5.10.2  Managing Port Trunks ....................243 5.10.2.1  Viewing a List of Port Trunks ................243 5.10.2.2  Adding a Port Trunk ...................
  • Page 13: Preface

    RUGGEDCOM ROS   User Guide Preface Preface This guide describes v4.3 of ROS (Rugged Operating System) running on the RUGGEDCOM RS900. 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 use by network and system planners, system programmers, and line technicians.
  • Page 14: Related Documents

    • The ability to configure an IP address and netmask on the computer’s Ethernet interface Accessing Documentation The latest user documentation for RUGGEDCOM ROS v4.3 is available online at www.siemens.com/ruggedcom. To request or inquire about a user document, contact Siemens Customer Support.
  • Page 15: Training

    Siemens Sales representative. Customer Support Customer support is available 24 hours, 7 days a week for all Siemens customers. For technical support or general information, contact Siemens Customer Support through any of the following methods: Online Visit http://www.siemens.com/automation/support-request...
  • Page 16 RUGGEDCOM ROS   User Guide Preface Customer Support...
  • Page 17: Introduction

    Chapter 1 User Guide Introduction Introduction Welcome to the RUGGEDCOM ROS v4.3 Software User Guide for the RS900. This Guide describes the wide array of carrier grade features made available by ROS (Rugged Operating System). CONTENTS • Section 1.1, “Features and Benefits”...
  • Page 18: Troubleshooting

    Network Management System (NMS). A feature of SNMP is the ability to generate traps upon system events. RUGGEDCOM NMS, the Siemens management solution, can record traps from multiple devices providing a powerful network troubleshooting tool. It also provides a graphical visualization of the network and is fully integrated with all Siemens products.
  • Page 19: Security Recommendations And Considerations

    RUGGEDCOM ROS Chapter 1 User Guide Introduction • Port Statistics and RMON (Remote Monitoring) RUGGEDCOM ROS provides continuously updating statistics per port that provide both ingress and egress packet and byte counters, as well as detailed error figures. Also provided is full support for RMON statistics. RMON allows for very sophisticated data collection, analysis and detection of traffic patterns.
  • Page 20 Consider using RSA key sizes of at least 2048 bits in length and certificates signed with SHA256 for increased cryptographic strength. Before returning the device to Siemens for repair, make sure encryption is disabled (to create a cleartext version of the configuration file) and replace the current certificates and keys with temporary throwaway certificates and keys that can be destroyed upon the device's return.
  • Page 21: Credential Files

    Siemens application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows, available from www.siemens.com/ruggedcom. The sequence of events related to Key Management during an upgrade to RUGGEDCOM ROS v4.3 or later is as follows: NOTE The auto-generation of SSH keys is not available for Non-Controlled (NC) versions of RUGGEDCOM ROS.
  • Page 22: Ssl Certificates

    Chapter 1 RUGGEDCOM ROS Introduction User Guide • Immediately after boot, RUGGEDCOM ROS will start to generate a unique SSL certificate and SSH key pair, and save each one to its corresponding flash file. This process may take several minutes to complete. As each one is created, the corresponding service is immediately restarted with the new keys.
  • Page 23 > ssl.crt For information on creating SSL certificates for use with RUGGEDCOM ROS in a Microsoft Windows environment, refer to the following Siemens application note: Creating/Uploading SSH Keys and SSL Certificates to ROS Using Windows. The following is an example of a self-signed SSL certificate generated by RUGGEDCOM ROS:...
  • Page 24: Ssh Key Pairs

    Chapter 1 RUGGEDCOM ROS Introduction User Guide DirName:/C=CA/ST=Ontario/L=Concord/O=RuggedCom.com/OU=RC/CN=ROS serial:CA:01:2D:C0:BF:F9:FD:F2 X509v3 Basic Constraints: CA:TRUE Signature Algorithm: sha1WithRSAEncryption 64:cf:68:6e:9f:19:63:0e:70:49:a6:b2:fd:09:15:6f:96:1d: 4a:7a:52:c3:46:51:06:83:7f:02:8e:42:b2:dd:21:d2:e9:07: 5c:c4:4c:ca:c5:a9:10:49:ba:d4:28:fd:fc:9d:a9:0b:3f:a7: 84:81:37:ca:57:aa:0c:18:3f:c1:b2:45:2a:ed:ad:dd:7f:ad: 00:04:76:1c:f8:d9:c9:5c:67:9e:dd:0e:4f:e5:e3:21:8b:0b: 37:39:8b:01:aa:ca:30:0c:f1:1e:55:7c:9c:1b:43:ae:4f:cd: e4:69:78:25:5a:a5:f8:98:49:33:39:e3:15:79:44:37:52:da: 28:dd Section 1.2.2.2 SSH Key Pairs Controlled versions of RUGGEDCOM ROS support SSH public/private key pairs that conform to the following specifications: •...
  • Page 25: Supported Networking Standards

    RUGGEDCOM ROS Chapter 1 User Guide Introduction 47:90:5d:6d:1b:27:d5:04:c5:de:57:7e:a7:a3:03: e8:fb:0a:d5:32:89:40:12 00:f4:81:c1:9b:5f:1f:eb:ac:43:2e:db:dd:77:51: 6e:1c:62:8d:4e:95:c6:e7:b9:4c:fb:39:9c:9d:da: 60:4b:0f:1f:c6:61:b0:fc:5f:94:e7:45:c3:2b:68: 9d:11:ba:e1:8a:f9:c8:6a:40:95:b9:93:7c:d0:99: 96:bf:05:2e:aa:f5:4e:f0:63:02:00:c7:c2:52:c7: 1a:70:7c:f7:e5:fe:dd:3d:57:02:86:ae:d4:89:20: ca:4b:46:80:ea:de:a1:30:11:5c:91:e2:40:d4:a3: 82:c5:40:3b:25:8e:d8:b2:85:cc:f5:9f:a9:1d:ea: 0a:ac:77:95:ee:d6:f7:61:e3 00:d5:db:48:18:bd:ec:69:99:eb:ff:5f:e1:40:af: 20:80:6d:5c:b1:23 01:f9:a1:91:c0:82:12:74:49:8a:d5:13:88:21:3e: 32:ea:f1:74:55:2b:de:61:6c:fd:dd:f5:e1:c5:03: 68:b4:ad:40:48:58:62:6c:79:75:b1:5d:42:e6:a9: 97:86:37:d8:1e:e5:65:09:28:86:2e:6a:d5:3d:62: 50:06:b8:d3:f9:d4:9c:9c:75:84:5b:db:96:46:13: f0:32:f0:c5:cb:83:01:a8:ae:d1:5a:ac:68:fb:49: f9:b6:8b:d9:d6:0d:a7:de:ad:16:2b:23:ff:8e:f9: 3c:41:16:04:66:cf:e8:64:9e:e6:42:9a:d5:97:60: c2:e8:9e:f4:bc:8f:6f:e0 Section 1.3 Supported Networking Standards The following networking standards are supported by RUGGEDCOM ROS: Standard 10 Mbps Ports 100 Mbps Ports...
  • Page 26: Available Services By Port

    Chapter 1 RUGGEDCOM ROS Introduction User Guide Figure 1:  RS900 Port Numbering (Typical) Use these numbers to configure applicable features on select ports. Section 1.5 Available Services by Port The following table lists the services available under RUGGEDCOM ROS. This table includes the following information: •...
  • Page 27 RUGGEDCOM ROS Chapter 1 User Guide Introduction Service Enabled/ Services Port Number Access Authorized Note Disabled management interfaces. HTTP TCP/80 Enabled — (configurable), redirects to 443 HTTPS TCP/443 Enabled (configurable) TCP/512 Disabled Only available (configurable) through two management interfaces. TFTP UDP/69 Disabled Only available...
  • Page 28: Snmp Management Interface Base (Mib) Support

    Chapter 1 RUGGEDCOM ROS Introduction User Guide Service Enabled/ Services Port Number Access Authorized Note Disabled come to CPU, dropped if service not configured RCDP — Disabled (configurable) Section 1.6 SNMP Management Interface Base (MIB) Support RUGGEDCOM ROS supports a variety of standard MIBs, proprietary RUGGEDCOM MIBs and Agent Capabilities MIBs, all for SNMP (Simple Network Management Protocol).
  • Page 29: Supported Proprietary Ruggedcom Mibs

    RUGGEDCOM ROS Chapter 1 User Guide Introduction Standard MIB Name Title RFC 4318 RSTP-MIB Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol RFC 3411 SNMP-FRAMEWORK-MIB An Architecture for Describing Simple Network Management Protocol (SNMP) Management Framework RFC 3414 SNMP-USER-BASED-SM-MIB User-based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3)
  • Page 30: Snmp Traps

    Chapter 1 RUGGEDCOM ROS Introduction User Guide File Name MIB Name Supported MIB RC-SNMPv2-MIB-AC.mib RC-SNMPv2-MIB-AC SNMPv2-MIB RC-UDP-MIB-AC.mib RC-UDP-MIB-AC UDP-MIB RC-TCP-MIB-AC.mib RC-TCP-MIB-AC TCP-MIB RC-SNMP-USER-BASED-SM-MIB-AC.mib RC-SNMP-USER-BASED-SM-MIB-AC SNMP-USER-BASED-SM-MIB-AC RC-SNMP-VIEW-BASED-ACM-MIB-AC.mib RC-SNMP-VIEW-BASED-ACM-MIB-AC SNMP-VIEW-BASED-ACM-MIB-AC RC-IF-MIB-AC.mib RC-IF-MIB-AC IF-MIB RC-BRIDGE-MIB-AC.mib RC-BRIDGE-MIB-AC BRIDGE-MIB RC-RMON-MIB-AC.mib RC-RMON-MIB-AC RMON-MIB RC-Q-BRIDGE-MIB-AC.mib RC-Q-BRIDGE-MIB-AC Q-BRIDGE-MIB RC-IP-MIB-AC.mib RC-IP-MIB-AC IP-MIB...
  • Page 31 RUGGEDCOM ROS Chapter 1 User Guide Introduction Trap fallingAlarm lldpRemoteTablesChange LLDP-MIB The device also generates the following proprietary traps: Table: Proprietary Traps Trap genericTrap RUGGEDCOM-TRAPS-MIB powerSupplyTrap swUpgradeTrap cfgChangeTrap 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.
  • Page 32: Modbus Management Support

    Chapter 1 RUGGEDCOM ROS Introduction User Guide Section 1.8 ModBus Management Support Modbus management support in RUGGEDCOM devices provides a simple interface for retrieving basic status information. ModBus support simplifies the job of SCADA (Supervisory Control and Data Acquisition) system integrators by providing familiar protocols for retrieving RUGGEDCOM device information. ModBus provides mostly read-only status information, but there are some writable registers for operator commands.
  • Page 33: Modbus Memory Map

    RUGGEDCOM ROS Chapter 1 User Guide Introduction Write Multiple Registers — 0x10 Example PDU Request Function Code 1 Byte 0x10 Starting Address 2 Bytes 0x0000 to 0xFFFF Number of Input Registers 2 Bytes Bytes 0x0001 to 0x0079 Byte Count 1 Byte 2 x N Registers Value x 2 Bytes...
  • Page 34: Ethernet Port Status

    Chapter 1 RUGGEDCOM ROS Introduction User Guide Address #Registers Description (Reference Table in UI) Format 0083 Clear Ethernet Statistics PortCmd 0085 Reset Serial Ports PortCmd 0087 Clear Serial Port Statistics PortCmd Alarms The following data is mapped to the alarms table: Address #Registers Description (Reference Table in UI)
  • Page 35 RUGGEDCOM ROS Chapter 1 User Guide Introduction Address #Registers Description (Reference Table in UI) Format 0412 Port s3/p2 Statistics - Ethernet In Packets Uinst32 0414 Port s3/p3 Statistics - Ethernet In Packets Uinst32 0416 Port s3/p4 Statistics - Ethernet In Packets Uinst32 0418 Port s4/p1 Statistics - Ethernet In Packets...
  • Page 36 Chapter 1 RUGGEDCOM ROS Introduction User Guide Address #Registers Description (Reference Table in UI) Format 045E Port s4/p4 Statistics - Ethernet Out Packets Uinst32 0460 Port s5/p1 Statistics - Ethernet Out Packets Uinst32 0462 Port s5/p2 Statistics - Ethernet Out Packets Uinst32 0464 Port s5/p3 Statistics - Ethernet Out Packets...
  • Page 37 RUGGEDCOM ROS Chapter 1 User Guide Introduction Address #Registers Description (Reference Table in UI) Format 04AA Port s6/p2 Statistics - Ethernet In Packets Uinst32 04AC Port s6/p3 Statistics - Ethernet In Packets Uinst32 04AE Port s6/p4 Statistics - Ethernet In Packets Uinst32 04B0 Port s7/p1 Statistics - Ethernet In Packets...
  • Page 38: Modbus Memory Formats

    Port 3 Statistics – Serial Out Packets Uint32 06C6 Port 4 Statistics – Serial Out Packets Uint32 Section 1.8.3 ModBus Memory Formats The following ModBus memory formats are supported by Siemens. CONTENTS • Section 1.8.3.1, “Text” • Section 1.8.3.2, “Cmd” • Section 1.8.3.3, “Uint16”...
  • Page 39: Text

    RUGGEDCOM ROS Chapter 1 User Guide Introduction • Section 1.8.3.8, “TruthValues” Section 1.8.3.1 Text The Text format provides a simple ASCII representation of the information related to the product. The most significant register byte of an ASCII characters comes first. For example, consider a Read Multiple Registers request to read Product Identification from location 0x0000. 0x04 0x00 0x00...
  • Page 40: Uint32

    Chapter 1 RUGGEDCOM ROS Introduction User Guide Section 1.8.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. The second register holds the least significant 16 bits of a 32 bit value. Section 1.8.3.5 PortCmd The PortCmd format describes a bit layout per port, where 1 indicates the requested action is true, and 0 indicates...
  • Page 41: Alarm

    RUGGEDCOM ROS Chapter 1 User Guide Introduction Section 1.8.3.6 Alarm The Alarm format is another form of text description. Alarm text corresponds to the alarm description from the table holding all of the alarms. Similar to the Text format, this format returns an ASCII representation of alarms. NOTE Alarms are stacked in the device in the sequence of their occurence (i.e.
  • Page 42: Ssh And Ssl Keys And Certificates

    Chapter 1 RUGGEDCOM ROS Introduction User Guide • 2 indicates the corresponding status for the device to be false Reading the FailSafe Relay Status From a Device Using TruthValue To understand how to use the TruthValue format to read the FailSafe Relay status from a device, consider a ModBus request to read multiple registers from location 0x0044.
  • Page 43: Certificate And Key Requirements

    RUGGEDCOM ROS Chapter 1 User Guide Introduction NOTE SSH is not supported in Non-Controlled (NC) versions of RUGGEDCOM ROS. NOTE Network exposure to a ROS unit operating with the default keys, although always only temporary by design, should be avoided. The best way to reduce or eliminate this exposure is to provision user- created certificate and keys as quickly as possible, and preferably before the unit is placed in network service.
  • Page 44 Chapter 1 RUGGEDCOM ROS Introduction User Guide MjIxMTA1M1owgZwxCzAJBgNVBAYTAlVTMRAwDgYDVQQIEwdPbnRhcmlvMRAwDgYD VQQHEwdDb25jb3JkMRIwEAYDVQQKEwlSdWdnZWRDb20xGTAXBgNVBAsTEEN1c3Rv bWVyIFN1cHBvcnQxFDASBgNVBAMTCzE5Mi4xNjguMS4yMSQwIgYJKoZIhvcNAQkB FhVTdXBwb3J0QHJ1Z2dlZGNvbS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ AoGBALfE4eh2aY+CE3W5a4Wz1Z1RGRP02COHt153wFFrU8/fFQXNhKlQirlAHbNT RSwcTR8ZFapivwYDivn0ogOGFXknYP90gv2oIaSVY08FqZkJW77g3kzkv/8Zrw3m W/cBsZJ8SyKLIDfy401HkHpDOle5NsQFSrziGUPjAOIvvx4rAgMBAAGjLDAqMAkG A1UdEwQCMAAwHQYDVR0OBBYEFER0utgQOifnrflnDtsqNcnvRB0XMA0GCSqGSIb3 DQEBBQUAA4GBAHtBsNZuh8tB3kdqR7Pn+XidCsD70YnI7w0tiy9yiRRhARmVXH8h 5Q1rOeHceri3JFFIOxIxQt4KgCUYJLu+c9Esk/nXQQar3zR7IQCt0qOABPkviiY8 c3ibVbhJjLpR2vNW4xRAJ+HkNNtBOg1xUlp4vOmJ2syYZR+7XAy/OP/S -----END CERTIFICATE----- -----BEGIN RSA PRIVATE KEY----- MIICXAIBAAKBgQC3xOHodmmPghN1uWuFs9WdURkT9Ngjh7ded8BRa1PP3xUFzYSp UIq5QB2zU0UsHE0fGRWqYr8GA4r59KIDhhV5J2D/dIL9qCGklWNPBamZCVu+4N5M 5L//Ga8N5lv3AbGSfEsiiyA38uNNR5B6QzpXuTbEBUq84hlD4wDiL78eKwIDAQAB AoGBAI2CXHuHg23wuk9zAusoOhw0MN1/M1jYz0k9aajIvvdZT3Tyd29yCADy8GwA eUmoWXLS/C4CcBqPa9til8ei3rDn/w8dveVHsi9FXjtVSYqN+ilKw+moMAjZy4kN /kpdpHMohwv/909VWR1AZbr+YTxaG/++tKl5bqXnZl4wHF8xAkEA5vwut8USRg2/ TndOt1e8ILEQNHvHQdQr2et/xNH4ZEo7mqot6skkCD1xmxA6XG64hR3BfxFSZcew Wr4SOFGCtQJBAMurr5FYPJRFGzPM3HwcpAaaMIUtPwNyTtTjywlYcUI7iZVVfbdx 4B7qOadPybTg7wqUrGVkPSzzQelz9YCSSV8CQFqpIsEYhbqfTLZEl83YjsuaE801 xBivaWLIT0b2TvM2O7zSDOG5fv4I990v+mgrQRtmeXshVmEChtKnBcm7HH0CQE6B 2WUfLArDMJ8hAoRczeU1nipXrIh5kWWCgQsTKmUrafdEQvdpT8ja5GpX2Rp98eaU NHfI0cP36JpCdome2eUCQDZN9OrTgPfeDIXzyOiUUwFlzS1idkUGL9nH86iuPnd7 WVF3rV9Dse30sVEk63Yky8uKUy7yPUNWldG4U5vRKmY= -----END RSA PRIVATE KEY----- For SSH, RUGGEDCOM ROS requires a DSA or RSA host key pair in PEM format.
  • Page 45: Using Ros

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Using ROS This chapter describes how to use the RUGGEDCOM ROS interface. CONTENTS • Section 2.1, “Connecting to ROS” • Section 2.2, “Logging In” • Section 2.3, “Logging Out” • Section 2.4, “Using the Web Interface” •...
  • Page 46: Connecting Via The Network

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide Configure the workstation as follows: • Speed (baud): 57600 • Data Bits: 8 • Parity: None • Flow Control: Off • Terminal ID: VT100 • Stop Bit: 1 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”...
  • Page 47: Logging In

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Using a Terminal or Terminal Emulation Software A terminal or computer running terminal emulation software provides access to the console interface for RUGGEDCOM ROS through a Telnet, RSH (Remote Shell) or SSH (Secure Shell) service. NOTE IP services can be restricted to control access to the device.
  • Page 48: Logging Out

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide NOTE The following default usernames and passwords are set on the device for each user type: Guest Operator Admin Username: guest Username: operator Username: admin Password: guest Password: operator Password: admin CAUTION! To prevent unauthorized access to the device, make sure to change the default guest, operator, and admin passwords before commissioning the device.
  • Page 49: Using The Web Interface

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Section 2.4 Using the Web Interface The Web interface is a Web-based Graphical User Interface (GUI) for displaying important information and controls in a Web browser. The interface is divided into three frames: the banner, the menu and the main frame. Figure 5: Web Interface Layout (Example) 1. Top Frame   ...
  • Page 50: Using The Console Interface

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide Figure 6: Elements of a Typical Screen (Example) 1. Title    2. Parameters and/or Data    3. Access Level or Alarm Notification    4. Controls NOTE If desired, the web interface can be disabled. For more information, refer to Section 4.5, “Enabling/ Disabling the Web Interface”...
  • Page 51 RUGGEDCOM ROS Chapter 2 User Guide Using ROS Figure 7: Console Interface (Example) 1. System Identification    2. Menus    3. Command Bar    4. Menu Name    5. Alarms Indicator NOTE The system identifier is user configurable. For more information about setting the system name, refer Section 4.1, “Configuring the System Information” Navigating the Interface Use the following controls to navigate between screens in the Console interface: Enter...
  • Page 52: Using The Command Line Interface

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide Commands The command bar lists the various commands that can be issued in the Console interface. Some commands are specific to select screens. The standard commands include the following: Ctrl + A Commits configuration changes made on the current screen.
  • Page 53 RUGGEDCOM ROS Chapter 2 User Guide Using ROS Command Description • port is a comma separated list of port numbers (e.g. 1,3-5,7) clearlogs Clears the system and crash logs. clrcblstats [ all | Clears cable diagnostics statistics for one or more ports. port Optional and/or required parameters include: •...
  • Page 54 Chapter 2 RUGGEDCOM ROS Using ROS User Guide Command Description • address is the target IP address. • count is the number of echo requests to send. The default is 4. • timeout is the time in milliseconds to wait for each reply. The range is 2 to 5000 seconds.
  • Page 55: Tracing Events

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Command Description sshpubkey List, remove and update key entries in sshpub.keys file. sslkeygen Generates a new SSL certificate in ssl.crt. keytype Optional and/or required parameters include: • keytype is the type of key, either rsa or ecc •...
  • Page 56: Executing Commands Remotely Via Rsh

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide trace protocol NOTE If required, expand the trace scope by stringing protocols and their associated options together using a vertical bar (|). Select the type of trace to run by typing: trace protocol option Where:...
  • Page 57: Finding The Correct Table

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS • Restoring the contents of a specific table, but not the whole configuration, to their factory defaults. • Search tables in the database for specific configurations. • Make changes to tables predicated upon existing configurations. When combined with RSH, SQL commands provide a means to query and configure large numbers of devices from a central location.
  • Page 58 Chapter 2 RUGGEDCOM ROS Using ROS User Guide Retrieving Information from a Table Use the following command to display a summary of the parameters within a table, as well as their values: sql select from table Where: • table is the name of the table Example: >sql select from ipAddrtable IP Address...
  • Page 59: Changing Values In A Table

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Port Name ifName Media State AutoN Speed Dupx FlowCtrl LFI Alarm Port 1 1000T Enabled Auto Auto Off On Port 2 1000T Enabled Auto Auto Off On Port 3 1000T Enabled Auto Auto Off On Port 4...
  • Page 60: Resetting A Table

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide Section 2.6.4.4 Resetting a Table Use the following command to reset a table back to its factory defaults: sql default into table Where: • table is the name of the table Section 2.6.4.5 Using RSH and SQL The combination of remote shell scripting and SQL commands offers a means to interrogate and maintain a large number of devices.
  • Page 61: Managing The Flash File System

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Use the All option to select all ports in the device, or, if available, use the None option to select none of the ports. Section 2.8 Managing the Flash File System The following section describes how to manage the flash file system. CONTENTS •...
  • Page 62: Defragmenting The Flash File System

    Mechanical hazard – risk of damage to the device. Excessive use of BIST functions may cause increase wear on the device, which may void the warranty. Avoid using BIST functions unless instructed by a Siemens Customer Support representative. To access BIST mode, do the following:...
  • Page 63: Managing Ssh Public Keys

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS IMPORTANT! Do not connect the device to the network when it is in BIST mode. The device will generate excess multicast traffic in this mode. Disconnect the device from the network. Connect to RUGGEDCOM ROS through the RS-232 console connection and a terminal application. For more information, refer to Section 2.1.1, “Connecting Directly”...
  • Page 64 Chapter 2 RUGGEDCOM ROS Using ROS User Guide The key must be in RFC4716 or PEM format, with any of the following header and footer lines: -----BEGIN PUBLIC KEY----- -----END PUBLIC KEY----- -----BEGIN SSH2 PUBLIC KEY----- -----END SSH2 PUBLIC KEY----- -----BEGIN RSA PUBLIC KEY----- -----END RSA PUBLIC KEY----- The following is an example of a valid entry in the sshpub.keys file in PEM format:...
  • Page 65: Viewing A List Of Public Keys

    RUGGEDCOM ROS Chapter 2 User Guide Using ROS Check the system log to make sure the files were properly transferred. For more information about viewing the system log, refer to Section 3.5.1, “Viewing Local Logs” Section 2.10.2 Viewing a List of Public Keys Admin users can view a list of existing public keys on the device.
  • Page 66: Deleting A Public Key

    Chapter 2 RUGGEDCOM ROS Using ROS User Guide Section 2.10.4 Deleting a Public Key Admin users can delete one or more public keys. To delete a public key, do the following: 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”...
  • Page 67: Device Management

    Section 3.1 Viewing Product Information During troubleshooting or when ordering new devices, Siemens personnel may request specific information about the device, such as the model, order code or serial number. To view information about the device, navigate to Diagnostics » View Product Information . The Product Information form appears.
  • Page 68 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 8: Product Information Form (Example) 1. MAC Address Box    2. Order Code Box    3. Classification Box    4. Serial Number Box    5. Boot Version Box    6. Main Version Box    7. Required Boot Box    8. Hardware ID Box    9. Reload Button This screen displays the following information: Parameter Description MAC Address...
  • Page 69: Viewing Cpu Diagnostics

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Rev C1), RSG2100, RS900G, RSG2200, RS969, RS900 (v2, 40-00-0066), RS900 (v2, 40-00-0067), , RS416 (40-00-0078), RMC30 (v2), RS930 (40-00-0089), RS969 (v2, 40-00-0090), RS910 (40-00-0091-001 Rev A), RS920L (40-00-0102-001 Rev A), RS940G (40-00-0097-000 Rev A), RSi80X series CPU board, RSG2300, RS416v2, ...
  • Page 70: Restoring Factory Defaults

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description The total size of RAM in the system. RAM Free Synopsis:   0 to 4294967295 The total size of RAM still available. RAM Low Watermark Synopsis:   0 to 4294967295 The size of RAM that have never been used during the system runtime.
  • Page 71: Uploading/Downloading Files

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 10: Load Factory Defaults Form 1. Defaults Choice List    2. Apply Button    3. Reload Configure the following parameter(s) as required: NOTE If the VLAN ID for the Management IP interface is not 1, setting Defaults Choice to Selected will automatically set it to 1.
  • Page 72: Uploading/Downloading Files Using Xmodem

    Chapter 3 RUGGEDCOM ROS Device Management User Guide NOTE The contents of the internal file system are fixed. New files and directories cannot be created, and existing files cannot be deleted. Only the files that can be uploaded to the device can be overwritten. Files that may need to be uploaded or downloaded include: •...
  • Page 73: Uploading/Downloading Files Using A Tftp Client

    RUGGEDCOM ROS Chapter 3 User Guide Device Management NOTE If available in the terminal emulation or Telnet software, select the XModem 1K protocol for transmission over the standard XModem option. When the device responds with Press Ctrl-X to cancel , launch the XMODEM transfer from the host computer. The device will indicate when the transfer is complete.
  • Page 74: Uploading/Downloading Files Using A Tftp Server

    Chapter 3 RUGGEDCOM ROS Device Management User Guide TFTP CMD: main.bin loading succesful. Section 3.4.3 Uploading/Downloading Files Using a TFTP Server To updload or download a file using a TFTP server, do the following: IMPORTANT! TFTP does not define an authentication scheme. Any use of the TFTP client or server is considered highly insecure.
  • Page 75: Managing Logs

    RUGGEDCOM ROS Chapter 3 User Guide Device Management user@host$ sftp admin@ros_ip Connecting to ros_ip... admin@ros_ip's password: sftp> put ROS-CF52_Main_v3-7-0.bin main.bin Uploading ROS-CF52_Main_v3-7-0.bin to /main.bin ROS-CF52_Main_v3-7-0.bin 100% 2139KB 48.6KB/s 00:44 sftp> Section 3.5 Managing Logs The crash (crashlog.txt) and system (syslog.txt) log files contain historical information about events that have occurred during the operation of the device.
  • Page 76: Clearing Local Logs

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.5.2 Clearing Local Logs To clear both the local crash and system logs, log in to the CLI shell and type: clearlogs To clear only the local system log, log in to the Web interface and do the following: Navigate to Diagnostics »...
  • Page 77: Managing Remote Logging

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Local Syslog Level Synopsis:   { EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE, INFORMATIONAL, DEBUGGING } Default:   INFORMATIONAL The severity of the message that has been generated. Note that the severity level selected is considered the minimum severity level for the system.
  • Page 78: Viewing A List Of Remote Syslog Servers

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 14: Remote Syslog Client Form 1. UDP Port    2. Apply Button    3. Reload Button Configure the following parameter(s) as required: Parameter Description UDP Port Synopsis:   1025 to 65535 or { 514 } Default:   514 The local UDP port through which the client sends information to the server(s).
  • Page 79: Adding A Remote Syslog Server

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Section 3.5.4.3 Adding a Remote Syslog Server RUGGEDCOM 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. Only messages of a severity level equal to or greater than the specified severity level are written to the log.
  • Page 80: Deleting A Remote Syslog Server

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description Default:   514 The UDP port number on which the remote server listens. Facility Synopsis:   { USER, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7 } Default:   LOCAL7 Syslog Facility is one information field associated with a syslog message.
  • Page 81: Managing Ethernet Ports

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 19: Remote Syslog Server Form 1. IP Address Box    2. UDP Port Box    3. Facility Box    4. Severity Box    5. Apply Button    6. Delete Button    7. Reload Button Click Delete. Section 3.6 Managing Ethernet Ports The following section describes how to set up and manage Ethernet ports. NOTE For information about configuring remote monitoring for Ethernet ports, refer to Section 3.10,...
  • Page 82: Controller Protection Through Link Fault Indication (Lfi)

    IEEE 802.3 standard, which means that some links partners may not support it. 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.
  • Page 83: Viewing The Status Of Ethernet Ports

    RUGGEDCOM ROS Chapter 3 User Guide Device Management IMPORTANT! If both link partners have the LFI feature, it must not be enabled on both sides of the link. If it is enabled on both sides, the link will never be established, as each link partner will be waiting for the other to transmit a link signal.
  • Page 84: Viewing Statistics For All Ethernet Ports

    Chapter 3 RUGGEDCOM ROS Device Management User Guide 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. Figure 22: Ethernet Statistics Table This table displays the following information: Parameter Description Port...
  • Page 85: Section 3.6.4, "Viewing Statistics For Specific Ethernet Ports

    RUGGEDCOM ROS Chapter 3 User Guide Device Management 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. InOctets Synopsis:  ...
  • Page 86 Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description • 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. OversizePkts Synopsis:  ...
  • Page 87: Clearing Statistics For Specific Ethernet Ports

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description as dropped and local received packets. This does not include rejected received packets. Pkt1024to1536Octets Synopsis:   0 to 4294967295 The number of received and transmitted packets with size of 1024 to 1536 octets.
  • Page 88: Configuring An Ethernet Port

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Section 3.6.6 Configuring an Ethernet Port To configure an Ethernet port, do the following: Navigate to Ethernet Ports » Configure Port Parameters . The Port Parameters table appears. Figure 25: Port Parameters Table Select an Ethernet port. The Port Parameters form appears. Figure 26: Port Parameters Form 1. Port Box   ...
  • Page 89 RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Default:   1 The port number as seen on the front plate silkscreen of the switch. Name Synopsis:   Any 15 characters Default:   Port x A descriptive name that may be used to identify the device connected on that port.
  • Page 90: Configuring Port Rate Limiting

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description When the port is half-duplex it is accomplished using 'backpressure' where the switch simulates collisions causing the sending device to retry transmissions according to the Ethernet backoff algorithm. When the port is full-duplex it is accomplished using PAUSE frames which causes the sending device to stop transmitting for a certain period of time.
  • Page 91 RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 27: Port Rate Limiting Table Select an Ethernet port. The Port Rate Limiting form appears. Figure 28: Port Rate Limiting Form 1. Port Box    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...
  • Page 92: Configuring Port Mirroring

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description • Bcast&Mcast - broadcast and multicast frames • Bcast&FloodUcast - broadcast and flooded unicast frames • Bcast&Mcast&FloodUcast - broadcast, multicast and flooded unicast frames • FloodUcast - only flooded unicast frames •...
  • Page 93: Configuring Link Detection

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 29: Port Mirroring Form 1. Port Mirroring Box    2. Source Port Box    3. Target Port Box    4. Apply Button    5. Reload Button Configure the following parameter(s) as required: Parameter Description Port Mirroring Synopsis:   { Disabled, Enabled } Default:  ...
  • Page 94 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 30: Link Detection Form 1. Fast Link Detection Box    2. Link Detection Time Box    3. Apply Button    4. Reload Button Configure the following parameter(s) as required: NOTE When Fast Link Detection is enabled, the system prevents link state change processing from consuming all available CPU resources.
  • Page 95: Detecting Cable Faults

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description could continue affect the system in terms of response time. This setting should be used with caution. • OFF - Turning this parameter OFF will disable FAST LINK DETECTION completely. The switch will need a longer time to detect a link failure.
  • Page 96 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:  ...
  • Page 97: Performing Cable Diagnostics

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description The number of times OPEN is detected on the cable pairs of the selected port. Short Synopsis:   0 to 65535 The number of times SHORT is detected on the cable pairs of the selected port.
  • Page 98 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 32: Cable Diagnostics Parameters Table Select an Ethernet port. The Cable Diagnostics Parameters form appears. Figure 33: Cable Diagnostics Parameters Form 1. Port Box    2. State Options    3. Runs Box    4. Calib. Box    5. Good Box    6. Open Box    7. Short Box    8. Imped Box    9. Pass / Fail /Total Box   ...
  • Page 99: Clearing Cable Diagnostics

    RUGGEDCOM ROS Chapter 3 User Guide 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”...
  • Page 100: Resetting Ethernet Ports

    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: Navigate to Ethernet Ports »...
  • Page 101: Viewing A List Of Ip Interfaces

    RUGGEDCOM ROS Chapter 3 User Guide Device Management • Section 3.7.3, “Deleting an IP Interface” 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: ...
  • Page 102 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 38:  IP Interfaces Form 1. Type Options    2. ID Box    3. Mgmt Options    4. IP Address Type Box    5. IP Address Box    6. Subnet Box    7. Apply Button    8. Delete Button    9. Reload 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.
  • Page 103: Deleting An Ip Interface

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Specifies the IP address of this device. An IP address is a 32-bit number that is notated by using four numbers from 0 through 255, separated by periods. Only a unicast IP address is allowed, which ranges from 1.0.0.0 to 233.255.255.255.
  • Page 104: Managing Ip Gateways

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 40:  IP Interfaces Form 1. IP Address Type Box    2. IP Address Box    3. Subnet Box    4. Apply Button    5. Delete Button    6. Reload Button Click Delete. Section 3.8 Managing IP Gateways RUGGEDCOM 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.
  • Page 105: Adding An Ip 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: Navigate to Administration »...
  • Page 106: Deleting An Ip Gateway

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 43: IP Gateways 1. Destination Box    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.
  • Page 107: Configuring Ip Services

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Select the IP gateway from the table. The IP Gateways form appears. Figure 45: IP Gateways Form 1. Destination Box    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: Navigate to Administration »...
  • Page 108 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 46: IP Services Form 1. Inactivity Timeout Box    2. Telnet Sessions Allowed Box    3. Web Server Users Allowed Box    4. TFTP Server Box    5. Modbus Address Box    6. SSH Sessions Allowed Box    7. RSH Server Options    8. IP Forward Options    9. Max Failed Attempts Box    10. Failed Attempts Window Box   ...
  • Page 109: Managing Remote Monitoring

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description Determines the Modbus address to be used for Management through Modbus. SSH Sessions Allowed (Controlled Version Only) Synopsis:   1 to 4 Default:   4 Limits the number of SSH sessions. RSH Server Synopsis:  ...
  • Page 110: Managing Rmon History Controls

    Chapter 3 RUGGEDCOM ROS Device Management User Guide • Section 3.10.3, “Managing RMON Events” 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. CONTENTS • Section 3.10.1.1, “Viewing a List of RMON History Controls”...
  • Page 111 RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 48: RMON History Controls Table 1. InsertRecord Click InsertRecord. The RMON History Controls form appears. Figure 49: RMON History Controls Form 1. Index Box    2. Port Box    3. Requested Buckets Box    4. Granted Buckets Box    5. Interval Box    6. Owner Box    7. Apply Button    8. Delete Button   ...
  • Page 112: Deleting An Rmon History Control

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Parameter Description Granted Buckets Synopsis:   0 to 65535 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.
  • Page 113: Managing Rmon Alarms

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Figure 51: RMON History Controls Form 1. Index Box    2. Port Box    3. Requested Buckets Box    4. Granted Buckets Box    5. Interval Box    6. Owner Box    7. Apply Button    8. Delete Button    9. Reload Button Click Delete. Section 3.10.2 Managing RMON Alarms When Remote Monitoring (RMON) alarms are configured, RUGGEDCOM ROS examines the state of a specific statistical variable.
  • Page 114: Viewing A List Of Rmon Alarms

    Chapter 3 RUGGEDCOM ROS Device Management User Guide 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.
  • Page 115: Adding An Rmon Alarm

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Section 3.10.2.2 Adding an RMON Alarm To add an RMON alarm, do the following: Navigate to Ethernet Stats » Configure RMON Alarms . The RMON Alarms table appears. Figure 54: RMON Alarms Table 1. InsertRecord Click InsertRecord. The RMON Alarms form appears. Figure 55: RMON Alarms Form 1. Index Box   ...
  • Page 116 Chapter 3 RUGGEDCOM ROS Device Management User Guide 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.
  • Page 117: Deleting An Rmon Alarm

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Parameter Description The index of the event that is used when a falling 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.
  • Page 118: Managing Rmon Events

    Chapter 3 RUGGEDCOM ROS Device Management User Guide 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 Click Delete.
  • Page 119: Viewing A List Of Rmon Events

    RUGGEDCOM ROS Chapter 3 User Guide Device Management • Section 3.10.3.3, “Deleting an RMON Event” 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.
  • Page 120 Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 60: RMON Events Form 1. Index Box    2. Type List    3. Community Box    4. Last Time Sent Box    5. Description Box    6. Owner Box    7. Apply Button    8. Delete Button    9. View Button    10. Reload Button Configure the following parameter(s) as required: Parameter Description Index Synopsis:  ...
  • Page 121: Deleting An Rmon Event

    RUGGEDCOM ROS Chapter 3 User Guide Device Management Section 3.10.3.3 Deleting an RMON Event To delete an RMON event, do the following: Navigate to Ethernet Stats » Configure RMON Events . The RMON Events table appears. Figure 61: RMON Events Table Select the event from the table. The RMON Events form appears. Figure 62: RMON Events Form 1. Index Box   ...
  • Page 122: Upgrading Firmware

    Upgrading Firmware Upgrading RUGGEDCOM 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.
  • Page 123: Resetting The Device

    Section 3.4, “Uploading/ Downloading Files” IMPORTANT! Never downgrade the RUGGEDCOM ROS software version beyond RUGGEDCOM ROS v4.3 when encryption is enabled. Make sure the device has been restored to factory defaults before downgrading. Restore the device to its factory defaults. For more information, refer to Section 3.3, “Restoring Factory...
  • Page 124: Decommissioning The Device

    Chapter 3 RUGGEDCOM ROS Device Management User Guide Figure 63: Reset Device Form 1. Confirm Button Click Confirm. 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: Disconnect all network cables from the device.
  • Page 125 RUGGEDCOM ROS Chapter 3 User Guide Device Management type syslog.txt When the phrase Generated ssh.keys was saved appears in the log, the SSH keys have been generated. 10. De-fragment and erase all free flash memory by typing: flashfile defrag This may take several minutes to complete. Decommissioning the Device...
  • Page 126 RUGGEDCOM ROS Chapter 3 User Guide Device Management Decommissioning the Device...
  • Page 127: System Administration

    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. CONTENTS • Section 4.1, “Configuring the System Information” • Section 4.2, “Customizing the Login Screen”...
  • Page 128: Customizing The Login Screen

    Chapter 4 RUGGEDCOM ROS System Administration User Guide Parameter Description The system name is displayed in all RUGGEDCOM ROS menu screens. This can make it easier to identify the switches within your network provided that all switches are given a unique name. Location Synopsis:  ...
  • Page 129 RUGGEDCOM ROS Chapter 4 User Guide System Administration User Type Rights Guest Operator Admin Change Basic Settings û ü ü Change Advanced Settings û û ü Run Commands û û ü Default passwords are configured for each user type initially. It is strongly recommended that these be changed before the device is commissioned.
  • Page 130 Chapter 4 RUGGEDCOM ROS System Administration User Guide NOTE RUGGEDCOM ROS requires that all user passwords meet strict guidelines to prevent the use of weak passwords. When creating a new password, make sure it adheres to the following rules: • Must not be less than 8 characters in length. •...
  • Page 131: Clearing Private Data

    RUGGEDCOM ROS Chapter 4 User Guide System Administration Parameter Description Related password is in field Oper Password; cannot change settings; can reset alarms, statistics, logs, etc. Operator Password Synopsis:   19 character ASCII string Related username is in field Oper Username; cannot change settings;...
  • Page 132: Enabling/Disabling The Web Interface

    Chapter 4 RUGGEDCOM ROS System Administration User Guide clear private data When prompted "Do you want to clear private data (Yes/No)?", answer yes and press Enter within five seconds. All configuration and keys in flash will be zeroized. An entry in the event log will be created. Crashlog.txt files (if existing) and syslog.txt files will be preserved.
  • Page 133: Viewing A List Of Pre-Configured Alarms

    RUGGEDCOM ROS Chapter 4 User Guide System Administration NOTE Alarms are volatile in nature. All alarms (active and passive) are cleared at startup. CONTENTS • Section 4.6.1, “Viewing a List of Pre-Configured Alarms” • Section 4.6.2, “Viewing and Clearing Latched Alarms” • Section 4.6.3, “Configuring an Alarm”...
  • Page 134: Viewing And Clearing Latched Alarms

    Chapter 4 RUGGEDCOM ROS System Administration User Guide 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 to Section 4.6.3, “Configuring an Alarm”...
  • Page 135 RUGGEDCOM ROS Chapter 4 User Guide System Administration IMPORTANT! Critical and Alert level alarms are not configurable and cannot be disabled. Navigate to Diagnostic » Configure Alarms . The Alarms table appears. Figure 69: Alarms Table Select an alarm. The Alarms form appears. Configuring an Alarm...
  • Page 136 Chapter 4 RUGGEDCOM ROS System Administration User Guide Figure 70: Alarms Form 1. Name Box    2. Level Box    3. Latch Box    4. Trap Box    5. Log Box    6. LED & Relay Box    7. Refresh Time Box    8. Apply Button    9. Reload Button Configure the following parameter(s) as required: Parameter Description Name Synopsis:  ...
  • Page 137: Authentication Related Security Alarms

    RUGGEDCOM ROS Chapter 4 User Guide System Administration Parameter Description Enables logging the occurrence of this alarm in syslog.txt. 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.
  • Page 138 Chapter 4 RUGGEDCOM ROS System Administration User Guide Weak Password Configured RUGGEDCOM ROS generates this alarm and logs a message in the syslog when a weak password is configured in the Passwords table. Message Name Alarm SNMP Trap Syslog Weak Password Configured Default Keys In Use RUGGEDCOM ROS generates this alarm and logs a message in the syslog when default keys are in use.
  • Page 139: Security Messages For Port Authentication

    RUGGEDCOM ROS Chapter 4 User Guide System Administration Message Name Alarm SNMP Trap Syslog Primary RADIUS Server Unreachable TACACS+ Server Unreachable RUGGEDCOM ROS generates this alarm and logs a message in the syslog when the primary TACACS+ server is unreachable. Message Name Alarm SNMP Trap...
  • Page 140: Managing The Configuration File

    Chapter 4 RUGGEDCOM ROS System Administration User Guide Message Name Alarm SNMP Trap Syslog MAC Address Authorization Failure Secure Port X Learned MAC Addr on VLAN X RUGGEDCOM ROS logs a message in the syslog and sends a configuration change trap when a MAC address is learned on a secure port.
  • Page 141 When sharing a configuration file between devices, make sure both devices have the same passphrase configured. Otherwise, the configuration file will be rejected. NOTE Encryption must be disabled before the device is returned to Siemens or the configuration file is shared with Customer Support. IMPORTANT! Never downgrade the RUGGEDCOM ROS software version beyond RUGGEDCOM ROS v4.3 when...
  • Page 142: Updating The Configuration File

    Chapter 4 RUGGEDCOM ROS System Administration User Guide Parameter Description This passphrase is used as a secret key to encrypt the configuration data. Encrypted data can be decrypted by any device configured with the same passphrase. Click Apply. Section 4.7.2 Updating the Configuration File Once downloaded from the device, the configuration file can be updated using a variety of different tools: NOTE For information about uploading/downloading files, refer to...
  • Page 143: Managing Radius Authentication

    RUGGEDCOM ROS Chapter 4 User Guide System Administration • Section 4.8.2, “Managing TACACS+ Authentication” Section 4.8.1 Managing RADIUS Authentication RUGGEDCOM ROS can be configured to act as a RADIUS client and forward user credentials to a RADIUS (Remote Authentication Dial In User Service) server for remote authentication and authorization. RADIUS is a UDP-based protocol used for carrying authentication, authorization and configuration information between a Network Access Server (NAS) that desires to authenticate its links and a shared authentication server.
  • Page 144: Configuring The Radius Server

    Chapter 4 RUGGEDCOM ROS System Administration User Guide Attribute Value EAP-Message { A message(s) received from the authenticating peer } EAP-Message is an extension attribute for RADIUS, as defined by 2869. CONTENTS • Section 4.8.1.1, “Configuring the RADIUS Server” • Section 4.8.1.2, “Configuring the RADIUS Client” Section 4.8.1.1 Configuring the RADIUS Server The Vendor-Specific attribute (or VSA) sent to the RADIUS server as part of the RADIUS request is used to...
  • Page 145 RUGGEDCOM ROS Chapter 4 User Guide System Administration Figure 72: RADIUS Server Table Select either Primary or Backup from the table. The RADIUS Server form appears. Figure 73: RADIUS Server Form 1. Server Box    2. IP Address Box    3. Auth UDP Port Box    4. Auth Key Box    5. Confirm Auth Key Box    6. Apply Button    7. Reload Button Configure the following parameter(s) as required: Parameter...
  • Page 146: Managing Tacacs+ Authentication

    Chapter 4 RUGGEDCOM ROS System Administration User Guide Section 4.8.2 Managing TACACS+ Authentication TACACS+ (Terminal Access Controller Access-Control System Plus) is a TCP-based access control protocol that provides authentication, authorization and accounting services to routers, Network Access Servers (NAS) and other networked computing devices via one or more centralized servers. The following section describes how to configure TACACs+ authentication.
  • Page 147: Configuring User Privileges

    RUGGEDCOM ROS Chapter 4 User Guide System Administration Figure 75: TACACS Plus Server Form 1. Server Box    2. IP Address Box    3. Auth TCP Port Box    4. Auth Key Box    5. Confirm Key Box    6. Apply Button    7. Reload Button Configure the following parameter(s) as required: Parameter Description Server Synopsis:  ...
  • Page 148 Chapter 4 RUGGEDCOM ROS System Administration User Guide To configure the privilege levels for each user type, do the following: Navigate to Administration » Configure Security Server » Configure TacPlus Server » Configure TACPLUS Serv Privilege Config . The TACPLUS Serv Privilege Config form appears. Figure 76: TACPLUS Serv Privilege Config Form 1. Admin Priv Box   ...
  • Page 149: Setup And Configuration

    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 RUGGEDCOM ROS. CONTENTS • Section 5.1, “Managing Virtual LANs” •...
  • Page 150: Vlan Concepts

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • Section 5.1.2, “Viewing a List of VLANs” • Section 5.1.3, “Configuring VLANs Globally” • Section 5.1.4, “Configuring VLANs for Specific Ethernet Ports” • Section 5.1.5, “Managing Static VLANs” Section 5.1.1 VLAN Concepts The following section describes some of the concepts important to the implementation of VLANs in RUGGEDCOM ROS.
  • Page 151: The Management Vlan

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.1.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.
  • Page 152: Forbidden Ports List

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Priority Tagged Frame Received Untagged Tagged (Valid VID) (VID = 0) VLAN ID associated with the frame PVID PVID VID in the Tag Frame dropped due to its tagged/untagged format Frame dropped if the ingress port is not a member of the VLAN the frame is associated with and ingress filtering is enabled Does not depend on the ingress port's VLAN configuration parameters.
  • Page 153: Garp Vlan Registration Protocol (Gvrp)

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.1.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.
  • Page 154: Pvlan Edge

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • 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 •...
  • Page 155 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration The outer tag VID is the PVID of the frame's ingress edge port. This means that traffic from an individual customer is tagged with their unique VID and is thus segregated from other customer's traffic. For untagged ingress frames, the switch will only add the outer VLAN tag.
  • Page 156: Vlan Advantages

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.1.1.11 VLAN Advantages The following are a few of the advantages offered by VLANs. Traffic Domain Isolation VLANs are most often used for their ability to restrict traffic flows between groups of devices. Unnecessary broadcast traffic can be restricted to the VLAN that requires it.
  • Page 157: Viewing A List Of Vlans

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration 199.85.245.1/25 199.85.245.128/26 199.85.245.192/26 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.1.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 »...
  • Page 158 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 82: Global VLAN Parameters Form 1. VLAN-aware Options    2. Ingress Filtering Options    3. QinQ Outer TPID options    4. Apply Button    5. Reload Button Configure the following parameter(s) as required: Parameter Description VLAN-aware Synopsis:   { No, Yes } Default:  ...
  • Page 159: Configuring Vlans For Specific Ethernet Ports

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.1.4 Configuring VLANs for Specific Ethernet Ports When a VLAN ID is assigned to an Ethernet port, the VLAN appears in the VLAN Summary table where it can be further configured. To configure a VLAN for a specific Ethernet port, do the following: Navigate to Virtual LANs »...
  • Page 160 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Default:   Edge This parameter specifies how the port determines its membership in VLANs. There are few types of ports: • Edge - the port is only a member of one VLAN (its native VLAN specified by the PVID parameter).
  • Page 161: Managing Static Vlans

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Click Apply. Section 5.1.5 Managing Static VLANs The following section describes how to configure and manage static VLANs. CONTENTS • Section 5.1.5.1, “Viewing a List of Static VLANs” • Section 5.1.5.2, “Adding a Static VLAN” •...
  • Page 162 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 86: Static VLANs Table 1. InsertRecord Click InsertRecord. The Static VLANs form appears. Figure 87: Static VLANs Form 1. VID Box    2. VLAN Name Box    3. Forbidden Ports Box    4. IGMP Options    5. MSTI Box    6. Apply Button    7. Delete Button    8. Reload Button Configure the following parameter(s) as required: NOTE If IGMP Options is not enabled for the VLAN, both IGMP messages and multicast streams will be...
  • Page 163: Deleting A Static Vlan

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter 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).
  • Page 164: Managing Spanning Tree Protocol

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 89: Static VLANs Form 1. VID Box    2. VLAN Name Box    3. Forbidden Ports Box    4. IGMP Options    5. MSTI Box    6. Apply Button    7. Delete Button    8. Reload Button Click Delete. Section 5.2 Managing Spanning Tree Protocol CONTENTS • Section 5.2.1, “RSTP Operation” •...
  • Page 165: Rstp States And Roles

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration it requires that frame transfer halt after a link outage until all bridges in the network are guaranteed to be aware of the new topology. Using the values recommended by 802.1D, this period lasts 30 seconds. The Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) was a further evolution of the 802.1D Spanning Tree Protocol.
  • Page 166 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide State There are three RSTP states: Discarding, Learning and Forwarding. The discarding state is entered when the port is first put into service. The port does not learn addresses in this state and does not participate in frame transfer.
  • Page 167: Edge Ports

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 90: Bridge and Port Roles 1. Root Bridge    2. Designated Bridge    3. Designated Port    4. Root Port    5. Alternate Port    6. Backup Port A port is alternate when it receives a better message from another bridge on the LAN segment it is connected to. The message that an Alternate Port receives is better than the port itself would generate, but not good enough to convince it to become the Root Port.
  • Page 168: Point-To-Point And Multipoint Links

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.2.1.3 Point-to-Point and Multipoint Links RSTP uses a peer-peer protocol called Proposing-Agreeing to ensure transitioning in the event of a link failure. This protocol is point-to-point and breaks down in multipoint situations, i.e. when more than two bridges operate on a shared media link.
  • Page 169: Bridge Diameter

    There is a relationship between the bridge diameter and the maximum age parameter. To achieve extended ring sizes, Siemens eRSTP™ uses an age increment of ¼ of a second. The value of the maximum bridge diameter is thus four times the configured maximum age parameter.
  • Page 170: Fast Root Failover

    User Guide Section 5.2.1.7 Fast Root Failover Siemens’s Fast Root Failover feature is an enhancement to RSTP that may be enabled or disabled. Fast Root Failover improves upon RSTP’s handling of root bridge failures in mesh-connected networks. IMPORTANT! In networks mixing RUGGEDCOM and non-RUGGEDCOM switches, or in those mixing Fast Root Failover algorithms, RSTP Fast Root Failover will not function properly and root bridge failure will result in an unpredictable failover time.
  • Page 171: Rstp In Structured Wiring Configurations

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Section 5.2.2.2, “RSTP in Ring Backbone Configurations” • Section 5.2.2.3, “RSTP Port Redundancy” Section 5.2.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.
  • Page 172: Rstp In Ring Backbone Configurations

    Enable RSTP Fast Root Failover option. This is a proprietary feature of Siemens. In a mesh network with only RUGGEDCOM devices in the core of the network, it is recommended to enable the RSTP Fast Root Failover option to minimize the network downtime in the event of a Root bridge failure.
  • Page 173 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 92: Example - Ring Backbone Configuration To design a ring backbone configuration with RSTP, do the following: 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.
  • Page 174: Rstp Port Redundancy

    Disable RSTP Fast Root Failover option. This is a proprietary feature of Siemens. In RUGGEDCOM ROS, the RSTP Fast Root Failover option is enabled by default. It is recommended to disable this feature when operating in a Ring network.
  • Page 175: Mstp Regions And Interoperability

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration to be derived from an analysis of data traffic on the bridged network, and from requirements for load sharing, redundancy, and path optimization. Once these parameters have all been derived, it is also critical that they are consistently applied and managed across all bridges in an MST region.
  • Page 176: Mstp Bridge And Port Roles

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide The IST is also the extension inside the MST region of the CIST (see below), which spans the entire bridged network, inside and outside of the MST region and all other RSTP and STP bridges, as well as any other MST regions.
  • Page 177: Benefits Of Mstp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Role Description • Alternate and Backup Ports function the same as they do in RSTP, but relative to the CIST Regional Root. MSTI Port Roles For each MSTI on a bridge: •...
  • Page 178: Implementing Mstp On A Bridged Network

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Isolation of Spanning Tree Reconfiguration. A link failure in an MSTP region that does not affect the roles of Boundary ports will not cause the CST to be reconfigured, nor will the change affect other MSTP regions. This is due to the fact that MSTP information does not propagate past a region boundary.
  • Page 179: Configuring Stp Globally

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Configure the Port Cost and Priority per Port for each MSTI. For more information, refer to Section 5.2.9.5, “Configuring an MSTI for an Ethernet Port” Set the STP Protocol Version to MSTP and enable STP. For more information, refer to Section 5.2.4, “Configuring STP Globally”...
  • Page 180: Configuring Stp For Specific Ethernet Ports

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Bridge Priority provides a way to control the topology of the STP connected network. The desired Root and Designated bridges can be configured for a particular topology. The bridge with the lowest priority will become root.
  • Page 181 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 95: Port RSTP Parameters Table Select an Ethernet port. The Port RSTP Parameters form appears. 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    7. Point to Point List    8. Restricted Role Box   ...
  • Page 182 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Enabling STP activates the STP or RSTP protocol for this port per the configuration in the STP Configuration menu. STP may be disabled for the port ONLY if the port does not attach to an STP enabled bridge in any way.
  • Page 183: Configuring Erstp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description cannot run the link in full-duplex mode. Force the parameter false when the port operates the link in full-duplex mode, but is still not point-to-point (e.g. a full-duplex link to an unmanaged bridge that concentrates two other STP bridges).
  • Page 184 (and may be relatively long) for any given mesh topology. This configuration parameter enables Siemens's enhancement to RSTP which detects a failure of the root switch and performs some extra RSTP processing steps, significantly reducing the network recovery time and making it deterministic.
  • Page 185: Viewing Global Statistics For Stp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description These are the supported configuration options: • Off - Fast Root Failover algorithm is disabled and hence a root switch failure may result in excessive connectivity recovery time. • On - Fast Root Failover is enabled and the most robust algorithm is used, which requires the appropriate support in the root switch.
  • Page 186 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 98: Bridge RSTP Statistics Form 1. Bridge Status Box    2. Bridge ID Box    3. Root ID Box    4. Root Port Box    5. Root Path Cost Box    6. Configure Hello Time Box    7. Learned Hello Time Box    8. Configured Forward Delay Box    9. Learned Forward Delay Box    10. Configured Max Age Box    11. Learned Max Age Box   ...
  • Page 187: Viewing Stp Statistics For Ethernet Ports

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description The actual Hello time provided by the root bridge as learned in configuration messages. This time is used in designated bridges. Configured Forward Delay Synopsis:   0 to 65535 The configured Forward Delay time from the Bridge RSTP Parameters menu.
  • Page 188 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide This table displays the following information: 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).
  • Page 189: Managing Multiple Spanning Tree Instances

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description The count of STP topology change notification messages received on this port. Excessively high or rapidly increasing counts signal network problems. TX Tcns Synopsis:   0 to 4294967295 The count of STP topology change notification messages transmitted on this port.
  • Page 190 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 100: Bridge MSTI Statistics Form 1. Instance Box    2. Get Button    3. Bridge Status Box    4. Bridge ID Box    5. Root ID Box    6. Root Port Box    7. Root Path Cost Box    8. Total Topology Changes Box    9. Reload Button This table displays the following information: Parameter Description Bridge Status...
  • Page 191: Viewing Statistics For Port Mstis

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description Excessively high or rapidly increasing counts signal network problems. Section 5.2.9.2 Viewing Statistics for Port MSTIs To view statistics for port MSTIs, navigate to Spanning Tree » View Port MSTI Statistics . The Port MSTI Statistics form appears.
  • Page 192: Configuring The Mst Region Identifier

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description 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. •...
  • Page 193: Configuring A Global Msti

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Configure the following parameter(s) as required: Parameter Description Name Synopsis:   Any 32 characters Default:   00-0A-DC-92-00-00 The name of the MST region. All devices in the same MST region must have the same region name configured. Synopsis:  ...
  • Page 194: Configuring An Msti For An Ethernet Port

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Under Instance ID, type an ID number for a Multiple Spanning Tree Instance (MSTI) and click GET. The settings for the MSTI are displayed. Any changes made to the configuration will be applied specifically to this instance ID.
  • Page 195 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 105: Port MSTI Parameters Form 1. Instance ID Box    2. Get Button    3. Port(s) Box    4. Priority List    5. STP Cost Box    6. RSTP Cost Box    7. Apply Button    8. Reload Button Under Instance ID, type an ID number for a Multiple Spanning Tree Instance (MSTI) and click GET. The settings for the MSTI are displayed.
  • Page 196: Clearing Spanning Tree Protocol Statistics

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description as negotiated (20,000 for 1Gbps, 200,000 for 100 Mbps links and 2,000,000 for 10 Mbps links). For MSTP, this parameter applies to both external and internal path cost. Click Apply. Section 5.2.10 Clearing Spanning Tree Protocol Statistics To clear all spanning tree protocol statistics, do the following:...
  • Page 197: Configuring Classes Of Service Globally

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • The Differentiated Services Code Point (DSCP) component of the Type Of Service (TOS) field in the IP header, if the frame is IP • The default CoS for the port Each frame’s CoS will be determined once the first examined parameter is found in the frame.
  • Page 198: Configuring Classes Of Service For Specific Ethernet Ports

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 107: Global CoS Parameters Form 1. CoS Weighting Options    2. Apply Button    3. Reload Button Configure the following parameter(s) as required: Parameter Description CoS Weighting Synopsis:   { 8:4:2:1, Strict } Default:   8:4:2:1 During traffic bursts, frames queued in the switch pending transmission on a port may have different CoS priorities.
  • Page 199 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 108: Port CoS Parameters Table Select an Ethernet port. The Port CoS Parameters form appears. Figure 109: Port CoS Parameters Form 1. Port(s) Box    2. Default Pri Box    3. Inspect TOS Options    4. Apply Button    5. Reload Button Configure the following parameter(s) as required: Parameter Description Port(s)
  • Page 200: Configuring Priority To Cos Mapping

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description is enabled the switch will use the Differentiated Services bits in the TOS field. Click Apply. Section 5.3.3 Configuring Priority to CoS Mapping Frames received untagged can be automatically assigned a CoS based on their priority level. To map a priority level to a CoS, do the following: Navigate to Classes of Service »...
  • Page 201: Configuring Dscp To Cos Mapping

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description Value of the IEEE 802.1p priority. Synopsis:   { Normal, Medium, High, Crit } Default:   Normal CoS assigned to received tagged frames with the specified IEEE 802.1p priority value. Click Apply.
  • Page 202: Managing Mac Addresses

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 113: DSCP to CoS Mapping Form 1. DSCP Box    2. CoS List    3. Apply Button    4. Reload Button Configure the following parameter(s) as required: 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.
  • Page 203: Viewing A List Of Mac Addresses

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Section 5.4.5, “Purging All Dynamic MAC Addresses” Section 5.4.1 Viewing a List of MAC Addresses To view a list of all static and dynamically learned MAC addresses, navigate to MAC Address Tables » View MAC Addresses .
  • Page 204: Configuring Mac Address Learning Options

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.4.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. Addresses can also be removed when a link failure or topology change occurs.
  • Page 205 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Navigate to MAC Address Tables » Configure MAC Address Flooding Options . The Flooding Options table appears. Figure 116: Flooding Options Table Select a port. The Flooding Options form appears. Figure 117: Flooding Options Form 1. Port(s) Box    2. Flood Unknown Unicast Options    3. Apply Button    4. Reload Button Configure the following parameter(s) as required: Parameter Description...
  • Page 206: Managing Static Mac Addresses

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.4.4 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.
  • Page 207 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 119: Static MAC Addresses Table 1. InsertRecord Click InsertRecord. The Static MAC Addresses form appears. Figure 120: Static MAC Addresses Form 1. MAC Address Box    2. VID Box    3. Port Box    4. CoS List    5. Apply Button    6. Delete Button    7. Reload Button Configure the following parameter(s) as required: Parameter Description...
  • Page 208: Deleting A Static Mac Address

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description VLAN Identifier of the VLAN upon which the MAC address operates. Option ANY allows learning a MAC address through the Port Security module on any VLAN's that are configured on the switch. Synopsis:  ...
  • Page 209: Purging All Dynamic Mac Addresses

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 122: Static MAC Addresses Form 1. MAC Address Box    2. VID Box    3. Port Box    4. CoS List    5. Apply Button    6. Delete Button    7. Reload Button Click Delete. Section 5.4.5 Purging All Dynamic MAC Addresses To purge the dynamic MAC address list of all entries, do the following: Navigate to MAC Address Tables »...
  • Page 210: Configuring The Time And Date

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • SNTP (Simple Network Time Protocol) client and server CONTENTS • Section 5.5.1, “Configuring the Time and Date” • Section 5.5.2, “Managing NTP” Section 5.5.1 Configuring the Time and Date To set the time, date and other time-keeping related parameters, do the following: Navigate to Administration »...
  • Page 211: Managing Ntp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description This setting allows for the conversion of UTC (Universal Coordinated Time) to local time. DST Offset Synopsis:   HH:MM:SS Default:   00:00:00 This parameter specifies the amount of time to be shifted forward/backward when DST begins and ends.
  • Page 212: Configuring Ntp Servers

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide NOTE If the device is running as an NTP server, NTP service must be enabled. Navigate to Administration » System Time Manager » Configure NTP » Configure NTP Service . The SNTP Parameters form appears. Figure 125: SNTP Parameters Form 1. SNTP Options   ...
  • Page 213: Managing Snmp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 127: NTP Servers Form 1. Server Box    2. IP Address Box    3. Update Period Box    4. Apply Button    5. Reload Button 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.
  • Page 214: Managing Snmp Users

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide model. A combination of a security model and level will determine which security mechanism is employed when handling an SNMP packet. Before configuring SNMPv3, note the following: • Each user belongs to a group •...
  • Page 215: Adding An Snmp User

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 128: SNMP Users Table If users have not been configured, add users as needed. For more information, refer to Section 5.6.1.2, “Adding an SNMP User” Section 5.6.1.2 Adding an SNMP User Multiple users (up to a maximum of 32) can be configured for the local SNMPv3 engine, as well as SNMPv1 and SNMPv2c communities.
  • Page 216 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 130: 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. Reload Button NOTE RUGGEDCOM ROS requires that all user passwords meet strict guidelines to prevent the use of weak passwords.
  • Page 217: Deleting An Snmp User

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description generated to trap receivers if request was received from this user, but from any other IP address.If IP address is empty, traps can not be generated to this user, but SNMP requests will be served for this user from any IP address.
  • Page 218 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 131: SNMP Users Table Select the user from the table. The SNMP Users form appears. Figure 132: 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   ...
  • Page 219: Managing Security-To-Group Mapping

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.6.2 Managing Security-to-Group Mapping The following section describes how to configure and manage security-to-group maps. CONTENTS • Section 5.6.2.1, “Viewing a List of Security-to-Group Maps” • Section 5.6.2.2, “Adding a Security-to-Group Map” • Section 5.6.2.3, “Deleting a Security-to-Group Map”...
  • Page 220 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 134: SNMP Security to Group Maps Table 1. InsertRecord Click InsertRecord. The SNMP Security to Group Maps form appears. Figure 135: SNMP Security to Group Maps Form 1. Security Model Box    2. Name Box    3. Group Box    4. Apply Button    5. Delete Button    6. Reload Button Configure the following parameter(s) as required: Parameter Description...
  • Page 221: Deleting A Security-To-Group Map

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.6.2.3 Deleting a Security-to-Group Map To delete a security-to-group map, do the following: Navigate to Administration » Configure SNMP » Configure SNMP Security to Group Maps . The SNMP Security to Group Maps table appears. Figure 136: SNMP Security to Group Maps Table Select the map from the table.
  • Page 222: Viewing A List Of Snmp Groups

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • Section 5.6.3.3, “Deleting an SNMP Group” Section 5.6.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 138: SNMP Access Table If SNMP groups have not been configured, add groups as needed.
  • Page 223 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 140: SNMP Access Form 1. Group Box    2. Security Model Box    3. Security Level Box    4. ReadViewName Box    5. WriteViewName Box    6. NotifyViewName Box    7. Apply Button    8. Delete Button    9. Reload Button Configure the following parameter(s) as required: Parameter Description Group Synopsis:  ...
  • Page 224: Deleting An Snmp Group

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Click Apply. Section 5.6.3.3 Deleting an SNMP Group To delete an SNMP group, do the following: Navigate to Administration » Configure SNMP » Configure SNMP Access . The SNMP Access table appears. Figure 141: SNMP Access Table Select the group from the table.
  • Page 225: Managing Network Discovery

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.7 Managing Network Discovery RUGGEDCOM ROS supports the Link Layer Discovery Protocol (LLDP) and RUGGEDCOM Discovery Protocol (RCDP), both Layer 2 protocols for automated network discovery. CONTENTS • Section 5.7.1, “Network Discovery Concepts” •...
  • Page 226: Ruggedcom Discovery Protocol (Rcdp)

    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. It is capable of discovering, identifying and performing basic configuration of RUGGEDCOM ROS-based devices via RCDP.
  • Page 227 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 143: Global LLDP Parameters Form 1. State Options    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:  ...
  • Page 228: Configuring Lldp For An Ethernet Port

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.7.3 Configuring LLDP for an Ethernet Port To configure LLDP for a specific Ethernet Port, do the following: Navigate to Network Discovery » Link Layer Discovery Protocol » Configure Port LLDP Parameters . The Port LLDP Parameters table appears.
  • Page 229: Enabling/Disabling Rcdp

    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. It is capable of discovering, identifying and performing basic configuration of RUGGEDCOM ROS-based devices via RCDP.
  • Page 230: Viewing Global Statistics And Advertised System Information

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 146: RCDP Parameters Form 1. RCDP Discovery Options    2. Apply Button    3. Reload Button Select Enabled to enable RCDP, or select Disabled to disable RCDP. Click Apply. Section 5.7.5 Viewing Global Statistics and Advertised System Information To view global statistics for LLDP and the system information that is advertised to neighbors, navigate to Network Discovery »...
  • Page 231: Viewing Statistics For Lldp Neighbors

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Parameter Description A number of times an entry was deleted from LLDP Neighbor Information Table because the information timeliness interval has expired. Ageouts Synopsis:   0 to 4294967295 A counter of all TLVs discarded. Section 5.7.6 Viewing Statistics for LLDP Neighbors To view statistics for LLDP neighbors, navigate to Network Discovery »...
  • Page 232: Viewing Statistics For Lldp Ports

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.7.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 149: LLDP Statistics Table This table displays the following information: Parameter Description...
  • Page 233: Managing Multicast Filtering

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.8 Managing Multicast Filtering Multicast traffic can be filtered using IGMP (Internet Group Management Protocol) snooping or GMRP (GARP Multicast Registration Protocol). CONTENTS • Section 5.8.1, “Managing IGMP” • Section 5.8.2, “Managing GMRP” Section 5.8.1 Managing IGMP IGMP is used by IP hosts to report their host group memberships with multicast routers.
  • Page 234 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 150: Example – IGMP In Operation 1. Producer    2. Membership Queries    3. Membership Reports    4. Consumer    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.
  • Page 235 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Passive Mode When such a switch is used in a network with a multicast router, it can be configured to run Passive IGMP. This mode prevents the switch from sending the queries that can confuse the router causing it to stop issuing IGMP queries.
  • Page 236 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide If RSTP detects a change in the network topology, IGMP will take some actions to avoid the loss of multicast connectivity and reduce network convergence time: • The switch will immediately issue IGMP queries (if in IGMP Active mode) to obtain potential new group membership information.
  • Page 237: Viewing A List Of Multicast Group Memberships

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration The membership report from host C1 for VLAN 3 will cause the switch to immediately begin forwarding multicast traffic from producer P2 to host C2. • 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.
  • Page 238: Viewing Forwarding Information For Multicast Groups

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide If the table is empty, do the following: • Make sure traffic is being sent to the device. • Make sure IGMP is properly configured on the device. For more information, refer to Section 5.8.1.4, “Configuring IGMP”...
  • Page 239: Configuring Igmp

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.8.1.4 Configuring IGMP To configure the IGMP, do the following: Make sure one or more static VLANs exist with IGMP enabled. For more information, refer to Section 5.1.5, “Managing Static VLANs” Navigate to Multicast Filtering » Configure IGMP Parameters . The IGMP Parameters form appears. Figure 154: IGMP Parameters Form 1. Mode Options   ...
  • Page 240: Managing Gmrp

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description NOTE This parameter also affects the Group Membership Interval (i.e. the group subscriber aging time), therefore, it takes effect even in PASSIVE mode. Router Ports Synopsis:   Comma-separated list of ports Default:  ...
  • Page 241: Gmrp Concepts

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Section 5.8.2.7, “Deleting a Static Multicast Group” Section 5.8.2.1 GMRP Concepts The following describes some of the concepts important to the implementation of multicast filtering using GMRP: Joining a Multicast Group In order to join a multicast group, an end station transmits a GMRP join message. The switch that receives the join message adds the port through which the message was received to the multicast group specified in the message.
  • Page 242 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide In this scenario, there are two multicast sources, S1 and S2, multicasting to Multicast Groups 1 and 2, respectively. A network of five switches, including one core switch (B), connects the sources to two hosts, H1 and H2, which receive the multicast streams from S1 and S2, respectively.
  • Page 243: Viewing A Summary Of Multicast Groups

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Switch C forwards the Group 2 multicast via Port C2, which has previously become a member of Group 2. • Ultimately, Host H2, connected to Port C2, receives the Group 2 multicast. Section 5.8.2.2 Viewing a Summary of Multicast Groups To view a summary of all multicast groups, navigate to Multicast Filtering »...
  • Page 244: Configuring Gmrp For Specific Ethernet Ports

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 157: Global GMRP Parameters Form 1. GMRP Enable Options    2. RSTP Flooding Options    3. Leave Timer Box    4. Apply Button    5. Reload Button Configure the following parameter(s) as required: Parameter Description GMRP Enable Synopsis:   { No, Yes } Default:  ...
  • Page 245 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 158: Port GMRP Parameters Table Select an Ethernet port. The Port GMRP Parameters form appears. Figure 159: Port GMRP Parameters Form 1. Port(s) Box    2. GMRP List    3. Apply Button    4. Reload Button Configure the following parameter(s) as required: Parameter Description Port(s)
  • Page 246: Viewing A List Of Static Multicast Groups

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.8.2.5 Viewing a List of Static Multicast Groups To view a list of static multicast groups, navigate to Multicast Filtering » Configure Static Multicast Groups . The Static Multicast Groups table appears. Figure 160: Static Multicast Groups Table If a static multicast group is not listed, add the group.
  • Page 247: Deleting A Static Multicast Group

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 162: Static Multicast Groups Form 1. MAC Address Box    2. VID Box    3. CoS List    4. Ports Box    5. Apply Button    6. Delete Button    7. Reload Button Configure the following parameter(s) as required: Parameter Description MAC Address Synopsis:   ##-##-##-##-##-## where ## ranges 0 to FF Default:  ...
  • Page 248: Managing Port Security

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 163: Static Multicast Groups Table Select the group from the table. The Static Multicast Groups form appears. Figure 164: Static Multicast Groups Form 1. MAC Address Box    2. VID Box    3. Priority Box    4. Ports Box    5. Apply Button    6. Delete Button    7. Reload Button Click Delete.
  • Page 249: Port Security Concepts

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration • Section 5.9.4, “Configuring IEEE 802.1X” Section 5.9.1 Port Security Concepts The following section describes some of the concepts important to the implementation of port security in RUGGEDCOM ROS. CONTENTS • Section 5.9.1.1, “Static MAC Address-Based Authentication” •...
  • Page 250: Ieee 802.1X Authentication With Mac Address-Based Authentication

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 165: IEEE 802.1x General Topology 1. Supplicant    2. Authenticator Switch    3. LAN    4. Authentication Server IMPORTANT! RUGGEDCOM 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.1x makes use of the Extensible Authentication Protocol (EAP), which is a generic PPP authentication protocol that supports various authentication methods.
  • Page 251: Assigning Vlans With Tunnel Attributes

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.9.1.4 Assigning VLANS with Tunnel Attributes RUGGEDCOM ROS supports assigning a VLAN to the authorized port using tunnel attributes, as defined in 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.
  • Page 252: Configuring Port Security

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description MAC Address Synopsis:   ##-##-##-##-##-## where ## ranges 0 to FF Authorized MAC address learned by the switch. Synopsis:   0 to 65535 VLAN Identifier of the VLAN upon which the MAC address operates. Sticky Synopsis:  ...
  • Page 253 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 168: Ports Security Form 1. Port Box    2. Security List    3. Autolearn Box    4. Sticky Options    5. Shutdown Time Box    6. Status Box    7. Apply Button    8. Reload Button Configure the following parameter(s) as required: Parameter Description Synopsis:   1 to maximum port number Port Default:  ...
  • Page 254: Configuring Ieee 802.1X

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description Only applicable when the 'Security' field has been set to 'Static MAC'. Change the behaviour of the port to either sticky or non- sticky. If Sticky is 'Yes', MACs/Devices authorized on the port 'stick' to the port and the switch will not allow them to move to a different port.
  • Page 255 RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 169: 802.1X Parameters Table Select an Ethernet port. The 802.1X Parameters form appears. Figure 170: 802.1X Parameters Form 1. Port Box    2. tX Period Box    3. quietPeriod Box    4. reAuthEnabled Options    5. reAuthPeriod Box    6. reAuthMax Box    7. suppTimeout Box    8. serverTimeout Box    9. maxReq Box    10. Apply Button    11. Reload Button Configure the following parameter(s) as required: Parameter Description...
  • Page 256: Managing Link Aggregation

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Parameter Description quietPeriod Synopsis:   0 to 65535 Default:   60 s The period of time not to attempt to acquire a Supplicant after the authorization session failed. reAuthEnabled Synopsis:   { No, Yes } Default:  ...
  • Page 257: Link Aggregation Concepts

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Figure 171: Examples of Link Aggregation 1. Switch    2. Server RUGGEDCOM ROS allows up to 15 port trunks to be configured on a single device, with each consisting of up to 8 ports. NOTE The maximum number of port trunks for each device depends on the number of ports available. At least two ports are required to configure a port trunk.
  • Page 258: Rules And Limitations

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide • Section 5.10.1.2, “Link Aggregation and Layer 2 Features” • Section 5.10.1.3, “Link Aggregation and Physical Layer Features” Section 5.10.1.1 Rules and Limitations The implementation of link aggregation must adhere to the following rules and limitations: •...
  • Page 259: Link Aggregation And Physical Layer Features

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Section 5.10.1.3 Link Aggregation and Physical Layer Features Physical layer features (e.g. physical link configuration, link status, rate limiting, Ethernet statistics) will still treat each aggregated port separately. • Physical configuration/status parameters will NOT be automatically applied to other ports in the trunk and will be displayed for each port as usual.
  • Page 260: Adding A Port Trunk

    Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Section 5.10.2.2 Adding a Port Trunk To add a port trunk, do the following: IMPORTANT! The port trunk must be properly configured on both sides of the aggregated link. In switch-to-switch connections, if the configuration of both sides does not match (i.e. some ports are mistakenly not included in the port trunk), it will result in a loop.
  • Page 261: Deleting A Port Trunk

    RUGGEDCOM ROS Chapter 5 User Guide Setup and Configuration Configure the following parameter(s) as required: Parameter Description Trunk ID Synopsis:   1 to 2 Default:   1 Trunk number. It doesn't affect port trunk operation in any way and is only used for identification. Synopsis:  ...
  • Page 262 Chapter 5 RUGGEDCOM ROS Setup and Configuration User Guide Figure 176: Port Trunks Form 1. Trunk ID Box    2. Trunk Name Box    3. Ports Box    4. Apply Button    5. Delete Button    6. Reload Button Click Delete. Deleting a Port Trunk...
  • Page 263: Troubleshooting

    RUGGEDCOM ROS Chapter 6 User Guide Troubleshooting Troubleshooting This chapter describes troubleshooting steps for common issues that may be encountered when using RUGGEDCOM ROS or designing a network. IMPORTANT! For further assistance, contact a Customer Service representative. CONTENTS • Section 6.1, “General” •...
  • Page 264: Ethernet Ports

    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, A possible cause of intermittent operation is that of a ‘duplex mismatch’. If one end of the but fails as traffic rates increase OR a link can link is fixed to full-duplex and the peer auto-negotiates, the auto-negotiating end falls back be pinged but has problems with FTP/SQL/...
  • Page 265: Vlans

    RUGGEDCOM ROS Chapter 6 User Guide Troubleshooting Problem 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.
  • Page 266 Chapter 6 RUGGEDCOM ROS Troubleshooting User Guide Problem Solution VLANs are not needed on the network. Can Yes. Simply leave all ports set to type edge and leave the native VLAN set to 1. This is the they be turned off? default configuration for the switch.

Table of Contents