arubaWiredVsfv2SplitDetectStatusDownReason

ARUBAWIRED-VSFv2-MIB · .1.3.6.1.4.1.47196.4.1.1.3.15.1.1.7
Commands MIB view Table view

Object

scalar SNMPv2-TCDisplayString 
The down reason of split detection operational status
can be one of:
          
'Split detection is not configured'                                   : split detection method is not configured.
'Mgmt interface admin state is down'                                  : split detection method is configured as Mgmt and Mgmt interface admin state is down.
'Mgmt interface link state is down'                                   : split detection method is configured as Mgmt and Mgmt interface link state is down.
'Split detection VLAN is not configured'                              : split detection method is configured as vlan and split detection VLAN is not configured.
'VLAN <VLAN_ID> is not configured'                                    : split detection method is configured as vlan and coresponding VLAN identifier is not configured.
'VLAN <VLAN_ID> admin state is down'                                  : split detection method is configured as vlan and coresponding VLAN identifier is admin down.
'VLAN <VLAN_ID> does not have split detection interfaces configured'  : split detection method is configured as vlan and coresponding VLAN identifier is not associated with any interface.
'Interface <ifname> admin state is down'                              : split detection method is configured as vlan and coresponding VLAN associated interface admin state is down.
'Interface <ifname> operational state is down'                        : split detection method is configured as vlan and coresponding VLAN associated interface operational state is down.
'VLAN <VLAN_ID> is configured only with one split detection interface': split detection method is configured as vlan and only one access port is part of split detection VLAN. Split detection VLAN should have one access port from the primary and one from the secondary.

Context

MIB
ARUBAWIRED-VSFv2-MIB
OID
.1.3.6.1.4.1.47196.4.1.1.3.15.1.1.7
Type
scalar
Access
readonly
Status
current
Parent
arubaWiredVsfv2Status
Groups
1

Net-SNMP examples

How SNMP and these commands work

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

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

Syntax

SNMPv2-TCDisplayString
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

Object Constraints
range: 0-128
Type Constraints
range: 0..255

Conformance

Member of
arubaWiredVsfv2StatusScalarGroup