TN-MGMT-MIB: View SNMP OID List / Download MIB

The mib module for managing all transition products.

A tnDMIRxIntrusionEvt event is sent if the tnDMIRxPowerLevel falls below the tnDMIRxPwrLvlPreset indicating an intrusion on the fiber.

A tnDMIRxPowerEvt event is sent when there is a warning or alarm on Rx Power.

A tnDMITxPowerEvt event is sent when there is a warning or alarm on Tx Power.

A tnDMITxBiasEvt event is sent when there is a warning or alarm on Tx Bias current.

A tnDMITemperatureEvt event is sent when there is a warning or alarm on DMI temperature.

when the device lost power, this dying gasp trap will be sent out.

This event is trigger when a port which has Limit control on dynamic MAC is enabled and the limit is reached.

A tnMgmtMibBoardTmpNotif will be sent out will be sent out when temperature of board is out of controlled range (TO BE CONTINUED).

A tnMgmtMibCPUTmpNotif will be sent out when temperature of CPU is out of controlled range (TO BE CONTINUED).

This table supplements the ENTITY-MIB for each device managed by this Agent.

A entry in the table contains additional information related to a device.

A user-defined string for this device. This can be used to unique identity the device for the user.Some devices may support less than the maximum length specified for this variable.

The device's system uptime in milliseconds if supported, 0 otherwise.

The device's 'tnDevSysUptime' can be reset. Enumeration: 'reset': 1, 'doNothing': 2.

The device can be reset or rebooted by setting this mib variable. running(1) - is a read-only value returned when the system is operational. coldStart(2) - This resets all the system states and reinitializes the system. All configuration is saved during a restart. warmStart(3) - The system restarts but the states are not initialized. Some devices may not support this operation. Enumeration: 'running': 1, 'warmStart': 3, 'coldStart': 2.

This number of ports on this device.

This mib variable can reset all system counters including port counters. Enumeration: 'perform': 1, 'doNothing': 2.

This mib variable can reset all system configuration to as it was shipped from the factory. Enumeration: 'perform': 1, 'doNothing': 2.

This shows the configuration mode of the device. The device may have a jumper or switch that disables software management of the device. When Configuration Mode is hardware(2), the devices take some of the configurations from dip switches or jumpers on the device. In software(1) mode all configurations are controlled by management. Enumeration: 'hardware': 2, 'software': 1.

This shows the configuration mode of the device's console access. Some of the device's have console interface through a USB port or a serial RS232 port through which the command line interface is accessible. When the device is deployed at a remote site, the customer can choose to disable this interface for security. Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

This shows the configuration about the mode of shared port. internal : Shared Port used as internal external : Shared Port used as external Enumeration: 'internal': 1, 'external': 2.

This table shows the information of hardware.

A entry in the table contains additional information related to a device.

Indicates the ID of Chip.

Indicates the reversion of Board .

Indicates the version of FPGA.

Indicates the temperature of Board.

Indicates the temperature of CPU.

This table supplements the ENTITY-MIB for 2-port devices managed by this Agent.

A entry in the table contains additional information related to a device.

Devices which support this feature allow write for enabling or disabling the feature. Most 2-port devices support this feature. Link pass through when enabled monitors the link status of one port, any change in its operational state is passed on to the other port and vice-versa. For eg: If Port 1 becomes operationally down, the Port 2 is brought down. When Port 1 becomes operational again, Port 2 is also brought up. Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

Devices which support this feature allow write for enabling or disabling the feature. Some of the 2-port devices which are capable of remote management of a similiar device support this feature. This needs a back to back setup of the same type of device. Transparent Link pass through when enabled monitors the link status of one port on device A, any change in its operational state is passed on to the peer device B port to bring down its far end port and vice-versa. For eg: If the devices are connected by Port 2 on each. If Device A - Port 1 becomes operationally down, the Device B - Port 1 is brought down. The devices can communicate with each other but the link condition is passed on so a network administrator can know of the fault condition. Port 2 is the port that is monitored. Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

