bsAdacUplinkPortList

BAY-STACK-ADAC-MIB · .1.3.6.1.4.1.45.5.9.1.1.11
Commands MIB view Table view

Object

scalar r/w Q-BRIDGE-MIBPortList 
The uplink ports are used usually when the Call Server is not
connected directly to the current module/stack.  This value
is used only when the current operating mode is either
untaggedFramesAdvanced(2) or taggedFrames(3).  It may not
be changed to an empty set of ports if the current operating
mode is one of these values.
          
Note that an implementation should support either
bsAdacCallServerPort and bsAdacUplinkPort, or
bsAdacCallServerPortList and bsAdacUplinkPortList, but not both.

Context

MIB
BAY-STACK-ADAC-MIB
OID
.1.3.6.1.4.1.45.5.9.1.1.11
Type
scalar
Access
readwrite
Status
current
Parent
bsAdacScalars

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 'BAY-STACK-ADAC-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BAY-STACK-ADAC-MIB::bsAdacUplinkPortList.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'BAY-STACK-ADAC-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BAY-STACK-ADAC-MIB::bsAdacUplinkPortList'

Syntax

Q-BRIDGE-MIBPortList
Source
Q-BRIDGE-MIBPortList
Base type
OctetString

Values & Constraints

No enumerated values or constraints recorded.