juniAaaAssignTunnelCallingNumberFormat
Juniper-AAA-MIB ·
.1.3.6.1.4.1.4874.2.2.20.1.1.1.9
Object
scalar r/w
Enumeration
The format of the interface identifier passed to L2TP during an authentication request. L2TP uses this identifier as the calling-number (type 22) attribute value. Note: if selected components of the calling number format are not available (i.e. PPPoE Agent Circuit Id and Agent Remote Id), then the juniAaaAssignTunnelCallingNumberFallbackFormat will be used. Optionally the SVLAN ID inclusion can be enabled
Context
- MIB
- Juniper-AAA-MIB
- OID
.1.3.6.1.4.1.4874.2.2.20.1.1.1.9- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- juniAaaAssignGeneral
- Groups
- 9
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'Juniper-AAA-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'Juniper-AAA-MIB::juniAaaAssignTunnelCallingNumberFormat.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'Juniper-AAA-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'Juniper-AAA-MIB::juniAaaAssignTunnelCallingNumberFormat'
Syntax
Enumeration
Values & Constraints
Enumerated Values
1 | descriptive |
2 | fixed |
3 | descriptiveIncludeAgentCircuitId |
4 | descriptiveIncludeAgentRemoteId |
5 | descriptiveIncludeAgentCircuitIdAndAgentRemoteId |
6 | agentCircuitId |
7 | agentRemoteId |
8 | agentCircuitIdIncludeAgentRemoteId |
9 | fixedIncludeSvlanId |
10 | fixedAdapterEmbedded |
11 | fixedAdapterNewField |
12 | fixedAdapterEmbeddedIncludeSvlanId |
13 | fixedAdapterNewFieldIncludeSvlanId |