Devices which support this feature allow write for enabling or disabling the feature. Some of the 2-port devices which are capable of remote management of a similiar device support this feature. This is typically supported by devices which support 'tnSysTransparentLPT'. Selective Link pass through when enabled monitors the link status of one port on device A, any change in its operational state is passed on to the device's other port to bring down its link and vice-versa. It is similiar to 'tnSysLinkPassThro' except it only works in one direction from Port 1 to Port 2 or Port 2 to Port 1 not both directions. Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

This mib variable is applicable only when the device supports 'tnSysSelectiveLPT' and/or 'tnSysTransparentLPT'. This determines which port is monitored for activating the link pass through. The value is the port number.

This mib variable is applicable only for some of the devices. When set to enabled(1), loss of fiber receive causes twisted pair interface to be disabled, and loss twisted pair link causes fiber transmit to be disabled. Warning: Must not be enabled at both ends of a fiber Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

This table supplements the ENTITY-MIB for 2-port devices managed by this Agent.

A entry in the table contains additional information related to a device.

Devices which support this feature allow write for enabling or disabling the feature. When a device detects the power is going to be lost, a system dying gasp procedure will be triggered internally. If this tnSysDyingGaspTrap is set to enabled, a tnDyingGaspEvt will be sent out. Other events may also be sent out in this procedure, e.g. LOAM event. The LOAM event (enabled by dot3OamDyingGaspEnable) and this Trap event will be processed at the same time if both enabled. If LOAM is enabled in multiple ports, the LOAM event will be sent out one port by one port begginning from the smaller port number (e.g. smallest one is copper port, port 1) If multiple trap servers are enabled, the trap will be sent out one server by one server begining from the server 1. Depends on different hardware, the dying gasp's power may be not enough for sending out all the LOAM event and Traps. So, it is suggested that users should keep as few targets as possible. Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

This table contols the device MAC address learning ability.

A entry in the table contains additional information related to a device.

This indicates the port's state on MAC learning. If the bit corresponding to the port is set, then learning is enabled else it is disabled.

This table supplements the ifTable in IF-MIB and ifMauAutoNegTable in MAU-MIB for Ethernet interfaces.

A entry in the table contains additional information related to an Ethernet interface.

When autonegotiation is disabled, this can be used to set the interface speed. Refer the MAU-MIB is used for autonegotiation configuration.

When autonegotiation is disabled, this can be used to set the interface duplex. Refer the MAU-MIB is used for autonegotiation configuration.

This shows the capability of the Ethernet interface to do MDI/MDIX Autocross.

If this Ethernet interface supports MDI/MDIX Autocross, then the mode can be set in this mib variable.

This shows the capability of the Ethernet interface to do Far End Fault Indication.

If this Ethernet interface supports Far End Fault Indication, then it can be set in this mib variable. Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

This shows the capability of the Ethernet interface to support different PHY modes.

This shows Ethernet PHY mode of this interface.

This is used to set the Ethernet PHY mode of this interface if 'tnEthPhyModeChangeCap' is true.

The maximum frame size in bytes that is allowed on this ethernet interface. Not all devices can support write capability.

This table has entries for interfaces which are capable of having Diagnostic monitoring capabilities.

A entry in the table represents diagnostic monitoring for an interface.

The DMI connector type indicates the external optical or electrical cable connector provided as the interface. From SFF 8472 Rev 9.5 Value Description of connector 00h Unknown or unspecified 01h SC 02h Fibre Channel Style 1 copper connector 03h Fibre Channel Style 2 copper connector 04h BNC/TNC 05h Fibre Channel coaxial headers 06h FiberJack 07h LC 08h MT-RJ 09h MU 0Ah SG 0Bh Optical pigtail 0C-1Fh Reserved 20h HSSDC II 21h Copper Pigtail 22h-7Fh Reserved 80-FFh Vendor specific

Bitrate in units of 100Mbps.

Specifies the link length that is supported by the transceiver while operating in single mode fiber. The value is in units of KM.

Specifies the link length that is supported by the transceiver while operating in single mode fiber. The value is in units of 100m.

Specifies the link length that is supported by the transceiver while operating in 50 micron multi mode fiber. The value is in units of 10m.

Specifies the link length that is supported by the transceiver while operating in 62.5 micron multi mode fiber. The value is in units of 10m.

Specifies the link length that is supported by the transceiver while operating in copper cable. The value is in units of meters.

