# Promiscuous Port Details

Port > Configure > Private VLAN > Promiscuous Port Details

This dialog box displays information on the secondary VLAN to primary VLAN remappings on this device's ports.

To view the definition for a particular MIB variable, click the appropriate link from the following list:

- Multi Primary VLAN (cpvlanPromPortMultiPrimaryVlan)

- Secondary Remap (cpvlanPromPortSecondaryRemap)

- Secondary Remap 2k (cpvlanPromPortSecondaryRemap2k)

- Secondary Remap 3k (cpvlanPromPortSecondaryRemap3k)

- Secondary Remap 4k (cpvlanPromPortSecondaryRemap4k)

- Two Way Remap (cpvlanPromPortTwoWayRemapCapable)

The following list specifies buttons in this dialog box, as well as their function:

- Click OK to continue.

- Click Apply to save the changes in the dialog box.

- Click Cancel to close the dialog box.

- Click Refresh to update the contents of the dialog box.

- Click Print to print the contents of the dialog box.

- Click Help to access online help.

Multi Primary VLAN (cpvlanPromPortMultiPrimaryVlan)

Indicates whether all the bits set as secondary VLANs in the corresponding remapping objects (for example, cpvlanPromPortSecondaryRemap) can belong to multiple primary VLANs. If this object is set to "false(2)", the value of cpvlanVlanAssociatedPrimaryVlan for the secondary VLANs with their bits set to "1" in those remapping objects must be the same.

Note: A promiscuous port can remap a secondary VLAN to its associated primary VLAN for outgoing traffic on the fly, as defined for the Private VLAN feature.

Secondary Remap (cpvlanPromPortSecondaryRemap)

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 with VlanIndexOrZero values of 8 through 15; and so on. The most significant bit of each octet is indicated by the lowest value of VlanIndexOrZero in that octet.

A bit can only be set to "1" when it corresponds to a Private VLAN isolated, community, or two-way community VLAN which has already been associated with a primary VLAN. Setting this bit to "1" results in one of the following:

- A secondary VLAN is remapped to its associated primary VLAN for outgoing traffic on the fly.

- A primary VLAN is remapped to its associated secondary VLAN if the secondary VLAN is the two-way community type and the value of cpvlanPromPortTwoWayRemapCapable for this port is set to "true(1)".

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 these octets from the end of this string in order to reduce the size of Set PDUs. An NMS may also omit trailing octets containing the value zero to reduce the size of GetResponse PDUs.

Secondary Remap 2k (cpvlanPromPortSecondaryRemap2k)

A string of octets containing one bit per VLAN for VLANs with VlanIndexOrZero values of 1024 through 2047 in the management domain on this port. The first octet corresponds to VLANs with VlanIndexOrZero values of 1024 through 1031; the second octet to VLANs with VlanIndexOrZero values of 1032 through 1039; and so on. The most significant bit of each octet is indicated by the lowest value of VlanIndexOrZero in that octet.

A bit can only be set to "1" when it corresponds to a Private VLAN isolated, community, or two-way community VLAN which has already been associated with a primary VLAN. Setting this bit to "1" results in one of the following:

- A secondary VLAN is remapped to its associated primary VLAN for outgoing traffic on the fly.

- A primary VLAN is remapped to its associated secondary VLAN if the secondary VLAN is the two-way community type and the value of cpvlanPromPortTwoWayRemapCapable for this port is set to "true(1)".

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 these octets from the end of this string in order to reduce the size of Set PDUs. An NMS may also omit trailing octets containing the value zero to reduce the size of GetResponse PDUs.

Note: This object is only instantiated on devices which support values ranging from the value of VlanIndexOrZero to 4095.

Secondary Remap 3k (cpvlanPromPortSecondaryRemap3k)

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 with VlanIndexOrZero values of 2056 through 2063; and so on. The most significant bit of each octet is indicated by the lowest value of VlanIndexOrZero in that octet.

A bit can only be set to "1" when it corresponds to a Private VLAN isolated, community, or two-way community VLAN which has already been associated with a primary VLAN. Setting this bit to "1" results in one of the following:

- A secondary VLAN is remapped to its associated primary VLAN for outgoing traffic on the fly.

- A primary VLAN is remapped to its associated secondary VLAN if the secondary VLAN is the two-way community type and the value of cpvlanPromPortTwoWayRemapCapable for this port is set to "true(1)".

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 these octets from the end of this string in order to reduce the size of Set PDUs. An NMS may also omit trailing octets containing the value zero to reduce the size of GetResponse PDUs.

Note: This object is only instantiated on devices which support values ranging from the value of VlanIndexOrZero to 4095.

Secondary Remap 4k (cpvlanPromPortSecondaryRemap4k)

A string of octets containing one bit per VLAN for VLANs with VlanIndexOrZero values of 3072 through 4095 in the management domain on this port. The first octet corresponds to VLANs with VlanIndexOrZero values of 3072 through 3079; the second octet to VLANs with VlanIndexOrZero values of 3080 through 3087; and so on. The most significant bit of each octet is indicated by the lowest value of VlanIndexOrZero in that octet.

A bit can only be set to "1" when it corresponds to a Private VLAN isolated, community, or two-way community VLAN which has already been associated with a primary VLAN. Setting this bit to "1" results in one of the following:

- A secondary VLAN is remapped to its associated primary VLAN for outgoing traffic on the fly.

- A primary VLAN is remapped to its associated secondary VLAN if the secondary VLAN is the two-way community type and the value of cpvlanPromPortTwoWayRemapCapable for this port is set to "true(1)".

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 these octets from the end of this string in order to reduce the size of Set PDUs. An NMS may also omit trailing octets containing the value zero to reduce the size of GetResponse PDUs.

Note: This object is only instantiated on devices which support values ranging from the value of VlanIndexOrZero to 4095.

Two Way Remap (cpvlanPromPortTwoWayRemapCapable)

Indicates whether a port is capable of remapping primary VLANs to the two-way community VLANs associated with them for the Private VLAN feature. When this object is set to " false(2)", a promiscuous port can perform only one-way remappings of secondary VLANs to their associated primary VLANs. When this object is set to " true(1)", a promiscuous port can also perform remappings of primary VLANs to the two-way community VLANs associated with them.