This node IS NOT DESCRIBED YET
View at oid-info.com
The volatile config lines (marked as V) will not be stored
in startup. This object returns alike(1) if both startup
and active are alike and no sync necessary between them.
It returns alikeExceptVolatile(2), only when the difference
is that there are some volatile commands in the active config.
In this case too, there is no need of syn between the both.
It returns different(3), when the startup and active are
different and may need a sync before the next reboot.
Parsed from file rstone-config-mib.txt
Company: None
Module: RIVERSTONE-CONFIG-MIB
The volatile config lines (marked as V) will not be stored
in startup. This object returns alike(1) if both startup
and active are alike and no sync necessary between them.
It returns alikeExceptVolatile(2), only when the difference
is that there are some volatile commands in the active config.
In this case too, there is no need of syn between the both.
It returns different(3), when the startup and active are
different and may need a sync before the next reboot.
Parsed from file RIVERSTONE-CONFIG-MIB.mib
Module: RIVERSTONE-CONFIG-MIB
rsCfgIsStartupActiveAlike OBJECT-TYPE SYNTAX INTEGER { alike(1), alikeExceptVolatile(2), different(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The volatile config lines (marked as V) will not be stored in startup. This object returns alike(1) if both startup and active are alike and no sync necessary between them. It returns alikeExceptVolatile(2), only when the difference is that there are some volatile commands in the active config. In this case too, there is no need of syn between the both. It returns different(3), when the startup and active are different and may need a sync before the next reboot." ::= { rsCfgObjects 5 }
rsCfgIsStartupActiveAlike OBJECT-TYPE SYNTAX INTEGER { alike(1), alikeExceptVolatile(2), different(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The volatile config lines (marked as V) will not be stored in startup. This object returns alike(1) if both startup and active are alike and no sync necessary between them. It returns alikeExceptVolatile(2), only when the difference is that there are some volatile commands in the active config. In this case too, there is no need of syn between the both. It returns different(3), when the startup and active are different and may need a sync before the next reboot." ::= { rsCfgObjects 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.5567.2.20.1.5.0 | rsCfgIsStartupActiveAlike | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.5567.2.20.1.1 | rsCfgNextTransferId | 0 | 0 | This object contains the next appropriate value to be used for rsCfgTransferId when creating entries in the rsCfgTransferTable. … |
| 1.3.6.1.4.1.5567.2.20.1.2 | rsCfgTransferTable | 1 | 14 | This table specifies Parameters related to a change session in the active config. This table is not persistent across reboots. |
| 1.3.6.1.4.1.5567.2.20.1.3 | rsCfgMaxEntriesInTransferTable | 1 | 1 | This node IS NOT DESCRIBED YET |
| 1.3.6.1.4.1.5567.2.20.1.4 | rsCfgMaxSimultaneousTransfers | 1 | 1 | This node IS NOT DESCRIBED YET |
| 1.3.6.1.4.1.5567.2.20.1.6 | rsCfgActiveLastChange | 1 | 1 | This node IS NOT DESCRIBED YET |
| 1.3.6.1.4.1.5567.2.20.1.7 | rsCfgStartupLastChange | 0 | 0 | This object returns the date and time when the startup config was changed last. |