MY-PRIVATE-VLAN-MIB :: mypvlanPromPortSecondaryRemap

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

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

mypvlanPromPortSecondaryRemap

Module: MY-PRIVATE-VLAN-MIB

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

OID (numeric): 1.3.6.1.4.1.171.10.97.2.44.1.2.2.1.2

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-write

Description: A string of octets containing one bit per VLAN in the management domain on this port. The first octet corresponds to VLANs with VlanIndexOrZero values of 0 through 7; the second octet to VLANs 8 through 15; 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, 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.

What is mypvlanPromPortSecondaryRemap?

This read-write bitmap, one bit per VLAN, marks which secondary, isolated or community, VLANs are enabled on this promiscuous port for remapping to its configured primary VLAN, covering VLAN IDs in the lower range of the management domain. A bit can only be set for a VLAN that is already an isolated or community type associated with a primary VLAN, enforcing that the promiscuous port only remaps VLANs that are validly configured as private secondary VLANs. Setting the bit for VLAN 201 in mypvlanPromPortSecondaryRemap would enable that isolated VLAN's traffic to be remapped through this promiscuous port to its associated primary VLAN.

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.2
snmpwalk -v2c -c public <target> MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap

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.2.1
snmpget -v2c -c public <target> MY-PRIVATE-VLAN-MIB::mypvlanPromPortSecondaryRemap.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.2.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::mypvlanPromPortSecondaryRemap 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.2mypvlanPromPortSecondaryRemapMY-PRIVATE-VLAN-MIB