| ctIFRemap2SourceSlot |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.1 |
|
The slot combined with the ctIFRemap2SourcePort which will
have all packets redirected to the destination port as defined
by ctIFRemap2DestSlot and ctIFRemap2DestPort.
|
| ctIFRemap2SourcePort |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.2 |
|
The port combined with the ctIFRemap2SourceSlot which will
have all packets redirected to the destination port as defined
by ctIFRemap2DestSlot and ctIFRemap2DestPort.
|
| ctIFRemap2DestSlot |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.3 |
|
The slot combined with the ctIFRemap2DestPort which will
see all packets redirected from ctIFRemap2SourceSlot and
ctIFRemap2SourcePort.
|
| ctIFRemap2DestPort |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.4 |
|
The port combined with the ctIFRemap2DestSlot which will
see all packets redirected from ctIFRemap2SourceSlot and
ctIFRemap2SourcePort.
|
| ctIFRemap2Status |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.5 |
|
Defines the status of the ifremap entry. Setting
ctIFRemap2Status to a value of enable(1) has the effect of
creating an entry in the table when it does not already exist.
Setting ctIFRemap2Status to a value of disable(2) disables the
entry and deletes the row from the table. Therefore this
table only contains entries that are active.
|
| ctIFRemap2PhysicalErrors |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.6 |
|
Enable or disable remapping of physical errors. This object
controls whether or not frames with physical errors should be
remapped out the destination port for this entry. By default,
this will be enabled when an entry is created.
NOTE: This action is always superseded by the value of
ctIFRemap2PhysErrsCapable for either the source or destination
port specified in this remap entry. If a port is not
physically capable of transmitting or receiving error frames,
then this object will return unsupported(3) and the value
cannot be changed.
|
| ctIFRemap2EgressType |
.1.3.6.1.4.1.52.4.1.1.14.1.1.1.7 |
|
Defines how each packet will be tagged when sent out the
ctIFRemap2DestPort. Setting ctIFRemap2EgressType to normal(1)
will set packets to be sent out as they are seen by
ctIFRemap2SourcePort. Setting ctIFRemap2EgressType to
alwaysTagged(2) will set packets to always be sent out
ctIFRemap2DestSlot and ctIFRemap2DestPort with a tag. Setting
ctIFRemap2EgressType to alwaysUntagged(3) will set packets to always
be sent out ctIFRemap2DestSlot and ctIFRemap2DestPort without a tag.
If the module is not configured to support packet tagging (i.e. 802.1d
bridge mode) then setting this object to alwaysTagged(2) or
alwaysUntagged(3) will return a BAD-VALUE error.
|
| ctIFRemap2PortSlot |
.1.3.6.1.4.1.52.4.1.1.14.1.2.1.1 |
|
Defines the slot in which the remap capable module resides.
In the case of a stand-alone device the slot will always be 1.
|
| ctIFRemap2PortIndex |
.1.3.6.1.4.1.52.4.1.1.14.1.2.1.2 |
|
Defines an port that is remappable or is able to accept a
remapped packet. Ideally indices will start with 1 and will
be numbered continuously through the number of available remap
ports. However, this need not necessarily be the case.
Indices may be sparse and begin with any number if desired
for a particular implementation.
|
| ctIFRemap2PortReference |
.1.3.6.1.4.1.52.4.1.1.14.1.2.1.3 |
|
This object returns an OID referencing an object which
uniquely corresponds to this remap port. The only criteria
is that this OID is a leaf, and that it exists and is
accessible. For example, if remap functionality is running
on an 802.1d compliant bridge, remap port #1 could reference
dot1dBasePort.1. Alternatively you could reference a mib2
interface like ifIndex.1 or a Cabletron Secure Fast port.
Mixing these types (some refer to bridge ports, others refer
to SFS ports) is not advised, but not prohibited
|
| ctIFRemap2PhysErrsCapable |
.1.3.6.1.4.1.52.4.1.1.14.1.2.1.4 |
|
Indicate whether the port is incapable of remapping physical
errors. If the capability is supported, this object will
return supported(1). If the capability is unsupported, this
object will return unsupported(2).
|
| ctIFRemap2SlotIndex |
.1.3.6.1.4.1.52.4.1.1.14.1.3.1.1 |
|
Defines the slot in which the remap capable module resides.
In
the case of a stand-alone device the slot will always be 1.
|
| ctIFRemap2SlotMaxRemaps |
.1.3.6.1.4.1.52.4.1.1.14.1.3.1.2 |
|
The maximum number of entries allowed to be sourced from the
module in this slot in the ctIFRemap2Table.
|
| ctIFRemap2SlotMaxRemoteDests |
.1.3.6.1.4.1.52.4.1.1.14.1.3.1.3 |
|
The maximum number of remote destination ports per remote
module. For example, a value of 3 means that I can have no
more than 3 remap destination ports between this module, and
any other given module in the same chassis simultaneously. I
can have multiple source ports remapped to each of the three
remote destination ports. I can also remap to up to three
remote destination ports on each of the other modules in the
chassis simultaneously.
|
| ctIFRemap2VlanSourceSlot |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.1 |
|
The slot combined with the ctIFRemap2VlanSourceVlan which will
have all packets redirected to the destination port as defined
by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort.
|
| ctIFRemap2VlanSourceVlan |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.2 |
|
The vlan combined with the ctIFRemap2VlanSourceSlot which will
have all packets redirected to the destination port as defined
by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort.
|
| ctIFRemap2VlanDestSlot |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.3 |
|
The slot combined with the ctIFRemap2VlanDestPort which will
see all packets redirected from ctIFRemap2VlanSourceSlot and
ctIFRemap2VlanSourceVlan.
|
| ctIFRemap2VlanDestPort |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.4 |
|
The port combined with the ctIFRemap2VlanDestSlot which will
see all packets redirected from ctIFRemap2VlanSourceSlot and
ctIFRemap2VlanSourceVlan.
|
| ctIFRemap2VlanStatus |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.5 |
|
Defines the status of the ifremap vlan entry. Setting
ctIFRemap2VlanStatus to a value of enable(1) has the effect of
creating an entry in the table when it does not already exist.
Setting ctIFRemap2VlanStatus to a value of disable(2) disables the
entry and deletes the row from the table. Therefore this
table only contains entries that are active.
If ctIFRemap2VlanSourceVlan is already being used by another
ctIfRemap2Vlan entry or ctifRemap2 Entry then a set to
ctIFRemap2VlanStatus of value enable(1) will return with a
BAD-VALUE error.
|
| ctIFRemap2VlanEgressType |
.1.3.6.1.4.1.52.4.1.1.14.1.4.1.6 |
|
Defines how each packet will be tagged when sent out the
ctIFRemap2VlanDestPort. Setting ctIFRemap2VlanEgressType to
received(1) will set packets to be sent out ctIFRemap2VlanDestSlot
and ctIFRemap2VlanDestPort exactly as they are received by
ctIFRemap2VlanSourceVlan. Setting ctIFRemap2VlanEgressType to
alwaysTagged(2) will set packets to be sent out
ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort with the
vlan tag associated with ctIFRemap2VlanSourceVlan. If this port
does not have a vlan tag associated with it then all packets will
be remapped without a tag. Setting ctIFRemap2VlanEgressType to
alwaysUntagged(3) will set packets to be sent out
ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort without any
tag reguardless of ctIFRemap2VlanSourceVlan's tagging status.
|