Specifies the physical device. The table below from SFF-8472 Rev 9.5 Standard gives description for the values. 00h Unknown or unspecified 01h GBIC 02h Module/connector soldered to motherboard 03h SFP 04-7Fh Reserved 80-FFh Vendor specific.

The Nominal transmitter output wavelength at room temperature. The units in nm

Temperature of fiber transceiver in tenths of degrees C.

.

Transmit bias current on local fiber interface, in microamperes.

. Enumeration: 'highAlarm': 7, 'normal': 1, 'lowAlarm': 6, 'highWarn': 4, 'lowWarn': 3, 'notSupported': 2.

DMI: Diagnostic Monitoring Interface for fiber transceivers. Transmit power on local fiber measured in microwatts.

. Enumeration: 'highAlarm': 7, 'normal': 1, 'lowAlarm': 6, 'highWarn': 4, 'lowWarn': 3, 'notSupported': 2.

DMI: Diagnostic Monitoring Interface for fiber transceivers. Receive power on local fiber measured in microwatts.

. Enumeration: 'highAlarm': 7, 'normal': 1, 'lowAlarm': 6, 'highWarn': 4, 'lowWarn': 3, 'notSupported': 2.

A preset level for Rx Power on the Fiber port, if the DMI read value falls below the preset value, an intrusion is detected, and a trap is generated.

The vendor name is a 16 character field that contains ASCII characters. The vendor name shall be the full name of the corporation, a commonly accepted abbreviation of the name of the corporation, the SCSI company code for the corporation, or the stock exchange code for the corporation.

The vendor organizationally unique identifier field (vendor OUI) is a 3-byte field that contains the IEEE Company Identifier for the vendor. A value of all zero in the 3-byte field indicates that the Vendor OUI is unspecified.

The vendor part number is a 16-byte field that contains ASCII characters, defining the vendor part number or product name. A value of all zero in the 16-byte field indicates that the vendor PN is unspecified.

The vendor revision number is a 4-byte field that contains ASCII characters, defining the vendor product revision number. A value of all zero in the 4-byte field indicates that the vendor revision is unspecified.

The vendor serial number is a 16 character field that contains ASCII characters, defining the vendor’s serial number for the transceiver. A value of all zero in the 16-byte field indicates that the vendor SN is unspecified.

This table has entries for bandwidth allocation for each interface.

Each entry limits the bandwidth of an interface.

This mib variable allows the user to select what bytes in a frame is to be counted. countAllLayer1(1) - Counts all Layer 1 bytes. Preamble(8 bytes) + DA to CRC + IFG (12 bytes) countAllLayer2(2) - Counts all Layer 2 bytes. Frame's DA to CRC countAllLayer3(3) - Counts all Layer 3 bytes. Frame's DA to CRC - 18 (DA+SA+EtherType+CRC) - 4 (If vlan tagged) Enumeration: 'countAllLayer1': 1, 'countAllLayer3': 3, 'countAllLayer2': 2.

Ingress bandwidth limiting in bits per second, but not faster than port speed. This is the Committed Information rate (CIR) on this interface for Ingress. Traffic rate which go over the the CIR are discarded.. Enumeration: 'rate350M': 48, 'rate128K': 3, 'rate70M': 22, 'rate256K': 5, 'rate90M': 36, 'rate768K': 9, 'rate400M': 27, 'rate60M': 21, 'rate45M': 40, 'rate384K': 7, 'rate6M': 14, 'rate250M': 47, 'rate600M': 29, 'rate85M': 44, 'rate2M': 11, 'rate100M': 24, 'rate8M': 15, 'rate850M': 53, 'rate10M': 16, 'rate4M': 13, 'rate750M': 52, 'rate65M': 42, 'rate75M': 43, 'rate192K': 4, 'rate35M': 39, 'noLimit': 1, 'rate320K': 6, 'rate800M': 31, 'rate40M': 19, 'rate50M': 20, 'rate550M': 50, 'rate95M': 45, 'rate300M': 26, 'rate80M': 23, 'rate1M': 10, 'rate7M': 34, 'rate15M': 37, 'rate3M': 12, 'rate150M': 46, 'rate450M': 49, 'rate900M': 32, 'rate9M': 35, 'rate25M': 38, 'rate30M': 18, 'rate650M': 51, 'rate500M': 28, 'rate512K': 8, 'rate20M': 17, 'rate5M': 33, 'rate950M': 54, 'rate700M': 30, 'rate64K': 2, 'rate200M': 25, 'rate55M': 41.

