PDN-UPLINK-TAGGING-MIB: View SNMP OID List / Download MIB

VENDOR: PARADYNE


 Home MIB: PDN-UPLINK-TAGGING-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, PDN-HEADER-MIB, Q-BRIDGE-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 pdnUplinkTagging 1.3.6.1.4.1.1795.2.24.2.37
This MIB contains objects that are used to configure Uplink Tagging (ULT). Uplink Tagging is a term used to describe a feature that simplifies the setup and administration of networks where a service provider wants to use a unique VLAN per subscriber port. Ingress frames will get tagged with a VLAN and these tagged frame will be transmitted on the uplink port towards the WAN. In cases where the hardware implementation permits, multiple units can be interconnected together to form a 'Uplink Tagging Domain (ULT Domain)'. A ULT domain is defined as the set of interconnected Paradyne DSLAMs that share a common block of VLAN IDs. The maximum number of Paradyne DSLAMs that can be interconnected is implementation dependent. Generally, all DSLAMs in a ULT Domain will be configured with the same block of VLAN IDs. Each chassis/unit will be assigned a unique ULT Index within the ULT Domain. There are two parts of configuring Uplink Tagging: 1. Uplink Base VLAN Tag - This object specifies the beginning VLAN ID for a particular common block of VLAN IDs. This object will be defined as an enumeration whose values will depend on the number of port in a chassis/unit. 2. Uplink Tag Index - This object specifies the index within some block of VLAN IDs. Generally, this index can thought of a chassis/unit number as can be seen with the examples below.
       pdnUplinkTaggingObjects 1.3.6.1.4.1.1795.2.24.2.37.1
           ultBaseVlanTag 1.3.6.1.4.1.1795.2.24.2.37.1.1 integer read-write
This object represents Uplink Tagging base index. This object has been deprecated. Please use an object defined in pdnUplinkTaggingObjectsR2. Enumeration: 'ultBase1536': 4, 'ultBase2048': 5, 'ultBase3072': 7, 'ultBase1024': 3, 'ultBase16': 1, 'ultBase2560': 6, 'ultBase3584': 8, 'ultBase512': 2.
           ultIndex 1.3.6.1.4.1.1795.2.24.2.37.1.2 integer read-write
This object represents VLAN tag index which represents an index into a block of VLAN Tags the unit will use. This object has been deprecated. Please use pdnUltIndex, which is more general below.
       pdnUplinkTaggingConformance 1.3.6.1.4.1.1795.2.24.2.37.2
           pdnUplinkTaggingGroups 1.3.6.1.4.1.1795.2.24.2.37.2.1
               pdn48PortUpLinkTaggingGroup 1.3.6.1.4.1.1795.2.24.2.37.2.1.1
Uplink Tagging Objects for 48-Port chassis/units.
               pdn24PortUpLinkTaggingGroup 1.3.6.1.4.1.1795.2.24.2.37.2.1.2
Uplink Tagging Objects for 24-Port chassis/units.
           pdnUplinkTaggingCompliances 1.3.6.1.4.1.1795.2.24.2.37.2.2
           pdnUplinkTaggingDeprecatedGroup 1.3.6.1.4.1.1795.2.24.2.37.2.3
               upLinkTaggingDeprecatedGroup 1.3.6.1.4.1.1795.2.24.2.37.2.3.1
Objects not to use.
       pdnUplinkTaggingObjectsR2 1.3.6.1.4.1.1795.2.24.2.37.3
           pdnUltIndex 1.3.6.1.4.1.1795.2.24.2.37.3.1 unsigned32 read-write
This object represents VLAN tag index which is an index into a block of VLAN Tags the unit will use. Generally, this can be also thought of as the chassis/unit number in the case where multiple units are interconnected and form a ULT Domain described above. It is strongly encouraged that the upper limit for a particular implementation be clearly documented in the product's SNMP Op Spec.
           pdnGenUltBaseVlanTag 1.3.6.1.4.1.1795.2.24.2.37.3.2 vlanid read-write
This object can be used to allow any Uplink Tagging Base Index to be entered when they don't like the 'canned' list defined in the objects below.
           pdn48UltBaseVlanTag 1.3.6.1.4.1.1795.2.24.2.37.3.3 integer read-write
This object represents Uplink Tagging base index which is the starting VLAN ID for a particular common block of VLAN IDs for chassis/units that contain 48 DSL subscriber ports. Enumeration: 'ultBase1536': 4, 'ultBase2048': 5, 'ultBase3072': 7, 'ultBase1024': 3, 'ultBase16': 1, 'ultBase2560': 6, 'ultBase3584': 8, 'ultBase512': 2.
           pdn24UltBaseVlanTag 1.3.6.1.4.1.1795.2.24.2.37.3.4 integer read-write
This object represents Uplink Tagging base index which is the starting VLAN ID for a particular common block of VLAN IDs for chassis/units that contain 24 DSL subscriber ports. Enumeration: 'ultBase1536': 7, 'ultBase3072': 13, 'ultBase2048': 9, 'ultBase1280': 6, 'ultBase2304': 10, 'ultBase256': 2, 'ultBase1024': 5, 'ultBase16': 1, 'ultBase3328': 14, 'ultBase768': 4, 'ultBase3840': 16, 'ultBase1792': 8, 'ultBase3584': 15, 'ultBase512': 3, 'ultBase2560': 11, 'ultBase2816': 12.