RuggedCom RMC30 User Manual

Rugged Operating System

(ROS®) v3.11 User Guide

For use with :

RMC30

July 19, 2012

www.RuggedCom.com

Rugged Operating System

Rugged Operating System: (ROS®) v3.11 User Guide

Copyright © 2012 RuggedCom Inc.

ALL RIGHTS RESERVED

Dissemination or reproduction of this document, or evaluation and communication of its contents, is not authorized except where
expressly permitted. Violations are liable for damages. All rights reserved, particularly for the purposes of patent application or
trademark registration.

This document contains proprietary information, which is protected by copyright. All rights are reserved. No part of this document may
be photocopied, reproduced or translated to another language without the prior written consent of RuggedCom Inc.

Disclaimer Of Liability

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.

The information given in this document is reviewed regularly and any necessary corrections will be included in subsequent editions.
We appreciate any suggested improvements. We reserve the right to make technical improvements without notice.

Registered Trademarks

RuggedServer™, RuggedWireless™, RuggedCom Discovery Protocol™ (RCDP™), RuggedExplorer™, Enhanced Rapid Spanning
Tree Protocol™ (eRSTP™), are trademarks of RuggedCom Inc. Rugged Operating System® (ROS®) and RuggedSwitch® are
registered trademarks of RuggedCom Inc. Other designations in this manual might be trademarks whose use by third parties for their
own purposes would infringe the rights of the owner.

Warranty

Five (5) years from date of purchase, return to factory. For warranty details, visit www.ruggedcom.com or contact your customer
service representative.

Contacting RuggedCom

Corporate Headquarters US Headquarters Europe Headquarters
RuggedCom Inc.

300 Applewood Crescent
Concord, Ontario
Canada, L4K 5C7
Tel: [phone]
Fax: [phone]
Toll-free: 1 888 264 0006

Technical Support
Toll Free (North America): 1 866 922 7975

International: [phone]
Email: [e-mail]

Web: www.RuggedCom.com

RuggedCom
1930 Harrison St., Suite 209
Hollywood, Florida
USA, 33020
Tel: [phone] ext. 103
Fax: [phone]
Toll-free: 1 888 264 0006

Email: [e-mail]

RuggedCom
Unit 41, Aztec Centre,
Aztec West, Almondsbury, Bristol
United Kingdom BS32 4TD
Tel: [phone]
Fax: [phone]

Rugged Operating System

Table of Contents

Preface ................................................................................................................................. 9

Supported Platforms ..................................................................................................... 9

Who Should Use This User Guide ............................................................................... 9

How Chapters are organized ....................................................................................... 9

Document Conventions ................................................................................................ 9

Applicable Firmware Revision .................................................................................... 10

Firmware/User Guide Version Numbering System ..................................................... 10

1. Administration ................................................................................................................. 11

1.1. The ROS® User Interface ................................................................................... 11

1.1.1. Using the RS232 Port to Access the User Interface ................................ 11

1.1.2. The Structure of the User Interface .......................................................... 11

1.1.3. Making Configuration Changes ................................................................ 12

1.1.4. Updates Occur In Real Time .................................................................... 13

1.1.5. Alarm Indications Are Provided ................................................................ 13

1.1.6. The CLI Shell ........................................................................................... 13

1.2. The ROS® Secure Shell Server ......................................................................... 13

1.2.1. Using a Secure Shell to Access the User Interface .................................. 13

1.2.2. Using a Secure Shell to Transfer Files ..................................................... 13

1.3. The ROS® Web Server Interface ....................................................................... 14

1.3.1. Using a Web Browser to Access the Web Interface ................................. 14

1.3.2. Customizing the Login Page .................................................................... 15

1.3.3. The Structure of the Web Interface .......................................................... 15

1.3.4. Making Configuration Changes ................................................................ 16

1.3.5. Updating Statistics Displays ..................................................................... 16

1.4. Security Recommendations ................................................................................. 16

1.5. Administration Menu ............................................................................................ 16

1.6. IP Interfaces ........................................................................................................ 17

1.7. IP Gateways ........................................................................................................ 18

1.8. IP Services .......................................................................................................... 19

1.9. System Identification ........................................................................................... 21

1.10. Passwords ......................................................................................................... 22

1.11. System Time Management ............................................................................... 24

1.11.1. Configuring System Time ....................................................................... 24

1.11.1.1. Configuring Time and Date .......................................................... 25

1.11.1.2. Configuring NTP Service ............................................................. 27

1.12. SNMP Management .......................................................................................... 28

1.12.1. SNMP Users ........................................................................................... 28

1.12.2. SNMP Security to Group Maps .............................................................. 30

1.12.3. SNMP Access ......................................................................................... 31

1.13. RADIUS ............................................................................................................. 33

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 3 RMC30

Rugged Operating System

1.14.3. User Privilge Level Configuartion ........................................................... 38

1.14.4. TACACS+ Server Privilege Configuration .............................................. 38

1.15. Syslog ................................................................................................................ 39

1.15.1. Configuring Local Syslog ........................................................................ 39

1.15.2. Configuring Remote Syslog Client .......................................................... 40

1.15.3. Configuring the Remote Syslog Server .................................................. 41

1.16. Troubleshooting ................................................................................................. 42

2. Serial Protocols .............................................................................................................. 43

2.1. Serial Protocols Overview ................................................................................... 43

2.1.1. Raw Socket protocol features .................................................................. 43

2.1.2. DNP over Raw Socket protocol features .................................................. 43

