lcsVLANPortStatusConflicts – LCOS-SX-MIB

Object

column SNMPv2-TCDisplayString

Two users may have conflicting requirements to a port's
configuration. For instance, one user may require
all frames to be tagged on egress while another requires
all frames to be untagged on egress.Since both
users cannot win, this gives rise to a conflict,
which is solved in a prioritized way. The Administrator
has the least priority. Other software modules are
prioritized according to their position in the drop-down
list: The higher in the list, the higher priority.
If conflicts exist, it will be displayed as 'Yes'.

Context

MIB: LCOS-SX-MIB
OID: .1.3.6.1.4.1.2356.14.1.10.2.6.2.1.8
Type: column
Access: readonly
Status: current
Parent: lcsVLANPortStatusEntry

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column

/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LCOS-SX-MIB::lcsVLANPortStatusConflicts'

More examples

Read one indexed instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LCOS-SX-MIB::lcsVLANPortStatusConflicts.<index>'

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LCOS-SX-MIB::lcsVLANPortStatusConflicts'

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

Type Constraints

range: 0..255