currSoftSaveAs

AT-SETUP-MIB · allied-old variant · .1.3.6.1.4.1.207.8.4.4.4.500.2.1.3

Object

Set with a filename to save the currently running software to the root 
of the flash. Only one save operation can be executed at a time across 
all SNMP users.
          
Immediately upon executing the set action the device will indicate that 
the SNMP set was a success. The actual firmware save operation itself 
will be started and continue on the device until it has completed.
          
Subsequent reads of the object will return one of several results:
saving x            A saving operation is currently in progress. You 
                    cannot start another save while the object is 
                    returning this value.
          
x success           The last save operation was successfully completed.
          
x failure: [error]  The last save operation failed, with the 
                    descriptive message attached. The most common 
                    failure is lack of remaining space on the flash.
          
idle                There is no save operation in progress and a new 
                    one may be started.
          
          
Upon reading a success or failure message, the message will be cleared 
and the next read will result in an 'idle' message. A new save operation 
can now be executed.

Context

MIB
AT-SETUP-MIB
OID
.1.3.6.1.4.1.207.8.4.4.4.500.2.1.3
Type
scalar
Access
readwrite
Status
current
Parent
currentFirmware

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'AT-SETUP-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AT-SETUP-MIB::currSoftSaveAs.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'AT-SETUP-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AT-SETUP-MIB::currSoftSaveAs'

Syntax

Source
SNMPv2-TCDisplayString
Base type
OctetString
Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
          
character set, as defined in pages 4, 10-11 of RFC 854.
          
To summarize RFC 854, the NVT ASCII repertoire specifies:
          
  - the use of character codes 0-127 (decimal)
          
  - the graphics characters (32-126) are interpreted as
    US ASCII
          
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854
          
  - the other 25 codes have no standard interpretation
          
  - the sequence 'CR LF' means newline
          
  - the sequence 'CR NUL' means carriage-return
          
  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.
          
  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)
          
Any object defined using this syntax may not exceed 255
characters in length.

Values & Constraints

Type Constraints
range: 0..255