MY-PRIVATE-VLAN-MIB :: mypvlanPromPortSecondaryRemap3k

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › MY-PRIVATE-VLAN-MIB › mypvlanPromPortSecondaryRemap3k

mypvlanPromPortSecondaryRemap3k

Module: MY-PRIVATE-VLAN-MIB

OID (symbolic): MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap3k

OID (numeric): 1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.4

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: A string of octets containing one bit per VLAN for VLANs with VlanIndexOrZero values of 2048 through 3071 in the management domain on this port. The first octet corresponds to VLANs with VlanIndexOrZero values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndexOrZero in that octet.

A bit can only be set to '1' when the bit is corresponding to a VLAN of Private VLAN isolated or community type which has already been associated with a primary VLAN.

Note that if the length of this string is less than 128 octets, any 'missing' octets are assumed to contain the value zero. An NMS may omit any zero-valued octets from the end of this string in order to reduce SetPDU size, and the agent may also omit zero-valued trailing octets, to reduce the size of GetResponse PDUs.

This object is only instantiated on devices which support the range of VlanIndexOrZero up to 4095.

What is mypvlanPromPortSecondaryRemap3k?

This read-write bitmap extends the secondary-VLAN remap coverage to VLAN IDs 2048 through 3071 on this promiscuous port. Like the other remap bitmaps, only bits corresponding to VLANs already configured as isolated or community type with a primary VLAN association can be set, and it exists only on devices supporting the full 4095-VLAN range. Setting the bit for VLAN 2500 in mypvlanPromPortSecondaryRemap3k would enable that secondary VLAN's traffic to be remapped through this promiscuous port.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.4
snmpwalk -v2c -c public <target> MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap3k

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.4.1
snmpget -v2c -c public <target> MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap3k.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.4.1 s <value>

Start monitoring D-Link managed switch (Private VLAN feature) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap3k OID value, configure state conditions and alerts, and monitor any D-Link managed switch (Private VLAN feature) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.171d_linkDE1500-MIB
1.3.6.1.4.1.171.10dlink_productsDES-1226G-MIB
1.3.6.1.4.1.171.10.97switchMibMY-SMI
1.3.6.1.4.1.171.10.97.2myMgmtMY-SMI
Numeric OIDNameModule
1.3.6.1.4.1.171.10.97.2.44myPrivateVlanMIBMY-PRIVATE-VLAN-MIB
1.3.6.1.4.1.171.10.97.2.44.1mypvlanMIBObjectsMY-PRIVATE-VLAN-MIB
1.3.6.1.4.1.171.10.97.2.44.1.2mypvlanPortObjectsMY-PRIVATE-VLAN-MIB
1.3.6.1.4.1.171.10.97.2.44.1.2.2mypvlanPromPortTableMY-PRIVATE-VLAN-MIB
1.3.6.1.4.1.171.10.97.2.44.1.2.2.1mypvlanPromPortEntryMY-PRIVATE-VLAN-MIB
1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.4mypvlanPromPortSecondaryRemap3kMY-PRIVATE-VLAN-MIB