2.1.3. Preemptive Raw Socket protocol features ............................................... 44

2.1.4. Modbus protocol features ......................................................................... 44

2.1.5. DNP protocol features .............................................................................. 44

2.1.6. Microlok protocol features ........................................................................ 44

2.1.7. WIN protocol features ............................................................................... 44

2.1.8. TIN protocol features ................................................................................ 44

2.1.9. TelnetComPort protocol features .............................................................. 44

2.2. Serial Protocols Operation .................................................................................. 45

2.2.1. Serial Encapsulation Applications ............................................................. 45

2.2.1.1. Character Encapsulation (Raw Socket) ......................................... 45

2.2.1.2. RTU Polling ................................................................................... 45

2.2.1.3. Broadcast RTU Polling .................................................................. 46

2.2.1.4. Preemptive Raw Socket ................................................................ 47

2.2.1.5. Use of Port Redirectors ................................................................. 48

2.2.1.6. Message Packetization .................................................................. 48

2.2.2. Modbus Server and Client Applications .................................................... 49

2.2.2.1. TCPModbus Performance Determinants ....................................... 49

2.2.2.2. A Worked Example ........................................................................ 51

2.2.2.3. Use of Turnaround Delay .............................................................. 51

2.2.3. DNP 3.0, Microlok, TIN and WIN Applications ......................................... 51

2.2.3.1. The Concept of Links .................................................................... 52

2.2.3.2. Address Learning ........................................................................... 52

2.2.3.2.1. Address Learning for TIN .................................................... 52

2.2.3.2.2. Address Learning for DNP .................................................. 53

2.2.3.2.3. Broadcast Messages ........................................................... 54

2.2.3.3. Transport Protocols ........................................................................ 54

2.2.3.3.1. Transport for Raw Socket ................................................... 54

2.2.3.3.2. Transport for Protocols with Defined Links .......................... 55

2.2.3.3.3. Use of Differentiated Services Code Point (DSCP) ............. 55

2.2.4. Force Half-Duplex Mode of Operation ...................................................... 55

2.3. Serial Protocol Configuration ............................................................................... 56

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 4 RMC30

Rugged Operating System

2.3.8. MicroLok ................................................................................................... 69

2.3.9. DNP .......................................................................................................... 70

2.3.10. DNP over Raw Socket ........................................................................... 71

2.3.11. Mirrored Bits ........................................................................................... 73

2.3.12. TelnetComPort ........................................................................................ 75

2.3.13. Device Addresses ................................................................................... 77

2.3.14. Dynamic Device Addresses .................................................................... 78

2.4. Serial Statistics .................................................................................................... 80

2.4.1. Link Statistics ........................................................................................... 80

2.4.2. Connection Statistics ................................................................................ 81

2.4.3. Serial Port Statistics ................................................................................. 82

2.4.4. Clearing Serial Port Statistics ................................................................... 83

2.4.5. Resetting Serial Ports ............................................................................... 84

2.5. Troubleshooting ................................................................................................... 84

3. Network Discovery ......................................................................................................... 86

3.1. RCDP Operation ................................................................................................. 86

3.2. Network Discovery Menu .................................................................................... 86

3.2.1. RCDP Configuration ................................................................................. 87

4. Diagnostics ..................................................................................................................... 88

4.1. Using the Alarm System ..................................................................................... 88

4.1.1. Active Alarms ............................................................................................ 88

4.1.2. Passive Alarms ......................................................................................... 89

4.1.3. Alarms and the Critical Failure Relay ....................................................... 89

4.1.4. Configuring Alarms ................................................................................... 89

4.1.5. Viewing and Clearing Alarms ................................................................... 91

4.2. Viewing CPU Diagnostics ................................................................................... 92

4.3. Viewing and Clearing the System Log ................................................................ 93

4.4. Viewing Product Information ............................................................................... 94

4.5. Loading Factory Default Configuration ................................................................ 95

4.6. Resetting the Device ........................................................................................... 96

4.7. Transferring Files ................................................................................................ 97

5. Using the CLI Shell ........................................................................................................ 98

5.1. Summary Of CLI Commands available in ROS® ................................................ 98

5.2. Obtaining Help For A Command ......................................................................... 98

5.3. Viewing Files ....................................................................................................... 98

5.3.1. Listing Files .............................................................................................. 99

5.3.2. Viewing and Clearing Log Files ................................................................ 99

5.4. Managing The Flash Filesystem ....................................................................... 100

5.4.1. Flash Filesystem Memory Mapping ........................................................ 100

5.4.2. Obtaining Information On A Particular File ............................................. 100

5.4.3. Defragmenting The Flash Filesystem ..................................................... 101

5.5. Pinging a Remote Device ................................................................................. 101

5.6. Tracing Events .................................................................................................. 102

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 5 RMC30

Rugged Operating System

6.1. Files Of Interest ................................................................................................. 105

6.2. File Transfer Mechanisms ................................................................................. 105

6.3. Console Sessions .............................................................................................. 105

6.4. Upgrading Firmware .......................................................................................... 105

6.4.1. Applying the Upgrade ............................................................................. 106

6.4.2. Security Considerations .......................................................................... 106

6.4.3. Upgrading Firmware Using XModem ...................................................... 106

6.4.4. Upgrading Firmware Using the ROS® TFTP Server .............................. 107

6.4.5. Upgrading Firmware Using the ROS® TFTP Client ............................... 107

6.4.6. Upgrading Firmware Using SFTP ........................................................... 108