Egress bandwidth limiting in bits per second, but not faster than port speed. Traffic which are over the rate are discarded. Enumeration: 'rate350M': 48, 'rate128K': 3, 'rate70M': 22, 'rate256K': 5, 'rate90M': 36, 'rate768K': 9, 'rate400M': 27, 'rate60M': 21, 'rate45M': 40, 'rate384K': 7, 'rate6M': 14, 'rate250M': 47, 'rate600M': 29, 'rate85M': 44, 'rate2M': 11, 'rate100M': 24, 'rate8M': 15, 'rate850M': 53, 'rate10M': 16, 'rate4M': 13, 'rate750M': 52, 'rate65M': 42, 'rate75M': 43, 'rate192K': 4, 'rate35M': 39, 'noLimit': 1, 'rate320K': 6, 'rate800M': 31, 'rate40M': 19, 'rate50M': 20, 'rate550M': 50, 'rate95M': 45, 'rate300M': 26, 'rate80M': 23, 'rate1M': 10, 'rate7M': 34, 'rate15M': 37, 'rate3M': 12, 'rate150M': 46, 'rate450M': 49, 'rate900M': 32, 'rate9M': 35, 'rate25M': 38, 'rate30M': 18, 'rate650M': 51, 'rate500M': 28, 'rate512K': 8, 'rate20M': 17, 'rate5M': 33, 'rate950M': 54, 'rate700M': 30, 'rate64K': 2, 'rate200M': 25, 'rate55M': 41.

This table has entries for interfaces which are capable of redundancy with another port.

A entry in the table represents redundancy configuration.

This feature is applicable in the devices that have 2 fiber ports and support redundancy on the ports. When set to enabled, the primary and backup fiber ports are assumed to be connected to the same destination. Only one of these paths will be active at any given time, and the configuration settings kept in sync between the ports. When set to disabled, the primary and backup ports are assumed to be connected to different destinations, and lose their special functions. Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

This mib variable is applicable only if 'tnIfRedundancy' is enabled. When there is a failure in the primary and secondary fiber takes over, this determines what happens when primary comes back again. Does the link switch back to primary or the secondary takes over as the primary link. Enumeration: 'notApplicable': 3, 'noRevert': 2, 'revert': 1.

The port's ifIndex which take part in the redundancy.

The port's ifIndex which take part in the redundancy.

This mib variable is applicable only if 'tnFiberRedundancy' is enabled. This indicates the current active port that is operational as the primary link.

This table has entries each interface and corresponding list of ports that it can forward.

A entry in the table represents forwarding configuration of each interface.

This maps the ifIndex to the Port physical number in this device. The 'tnIfFwdPortList' uses this port number for decoding the bitmap.

The complete set of ports, that frames ingressing this interface can be forwarded to. Each bit represents if it is in the forwarding list of this port or not according to it is set or cleared. Port 1 is represented by BIT0, Port 2.

This table has entries for interfaces to manage its L2CP processing.

A entry in the table represents the configuration of an interface's L2CP processing.

Any STP/RSTP/MSTP protocol frames with destination address of 01-80-C2-00-00-00 is discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

Any LACP/LAMP protocol frames with destination address of 01-80-C2-00-00-02 is discarded at this port or passed. Since this device pairs link OAM frames, these frames will not be forwarded or discarded. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

Port authentication protocol frames with destination address of 01-80-C2-00-00-03 is discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

E-LMI protocol frames with destination address of 01-80-C2-00-00-07 is discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

LLDP protocol frames with destination address of 01-80-C2-00-00-0E and ethertype of 0x88CC which are not TN discovery LLDP frames are discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

Bridge Management protocol frames with destination address of 01-80-C2-00-00-10 is discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

GARP/MRP with destination address of 01-80-C2-00-00-20 to 01-80-C2-00-00-2F is discarded at this port or passed. Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

