nextBootPath

AT-SETUP-MIB · .1.3.6.1.4.1.207.8.4.4.4.500.2.2.2

Object

The full path of the release to be used the next time the
device restarts. There is no guarantee that the file
referenced exists (i.e. it may have been deleted since the boot
path was last set).
          
Only one set operation can be executed at a time across all
SNMP users, and an operation may not be started unless the
current value of nextBootSetStatus is 'idle'. The path must not
contain whitespace characters.
          
Immediately upon setting this object, the system will attempt
to set the new boot path, and the process will continue on the
device until it has completed or a failure occurs. The current
status of the operation can be determined by reading
nextBootSetStatus, and the result of the last completed
operation is indicated by nextBootLastSetResult.
          
This object can be set with an empty string in order to clear
the current boot firmware. Otherwise, the path should be of the
form 'flash:/filename.rel' or 'card:/filename.rel'.
          
There are several requirements that must be met in order to set
a boot release file successfully:
- The file must exist.
- The file must be in the root of flash (on the active master
  in a stacked environment) or card.
- The file must not be the same as the currently set backup
  release.
- The file must have a .rel suffix.
- The file must be a valid release file.
- In a stacked environment, there must be enough disk space
  available to store the release file on each stack member.
- The device must have a current release license for the
  specified release.

Context

MIB
AT-SETUP-MIB
OID
.1.3.6.1.4.1.207.8.4.4.4.500.2.2.2
Type
scalar
Access
readwrite
Status
current
Parent
nextBootFirmware

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:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AT-SETUP-MIB::nextBootPath.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'AT-SETUP-MIB' -M '/opt/observium/mibs/allied:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AT-SETUP-MIB::nextBootPath'

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