All MIBs › HP-SN-AGENT-MIB › snAgCfgLoad
snAgCfgLoad
Module: HP-SN-AGENT-MIB
OID (symbolic): HP-SN-AGENT-MIB::snAgCfgLoad
OID (numeric): 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1.9
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Action object to down/up load a config image to the agent. The following values can be read : Error values: from normal(1) to operationError(17) and tftpWrongFileType(29). loading(18) .. operation is in process.
The following value can be used to set: uploadFromFlashToServer(20)..upload the config from flash to tftp server. downloadToFlashFromServer(21)..download the config to flash from tftp server. uploadFromDramToServer(22)..upload the config from DRAM to tftp server. downloadToDramFromServer(23)..download the config to DRAM from tftp server.
The following value can be used to set: uploadFromFlashToNMS(24)..upload the config from flash to NMS. downloadToFlashFromNMS(25)..download the config to flash from NMS. uploadFromDramToNMS(26)..upload the config from DRAM to NMS. downloadToDramFromNMS(27)..download the config to DRAM from NMS.
The config filename is defined in snAgCfgFname. The tftp server address is defined in snAgTftpServerIp. Atomic set of snAgCfgLoad, snAgCfgFname and snAgTftpServerIp is required to allow down/up load to happen. And the write request will be rejected during loading until error or normal. For those NMS commands from (24) to (27), The snAgCfgEosTable MIB must be sent along in one PDU. A seperate write memory cli or set snAgWriteNVRAM is required to save the config to NVRAM.
What is snAgCfgLoad?
An action object that drives configuration file transfers between the agent's flash/DRAM and either a TFTP server or an NMS: writing values like uploadFromFlashToServer or downloadToFlashFromServer starts the corresponding transfer, while reading it returns normal, an error code, or loading while in progress. An admin must also set the config filename and TFTP server address for a transfer to succeed, and for the NMS variants the snAgCfgEosTable data must be sent in the same SNMP request; a separate write to NVRAM (or snAgWriteNVRAM) is still needed afterward to persist the config.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1.9 snmpwalk -v2c -c public <target> HP-SN-AGENT-MIB::snAgCfgLoad
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1.9.1 snmpget -v2c -c public <target> HP-SN-AGENT-MIB::snAgCfgLoad.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1.9.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> snAgCfgLoad.1
Start monitoring HP/Foundry-heritage chassis-based network switch with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HP-SN-AGENT-MIB::snAgCfgLoad OID value, configure state conditions and alerts, and monitor any HP/Foundry-heritage chassis-based network switch from a single console.
OID Breakdown
Upper-level ancestors (14 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.11 | hp | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2 | nm | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2.3 | hpsystem | CLJ8500-MIB |
| 1.3.6.1.4.1.11.2.3.7 | netElement | HP-BASE-MIB |
| 1.3.6.1.4.1.11.2.3.7.11 | hpEtherSwitch | HP-BASE-MIB |
| 1.3.6.1.4.1.11.2.3.7.11.12 | hpSwitchCore | HP-SN-ROOT-MIB |
| 1.3.6.1.4.1.11.2.3.7.11.12.1 | switch | HP-SN-ROOT-MIB |
| 1.3.6.1.4.1.11.2.3.7.11.12.1.2 | snAgentSys | HP-SN-ROOT-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1 | snAgentGbl | HP-SN-AGENT-MIB |
| 1.3.6.1.4.1.11.2.3.7.11.12.1.2.1.9 | snAgCfgLoad | HP-SN-AGENT-MIB |