6.5. Updating Configuration ...................................................................................... 108

6.6. Backing Up ROS®System Files ........................................................................ 109

6.6.1. Backing Up Files Using SFTP ................................................................ 110

6.7. Using SQL Commands ..................................................................................... 110

6.7.1. Getting Started ....................................................................................... 110

6.7.2. Finding the Correct Table ....................................................................... 110

6.7.3. Retrieving Information ............................................................................. 111

6.7.4. Changing Values in a Table ................................................................... 112

6.7.5. Setting Default Values in a Table ........................................................... 112

6.7.6. Using RSH and SQL .............................................................................. 112

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. ModBus Management Support and Memory Map ....................................................... 125

D.1. Modbus Memory Map ....................................................................................... 126

D.1.1. Text ........................................................................................................ 129

D.1.2. Cmd ........................................................................................................ 129

D.1.3. Uint16 ..................................................................................................... 130

D.1.4. Uint32 ..................................................................................................... 130

D.1.5. PortCmd ................................................................................................. 130

D.1.6. Alarm ...................................................................................................... 131

D.1.7. PSStatusCmd ......................................................................................... 131

D.1.8. TruthValue .............................................................................................. 132

E. Command Line Listing ................................................................................................. 133

F. Security Messages for Authentication .......................................................................... 135

F.1. Security Messages for Login Authentication ..................................................... 135

F.2. Security Messages for Port Authentication ....................................................... 137

ROS® v3.11User Guide 6 RMC30

Rugged Operating System

List of Figures

1.1. Main Menu With Screen Elements Identified .............................................................. 12

1.2. The ROS® log in page ............................................................................................... 14

1.3. Main Menu via Web Server Interface ......................................................................... 15

1.4. Web Page Header Showing Alarms Link .................................................................... 15

1.5. Parameters Form Example ......................................................................................... 16

1.6. Administration Menu ................................................................................................... 17

1.7. IP Gateways Form ...................................................................................................... 19

1.8. IP Services Form ........................................................................................................ 20

1.9. System Identification Form ......................................................................................... 21

1.10. Passwords Form ....................................................................................................... 23

1.11. System Time Manager Menu .................................................................................... 25

1.12. Time and Date Form ................................................................................................. 25

1.13. NTP Server List ........................................................................................................ 27

1.14. NTP Server Form ...................................................................................................... 27

1.15. SNMP User Table ..................................................................................................... 28

1.16. SNMP User Form ..................................................................................................... 29

1.17. SNMP Security to Group Maps Table ....................................................................... 30

1.18. SNMP Security to Group Maps Form ....................................................................... 31

1.19. SNMP Access Table ................................................................................................. 32

1.20. SNMP Access Form .................................................................................................. 32

1.21. RADIUS Server Summary ......................................................................................... 35

1.22. RADIUS Server Form ............................................................................................... 35

1.23. TACACS+ Server Summary ..................................................................................... 37

1.24. TACACS+ Server Form ............................................................................................ 37

1.25. TACACS+ Server Privilege Form .............................................................................. 38

1.26. Local Syslog Form .................................................................................................... 40

1.27. Remote Syslog Client Form ...................................................................................... 40

1.28. Remote Syslog Server Table .................................................................................... 41

1.29. Remote Syslog Server Form .................................................................................... 41

1.30. Using A Router As A Gateway ................................................................................. 42

2.1. Character Encapsulation ............................................................................................. 45

2.2. RTU Polling ................................................................................................................. 45

2.3. Broadcast RTU Polling ................................................................................................ 46

2.4. Permanent and Dynamic Master Connection Support ................................................ 47

2.5. Modbus Client and Server .......................................................................................... 49

2.6. Sources of Delay and Error in an End-to-End Exchange ............................................ 50

2.7. Source/Destination Two-Way Communication ............................................................ 52

2.8. Optical Loop Topology ................................................................................................ 55

2.9. Serial Protocols Menu ................................................................................................. 56

2.10. Serial Port Table ....................................................................................................... 57

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 7 RMC30

Rugged Operating System

2.17. Preemptive Raw Socket Form .................................................................................. 63

2.18. Modbus Server Table ................................................................................................ 65

2.19. Modbus Server Form ................................................................................................ 65

2.20. Modbus Client Form .................................................................................................. 66

2.21. WIN and TIN Form ................................................................................................... 67

2.22. MicroLok Form .......................................................................................................... 69

2.23. DNP Form ................................................................................................................. 70

2.24. DNP over Raw Socket Table .................................................................................... 71

2.25. DNP over Raw Socket Form .................................................................................... 72

2.26. Mirrored Bits Table ................................................................................................... 73

2.27. Mirrored Bits Form .................................................................................................... 74

2.28. TelnetComPort Form ................................................................................................. 75

2.29. Device Address Table ............................................................................................... 77

2.30. Device Address Form ............................................................................................... 77

2.31. Dynamic Device Address Table ................................................................................ 79

2.32. Dynamic Device Address Form ................................................................................ 79

2.33. Link Statistics Table .................................................................................................. 80

2.34. Link Statistics Form ................................................................................................... 80

2.35. Connection Statistics Table ....................................................................................... 81

2.36. Serial Port Statistics Table ........................................................................................ 82

2.37. Clear Serial Port Statistics Form ............................................................................... 83

2.38. Reset Serial Port(s) Form ......................................................................................... 84

3.1. Network Discovery Main Menu ................................................................................... 87

3.2. RCDP Parameters Form ............................................................................................. 87