This mib variable passes or discards all the IEEE multicast frames in the bridge block of addresses [01-80-C2-00-00-04 to 01-80-C2-00-00-0F]. The mib variables applies to all addresses in this block that are not covered by the other mib variables in this table. i.e this is not applicable for STP, slow protocols, etc., Enumeration: 'discard': 2, 'pass': 1, 'notApplicable': 3.

This table has entries for interfaces to manage TN Topology Discovery Protocol processing.

A entry in the table represents the configuration of an interface's TN Topology Discovery Protocol processing.

If enabled, TN Topology Discovery Data will be sent out from this interface. If disabled, TN Topology Discovery Data will not be sent out from this interface. Enumeration: 'disabled': 2, 'notSupported': 3, 'enabled': 1.

A table containing information about TDR (Time Domain Reflectometery) test on an interfaces. An entry appears in this table for each interface which is capable to run TDR test.

Each entry represents the an interface capable of TDR test.

Indicates the TDR test action to be executed on the interface and whether the test is currently running or not. 'perform' -- start the TDR test on the interface. 'doNothing' -- Normal state, test has not been intiated or the test may have been completed. Enumeration: 'perform': 1, 'doNothing': 2.

Indicates the status of the last TDR test action set on the interface. Enumeration: 'testFailed': 2, 'testAlreadyRunning': 3, 'testSuccess': 1, 'testUnknownState': 4.

Indicates the timestamp when TDR test is last run on the interface. If TDR test is never run on an interface, then this object value will be zero.

Indicates whether the TDR test result on the interface is valid for the user to retrieve or not.

A table containing information about TDR test result on the device's interfaces. An entry appears in this table for each cable pair on an interface which has valid TDR test result, i.e., the value of tnIfTDRResultValid for the interface is true(1).

An entry in the tnIfTDRResultTable, containing the information about TDR test on an interface.

The local cable pair index. 'pair1to2' -- the pair with cable connectors 1 and 2. 'pair3to6' -- the pair with cable connectors 3 and 6. 'pair4to5' -- the pair with cable connectors 4 and 5. 'pair7to8' -- the pair with cable connectors 7 and 8. Enumeration: 'pair1to2': 1, 'pair7to8': 4, 'pair3to6': 2, 'pair4to5': 3.

The length of the cable pair. A value of -1 indicates the length value is invalid. The unit of this value is indicated by tnIfTDRResultPairLengthUnit of the same cable pair.

The distance to the fault point of the cable pair. A value of -1 indicates this value is invalid. The unit of this value is indicated by tnIfTDRResultPairLengthUnit of the same cable pair.

The measurement unit on the length or the distance to fault point for the cable pair. 'unknown' -- none of the following. 'meter' -- the unit is meter. 'centimeter' -- the unit is centimeter. 'kilometer' -- the unit is kilometer. Enumeration: 'unknown': 1, 'kilometer': 4, 'centimeter': 3, 'meter': 2.

The status of the cable pair. 'unknown' -- none of the following. 'normal' -- the pair is properly terminated at the remote end. 'open' -- the pair is open. 'shorted' -- the pair is shorted. 'impedanceMismatch' -- the impedance of the pair is mismatched. Enumeration: 'unknown': 1, 'open': 5, 'impedanceMismatch': 3, 'shorted': 4, 'normal': 2.

A table containing information about loopback testing on interfaces. An entry appears in this table for each interface which is capable of loopback testing.

Each entry represents the an interface capable of TDR test.

This gives the loopback capabilities for this interface.

Loopback is used to diagnose any hardware or configuration problem on an interface. It can also be used to verify configurations such as bandwidth limiting. This mib variable allows to enable loopback on this interface. There may be several loopback options supported on this interface, the 'tnIfLoopbackCapability' lists the supported loopback methods on this interface.

This gives the loopback status for this interface when enabled. The only two possible values for a SET operation are intiateLoopback(2) and terminateLoopback(3). The rest of the values are read-only to show the status of the loopback operation. Enumeration: 'intiateLoopback': 2, 'noLoopback': 1, 'inProcess': 4, 'remoteInLoopback': 6, 'terminateLoopback': 3, 'localInLoopback': 5.

