CTRON-IF-REMAP-2-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CTRON-IF-REMAP-2-MIB.
30
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
30 total| Object Name |
|---|
ctIFRemap2Config OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.1.14.1 |
IMPORTS Unknown .1.3.6.1.4.1.52.4.1.1.14.1 |
ctIFRemap2TableThis table provides the ability to remap all frames from one
port onto another port. A port is defined by
ctIFRemap2PortIndex
from the ctIFRemap2PortTable below. Only ports listed in the
ctIFRemap2PortTable are available for remapping.
A given source port may only be mapped to only one destination
port. Once a port is reserved as part of a ctIFRemap2Table entry,
it may not be used in any other ctIFRemap2Table entries (ie. If
remapping port 1 to port 3, then neither port 1 or port 3 may be
used as a ctIFRemap2SourcePort or ctIFRemap2DestPort in another
ctIFRemap2Table entry).
Each row that exists in this table defines such a relationship.
By disabling a row in this table the remapping relationship no
longer exists.
Each entry will be referenced by slot. In the case of a
stand-alone device the slot will always be 1.
If a given relationship cannot be created the set will fail
with a BAD-VALUE error. SEQUENCE OF CtIFRemap2Entry .1.3.6.1.4.1.52.4.1.1.14.1.1 |
ctIFRemap2EntryDescribes a particular ifremap entry. CtIFRemap2Entry .1.3.6.1.4.1.52.4.1.1.14.1.1.1 |
ctIFRemap2SourceSlotThe slot combined with the ctIFRemap2SourcePort which will
have all packets redirected to the destination port as defined
by ctIFRemap2DestSlot and ctIFRemap2DestPort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.1.1.1 |
ctIFRemap2SourcePortThe port combined with the ctIFRemap2SourceSlot which will
have all packets redirected to the destination port as defined
by ctIFRemap2DestSlot and ctIFRemap2DestPort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.1.1.2 |
ctIFRemap2DestSlotThe slot combined with the ctIFRemap2DestPort which will
see all packets redirected from ctIFRemap2SourceSlot and
ctIFRemap2SourcePort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.1.1.3 |
ctIFRemap2DestPortThe port combined with the ctIFRemap2DestSlot which will
see all packets redirected from ctIFRemap2SourceSlot and
ctIFRemap2SourcePort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.1.1.4 |
ctIFRemap2StatusDefines 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.rw Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.1.1.5 |
ctIFRemap2PhysicalErrorsEnable 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.rw Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.1.1.6 |
ctIFRemap2EgressTypeDefines 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.rw Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.1.1.7 |
ctIFRemap2PortTableThis table holds all valid ports that are remappable or
able to accept a remapped packet. SEQUENCE OF CtIFRemap2PortEntry .1.3.6.1.4.1.52.4.1.1.14.1.2 |
ctIFRemap2PortEntryDescribes a particular supported remappable port. CtIFRemap2PortEntry .1.3.6.1.4.1.52.4.1.1.14.1.2.1 |
ctIFRemap2PortSlotDefines the slot in which the remap capable module resides.
In the case of a stand-alone device the slot will always be 1.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.2.1.1 |
ctIFRemap2PortIndexDefines 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.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.2.1.2 |
ctIFRemap2PortReferenceThis 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 prohibitedro OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.1.14.1.2.1.3 |
ctIFRemap2PhysErrsCapableIndicate 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).ro Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.2.1.4 |
ctIFRemap2SlotTableThis table contains all information pertaining to the
abilities or limitations of a particular remap capable
module. SEQUENCE OF CtIFRemap2SlotEntry .1.3.6.1.4.1.52.4.1.1.14.1.3 |
ctIFRemap2SlotEntryDescribes a particular entry in the ctIFRemap2SlotTable.
Each entry is indexed by the physical slot in which the
module resides. CtIFRemap2SlotEntry .1.3.6.1.4.1.52.4.1.1.14.1.3.1 |
ctIFRemap2SlotIndexDefines the slot in which the remap capable module resides.
In
the case of a stand-alone device the slot will always be 1.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.3.1.1 |
ctIFRemap2SlotMaxRemapsThe maximum number of entries allowed to be sourced from the
module in this slot in the ctIFRemap2Table.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.3.1.2 |
ctIFRemap2SlotMaxRemoteDestsThe 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.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.3.1.3 |
ctIFRemap2VlanTableThis table provides the ability to remap all frames from any
port on a particular vlan to a specific destination port.
Each row that exists in this table defines such a relationship.
By disabling a row in this table the remapping relationship no
longer exists.
Multiple vlans may be mapped to a given destination port
(ie. vlan 11 and vlan 35 may both remap to port 10).
A port is defined by ctIFRemap2PortIndex in the ctIFRemap2PortTable,
above. Only ports listed in the ctIFRemap2PortTable are available
for remapping. A vlan is defined by ctVlanVID in the
ctVlanConfigTable. Only vlans listed in the ctVlanConfigTable are
available for remapping.
Each entry will be referenced by slot. In the case of a
stand-alone device the slot will always be 1.
If a given relationship cannot be created the set will fail
with a BAD-VALUE error. SEQUENCE OF CtIFRemap2VlanEntry .1.3.6.1.4.1.52.4.1.1.14.1.4 |
ctIFRemap2VlanEntryDescribes a particular ifremap Vlan entry. CtIFRemap2VlanEntry .1.3.6.1.4.1.52.4.1.1.14.1.4.1 |
ctIFRemap2VlanSourceSlotThe slot combined with the ctIFRemap2VlanSourceVlan which will
have all packets redirected to the destination port as defined
by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.4.1.1 |
ctIFRemap2VlanSourceVlanThe vlan combined with the ctIFRemap2VlanSourceSlot which will
have all packets redirected to the destination port as defined
by ctIFRemap2VlanDestSlot and ctIFRemap2VlanDestPort.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.4.1.2 |
ctIFRemap2VlanDestSlotThe slot combined with the ctIFRemap2VlanDestPort which will
see all packets redirected from ctIFRemap2VlanSourceSlot and
ctIFRemap2VlanSourceVlan.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.4.1.3 |
ctIFRemap2VlanDestPortThe port combined with the ctIFRemap2VlanDestSlot which will
see all packets redirected from ctIFRemap2VlanSourceSlot and
ctIFRemap2VlanSourceVlan.ro INTEGER .1.3.6.1.4.1.52.4.1.1.14.1.4.1.4 |
ctIFRemap2VlanStatusDefines 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.rw Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.4.1.5 |
ctIFRemap2VlanEgressTypeDefines 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.rw Enumeration .1.3.6.1.4.1.52.4.1.1.14.1.4.1.6 |