4.1. Diagnostics Menu ........................................................................................................ 88

4.2. Alarm Configuration Table .......................................................................................... 90

4.3. Alarm Configuration Form ........................................................................................... 90

4.4. Alarm Table ................................................................................................................. 92

4.5. CPU Diagnostics Form ............................................................................................... 92

4.6. Viewing the System Log ............................................................................................. 94

4.7. Product Information Form ........................................................................................... 94

4.8. Load Factory Defaults Dialog ..................................................................................... 96

4.9. Reset Device Dialog ................................................................................................... 96

4.10. Files Transfer Form ................................................................................................... 97

5.1. Displaying Help For A Command ............................................................................... 98

5.2. Displaying The Directory Of A ROS®Device .............................................................. 99

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 8 RMC30

Preface

Preface

This manual contains instructions, examples, guidelines, and general theory on how to use
the Rugged Operating System (ROS®) management software.

Supported Platforms

ROS® is designed to work on many RuggedCom product hardware platforms, ensuring
a consistent user experience when migrating from one product model to another. ROS®
supports the following RuggedCom products:

• RuggedSwitch® i800, i801, i802, and i803

• RuggedSwitch® RS8000 and RS1600

• RuggedSwitch® RS900/RS930 with both ‘L’ (EoVDSL) and ‘W’ (WLAN) port variants

• RuggedSwitch® RS900GP

• RuggedSwitch® RS900G/RS940G with Gigabit

• RuggedSwitch® RS950G

• RuggedSwitch® RS969/M969 waterproof with Gigabit

• RuggedSwitch® RSG2100/M2100, RSG2200/M2200, and RSG2300 modular switches with

Gigabit Ethernet

• RuggedSwitch® RSG2288 modular switch with Gigabit Ethernet, PTP (Precision Time

Protocol - IEEE 1588), GPS, and IRIG-B support

• RuggedServer™ RS416, RS910 and RS920 modular serial servers

• RuggedServer™ RS416v2 modular serial server with PTP and IRIG-B support

• RuggedServer™ RS400

• 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.

Who Should Use This User Guide

This guide is to be used by network technical support personnel who are familiar with the
operation of networks. Others who might find the book useful are network and system planners,
system programmers and line technicians.

How Chapters are organized

The index of this guide has been prepared with:

• Entries to each of the “Features” sections of the manual

• Entries to each of the “Troubleshooting” sections of the manual (located at the end of each

chapter)

• Entries to each of the Menus, organized by name

Document Conventions

This publication uses the following conventions:

ROS® v3.11User Guide 9 RMC30

Preface

Means reader take note. Notes contain helpful suggestions or references to
materials not contained in this guide.

It is recommended that you use this guide along with the following applicable documents:

• RMC30 Family Installation Guide

• RuggedCom Fiber Guide

• RuggedCom Wireless Guide

• White paper: Rapid Spanning Tree in Industrial Networks

Applicable Firmware Revision

This guide is applicable to ROS® software version 3.11.

Firmware/User Guide Version Numbering System

ROS® has a three-digit version numbering system of the form X.Y.Z where each digit is a
number starting from zero. The 'X.Y' digits represent the functional version of ROS® whereas
the 'Z' digit represents firmware patches. The 'X' digit is incremented for major functional
updates of the product. The 'Y' digit is incremented for minor functional updates of the product.
The 'Z' digit is incremented for bug fixes, cosmetic enhancements and other minor issues.

User guides follow the same format. In general, a user guide will have the same 'X.Y' digits
as the firmware to which it corresponds.

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. It is for this reason that release notes are created detailing all patches for a given
functional version.

ROS® v3.11User Guide 10 RMC30

1. Administration

1. Administration

The Administration menu covers the configuration of administrative parameters of both device
and network (local services availability, security methods employed, system identification and
functionality related to the IP network):

• IP Address, Subnet Mask and Gateway Address (static or dynamically obtainable)

• Management VLAN

• Management Connection Inactivity Timeout

• TFTP Server Permissions

• System Identification

• Passwords

• Time-keeping

• SNMP Management

• Radius Server

• Remote Syslog

1.1. The ROS® User Interface

1.1.1. Using the RS232 Port to Access the User Interface

Attach a terminal (or PC running terminal emulation software) to the RS232 port. The terminal
should be configured for 8 bits, no parity operation at 57.6 Kbps. Hardware and software flow
control must be disabled. Select a terminal type of VT100.

Once the terminal is connected, restart the unit and press and hold <Ctrl-Z>. The following
will be printed:

“Console mode...
Type ‘yes’ if you want to enter console mode: ”
After typing 'yes', pressing any key on the keyboard will prompt for the user name and

password to be entered.

To prevent unauthorized access to the device, make sure to change the default
user, admin and guest passwords before commissioning the device.

The switch is shipped with a default administrator user name - “admin” - and password ­“admin”. Once successfully logged in, the user will be presented with the main menu.

1.1.2. The Structure of the User Interface

The user interface is organized as a series of menus with an escape to a command line
interface (CLI) shell. Each menu screen presents the switch name (as provided by the
System Identification parameter), Menu Title, Access Level, Alarms indicator, Sub-Menus and
Command Bar.

Sub-menus are entered by selecting the desired menu with the arrow keys and pressing the
enter key. Pressing the escape key returns you to the parent menu.

ROS® v3.11User Guide 11 RMC30

1. Administration

Figure 1.1. Main Menu With Screen Elements Identified

The command bar offers a list of commands that apply to the currently displayed menu. These
commands include:

• <Ctrl-Z> to display help on the current command or data item

• <Ctrl-S> to switch to the CLI shell

• <Ctrl-Up/Down> to jump to next/previous page of a status display
The main menu also provides a <Ctrl-X> command, which will terminate the session. This type

of menu is accessible via serial console, telnet session and SSH session.

1.1.3. Making Configuration Changes

When changing a data item, the user selects the data item by the cursor keys and then pressing
the enter key. The cursor will change position to allow editing of the data item.

Typing a new value after pressing enter always erases the old parameter value. The left and
right cursor keys can be used to position the edit point without erasing the old parameter value.
The up and down cursor keys can be used to cycle through the next higher and lower values
for the parameter.

After the parameter has been edited, press enter again to change other parameters. When
all desired parameters have been modified, press <Ctrl-A> to apply changes. The switch will
automatically prompt you to save changes when you leave a menu in which changes have
been made.

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 12 RMC30

1. Administration

1.1.4. Updates Occur In Real Time

All configuration and display menus present the current values, automatically updating if
changed from other user interface sessions or SNMP. All statistics menus will display changes
to statistics as they occur.

1.1.5. Alarm Indications Are Provided

Alarms are events for which the user is notified through the Diagnostics sub-menu. All
configuration and display menus present an indication of the number of alarms (in the upper
right hand corner of the screen) as they occur, automatically updating as alarms are posted
and cleared.

1.1.6. The CLI Shell

The user interface provides a Command Line Interface shell for operations that are more easily
performed at the command line. You may switch back and forth from the menu system and
shell by pressing <Ctrl-S>. For more information on the capabilities of the shell please refer
to Chapter 5, Using the CLI Shell.

1.2. The ROS® Secure Shell Server

1.2.1. Using a Secure Shell to Access the User Interface

SSH (Secure Shell) is a network protocol which provides a replacement for insecure remote
login and command execution facilities, such as telnet and remote shell. SSH encrypts traffic
in both directions, preventing traffic sniffing and password theft.

SSH protocol version 2 is implemented in ROS®. The authentication method is “keyboard­interactive” password authentication. A user logged in via SSH has the same privileges as
one logged in via the console port.

1.2.2. Using a Secure Shell to Transfer Files

ROS® implements an SFTP server via SSH to transfer files securely. The file system visible
on the RuggedSwitch® has a single directory. The files in it are created at startup time and
can be neither deleted nor renamed. Existing files can be downloaded from the switch. For
example, firmware images may be downloaded for backup and log files may be downloaded
for analysis. 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

get

download a file from the switch

put

upload a file to the switch

ROS® v3.11User Guide 13 RMC30

1. Administration

The files that may be overwritten via SFTP upload are:

main.bin

main ROS® firmware image

boot.bin

RuggedSwitch bootloader image

config.csv

ROS® configuration file

fpga.xsvf

FPGA configuration file

1.3. The ROS® Web Server Interface

1.3.1. Using a Web Browser to Access the Web Interface

A web browser uses a secure communications method called SSL (Secure Socket Layer) to
encrypt traffic exchanged with its clients. The web server guarantees that communications
with the client are kept private. If the client requests access via an insecure HTTP port, it will
be rerouted to the secure port. Access to the web server via SSL will be granted to a client
that provides a valid user name / password pair.

It can happen that upon connecting to the ROS® web server, a web browser may
report that it cannot verify the authenticity of the server's certificate against any of its
known certificate authorities. This is expected, and it is safe to instruct the browser to
accept the certificate. Once the browser accepts the certificate, all communications
with the web server will be secure.

Start a web browser session and open a connection to the switch by entering a URL that
specifies its host name or IP address. For example, in order to access the unit at its factory
default IP address, enter https://192.168.0.1. Once in contact with the switch, start the login
process by clicking on the “Login” link. The resulting page should be similar to that presented
below:

Figure 1.2. The ROS® log in page

To prevent unauthorized access to the device, make sure to change the default
user, admin and guest passwords before commissioning the device.

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 14 RMC30

1. Administration

1.3.2. Customizing the Login Page

To display a custom welcome message, device information or any other information on the
login page, add text to the “banner.txt” file. If the “banner.txt” file is empty, only the username
and password fields will appear on the login page.

For more information, see Section 6.1, “Files Of Interest”.

1.3.3. The Structure of the Web Interface

The user interface is organized as a series of linked web pages. The main menu provides the
links at the top level of the menu hierarchy and allows them to be expanded to display lower­level links for each configuration subsystem.

Figure 1.3. Main Menu via Web Server Interface

Every web page in the menu system has a common header section which contains:

• 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.

• A “Back” link at left and below “Log out” links back to the previously viewed page.

• The menu title, in the center of the page and below the banner, is a link to a context-sensitive

help page.

• The access level, e.g. “access admin”, is displayed by default at the right of the page and

below the banner. If, however, any alarms are pending, the text will be replaced with a link
which displays the number of pending alarms. Following this link displays a table of pending
alarms.

Figure 1.4. Web Page Header Showing Alarms Link

ROS® v3.11User Guide 15 RMC30

1. Administration

1.3.4. Making Configuration Changes

When changing a data item, the user selects the data item by selecting the field to edit with
the mouse, entering a new value and clicking on the apply field. More than one parameter
may be modified at a time.

Figure 1.5. Parameters Form Example

Some menus will require you to create or delete new records of information.

1.3.5. Updating Statistics Displays

You may click the refresh button to update statistics displays.

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.

