CTRON-IF-REMAP-2-MIB

File: CTRON-IF-REMAP-2-MIB.mib (19941 bytes)

Imported modules

RFC-1212 CTRON-MIB-NAMES

Imported symbols

OBJECT-TYPE ctIFRemap2

Defined Types

CtIFRemap2Entry  
SEQUENCE    
  ctIFRemap2SourceSlot INTEGER
  ctIFRemap2SourcePort INTEGER
  ctIFRemap2DestSlot INTEGER
  ctIFRemap2DestPort INTEGER
  ctIFRemap2Status INTEGER
  ctIFRemap2PhysicalErrors INTEGER
  ctIFRemap2EgressType INTEGER

CtIFRemap2PortEntry  
SEQUENCE    
  ctIFRemap2PortSlot INTEGER
  ctIFRemap2PortIndex INTEGER
  ctIFRemap2PortReference OBJECT IDENTIFIER
  ctIFRemap2PhysErrsCapable INTEGER

CtIFRemap2SlotEntry  
SEQUENCE    
  ctIFRemap2SlotIndex INTEGER
  ctIFRemap2SlotMaxRemaps INTEGER
  ctIFRemap2SlotMaxRemoteDests INTEGER

CtIFRemap2VlanEntry  
SEQUENCE    
  ctIFRemap2VlanSourceSlot INTEGER
  ctIFRemap2VlanSourceVlan INTEGER
  ctIFRemap2VlanDestSlot INTEGER
  ctIFRemap2VlanDestPort INTEGER
  ctIFRemap2VlanStatus INTEGER
  ctIFRemap2VlanEgressType INTEGER

Defined Values

ctIFRemap2Config 1.3.6.1.4.1.52.4.1.1.14.1
OBJECT IDENTIFIER    

ctIFRemap2Table 1.3.6.1.4.1.52.4.1.1.14.1.1
This 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.
OBJECT-TYPE    
  SEQUENCE OF  
    CtIFRemap2Entry

ctIFRemap2Entry 1.3.6.1.4.1.52.4.1.1.14.1.1.1
Describes a particular ifremap entry.
OBJECT-TYPE    
  CtIFRemap2Entry  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

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.
OBJECT-TYPE    
  INTEGER enable(1), disable(2), unsupported(3)  

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.
OBJECT-TYPE    
  INTEGER normal(1), alwaysTagged(2), alwaysUntagged(3)  

ctIFRemap2PortTable 1.3.6.1.4.1.52.4.1.1.14.1.2
This table holds all valid ports that are remappable or able to accept a remapped packet.
OBJECT-TYPE    
  SEQUENCE OF  
    CtIFRemap2PortEntry

ctIFRemap2PortEntry 1.3.6.1.4.1.52.4.1.1.14.1.2.1
Describes a particular supported remappable port.
OBJECT-TYPE    
  CtIFRemap2PortEntry  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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
OBJECT-TYPE    
  OBJECT IDENTIFIER  

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).
OBJECT-TYPE    
  INTEGER supported(1), unsupported(2)  

ctIFRemap2SlotTable 1.3.6.1.4.1.52.4.1.1.14.1.3
This table contains all information pertaining to the abilities or limitations of a particular remap capable module.
OBJECT-TYPE    
  SEQUENCE OF  
    CtIFRemap2SlotEntry

ctIFRemap2SlotEntry 1.3.6.1.4.1.52.4.1.1.14.1.3.1
Describes a particular entry in the ctIFRemap2SlotTable. Each entry is indexed by the physical slot in which the module resides.
OBJECT-TYPE    
  CtIFRemap2SlotEntry  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

ctIFRemap2VlanTable 1.3.6.1.4.1.52.4.1.1.14.1.4
This 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.
OBJECT-TYPE    
  SEQUENCE OF  
    CtIFRemap2VlanEntry

ctIFRemap2VlanEntry 1.3.6.1.4.1.52.4.1.1.14.1.4.1
Describes a particular ifremap Vlan entry.
OBJECT-TYPE    
  CtIFRemap2VlanEntry  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER  

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.
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

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.
OBJECT-TYPE    
  INTEGER received(1), alwaysTagged(2), alwaysUntagged(3)