This clears the counters maintained for this interface. This may be useful when doing loopback testing to verify the test frames sent and received counters. Enumeration: 'reset': 1, 'doNothing': 2.

A table containing port level security configuration.

Each entry represents each port's security settings.

The Source Address Lock when set to true(1) monitors for source MAC address change on this port. This feature is useful to detect if the device connected to this port has been changed and also for intrusion when unknown MAC address ingress this port.

The 'tnIfSourceAddrLock' when set to true(1) monitors for source MAC address change on this port. This MIB variable sets the action to be taken when such an event is detected. This feature is useful to detect if the device connected to this port has been changed and also for intrusion when unknown MAC address ingress this port. The actions performed on encountering an unknown address : discard(1) - The frame will unknown MAC are discarded. This is the default value. discardAndNotify(2) - A trap is sent to notify the intrusion/SA change and the frame is discarded. shutdown(3) - This will shutdown the interface on receiving the frame. all(4) - All the above actions take place. The frame is discarded, a trap is sent and the port is shutdown to prevent intrusion attack. Enumeration: 'discard': 1, 'discardAndNotify': 2, 'all': 5, 'shutdown': 3.

This filters all unicast frames with unknown destination address from egressing this Port.

This filters all multicast frames with unknown destination address from egressing this Port.

A table containing configuration for interface level MAC Learning limits. It allows for limiting the number of users on a given port. A user is identified by a MAC address and VLAN ID. If Limit Control is enabled on a port, the limit specifies the maximum number of users on the port. If this number is exceeded, an action is taken. The action can be one of the four different actions as described below.

Each entry represents each interface's MAC limit settings.

Mode Controls whether Limit Control is enabled on this port. Both this and the Global Mode must be set to Enabled for Limit Control to be in effect.

The maximum number of MAC addresses that can be secured on this port. This number cannot exceed 1024. If the limit is exceeded, the corresponding action is taken. The switch is set with a total number of MAC addresses from which all ports draw whenever a new MAC address is seen on a Port Security-enabled port. Since all ports draw from the same pool, it may happen that a configured maximum cannot be granted, if the remaining ports have already used all available MAC addresses.

If Limit is reached, the switch can take one of the following actions: none(0) : Do not allow more than Limit MAC addresses on the port, but take no further action. trap(1) : If tnIfLimitDynMACMaxCount + 1 MAC addresses is seen on the port, send an SNMP trap. If Aging is disabled, only one SNMP trap will be sent, but with Aging enabled, new SNMP traps will be sent everytime the limit gets exceeded. shutdown(2) : If tnIfLimitDynMACMaxCount + 1 MAC addresses is seen on the port, shut down the port. This implies that all secured MAC addresses will be removed from the port, and no new address will be learned. Even if the link is physically disconnected and reconnected on the port (by disconnecting the cable), the port will remain shut down. There are three ways to re-open the port: 1) Boot the switch, 2) Disable and re-enable Limit Control on the port or the switch, 3) enable using tnIfLimitDynMACReopen. trapShutdown(3) : If tnIfLimitDynMACMaxCount + 1 MAC addresses is seen on the port, both the Trap and the Shutdown actions described above will be taken Enumeration: 'none': 0, 'trap': 1, 'shutdown': 2, 'trapShutdown': 3.

This column shows the current state of the port as seen from the Limit Control's point of view. The state takes one of four values: disabled(0) : Limit Control is either globally disabled or disabled on the port. ready(1) : The limit is not yet reached. This can be shown for all actions. limitReached(2) : Indicates that the limit is reached on this port. This state can only be shown if Action is set to None or Trap. shutdown(3) : Indicates that the port is shut down by the Limit Control module. This state can only be shown if Action is set to Shutdown or Trap & Shutdown. Enumeration: 'disabled': 0, 'ready': 1, 'limitReached': 2, 'shutdown': 3.

If a port is shutdown by this module, you may reopen it by setting this mib variable to enabled.

Table for Egress queuing method confiration by per port.

Entry for Egress queuing method confiration by per port

The port interface of the TnEgressQueueModeEntry.

The queuing method for the egress prioQueue. wrr(1),strict(2) Enumeration: 'strict': 2, 'wrr': 1.