• Use strong passwords. For more information about creating strong passwords, refer to the

password requirements in Section 1.10, “Passwords”.

1.5. Administration Menu

The Administration menu provides ability to configure network and switch administration
parameters.

ROS® v3.11User Guide 16 RMC30

1. Administration

Figure 1.6. Administration Menu

1.6. IP Interfaces

These parameters provide the ability to configure IP connection parameters, such as address,
network, and mask. Only one IP interface can be configured.

You can choose from the following IP Address types: Static, DHCP, BOOTP, and Dynamic.
The Static IP Address type refers to the manual assignment of an IP address. The 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.

BOOTP is a subset of the DHCP protocol. ROS® supports the transfer of a BOOTFILE via
BOOTP. The BOOTFILE represents any valid ROS® file, such as config.csv. The name of the
BOOTFILE on the BOOTP server must match the corresponding ROS® file.

The Dynamic IP Address type refers to a combination of the BOOTP and DHCP protocols.
Starting with BOOTP, the system tries BOOTP and DHCP in a round-robin fashion until it
receives a response from the corresponding server.

On non-management interfaces, only static IP addresses can be assigned.
On the management interface, the user can choose from the following IP Address types:

Static, DHCP, BOOTP and Dynamic. Static IP Address type refers to the manual assignment
of an 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 17 RMC30

1. Administration

BOOTP is a subset of the DHCP protocol. ROS® supports the transfer of a BOOTFILE via
BOOTP. The BOOTFILE represents any valid ROS® file such as config.csv. The name of
BOOTFILE on the BOOTP server must match the corresponding ROS® file.

The Dynamic IP Address type refers to a combination of the BOOTP and DHCP protocols.
Starting with BOOTP, the system will try BOOTP and DHCP in a round-robin fashion until it
receives a response from the corresponding server.

You can use the ROS® web interface to change the IP Address Type of the
management interface from Static to DHCP. However, after doing so, you cannot
use the web interface to change the IP Address Type back to Static and set an IP
address. If you need to change the IP Address Type of the management interface
from DHCP to Static, configure the setting through a telnet, SSH, RSH, or serial
port connection, or upload a new configuration file to the device.

IP Address Type

Synopsis: { Static, Dynamic, DHCP, BOOTP }
Default: Static

Specifies whether the IP address is static or is dynamically assigned via DHCP or BOOTP.
The Dynamic option automatically switches between BOOTP and DHCP until it receives
a response from the relevant server. The Static option must be used for non-management
interfaces.

IP Address

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default: 192.168.0.1

Specifies the IP address of this device. An IP address is a 32-bit number that is notated by
using four numbers from 0 through 255, separated by periods. Only a unicast IP address
is allowed, which ranges from 1.0.0.0 to 233.255.255.255.

Subnet

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default: 255.255.255.0

Specifies the IP subnet mask of this device. An IP subnet mask is a 32-bit number that is
notated by using four numbers from 0 through 255, separated by periods. Typically, subnet
mask numbers use either 0 or 255 as values (e.g. 255.255.255.0) but other numbers can
appear.

1.7. 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 18 RMC30

1. Administration

Figure 1.7. IP Gateways Form

Destination

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default: 0.0.0.0

Specifies the IP address of the destination device. An IP address is a 32-bit number that
is notated by using four numbers from 0 through 255, separated by periods.

Subnet

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default: 0.0.0.0

Specifies the IP subnet mask of the destination. An IP subnet mask is a 32-bit number
that is notated by using four numbers from 0 through 255, separated by periods. Typically,
subnet mask numbers use either 0 or 255 as values (e.g. 255.255.255.0) but other
numbers can appear.

Gateway

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default: 0.0.0.0

Specifies the gateway IP address. The gateway address must be on the same IP subnet
as this device.

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 19 RMC30

1. Administration

Figure 1.8. IP Services Form

Inactivity Timeout

Synopsis: 1 to 60 or { Disabled }
Default: 5 min

Specifies when the console will timeout and display the login screen if there is no user
activity. A value of zero disables timeouts for console and Telnet users. For Web Server
users maximum timeout value is limited to 30 minutes.

Telnet Sessions Allowed

Synopsis: 0 to 4
Default: 0 (controlled version)
Default: 4 (non-controlled version)

Limits the number of Telnet sessions. A value of zero prevents any Telnet access.

Web Server Users Allowed

Synopsis: 1 to 16
Default: 16

Limits the number of simultaneous web server users.

TFTP Server

Synopsis: { Disabled, Get Only, Enabled }
Default: Disabled

As TFTP is a very insecure protocol, this parameter allows the user to limit or disable TFTP
Server access.

DISABLED - disables read and write access to TFTP Server
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 20 RMC30

1. Administration

SSH Sessions Allowed (Controlled Version Only)

Synopsis: 1 to 4
Default: 4

Limits the number of SSH sessions.

RSH Server

Synopsis: { Disabled, Enabled }
Default: Disabled (controlled version)
Default: Enabled (non-controlled version)

Disables/enables Remote Shell access.

1.9. System Identification

The system identification is displayed in the sign-on screen and in the upper left hand corner
of all ROS® screens.

Figure 1.9. System Identification Form

System Name

Synopsis: Any 19 characters
Default: System Name

The system name is displayed in all 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: Any 49 characters
Default: Location

The location can be used to indicate the physical location of the switch. It is displayed in
the login screen as another means to ensure you are dealing with the desired switch.

Contact

Synopsis: Any 49 characters
Default: Contact

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 21 RMC30

