Page 1 Rugged Operating System (ROS®) v3.11 User Guide For use with : RMC30 July 19, 2012 www.RuggedCom.com...
Page 2 We have checked the contents of this manual against the hardware and software described. However, deviations from the description cannot be completely ruled out. RuggedCom shall not be liable for any errors or omissions contained herein or for consequential damages in connection with the furnishing, performance, or use of this material.
Page 3: Table Of Contents
1.13.1. RADIUS overview ................... 33 1.13.2. User Login Authentication and Authorization .......... 33 1.13.3. Radius Server Configuration ..............35 1.14. TACACS+ ......................36 1.14.1. User Login Authentication and Authorization .......... 36 1.14.2. TACACS+ Server Configuration ............. 37 ROS® v3.11User Guide RMC30...
Page 4 2.3.1. Serial Ports ....................57 2.3.2. Raw Socket ....................59 2.3.3. Remote Hosts ................... 62 2.3.4. Preemptive Raw Socket ................63 2.3.5. Modbus Server ..................65 2.3.6. Modbus Client ................... 66 2.3.7. WIN and TIN .................... 67 ROS® v3.11User Guide RMC30...
Page 5 5.6.1. Enabling Trace ..................102 5.6.2. Starting Trace ..................103 5.7. Viewing DHCP Learned Information ..............104 5.8. Executing Commands Remotely Through RSH ..........104 5.9. Resetting the Device ..................104 6. Firmware Upgrade and Configuration Management ............ 105 ROS® v3.11User Guide RMC30...
Page 6 A. SNMP MIB Support ..................... 114 A.1. Standard MIBs ....................114 A.2. RuggedCom proprietary MIBs ................115 A.3. RuggedCom Supported Agent Capabilities MIBs ..........115 B. SNMP Trap Summary ....................119 C. List of Objects Eligible for RMON Alarms ..............120 D.
Page 7 2.11. Serial Port Configuration Form ................. 57 2.12. Raw Socket Table ..................... 59 2.13. Raw Socket Form ..................... 60 2.14. Remote Hosts Table ....................62 2.15. Remote Hosts Form ....................62 2.16. Preemptive Raw Socket Table .................. 63 ROS® v3.11User Guide RMC30...
Page 8 5.3. Flashfiles command summary .................. 100 5.4. Flashfile Memory Mapping Summary ................ 100 5.5. Obtaining Information About "main.bin" ..............101 5.6. Displaying Trace Settings ..................102 5.7. Enabling Trace ......................103 5.8. Starting Trace ......................103 ROS® v3.11User Guide RMC30...
Page 9: Preface
• RuggedMC™ Media Converters RMC30 and RP110 Each product model has a subset of the entire ROS® feature set. This manual is intended for use with the RMC30 product family and has been streamlined to only describe the relevant features.
Page 10: Applicable Firmware Revision
It is RuggedCom's policy to provide Web access to only the latest 'patch' release for a version of firmware. If you decide that an upgrade is merited, then getting all the fixes only makes sense.
Page 11: Administration
System Identification parameter), Menu Title, Access Level, Alarms indicator, Sub-Menus and Command Bar. Sub-menus are entered by selecting the desired menu with the arrow keys and pressing the enter key. Pressing the escape key returns you to the parent menu. ROS® v3.11User Guide RMC30...
Page 12: Making Configuration Changes
Some menus will require you to press <Ctrl-I> to insert a new record of information and <Ctrl- L> to delete a record. ROS® v3.11User Guide RMC30...
Page 13: Updates Occur In Real Time
Some files may be overwritten by uploading a file of the same name to the switch, as would be done in order to upgrade the firmware. The implemented commands are: dir/ls list directory contents download a file from the switch upload a file to the switch ROS® v3.11User Guide RMC30...
Page 14: The Ros® Web Server Interface
Enter the “admin” user name and the password for the admin user, and then click the “LogIn” button. The switch is shipped with a default administrator password of “admin”. After successfully logging in, the main menu appears. ROS® v3.11User Guide RMC30...
Page 15: Customizing The Login Page
• The System Name, as configured in the System Identification menu, is displayed in the top banner, in between elements of the RuggedCom logo. • A “Log out” link at left and immediately below the banner, terminates the current web session.
Page 16: Making Configuration Changes
1.4. Security Recommendations To prevent unauthorized access to the device, note the following security recommendations: • Do not connect the RMC30 directly to the Internet. The device should be protected by appropriate security appliances. • Replace the default passwords for the standard admin, operator and guest profiles before the device is deployed.
Page 17: Ip Interfaces
IP address while DHCP, BOOTP and Dynamic IP Address types refer to the automatic assignment of an IP address. DHCP is widely used in LAN environments to dynamically assign IP addresses from a centralized server, which reduces the overhead of administrating IP addresses. ROS® v3.11User Guide RMC30...
Page 18: Ip Gateways
These parameters provide the ability to configure gateways. A maximum of 10 gateways can be configured. When both the Destination and Subnet fields are both 0.0.0.0 (displayed as blank space), the gateway is a default gateway. ROS® v3.11User Guide RMC30...
Page 19: Ip Services
The default gateway configuration will not be changed when resetting all configuration parameters to defaults. 1.8. IP Services These parameters provide the ability to configure properties for IP services provided by the device. ROS® v3.11User Guide RMC30...
Page 20: Ip Services Form
GET ONLY - only allows reading of files via TFTP Server ENABLED - allows reading and writing of files via TFTP Server ModBus Address Synopsis: 1 to 254 or { Disabled } Default: Disabled Determines the Modbus address to be used for Management through Modbus. ROS® v3.11User Guide RMC30...
Page 21: System Identification
The contact can be used to help identify the person responsible for managing the switch. You can enter name, phone number, email, etc. It is displayed in the login screen so that this person may be contacted, should help be required. ROS® v3.11User Guide RMC30...
Page 22: Passwords
Sub123 and Sub19826 are permitted, but Sub12345 is not. An alarm will generate if a weak password is configured. The weak password alarm can be disabled by user. For more information about disabling alarms, refer to Section 4.1.4, “Configuring Alarms”. ROS® v3.11User Guide RMC30...
Page 23: Passwords Form
Related password is in the Guest Password field; view only, cannot change settings or run any commands. Guest Password Synopsis: 15 character ASCII string Default: guest Related user name is in the Guest Username field; view only, cannot change settings or run any commands. ROS® v3.11User Guide RMC30...
Page 24: System Time Management
Default: None Confirm the input of the above Admin Password. 1.11. System Time Management ROS® running on the RMC30 offers the following time-keeping and time synchronization features: • Local hardware time keeping and time zone management • SNTP time synchronization 1.11.1.
Page 25: Configuring Time And Date
UTC-10:00 (Hawaii), UTC-9:00 (Alaska), UTC-8:00 (Los Angeles, Vancouver), UTC-7:00 (Calgary, Denver), UTC-6:00 (Chicago, Mexico City), UTC-5:00 (New York, Toronto), UTC-4:00 (Caracas, Santiago), UTC-3:30 (Newfoundland), UTC-3:00 (Brasilia, Buenos Aires), UTC-2:00 (Mid Atlantic), UTC-1:00 (Azores), UTC-0:00 (Lisbon, London), UTC+1:00 (Berlin, Paris, Rome), ROS® v3.11User Guide RMC30...
Page 26 Bulletin-C message is sent out, which reports whether or not to add a leap second in the end of June and December. Please note that change in the Current UTC Offset parameter will result in a temporary disruption in the timing network. ROS® v3.11User Guide RMC30...
Page 27: Configuring Ntp Service
This setting determines how frequently the (S)NTP server is polled for a time update. If the server cannot be reached, three attempts are made at one-minute intervals and then an alarm is generated, at which point the programmed rate is resumed. ROS® v3.11User Guide RMC30...
Page 28: Snmp Management
SNMPv1 and SNMPv2c. Note that when employing the SNMPv1 or SNMPv2c security level, the User Name maps the community name with the security group and access level. Up to 32 entries can be configured. Figure 1.15. SNMP User Table ROS® v3.11User Guide RMC30...
Page 29: Snmp User Form
Default: noAuth An indication of whether messages sent on behalf of this user to/from SNMP engine, can be authenticated, and if so, the type of authentication protocol which is used. Priv Protocol Synopsis: { noPriv, CBC-DES } ROS® v3.11User Guide RMC30...
Page 30: Snmp Security To Group Maps
Entries in this table map configuration of security model and security name (user) into a group name, which is used to define an access control policy. Up to 32 entries can be configured. Figure 1.17. SNMP Security to Group Maps Table ROS® v3.11User Guide RMC30...
Page 31: Snmp Access
View names are predefined: • noView - access is not allowed • V1Mib - SNMPv3 MIBs excluded • allOfMibs - all supported MIBs are included. ROS® v3.11User Guide RMC30...
Page 32: Snmp Access Table
The minimum level of security required in order to gain the access rights allowed by this entry. A security level of noAuthNoPriv is less than authNoPriv, which is less than authPriv. ReadViewName Synopsis: { noView, V1Mib, allOfMib } Default: noView ROS® v3.11User Guide RMC30...
Page 33: Radius
HMI via Serial Console, Telnet, SSH, RSH, Web Server (see Password Configuration). ROS® implements a RADIUS client which uses the Password Authentication Protocol (PAP) to verify access. Attributes sent to a RADIUS server are: ROS® v3.11User Guide RMC30...
Page 34 • user password • service type: Login • vendor specific, currently defined as the following: vendor ID: RuggedCom Inc. enterprise number (15004) assigned by the Internet Assigned Numbers Authority (IANA) string, sub-attribute containing specific values: subtype: 1 (vendor's name subtype) length: 11 (total length of sub-attribute of subtype 1) ASCII string “RuggedCom”...
Page 35: Radius Server Configuration
1. Administration 1.13.3. Radius Server Configuration Figure 1.21. RADIUS Server Summary Figure 1.22. RADIUS Server Form Server Synopsis: Any 8 characters Default: Primary This field tells whether this configuration is for a primary or a backup server ROS® v3.11User Guide RMC30...
Page 36: Tacacs
It is based on, but is not compatible with, the older TACACS protocol. TACACS+ has generally replaced its predecessor in more recently built or updated networks, although TACACS and XTACACS are still used on many older networks. Note that RuggedCom's TACACS+ client implementation always has encryption enabled.
Page 37: Tacacs+ Server Configuration
1. Administration 1.14.2. TACACS+ Server Configuration Figure 1.23. TACACS+ Server Summary Figure 1.24. TACACS+ Server Form Server Synopsis: Any 8 characters Default: Primary This field indicates whether this configuration is for a primary or a backup server. ROS® v3.11User Guide RMC30...
Page 38: User Privilge Level Configuartion
You can also configure a different non-default access level for admin, operator or guest users. If an access level is not received in the response packet from the server, access is not be granted to the user. 1.14.4. TACACS+ Server Privilege Configuration Figure 1.25. TACACS+ Server Privilege Form ROS® v3.11User Guide RMC30...
Page 39: Syslog
The local syslog configuration enables users to control what level of syslog information will be logged. Only messages of a severity level equal to or greater than the configured severity level are written to the syslog.txt file in the unit. ROS® v3.11User Guide RMC30...
Page 40: Configuring Remote Syslog Client
1.15.2. Configuring Remote Syslog Client Figure 1.27. Remote Syslog Client Form UDP Port Synopsis: 1025 to 65535 or { 514 } Default: 514 The local UDP port through which the client sends information to the server(s). ROS® v3.11User Guide RMC30...
Page 41: Configuring The Remote Syslog Server
Syslog server IP Address. UDP Port Synopsis: 1025 to 65535 or { 514 } Default: 514 The UDP port number on which the remote server listens. Facility Synopsis: { USER, LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7 } ROS® v3.11User Guide RMC30...
Page 42: Troubleshooting
10.0.0.1 will cause the switch to forward unresolvable frames to the router. This problem will also occur if the gateway address is not configured and the switch tries to raise an SNMP trap to a host that is not on the local subnet. ROS® v3.11User Guide RMC30...
Page 43: Serial Protocols
2. Serial Protocols 2. Serial Protocols RuggedCom devices support the following serial protocols: • Raw Socket serial encapsulation • Preemptive Raw Socket • TCPModbus (client and server modes) • DNP 3 • DNP packetization over Raw Socket • Microlok • WIN and TIN •...
Page 44: Preemptive Raw Socket Protocol Features
• CRC checking for messages received from the serial port. • Remote source address learning, specific for two different modes. 2.1.9. TelnetComPort protocol features • RawSocket protocol with additional support for the serial break signal. • Compliant with RFC2217. ROS® v3.11User Guide RMC30...
Page 45: Serial Protocols Operation
(e.g. RawSocket) that can be made to be (partly) compatible. Host equipment may connect directly to a RuggedServer™ via a serial port, may use a port redirection package, or may connect natively to the (Ethernet / IP) network. Figure 2.2. RTU Polling ROS® v3.11User Guide RMC30...
Page 46: Broadcast Rtu Polling
The host sequentially polls each RTU. Each poll received by the host server is forwarded (i.e. broadcast) to all of the remote servers. All RTUs receive the request and the appropriate RTU issues a reply. The reply is returned to the host server, where it is forwarded to the host. ROS® v3.11User Guide RMC30...
Page 47: Preemptive Raw Socket
RTUs will point to that Raw Socket as a permanent master (IP address and Remote IP port). A dynamic master can establish a connection to any Preemptive Raw Socket port at any time and temporarily suspend the polling process (until the dynamic connection is cleared or times out). ROS® v3.11User Guide RMC30...
Page 48: Use Of Port Redirectors
OS to prevent the problem or increasing the packetizing timer. Finally, the server will always packetize and forward on a specific packet size, i.e. when the number of characters received from the serial port reaches a configured value. ROS® v3.11User Guide RMC30...
Page 49: Modbus Server And Client Applications
The following figure presents a complex network of Client Gateways, Server Gateways and native TCPModbus devices. Figure 2.5. Modbus Client and Server 2.2.2.1. TCPModbus Performance Determinants The following description provides some insight into the possible sources of delay and error in an end-to-end TCPModbus exchange. ROS® v3.11User Guide RMC30...
Page 50: Sources Of Delay And Error In An End-To-End Exchange
Server Gateway receives the RTU response in error. The Server Gateway will issue an exception to the originator. If sending exceptions has not been enabled, the Server Gateway will not send any response. ROS® v3.11User Guide RMC30...
Page 51: A Worked Example
Each device supporting one of these protocols must have a unique address within the collection of devices sending and receiving messages to and from each other. ROS® v3.11User Guide RMC30...
Page 52: The Concept Of Links
For each link, a statistical record will be available to the user if link statistics collection is enabled in the protocol configuration. 2.2.3.2. Address Learning 2.2.3.2.1. Address Learning for TIN Address learning is implemented for the TIN protocol and learned entries are viewable in the Dynamic Device Address Table. ROS® v3.11User Guide RMC30...
Page 53: Address Learning For Dnp
The aging timer is reset whenever a message is received or sent to the specified address. This concept makes the DNP protocol configurable with the minimum number of parameters: an IP port, a learning IP interface and an aging timer. ROS® v3.11User Guide RMC30...
Page 54: Broadcast Messages
UDP port to which the remote hosts are transmitting. Data received from the serial port will be forwarded to all remote hosts configured to communicate with that serial port. ROS® v3.11User Guide RMC30...
Page 55: Transport For Protocols With Defined Links
2.2.4. Force Half-Duplex Mode of Operation A "force half-duplex" mode of operation allows use of extensions that create echo loops (as optical loop topology that utilizes the RMC20 repeat mode function). Figure 2.8. Optical Loop Topology ROS® v3.11User Guide RMC30...
Page 56: Serial Protocol Configuration
This topology can be used for RS232, RS485, or RS422 multi-drop networks. In all cases, all slaves have the repeat function (DIP position 4) ON, while the one connected to the RMC30 is configured with the repeat function OFF. The port used on the RMC30 must be in full-duplex mode, while the ForceHD (Force Half-Duplex) parameter must be turned ON.
Page 57: Serial Ports
Figure 2.10. Serial Port Table Figure 2.11. Serial Port Configuration Form Port Synopsis: 1 to maximum port number Default: 1 The port number as seen on the front plate silkscreen of the switch. Name Synopsis: Any 15 characters ROS® v3.11User Guide RMC30...
Page 58 For Modbus protocol this value must be non-zero. It represents the delay between sending a brodcast message and the next poll out of the serial port. Because RTUs do not reply to a broadcast, enough time must be ensured to process it. ROS® v3.11User Guide RMC30...
Page 59: Raw Socket
It provides the connected device with time to turn off its transmitter and to turn on its receiver, helping to ensure that the device receives the next message without data loss. 2.3.2. Raw Socket Figure 2.12. Raw Socket Table ROS® v3.11User Guide RMC30...
Page 60: Raw Socket Form
Synopsis: 64 to 1400 or { Maximum } Default: Maximum The maximum number of bytes received from the serial port to be forwarded. Flow Control Synopsis: { None, XON/XOFF } Default: None The Flowcontrol setting for serial port. ROS® v3.11User Guide RMC30...
Page 61 UDP, the remote port is configured using the "Remote Hosts" table. For more information, see the Remote Hosts section. Link Stats Synopsis: { Disabled, Enabled } Default: Enabled Enables link statistics collection for the protocol. ROS® v3.11User Guide RMC30...
Page 62: Remote Hosts
The IP port that remote host listens to. If this is zero (Unknown), the unit only receives from the remote host but does not transmit to it. Port(s) Synopsis: Any combination of numbers valid for this parameter Default: All The local serial ports that the remote host is allowed to communicate with. ROS® v3.11User Guide RMC30...
Page 63: Preemptive Raw Socket
2. Serial Protocols 2.3.4. Preemptive Raw Socket Figure 2.16. Preemptive Raw Socket Table Figure 2.17. Preemptive Raw Socket Form Port Synopsis: 1 to 4 ROS® v3.11User Guide RMC30...
Page 64 The character that can be used to force the forwarding of accumulated data to the network for connection to a dynamic master. If a packetization character is not configured, accumulated data will be forwarded based upon the packetization timeout parameter. Dyn Pack Timer Synopsis: 3 to 1000 Default: 10 ms ROS® v3.11User Guide RMC30...
Page 65: Modbus Server
The protocol listens to the socket open to the dynamic master, and if no data are received within this time, the connection will be closed. 2.3.5. Modbus Server Figure 2.18. Modbus Server Table Figure 2.19. Modbus Server Form Port Synopsis: 1 to maximum port number ROS® v3.11User Guide RMC30...
Page 66: Modbus Client
RTU within expected time. Link Stats Synopsis: { Disabled, Enabled } Default: Enabled Enables link statistics collection for this protocol. 2.3.6. Modbus Client Figure 2.20. Modbus Client Form IP Port Synopsis: 1 to 65535 Default: 502 ROS® v3.11User Guide RMC30...
Page 67: Win And Tin
DSCP Synopsis: 0 to 63 Default: 0 To set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.7. WIN and TIN Figure 2.21. WIN and TIN Form ROS® v3.11User Guide RMC30...
Page 68 Broadcast Addresses Synopsis: { Static, Dynamic, StaticAndDynamic } Default: Static The device address table in which addresses will be found for broadcast messages. Unicast Addresses Synopsis: { Static, Dynamic, StaticAndDynamic } Default: Dynamic ROS® v3.11User Guide RMC30...
Page 69: Microlok
To set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.8. MicroLok Figure 2.22. MicroLok Form Transport Synopsis: { TCP, UDP } Default: UDP The network transport used to transport protocol data over an IP network. IP Port Synopsis: 1024 to 65535 Default: 60000 ROS® v3.11User Guide RMC30...
Page 70: Dnp
The network transport used to transport protocol data over an IP network. IP Port Synopsis: 1024 to 65535 Default: 20000 A local port number on which the DNP protocol listens for UDP datagrams. Remote UDP Port Synopsis: { IP Port, Learn } ROS® v3.11User Guide RMC30...
Page 71: Dnp Over Raw Socket
Synopsis: 0 to 63 Default: 0 To set the DS byte in the IP header. DS byte setting is supported in the egress direction only. 2.3.10. DNP over Raw Socket Figure 2.24. DNP over Raw Socket Table ROS® v3.11User Guide RMC30...
Page 72: Dnp Over Raw Socket Form
Synopsis: 1 to 64 Default: 1 The maximum number of allowed incoming TCP connections. Loc Port Synopsis: 1 to 65535 Default: 21001 The local IP port to use when listening for an incoming connection or UDP data. ROS® v3.11User Guide RMC30...
Page 73: Mirrored Bits
• For UDP transport, this is the IP address of the interface to listen to for UDP datagrams. Link Stats Synopsis: { Disabled, Enabled } Default: Enabled Enables links statistics collection for the protocol. 2.3.11. Mirrored Bits Figure 2.26. Mirrored Bits Table ROS® v3.11User Guide RMC30...
Page 74: Mirrored Bits Form
For an outgoing TCP connection (client) and UDP transport, this is the remote IP address to communicate with. For an incoming TCP connection (server), the local interface IP address on which to listen for connection requests. An empty string implies the default: the IP address of the management interface. ROS® v3.11User Guide RMC30...
Page 75: Telnetcomport
Figure 2.28. TelnetComPort Form Port Synopsis: 1 to maximum port number Default: 1 The serial port number as seen on the front plate silkscreen of the RuggedServer. Pack Char Synopsis: 0 to 255 or { Off } Default: Off ROS® v3.11User Guide RMC30...
Page 76 For direction 'BOTH' (client or server), remote IP address to use when placing an outgoing TCP connection requestListening interface will be chosen by matching mask. This parameter is applicable only to TCP connections. If the transport protocol is set to ROS® v3.11User Guide RMC30...
Page 77: Device Addresses
Synopsis: { Disabled, Enabled } Default: Enabled Enables links statistics collection for this protocol. 2.3.13. Device Addresses Up to 1024 entries can be created in this table. Figure 2.29. Device Address Table Figure 2.30. Device Address Form ROS® v3.11User Guide RMC30...
Page 78: Dynamic Device Addresses
Address Synopsis: Any 31 characters Default: The complete address of a device, which might be either local to the RuggedCom device or remote. A local address is one associated with a device connected to a serial port on this device.
Page 79: Dynamic Device Address Table
The IP Address of the remote host. IP Port Synopsis: 1 to 65535 The remote port number from which a UDP datagram was received from a remote device, or from which a TCP connection was established. ROS® v3.11User Guide RMC30...
Page 80: Serial Statistics
Aging Timer setting for the protocol, the device will be removed from the table. This value is updated every 10 seconds. 2.4. Serial Statistics 2.4.1. Link Statistics This table presents detailed statistics for serial links between two devices. Figure 2.33. Link Statistics Table Figure 2.34. Link Statistics Form ROS® v3.11User Guide RMC30...
Page 81: Connection Statistics
2.4.2. Connection Statistics This table presents statistics for all active TCP connections on serial protocols. The statistics are updated once every second. Figure 2.35. Connection Statistics Table Remote IP Synopsis: ###.###.###.### where ### ranges from 0 to 255 ROS® v3.11User Guide RMC30...
Page 82: Serial Port Statistics
The port number as seen on the front plate silkscreen of the switch. Protocol Synopsis: Any 15 characters The serial protocol supported on this serial port. Rx Chars Synopsis: 0 to 4294967295 The number of received characters. Tx Chars Synopsis: 0 to 4294967295 ROS® v3.11User Guide RMC30...
Page 83: Clearing Serial Port Statistics
Figure 2.37. Clear Serial Port Statistics Form This command clears statistics on one or more serial ports. To clear statistics for one or more ports, check the boxes corresponding to the selected ports and select "Apply". ROS® v3.11User Guide RMC30...
Page 84: Resetting Serial Ports
What is happening? Are framing, parity or overrun errors reported by either the client or server? Is the Server Gateway set up for the correct baud, parity and stop bits? Is the RTU online? ROS® v3.11User Guide RMC30...
Page 85 How do I get figures (like those presented earlier in the chapter) for my own analysis? Activating tracing at the IP level and serial port level. The trace package displays timestamps, packet sizes, message directions and timeout event occurrences. ROS® v3.11User Guide RMC30...
Page 86: Network Discovery
• Perform basic device configuration 3.1. RCDP Operation The purpose of the RuggedCom Discovery Protocol™ is to support the deployment of ROS®- based devices that have not been configured since leaving the factory. ROS® devices that have not been configured all have the default IP (Layer 3) address. Connecting more than one of them on a Layer 2 network means that one cannot use standard IP-based configuration tools to configure them.
Page 87: Rcdp Configuration
3. Network Discovery Figure 3.1. Network Discovery Main Menu 3.2.1. RCDP Configuration Figure 3.2. RCDP Parameters Form RCDP Discovery Synopsis: { Disabled, Enabled } Default: Enabled Disables/Enables Device Discovery through RuggedCom Proprietary RCDP. ROS® v3.11User Guide RMC30...
Page 88: Diagnostics
Examples of active alarms include links that should be up but are not or error rates that are continuously exceeding a certain threshold. Active alarms are removed (cleared) either by solving the original cause of the alarm or by explicitly clearing the alarm itself. ROS® v3.11User Guide RMC30...
Page 89: Passive Alarms
• Alarms cannot be added to or deleted from the system. • Alarm configuration settings changed by a user will be saved in the configuration file. • The "alarms" CLI command lists all alarms - configurable and non-configurable. ROS® v3.11User Guide RMC30...
Page 90: Alarm Configuration Table
4. Diagnostics Figure 4.2. Alarm Configuration Table Figure 4.3. Alarm Configuration Form Name Synopsis: Any 34 characters ROS® v3.11User Guide RMC30...
Page 91: Viewing And Clearing Alarms
Default: 60 s Refreshing time for this alarm. 4.1.5. Viewing and Clearing Alarms Alarms are displayed in the order in which they occurred, even if the real time clock was incorrect at the time of the alarm. ROS® v3.11User Guide RMC30...
Page 92: Viewing Cpu Diagnostics
Description of the alarm; gives details about the frequency of the alarm if it has occurred again since the last clear. Alarms can be cleared from the Clear Alarms option. 4.2. Viewing CPU Diagnostics Figure 4.5. CPU Diagnostics Form ROS® v3.11User Guide RMC30...
Page 93: Viewing And Clearing The System Log
Synopsis: 0 to 4294967295 Free Rx Buffers. Free Tx Bufs Synopsis: 0 to 4294967295 Free Tx Buffers. 4.3. Viewing and Clearing the System Log The system log records various events including reboots, user sign-ins, alarms and configuration saves. ROS® v3.11User Guide RMC30...
Page 94: Viewing Product Information
The Clear System Log option will clear the system log. Clearing the log is recommended after a firmware upgrade. 4.4. Viewing Product Information Figure 4.7. Product Information Form MAC Address Synopsis: ##-##-##-##-##-## where ## ranges 0 to FF Shows the unique MAC address of the device. ROS® v3.11User Guide RMC30...
Page 95: Loading Factory Default Configuration
Shows the version and build date of the main operating system software. Hardware ID Synopsis: { RSMCPU (40-00-0008 Rev B1), RSMCPU2 (40-00-0026 Rev A1), RS400 (40-00-0010 Rev B2), RMC30, RS900 (40-00-0025 Rev B1), RS900 (40-00-0032 Rev B1), RS1600M, RS400 (40-00-0010 Rev C1), RSG2100, RS900G, RSG2200, RS969, RS900 (v2, 40-00-0066),...
Page 96: Resetting The Device
“sql” command. Please refer to the section entitled: “Upgrading Firmware and Managing Configurations”. 4.6. Resetting the Device This operation will warm-start the device after the user has confirmed the reset operation from the Reset Device option. Figure 4.9. Reset Device Dialog ROS® v3.11User Guide RMC30...
Page 97: Transferring Files
The path and name of the file on your local PC. Use the Browse button to locate the file. Device File The name of the file on the device. TFTP Server IP Address The IP address of a TFTP server. A TFTP server application must be installed on your local PC. ROS® v3.11User Guide RMC30...
Page 98: Using The Cli Shell
Figure 5.1. Displaying Help For A Command 5.3. Viewing Files RuggedCom devices maintain a number of volatile and non-volatile files. These files can aid in the resolution of problems and serve as a useful gauge of the device’s health. ROS® v3.11User Guide...
Page 99: Listing Files
Syslog.txt file will accumulate information until it fills, holding approximately 3 megabytes of characters. The “clearlogs” command resets these logs. It is recommended to run “clearlogs” command after every firmware upgrade. ROS® v3.11User Guide RMC30...
Page 100: Managing The Flash Filesystem
5.4.2. Obtaining Information On A Particular File When the flashfiles command is invoked with the key word, info, followed by the name of a file in memory as arguments, detailed information is displayed for the named file. For example: ROS® v3.11User Guide RMC30...
Page 101: Defragmenting The Flash Filesystem
ARP request for the MAC address of the device is issued. If the device to be pinged is not on the same network as the device pinging the other device, the default gateway must be programmed. ROS® v3.11User Guide RMC30...
Page 102: Tracing Events
Figure 5.6. Displaying Trace Settings 5.6.1. Enabling Trace Tracing can be enabled on a per subsystem basis. Obtain detailed information about individual subsystems by entering “trace subsystem_name ?<CR>”. Some subsystems offer a mechanism to enable tracing only on certain ports. ROS® v3.11User Guide RMC30...
Page 103: Starting Trace
0.00, maxage 20, hello 2, fwddelay 15 V1Length 0 Figure 5.8. Starting Trace The trace package includes the “forward” subsystem, a remote reporting facility intended to be used only under the direction of RuggedCom service personnel. ROS® v3.11User Guide RMC30...
Page 104: Viewing Dhcp Learned Information
–l auth_token command_string where: • ipaddr = The address or resolved name of the RuggedCom device. • auth_token = The authentication token, which for ROS® rsh is the user name (guest, operator, or admin) and corresponding password separated by a comma. For example, to run a command as user - "admin"...
Page 105: Firmware Upgrade And Configuration Management
Upgrading ROS® firmware may sometimes be necessary in order to take advantage of new features or bug fixes. In normal circumstances, only the main ROS® application firmware is updated; the boot loader and FPGA firmware remain invariant. The main ROS® application ROS® v3.11User Guide RMC30...
Page 106: Applying The Upgrade
6. Firmware Upgrade and Configuration Management firmware image is a binary file available from RuggedCom. Please check the RuggedCom web site, www.RuggedCom.com, for the availability of updates to ROS® firmware or contact RuggedCom support. Firmware upgrades may be performed using any of the transfer methods and protocols listed Section 6.2, “File Transfer...
Page 107: Upgrading Firmware Using The Ros® Tftp Server
Establish a console connection with administrative privileges to the ROS® device to be upgraded (i.e. via RS232, telnet, or SSH). Enter the CLI shell and run the TFTP client command to receive the firmware image, for example: ROS® v3.11User Guide RMC30...
Page 108: Upgrading Firmware Using Sftp
Configuration files from different units may be compared using standard text processing tools. The transfer mechanisms supported for the update of config.csv are the same as for ROS® firmware image files: ROS® v3.11User Guide RMC30...
Page 109: Backing Up Ros®System Files
An example of backing up a file using SFTP follows. For descriptions on the use of the other file transfer mechanisms, please refer to the examples in Section 6.4, “Upgrading Firmware”. Note that only the direction of file transfer changes. ROS® v3.11User Guide RMC30...
Page 110: Backing Up Files Using Sftp
Allows for existing records in a table to be updated. 6.7.2. Finding the Correct Table Many SQL commands operate upon specific tables in the database, and require the table name to be specified. Navigating the menu system to the desired menu and pressing <Ctrl- ROS® v3.11User Guide RMC30...
Page 111: Retrieving Information
Addition of "where" clause to the "select" statement will limit the results returned. For example, suppose that it is desirable to identify all ports on the device operating in Auto Select mode: ROS® v3.11User Guide RMC30...
Page 112: Changing Values In A Table
/F %i in (devices) do rsh %i -l admin,admin sql select from ethportcfg where flow_control = disabled C:\>rsh 10.0.1.1 -l admin,admin sql select from ethportcfg where flow_control = disabled Port Name Status Media Type Flow Control FEFI Link Alarms ROS® v3.11User Guide RMC30...
Page 113 Link Alarms Port 3 Enabled Auto Select Disabled Disabled Enabled Port 7 Enabled Auto Select Disabled Disabled Enabled Port 8 Enabled Auto Select Disabled Disabled Enabled Port 13 Enabled Auto Select Disabled Disabled Enabled 4 records selected ROS® v3.11User Guide RMC30...
Page 114: Snmp Mib Support
Management Information Base Module for LLDP Configuration, Statistics, Local System Data and Remote Systems Data Components RFC 4363 Q-BRIDGE-MIB Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions Table A.1. Standard MIBs ROS® v3.11User Guide RMC30...
Page 115: Ruggedcom Proprietary Mibs
When this table is retrieved by an NMS, all Agent Capabilities supported by devices (sysORID object) and their descriptions (sysORDescr) are retrieved. These Agent Capabilities and descriptions are defined in RuggedCom Agent Capabilities MIBs. Each supported MIB is accompanied with Agent Capabilities MIBs. Agent Capabilites list supported MIBs, supported groups of objects in them, and possible variations for particular objects.
Page 116 The following is an example from an RS416 device that describes the way to find objects and variations for supported MIBs: RS416 running ROS®-CF52 Main v3.11 supports “ruggecomRcTrapsAC01”. RC-RUGGEDCOM-TRAPS-MIB-AC defines “ruggecomRcTrapsAC01” support for the following groups from RUGGEDCOM-TRAPS-MIB: ruggedcomGenericTrapGroup, ruggedcomPowerSupplyGroup,...
Page 117 42.20.41.67.65.6E.74.20.43.61.70.61.62.69.6C.69.74.69.65.73.2E (hex)] 27: sysORDescr.7 (DisplayString) UDP-MIB Agent Capabilities. [55.44.50.2D.4D.49. 42.20.41.67.65.6E.74.20.43.61.70.61.62.69.6C.69.74.69.65.73.2E (hex)]28: sysORDescr.8 (DisplayString) IP-MIB Agent Capabilities. [49.50.2D.4D.49.42.20.41. 67.65.6E.74.20.43.61.70.61.62.69.6C.69.74.69.65.73.2E (hex)] 29: sysORDescr.9 (DisplayString) RUGGEDCOM-IP-MIB Agent Capabilities. [52.55. 47.47.45.44.43.4F.4D.2D.49.50.2D.4D.49.42.20.41.67.65.6E.74.20.43.61.70.61.62. 69.6C.69.74.69.65.73.2E (hex)] 30: sysORDescr.10 (DisplayString) RUGGEDCOM-TRAPS-MIB Agent Capabilities 01. [52.55.47.47.45.44.43.4F.4D.2D.54.52.41.50.53.2D.4D.49.42.20.41.67.65.6E.74.20. 43.61.70.61.62.69.6C.69.74.69.65.73.20.30.31.2E (hex)] 31: sysORDescr.11 (DisplayString) RUGGEDCOM-SYS-INFO-MIB Agent Capabilities 01.
Page 118 Appendix A. SNMP MIB Support [52.55.47.47.45.44.43.4F.4D.2D.53.45.52.49.41.4C.2D.4D.49.42.20.41.67.65.6E. 74.20.43.61.70.61.62.69.6C.69.74.69.65.73.2E (hex)] Notice the sysORID.10 object value. The sysORTable will describe precisely which MIB and which parts of the MIB are supported by the device. ROS® v3.11User Guide RMC30...
Page 119: Snmp Trap Summary
Generic Traps carry information about event in severity and description objects. They are sent at the time that an alarm is generated for the device. The following are examples of RuggedCom Generic Traps, along with the severity of each one in brackets: • heap error (alert) •...
Page 120: List Of Objects Eligible For Rmon Alarms
The total number of received packets that were between 512 and 1023 bytes long. etherStatsPkts64Octets The total number of received packets that were 64 bytes long. etherStatsPkts65to127Octets The total number of received packets that were between 65 and 127 bytes long. ROS® v3.11User Guide RMC30...
Page 121 The total number of transmitted packets which were not addressed to a multicast or broadcast address. This object is a 64 bit version of ifOutUcastPkts. ifOutUcastPkts The total number of transmitted packets which were not addressed to a multicast or broadcast address. ROS® v3.11User Guide RMC30...
Page 122 (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams. ipRasmReqds The number of IP fragments received which needed to be reassembled at this entity. ipReasmFails The number of IP datagrams successfully reassembled. ROS® v3.11User Guide RMC30...
Page 123 The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. tcpAttemptFails The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT or the SYN-RCVD, ROS® v3.11User Guide RMC30...
Page 124 The total number of received UDP datagrams for which there was no application at the destination port. udpOutDatagrams The number of sent UDP datagrams. ROS® v3.11User Guide RMC30...
Page 125: Modbus Management Support And Memory Map
Starting Address 2 Bytes 0x0000 to 0xFFFF Number of Registers 2 Bytes 1 to 121 (0x79) Note that as RuggedCom devices have a variable number of ports, not all registers and bits apply to all products. ROS® v3.11User Guide RMC30...
Page 126: Modbus Memory Map
Registers that are not applicable to a particular product return a zero value. For example, registers referring to serial ports are not applicable to RuggedSwitch® products. No Ethernet port statistics are available for the Ethernet port on RMC30. D.1. Modbus Memory Map...
Page 127 Port 20 Statistics - Ethernet Out Packets R Uint32 0480 Port 1 Statistics - Ethernet In Octets Uint32 0482 Port 2 Statistics - Ethernet In Octets Uint32 0484 Port 3 Statistics - Ethernet In Octets Uint32 ROS® v3.11User Guide RMC30...
Page 128 Port 18 Statistics - Ethernet Out Octets R Uint32 04E4 Port 19 Statistics - Ethernet Out Octets R Uint32 04E6 Port 20 Statistics - Ethernet Out Octets R Uint32 SERIAL STATISTICS (table Name: uartPortStatus) 0600 Port 1 Statistics – Serial In characters Uint32 ROS® v3.11User Guide RMC30...
Page 129: Text
This format instructs the device to set the output to either ‘true’ or ‘false’. The most significant byte comes first. • FF 00 hex requests output to be True. • 00 00 hex requests output to be False. • Any value other than the suggested values does not affect the requested operation. ROS® v3.11User Guide RMC30...
Page 130: Uint16
0xFE 0x00 0x02 The response depends on how many ports are available on the device. For example, if the maximum number of ports on a connected RuggedCom device is 20, the response would look like the following: 0x04 0x04 0xF2...
Page 131: Alarm
Similar to the ‘Text’ format, this format returns ASCII representation of alarms. Note that alarms are stacked in the RuggedCom device in the sequence of their occurrence. That is, the first alarm on the stack is Alarm 1, the next latched alarm in the device is Alarm 2, and so on.
Page 132: Truthvalue
0x04 0x00 0x45 0x00 0x01 Response may look like: 0x04 0x02 0x00 0x01 The register’s lower byte shows the alarm status. In this example, there is no active ERROR, ALERT or CRITICAL alarm in the device. ROS® v3.11User Guide RMC30...
Page 133: Command Line Listing
If no command is specified, a list of all available commands is displayed along with a brief description of each one. ipconfig Displays IP configuration loaddflts Load Factory Default Configuration. login Login to the shell i.e. set the access level logout Logout of the shell ROS® v3.11User Guide RMC30...
Page 134 Enter 'dir' for a directory listing of files. type filename version Prints software versions xmodem xmodem direction filename direction: send - send file to client receive - receive file from client filename: Enter 'dir' for list of all filenames ROS® v3.11User Guide RMC30...
Page 135: Security Messages For Authentication
Login attempts are logged regardless of how the user accesses the device (i.e. SSH, Web, Console, Telnet or RSH). However, when a user logs out, a message is only logged when the user is accessing the device through SSH, Telnet or Console. Message Name Alarm SNMP Trap Syslog Successful Login ROS® v3.11User Guide RMC30...
Page 136 Table F.6. Configurable Options SNMP Authentication Failure ROS® generates this alarm, sends an authentication failure trap, and logs a message in the syslog when an SNMP manager with incorrect credentials communicates with the SNMP agent in ROS®. ROS® v3.11User Guide RMC30...
Page 137: Security Messages For Port Authentication
MAC-Auth" ROS® this alarm and logs a message in the syslog when the host connected to a secure port tries to communicate using incorrect login credentials. Message Name Alarm SNMP Trap Syslog 802.1x Port Authentication Failure ROS® v3.11User Guide RMC30...
Page 138 Appendix F. Security Messages for Authentication Message Name Alarm SNMP Trap Syslog 802.1x Port X Authorized Addr. XXX Table F.10. Configurable Options ROS® v3.11User Guide RMC30...

RuggedCom RMC30 User Manual

1 Administration

2 Serial Protocols

3 Network Discovery

4 Diagnostics

5 Using the CLI Shell

6 Firmware Upgrade and Configuration Management

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for RuggedCom RMC30

Summary of Contents for RuggedCom RMC30

Table of Contents