All MIBs › IBM-BCCUSTOM-MIB › iomSnmpv3UserStateStatusString
iomSnmpv3UserStateStatusString
Module: IBM-BCCUSTOM-MIB
OID (symbolic): IBM-BCCUSTOM-MIB::iomSnmpv3UserStateStatusString
OID (numeric): 1.3.6.1.4.1.2.6.215.6.1.10
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-only
Description: This object will be a bit string that contains detailed information about the SNMPv3 user account status. The intent is that the information string will be passed to the external application in the event that the MM set an <91>enable<92> state using the object <91>iomSnmpv3UserState<92> and the response to the write of that object was a failure due to an invalid account parameter. The bit string in this object is only to be used by the MM for the case above, otherwise the data is not guaranteed to be accurate. The bit mask is treated as 32 bits in network byte order. That is the bit 0 will be the left most bit and bit 31 will be the right most bit. The bit pattern definition is defined as below: Bit(8:31): reserved must be set to zeroes. Bit(8): Set to 1 to indicate the IPv6 trap address is invalid. Bit(7): Set to 1 to indicate the IPv4 trap address is invalid Bit(6): Set to 1 to indicate the access type is invalid or not set. Bit(5): Set to 1 to indicate the privacy 2486 password is invalid or not set Bit(4): Set to 1 to indicate the privacy protocol is invalid or not set. Bit(3): Set to 1 to indicate 1 the authentication password is invalid or not set. Bit(2): Set to 1 to indicate the authentication protocol is invalid or not set. Bit(1): Set to 1 to indicate the user-name is invalid or not set. Bit(0): If this bit is set to <91>0<92> then this will indicate all account parameters are correct. The MM will then ignore all other bits within this object. If this bit is set to <91>1<92> then then at least one other bit must be set to indicate what specific account parameter(s) are invalid and caused the failed response to the <91>iomSnmpv3UserState<92> enable.
What is iomSnmpv3UserStateStatusString?
A 4-octet bitmask returned after a failed attempt to enable the SNMPv3 user account (via iomSnmpv3UserState), where each bit flags a specific invalid parameter -- e.g. bit 1 for a bad username, bit 4 for a missing privacy protocol, bit 8 for an invalid IPv6 trap address. Bit 0 clear means every parameter was valid; the management module reads this only right after an enable failure to pinpoint what to fix.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.6.215.6.1.10 snmpwalk -v2c -c public <target> IBM-BCCUSTOM-MIB::iomSnmpv3UserStateStatusString
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.6.215.6.1.10.1 snmpget -v2c -c public <target> IBM-BCCUSTOM-MIB::iomSnmpv3UserStateStatusString.1
Start monitoring IBM-branded Brocade SAN/Fibre Channel switch (Pharos embedded platform) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IBM-BCCUSTOM-MIB::iomSnmpv3UserStateStatusString OID value, configure state conditions and alerts, and monitor any IBM-branded Brocade SAN/Fibre Channel switch (Pharos embedded platform) from a single console.
OID Breakdown
Upper-level ancestors (8 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.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.6 | ibmProd | IBM-6611-APPN-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.6.215 | bcCustom | IBM-BCCUSTOM-MIB |
| 1.3.6.1.4.1.2.6.215.6 | snmpuser | IBM-BCCUSTOM-MIB |
| 1.3.6.1.4.1.2.6.215.6.1 | iomSnmpv3Cfg | IBM-BCCUSTOM-MIB |
| 1.3.6.1.4.1.2.6.215.6.1.10 | iomSnmpv3UserStateStatusString | IBM-BCCUSTOM-MIB |