1. Administration

1.10. Passwords

These parameters provide the ability to configure parameters for authorized and authenticated
access to the device's services (HMI via Serial Console, Telnet, SSH, RSH, Web Server).
Access to the switch can be authorized and authenticated via RADIUS or TACACS+ servers,
or using locally configured passwords that are configured per user name and access level.

Note that access via the Serial Console is authorized first using local settings. If a local match
is not found, RADIUS/TACACS+ will be used if enabled. For all other services, if RADIUS
or TACACS+ is enabled for authentication and authorization, but is unreachable, the local
settings will be used if configured.

To access the unit, the user name and password must be provided.
Three user names and passwords can be configured. They correspond to three access levels,

which provide or restrict access to change settings and execute various commands within the
device.

• guest users can view most settings, but may not change settings or run commands

• operator cannot change settings, but can reset alarms, clear statistics and logs

• admin user can change all the settings and run commands

To prevent unauthorized access to the device, make sure to change the default
user, admin and guest passwords before commissioning the device.

When creating a new password, it should adhere to the following rules:

• Must not be less than 6 characters in length.

• Must not include the username or any 4 continous alphanumeric characters found in

the username. For example, if the username is Subnet25, the password may not be
subnet25admin or subnetadmin. However, net25admin or Sub25admin is permitted.

• Must have at least one alphabetic character and one number. Special characters are

permitted.

• Must not have more than 3 continuously incrementing or decrementing numbers. For

example, Sub123 and Sub19826 are permitted, but Sub12345 is not.

An alarm will generate if a weak password is configured. The weak password alarm can
be disabled by user. For more information about disabling alarms, refer to Section 4.1.4,

“Configuring Alarms”.

ROS® v3.11User Guide 22 RMC30

1. Administration

Figure 1.10. Passwords Form

Auth Type

Synopsis: { Local, RADIUS, TACACS+, RADIUSorLocal, TACACS
+orLocal }
Default: Local

Password authentication can be performed using locally configured values, a remote
RADIUS server, or a remote TACACS+ server. Setting this value to one of the
combinations that includes RADIUS or TACACS+ requires that the Security Server Table
be configured.

• Local - authentication from the local Password Table

• RADIUS - authentication using a RADIUS server

• TACACS+ - authentication using a TACACS+ server

• RADIUSOrLocal - authentication using RADIUS. If the server cannot be reached,
authenticate from the local Password Table.

• TACACS+OrLocal - authentication using TACACS+. If the server cannot be reached,
authenticate from the local Password Table

Guest Username

Synopsis: 15 character ASCII string
Default: guest

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 23 RMC30

1. Administration

Confirm Guest Password

Synopsis: 15 character ASCII string
Default: None

Confirm the input of the above Guest Password.

Operator Username

Synopsis: 15 character ASCII string
Default: operator

Related password is in the Oper Password field; cannot change settings; can reset alarms,
statistics, logs, etc.

Operator Password

Synopsis: 15 character ASCII string
Default: operator

Related user name is in the Oper Username field; cannot change settings; can reset
alarms, statistics, logs, etc.

Confirm Operator Password

Synopsis: 15 character ASCII string
Default: None

Confirm the input of the above Operator Password.

Admin Username

Synopsis: 15 character ASCII string
Default: admin

Related password is in the Admin Password field; full read/write access to all settings and
commands.

Admin Password

Synopsis: 15 character ASCII string
Default: admin

Related user name is in the Admin Username field; full read/write access to all settings
and commands.

Confirm Admin Password

Synopsis: 15 character ASCII string
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. Configuring System Time

The System Time Manager option within the ROS® Administration menu fully configures time
keeping functions on a ROS®-based device:

ROS® v3.11User Guide 24 RMC30

1. Administration

Figure 1.11. System Time Manager Menu

1.11.1.1. Configuring Time and Date

This menu configures the current time, date, time zone, and DST (Daylight Savings Time)
settings.

Figure 1.12. Time and Date Form

Time

Synopsis: HH:MM:SS

This parameter enables both the viewing and setting of the local time.

Date

Synopsis: MMM DD, YYYY

This parameter enables both the viewing and setting of the local date.

Time Zone

Synopsis: {
UTC-12:00 (Eniwetok, Kwajalein), UTC-11:00 (Midway Island,
Samoa),
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 25 RMC30

1. Administration

UTC+2:00 (Athens, Cairo, Helsinki), UTC+3:00 (Baghdad, Moscow),
UTC+3:30 (Teheran), UTC+4:00 (Abu Dhabi, Kazan, Muscat),
UTC+4:30 (Kabul), UTC+5:00 (Islamabad, Karachi),
UTC+5:30 (Calcutta, New Delhi), UTC+5:45 (Kathmandu),
UTC+6:00 (Almaty, Dhaka), UTC+6:30 (Rangoon),
UTC+7:00 (Bangkok, Hanoi), UTC+8:00 (Beijing, Hong Kong)
UTC+9:00 (Seoul, Tokyo), UTC+9:30 (Adelaide, Darwin),
UTC+10:00 (Melbourne, Sydney), UTC+11:00 (Magadan, New
Caledonia),
UTC+12:00 (Auckland, Fiji) }
Default: UTC-0:00 (Lisbon, London)

This setting enables 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. For example, for most of the USA and Canada, DST time shift is 1 hour
(01:00:00) forward when DST begins and 1 hour backward when DST ends.

DST Rule

