pdnUplinkTagging MODULE-IDENTITY
LAST-UPDATED "200303120000Z" -- March 12, 2003
ORGANIZATION "Paradyne Networks"
CONTACT-INFO
"Paradyne Networks, Inc.
8545 126th Avenue North
Largo, FL 33733
http://www.paradyne.com
General Comments to: [email protected]
Editors
Clay Sikes"
DESCRIPTION
"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."
REVISION "200303120000Z" -- March 12, 2003
DESCRIPTION
"Deprecated the origional objects, ultBaseVlanTag and ultIndex. Added new objects as follows:
1. pdnUltIndex - This new object is basically an Unsigned32 that excludes '0'. It idea is that different implementations will support different maximum values of the index. As such, the syntax for this object will cover any implementation and actual implementation specific maximum values should be documented in something like the implementation's SNMP Op Spec.
2. pdnGenUltBaseVlanTag - This object allows a any base VLAN Tag to be defined.
3. pdn48UltBaseVlanTag - This object defines a set of enumerations for base VLAN Tags for chassis/units that contain 48 ports.
4. pdn24UltBaseVlanTag - This object defines a set of enumerations for base VLAN Tags for chassis/units that
contain 24 ports."
REVISION "200205150000Z" -- May 15, 2002
DESCRIPTION
"Initial Release."
View at oid-info.com
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.
Parsed from file pdn_header.mib.txt
Company: paradyne
Module: PDN-HEADER-MIB
pdnUplinkTagging OBJECT IDENTIFIER ::= { pdn-common 37 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1795.2.24.2.37.1 | pdnUplinkTaggingObjects | 2 | 4 | None |
| 1.3.6.1.4.1.1795.2.24.2.37.2 | pdnUplinkTaggingConformance | 3 | 6 | None |
| 1.3.6.1.4.1.1795.2.24.2.37.3 | pdnUplinkTaggingObjectsR2 | 4 | 8 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1795.2.24.2.1 | pdn-frontPanel | 1 | 17 | None |
| 1.3.6.1.4.1.1795.2.24.2.2 | pdn-chassis | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.3 | pdn-callDir | 1 | 9 | None |
| 1.3.6.1.4.1.1795.2.24.2.4 | pdn-devStatus | 1 | 19 | None |
| 1.3.6.1.4.1.1795.2.24.2.5 | pdn-devID | 1 | 3 | None |
| 1.3.6.1.4.1.1795.2.24.2.6 | pdn-interfaces | 20 | 1450 | None |
| 1.3.6.1.4.1.1795.2.24.2.7 | pdn-devConfig | 10 | 50 | None |
| 1.3.6.1.4.1.1795.2.24.2.8 | pdn-security | 9 | 30 | None |
| 1.3.6.1.4.1.1795.2.24.2.9 | pdn-traps | 3 | 10 | None |
| 1.3.6.1.4.1.1795.2.24.2.10 | pdn-control, pdnControl | 13 | 135 | This MIB Module allow a user to reset a device in the DSLAM, as well as perform various operations related to the storage and ret… |
| 1.3.6.1.4.1.1795.2.24.2.11 | pdn-ipInjection | 1 | 7 | None |
| 1.3.6.1.4.1.1795.2.24.2.12 | pdn-ip | 4 | 129 | None |
| 1.3.6.1.4.1.1795.2.24.2.13 | pdn-rmon | 2 | 34 | None |
| 1.3.6.1.4.1.1795.2.24.2.14 | pdn-fileXfer | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.15 | pdn-feature | 2 | 4 | None |
| 1.3.6.1.4.1.1795.2.24.2.16 | pdn-diagnostics | 2 | 103 | None |
| 1.3.6.1.4.1.1795.2.24.2.17 | pdn-dns | 2 | 18 | None |
| 1.3.6.1.4.1.1795.2.24.2.18 | pdn-ether | 2 | 22 | This MIB contains objects that are used to configure ethernet interfaces. |
| 1.3.6.1.4.1.1795.2.24.2.19 | pdn-socket | 2 | 15 | None |
| 1.3.6.1.4.1.1795.2.24.2.20 | pdn-time | 2 | 16 | None |
| 1.3.6.1.4.1.1795.2.24.2.21 | pdn-bridge | 2 | 31 | None |
| 1.3.6.1.4.1.1795.2.24.2.22 | pdn-domain | 2 | 42 | None |
| 1.3.6.1.4.1.1795.2.24.2.23 | pdn-filter | 2 | 118 | None |
| 1.3.6.1.4.1.1795.2.24.2.24 | pdn-dslam | 2 | 77 | The DSLAM MIB. This MIB is specific to portcards and DSLAM configuration/stats for MCC and the portcards. The objects defined in … |
| 1.3.6.1.4.1.1795.2.24.2.25 | pdn-radius | 2 | 14 | None |
| 1.3.6.1.4.1.1795.2.24.2.26 | pdn-inet | 2 | 19 | This mib is used to configure ip address of some interface |
| 1.3.6.1.4.1.1795.2.24.2.27 | pdn-arp | 2 | 57 | This MIB contains objects that are used to configure ARP entries and display ARP information. |
| 1.3.6.1.4.1.1795.2.24.2.28 | pdn-devStats | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.29 | pdn-dhcp | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.30 | pdn-nat | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.31 | pdn-syslog | 2 | 38 | None |
| 1.3.6.1.4.1.1795.2.24.2.32 | pdn-dialControl | 1 | 31 | None |
| 1.3.6.1.4.1.1795.2.24.2.33 | pdn-devNetTiming | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.34 | pdnIPSec | 1 | 79 | This MIB contains objects that are used to configure vpn ipsec manula keys. |
| 1.3.6.1.4.1.1795.2.24.2.35 | mpeEntitySensor | 3 | 30 | The MPE-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable. This mib is cop… |
| 1.3.6.1.4.1.1795.2.24.2.36 | pdnStackable | 3 | 34 | This MIB contains objects that are used for configuration and statistics reporting things that are unique to a stackable product. |
| 1.3.6.1.4.1.1795.2.24.2.38 | pdnSpectrumMgr | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.39 | pdn-dot1q | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.40 | pdnLinkFaultMgmt | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.41 | pdnEntityRedundancy | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.42 | pdnLinkLoadSharing | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.43 | pdnAtmBridgeIwfMIB | 3 | 13 | This MIB contains objects that are used for monitoring and controlling the ATM/Bridge Interworking Function. |
| 1.3.6.1.4.1.1795.2.24.2.44 | pdnMpdExt | 0 | 0 | None |
| 1.3.6.1.4.1.1795.2.24.2.45 | pdnEntitySensorExtMIB | 4 | 20 | This MIB module is a supplement to the ENTITY-SENSOR-MIB, RFC 3433. |
| 1.3.6.1.4.1.1795.2.24.2.46 | pdnVlanMIB | 4 | 16 | This MIB module contains objects pertaining to VLANs. |
| 1.3.6.1.4.1.1795.2.24.2.47 | pdnIgmpStdExtMIB | 4 | 27 | This MIB module is a supplement to the IGMP-STD-MIB. |
| 1.3.6.1.4.1.1795.2.24.2.48 | pdnIpMcastMIB | 4 | 17 | This MIB contains the objects pertaining to the configuration and maintenance of the Internet Group Management Protocol (IGMP) a… |