Rugged Operating System (ROS ® ) Software User ... - RuggedCom
Rugged Operating System (ROS ® ) Software User ... - RuggedCom
Rugged Operating System (ROS ® ) Software User ... - RuggedCom
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 1<br />
Introduction<br />
RUGGEDCOM <strong>ROS</strong><br />
<strong>User</strong> Guide<br />
Section 1.1.3<br />
Bootloader Considerations<br />
NOTE<br />
<strong>ROS</strong> Key Management features require Boot <strong>Software</strong> v2.20.0 at minimum. It is strongly<br />
recommended to update the bootloader to this version or higher.<br />
NOTE<br />
If a Boot upgrade is required from Boot v2.15.0 or older, it is recommended to run the "flashfiles defrag"<br />
command from the CLI Shell prior to the bootloader upgrade.<br />
In the event that it is impracticable to update the bootloader to v2.20.0 or higher, some of the key management<br />
features will nevertheless be available, although in a degraded mode. A <strong>ROS</strong> system running Main <strong>Software</strong> v<br />
and Boot <strong>Software</strong> earlier than v2.20.0 will have the following behaviour:<br />
• The unit will use the default keys after every reset, and immediately begin generating ssl.crt and<br />
ssh.keys. It will not, however, write these files to flash.<br />
• The unit will accept user-uploaded ssl.crt and ssh.keys, but again, it will not write these files to flash.<br />
WARNING!<br />
If <strong>ROS</strong> Boot <strong>Software</strong> earlier than v2.20.0 runs and creates log entries, there is the possibility that it will<br />
overflow into an area of Flash memory that is reserved by <strong>ROS</strong> Main <strong>Software</strong> v or newer for keys. If<br />
this were to occur, some syslog data would not be readable by Main.<br />
In the even more unlikely event that <strong>ROS</strong> Boot <strong>Software</strong> v2.20.0 or newer had been installed and Main had<br />
written the ssl.crt and ssh.keys files, and the unit had subsequently had a downgrade to Boot <strong>Software</strong><br />
earlier than v2.20.0, there is a possibility similar to the warning above, whereby Boot logging could possibly<br />
overwrite and therefore destroy one or both installed key files.<br />
Section 1.2<br />
SNMP MIB Support<br />
Section 1.2.1<br />
Standard MIBs<br />
Table: Standard MIBs<br />
Standard MIB Name Title<br />
RFC 2578 SNMPv2-SMI Structure of Management Information Version 2<br />
RFC 2579 SNMPv2-TC Textual Convention s for SMIv2<br />
RFC 2580<br />
SNMPv2-CONF<br />
IANAifType<br />
Conformance Statements for SMIv2<br />
Enumerated Values of The ifType Object Defined<br />
ifTable defined in IF-MIB<br />
RFC 1907 SNMPv2-MIB Management Information Base for SNMPv2<br />
RFC 2011 IP-MIB SNMPv2 Mnagement Information Base for Internet<br />
Protocol using SMIv2<br />
6 Bootloader Considerations
Change language