Synopsis: mm.n.d/HH:MM:SS mm.n.d/HH:MM:SS
Default:

This parameter specifies a rule for time and date when the transition between Standard
and Daylight Saving Time occurs.

• mm - Month of the year (01 - January, 12 - December)

• n - week of the month (1 - 1st week, 5 - 5th/last week)

• d - day of the week (0 - Sunday, 6 - Saturday)

• HH - hour of the day (0 - 24)

• MM - minute of the hour (0 - 59)

• SS - second of the minute (0 - 59)

Example: The following rule applies in most of the USA and Canada:

03.2.0/02:00:00 11.1.0/02:00:00

In the example, DST begins on the second Sunday in March at 2:00am, and ends on the
first Sunday in November at 2:00am.

Current UTC Offset

Synopsis: 0 s to 1000 s
Default: 34 s

Coordinated Universal Time (UTC) is a time standard based on International Atomic
Time (TAI) with leap seconds added at irregular intervals to compensate for the Earth's
slowing rotation. The Current UTC Offset parameter allows the user to adjust the difference
between UTC and TAI. The International Earth Rotation and Reference System Service
(IERS) observes the Earth's rotation and nearly six months in advance (January and July)
a 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 26 RMC30

1. Administration

1.11.1.2. Configuring NTP Service

ROS® may optionally be configured to refer periodically to a specified NTP server to correct
any accumulated drift in the on-board clock. ROS® will also serve time via SNTP to hosts
that request it.

Two NTP servers (primary and secondary) may be configured for the device. The primary
server is contacted first upon each attempt to update the system time. If the primary server
fails to respond, the secondary server is contacted. If either the primary or secondary server
fails to respond, an alarm is raised.

Figure 1.13. NTP Server List

Figure 1.14. NTP Server Form

Server

Synopsis: Primary, Secondary

This field displays the chosen NTP server. The remaining fields on this form correspond
to the chosen server.

IP Address

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default:

This parameter specifies the IP address of an (S)NTP server ((Simple) Network Time
Protocol); programming an address of '0.0.0.0' disables SNTP requests. This device is an
SNTP client which may connect to only one server. If a server address is programmed
then a manual setting of the time will be overwritten at the next update period.

Update Period

Synopsis: 1 to 1440
Default: 60 min

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 27 RMC30

1. Administration

1.12. SNMP Management

ROS® supports Simple Network Management Protocol Versions 1 (SNMPv1), 2 (SNMPv2c),
and 3 (SNMPv3). SNMPv3 protocol provides secure access to devices by a combination of
authentication and packet encryption over the network. SNMPv3 security features include the
following:

• message integrity – ensures that a packet has not been tampered with in-transit.

• authentication – determines the message is from a valid source.

• encryption – scrambles the contents of a packet to prevent it from being seen by an
unauthorized source.

SNMPv3 provides security models and security levels. A security model is an authentication
strategy that is set up for a user and the group in which the user resides. A security level is
a permitted level of security within a security model. A combination of a security model and
security level will determine which security mechanism is employed when handling an SNMP
packet.

Note the following about the SNMPv3 protocol:

• each user belongs to a group.

• a group defines the access policy for a set of users.

• an access policy defines what SNMP objects can be accessed for: reading, writing and
creating notifications.

• a group determines the list of notifications its users can receive.

• a group also defines the security model and security level for its users.

Community is configured for protocols v1 and v2c. Community is mapped to the group and
access level with security name (which is configured as User name).

1.12.1. SNMP Users

These parameters provide the ability to configure users for the local SNMPv3 engine, along
with the community for 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 28 RMC30

1. Administration

Figure 1.16. SNMP User Form

Name

Synopsis: Any 32 characters
Default: initial

The name of the user. This user name also represents the security name that maps this
user to the security group.

IP Address

Synopsis: ###.###.###.### where ### ranges from 0 to 255
Default:

The IP address of the user's SNMP management station. If IP address is configured, SNMP
requests from that user will be verified by IP address as well. SNMP Authentication trap
will be 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.

v1/v2c Community

Synopsis: Any 32 characters
Default:

The community string which is mapped by this user/security name to the security group if
security model is SNMPv1 or SNMPv2c. If this string is left empty, it will be assumed to
be equal to the same as user name.

Auth Protocol

Synopsis: { noAuth, HMACMD5 }
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 29 RMC30

1. Administration

Default: noPriv

An indication of whether messages sent on behalf of this user to/from SNMP engine can
be protected from disclosure, and if so, the type of privacy protocol which is used.

Auth Key

Synopsis: 31 character ASCII string
Default:

The secret authentication key (password) that must be shared with SNMP client. if the key
is not an emtpy string, it must be at least 6 characters long.

Confirm Auth Key

Synopsis: 31 character ASCII string
Default:

The secret authentication key (password) that must be shared with SNMP client. if the key
is not an emtpy string, it must be at least 6 characters long.

Priv Key

Synopsis: 31 character ASCII string
Default:

The secret encription key (password) that must be shared with SNMP client. if the ke is
not an emtpy string, it must be at least 6 characters long.

Priv Key

Synopsis: 31 character ASCII string
Default:

The secret encription key (password) that must be shared with SNMP client. if the ke is
not an emtpy string, it must be at least 6 characters long.

1.12.2. SNMP Security to Group Maps

Entries in this table map configuration of security model and security name (user) into a group
name, which is used to define an access control policy. Up to 32 entries can be configured.

Figure 1.17. SNMP Security to Group Maps Table

ROS® v3.11User Guide 30 RMC30