V2H124-24-MIB: View SNMP OID List / Download MIB

The MIB module for V2H124-24.

The VLAN on which management is done.

The total number of switches present on this system.

Table of descriptive and status information about the switch units in this system.

Table providing descriptions and status information for switch units.

This object identifies the switch within the system for which this entry contains information. This value can never be greater than switchNumber.

Hardware version of the main board.

Microcode version of the main board.

Loader version of the main board.

Boot ROM code version of the main board.

Operation code version of the main board.

The number of ports of this switch.

Indicates the switch using internalPower(1), redundantPower(2) or both(3) Enumeration: 'internalAndRedundantPower': 3, 'internalPower': 1, 'redundantPower': 2.

Indicates the switch is master(1), backupMaster(2) or slave(3) in this system. Enumeration: 'backupMaster': 2, 'slave': 3, 'master': 1.

Serial number of the switch.

Type of expansion module in this switch slot 1. Enumeration: 'thousandBaseLxScSmf': 9, 'hundredBaseFxScSmf': 4, 'hundredBaseFxScMmf': 3, 'stackingModule': 11, 'thousandBaseSxScMmf': 6, 'tenHundredBaseT': 16, 'thousandBaseXGbic': 8, 'thousandBaseT': 10, 'other': 2, 'thousandBaseSfp': 12, 'comboStackingSfp': 15, 'thousandBaseSxMtrjMmf': 7, 'tenHundredBaseT4port': 13, 'notPresent': 1, 'tenHundredBaseFxMtrj4port': 14, 'hundredBaseFxMtrjMmf': 5.

Type of expansion module in this switch slot 2. Enumeration: 'thousandBaseLxScSmf': 9, 'hundredBaseFxScSmf': 4, 'hundredBaseFxScMmf': 3, 'stackingModule': 11, 'thousandBaseSxScMmf': 6, 'tenHundredBaseT': 16, 'thousandBaseXGbic': 8, 'thousandBaseT': 10, 'other': 2, 'thousandBaseSfp': 12, 'comboStackingSfp': 15, 'thousandBaseSxMtrjMmf': 7, 'tenHundredBaseT4port': 13, 'notPresent': 1, 'tenHundredBaseFxMtrj4port': 14, 'hundredBaseFxMtrjMmf': 5.

Service tag serial-number of the switch.

Global operation state of the switch. Enumeration: 'ok': 3, 'unknown': 2, 'other': 1, 'critical': 5, 'noncritical': 4, 'nonrecoverable': 6.

The product name of this switch.

The product manufacturer of this switch.

The product description of this switch.

The runtime code version of this switch.

The URL of this switch, which we can connect through a web browser.

A unique identifier of which switch in the chassis is currently being looked at.

The service tag of the chassis this switch resides in.

Table about statuses of individual powers.

Table about statuses of individual powers.

This is defined as v2h124swUnitIndex.

1 means internal power. 2 means external power. Enumeration: 'internalPower': 1, 'externalPower': 2.

notPresent(1) means not present. green(2) means up. red(3) means down. Enumeration: 'notPresent': 1, 'green': 2, 'red': 3.

Table of descriptive and status information describing the configuration of each switch port. This table also contains information about each trunk.

An entry in the table, describing the configuration of one switch port or trunk.

The port and the trunk (including trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

The name of the port or trunk. This is the same as ifAlias in the IF-MIB (RFC2863 or later).

Indicates the port type of the configuration of the switch Enumeration: 'hundredBaseFX': 3, 'thousandBaseGBIC': 7, 'thousandBaseLX': 5, 'hundredBaseTX': 2, 'hundredBaseFxScSingleMode': 9, 'thousandBaseT': 6, 'other': 1, 'thousandBaseSfp': 8, 'hundredBaseFxScMultiMode': 10, 'thousandBaseSX': 4.

Configures the speed and duplex mode for a port or trunk, according to: halfDuplex10(2) - 10Mbps and half duplex mode fullDuplex10(3) - 10Mbps and full duplex mode halfDuplex100(4) - 100Mbps and half duplex mode fullDuplex100(5) - 100Mbps and full duplex mode halfDuplex1000(6) - 1000Mbps and half duplex mode fullDuplex1000(7) - 1000Mbps and full duplex mode hundredBaseTX port can be set as halfDuplex10(2) fullDuplex10(3) halfDuplex100(4) fullDuplex100(5) hundredBaseFX port can be set as halfDuplex100(4) fullDuplex100(5) thousandBaseSX port can be set as halfDuplex1000(6) fullDuplex1000(7) The actual operating speed and duplex of the port is given by portSpeedDpxStatus. Enumeration: 'fullDuplex10': 3, 'halfDuplex1000': 6, 'fullDuplex1000': 7, 'halfDuplex100': 4, 'halfDuplex10': 2, 'fullDuplex100': 5, 'reserved': 1.

(1) Flow control mechanism is enabled. If the port type is hundredBaseTX or thousandBaseSX: When the port is operating in halfDuplex mode, the port uses backPressure flow control mechanism. When the port is operating in fullDuplex mode, the port uses IEEE 802.3x flow control mechanism. If the port type is hundredBaseFX: When the port is operating in halfDuplex mode, the port uses backPressure flow control mechanism. When the port is operating in fullDuplex mode, Flow control mechanism will not function. (2) Flow control mechanism is disabled. (3) Flow control mechanism is backPressure. when the port is in fullDuplex mode.This flow control mechanism will not function. (4) Flow control mechanism is IEEE 802.3x flow control. when the port is in halfDuplex mode.This flow control mechanism will not function. hundredBaseTX and thousandBaseSX port can be set as: enabled(1), disabled(2), backPressure(3), dot3xFlowControl(4). hundredBaseFX port can be set as: enabled(1), disabled(2), backPressure(3). The actual flow control mechanism is used given by portFlowCtrlStatus. Enumeration: 'disabled': 2, 'backPressure': 3, 'dot3xFlowControl': 4, 'enabled': 1.

Port or trunk capabilities. Bits: 'reserved11': 11, 'reserved10': 10, 'reserved13': 13, 'reserved12': 12, 'reserved7': 7, 'portCap100full': 3, 'portCap1000half': 4, 'portCap10half': 0, 'portCapFlowCtrl': 15, 'portCapSym': 14, 'reserved9': 9, 'reserved8': 8, 'portCap1000full': 5, 'portCap10full': 1, 'reserved6': 6, 'portCap100half': 2.

Whether auto-negotiation is enabled.

The operating speed and duplex mode of the switched port or trunk. If the entry represents a trunk, the speed is that of its individual members unless the member ports have been inconsistently configured in which case the value is error(1). Enumeration: 'fullDuplex10': 3, 'halfDuplex1000': 6, 'error': 1, 'fullDuplex1000': 7, 'halfDuplex100': 4, 'halfDuplex10': 2, 'fullDuplex100': 5.

(2) BackPressure flow control machanism is used. (3) IEEE 802.3 flow control machanism is used. (4) Flow control mechanism is disabled. If the entry represents a trunk and the member ports have been inconsistently configured then this value is error(1). Enumeration: 'none': 4, 'dot3xFlowControl': 3, 'backPressure': 2, 'error': 1.

The trunk to which this port belongs. A value of 0 means that this port does not belong to any trunk. A value greater than zero means that this port belongs to trunk at trunkIndex, defined by the corresponding trunkPorts.

The maximum number for a trunk identifier.

The number of valid trunks.

Table describing the configuration and status of each trunk.

An entry describing the configuration and status of a particular trunk.

Identifies the trunk within the switch that is described by the table entry.

The complete set of ports currently associated with this trunk.

A value of static(1) means a statically configured trunk. A value of lacp(2) means an LACP-configured trunk. Enumeration: 'lacp': 2, 'static': 1.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry. A trunk created by LACP cannot be manually destroyed or (re)configured.

Table for LACP port configuration.

Entry for LACP port configuration. While an entry may exist for a particular port, the port may not support LACP and an attempt to enable LACP may result in failure.

The port interface of the lacpPortTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Whether 802.3ad LACP is enabled.

Global spanning tree status. (1) Spanning tree protocol is enabled. (2) Spanning tree protocol is disabled.

The table manages port settings for Spanning Tree Protocol 802.1d, or 802.1w depending on the value specified by staProtocolType.

The conceptual entry of staPortTable.

Whether fast forwarding is enabled.

When operating in RSTP (version 2) mode, setting this object to TRUE(1) object forces the port to transmit RSTP BPDUs. Any other operation on this object has no effect and it always returns FALSE(2) when read.

The administrative value of the Edge Port parameter. A value of TRUE(1) indicates that this port should be assumed to be an edge-port and a value of FALSE(2) indicates that this port should be assumed to be a non-edge-port.

The operational value of the Edge Port parameter. The object is initialized to the value of staPortAdminEdgePort and is set FALSE when a BPDU is received.

The administrative point-to-point status of the LAN segment attached to this port. A value of forceTrue(0) indicates that this port should always be treated as if it is connected to a point-to-point link. A value of forceFalse(1) indicates that this port should be treated as having a shared media connection. A value of auto(2) indicates that this port is considered to have a point-to-point link if it is an Aggregator and all of its members can be aggregated, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by explicit configuration. Enumeration: 'forceFalse': 1, 'forceTrue': 0, 'auto': 2.

The operational point-to-point status of the LAN segment attached to this port. It indicates whether a port is considered to have a point-to-point connection or not. The value is determined by explicit configuration or by auto-detection, as described in the staPortAdminPointToPoint object.

The contribution of this port to the path cost (as a 32 bit value) of paths towards the spanning tree root which include this port. This object is used to configure the spanning tree port path cost as a 32 bit value when the staPathCostMethod is long(2). If the staPathCostMethod is short(1), this MIB object is not instantiated.

The version of Spanning Tree Protocol the bridge is currently running. The value 'stp(1)' indicates the Spanning Tree Protocol is as specified in IEEE 802.1D,'rstp(2)' indicates the Rapid Spanning Tree Protocol is as specified in IEEE 802.1w New values may be defined in the future as new or updated versions of the protocol become available. Enumeration: 'stp': 1, 'rstp': 2.

The minimum interval between the transmission of consecutive RSTP/MSTP BPDUs in seconds.

Indicates the type of spanning tree path cost mode configured on the switch. This mode applies to all instances of the Spanning tree protocol running on the switch. When the value of this MIB object is changed, the path cost of all ports will be reassigned to the default path cost values based on the new spanning tree path cost mode and the ports' speed. When the value of this MIB object is set to long(2), the staPortLongPathCost MIB object must be used to retrieve/ configure the spanning tree port path cost as a 32 bit value. The set operation on dot1dStpPortPathCost in the BRIDGE-MIB will be rejected. When retrieving the value of dot1dStpPortPathCost, the maximum value of 65535 will be returned if the value of staPortLongPathCost for the same instance exceeds 65535. When the value of this MIB object is set to short(1), the dot1dStpPortPathCost in the BRIDGE-MIB must be used. Enumeration: 'short': 1, 'long': 2.

This table is used to configure Rapid Spanning Tree. Only the first row of the table is used by RST. In the future this table may be used to support other spanning tree protocols.

A conceptual row containing the properties of the RST instance.

The index for an entry in the xstInstanceCfgTable table. For RST only the first row in the table is used.

The priority of a specific spanning tree instance. The value assigned should be in the range 0-61440 in steps of 4096.

The time (in hundredths of second) since the last topology change detected by the bridge entity in RST.

The total number of topology changes detected by this bridge in RST since the management entity was last reset or initialized.

The bridge identifier of the root of the spanning tree as determined by the Rapid Spanning Tree Protocol (802.1w) executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.

The cost of the path to the root as seen from this bridge of the RST.

The number of the port which offers the lowest cost path from this bridge to the root bridge of the RST .

The maximum age of Rapid Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.

The amount of time between the transmission of Configuration bridge PDUs by this node on any port when it is the root of the spanning tree or trying to become so, in units of hundredths of a second. This is the actual value that this bridge is currently using in RST.

This time value determines the interval length during which no more than two Configuration bridge PDUs shall be transmitted by this node, in units of hundredths of a second.

For the RST protocol, this time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used, when a topology change has been detected and is underway, to age all dynamic entries in the Forwarding Database. This value is the current value being used by the bridge. xstInstanceCfgBridgeForwardDelay defines the value that this bridge and all others would start using if/when this bridge were to become the root.

For RST protocol, the time (in hundredths of second) that all bridges use for MaxAge when this bridge is acting as the root. Note that 802.1D-1990 specifies that the range for this parameter is related to the value of xstInstanceCfgBridgeHelloTime. The granularity of this timer is specified by 802.1D-1990 to be 1 second.

For the RST protocol, the time (in hundredths of second) that all bridges use for HelloTime when this bridge is acting as the root. The granularity of this timer is specified by 802.1D-1990 to be 1 second.

For the RST protocol, the time (in hundredths of second) that all bridges use for ForwardDelay when this bridge is acting as the root. Note that 802.1D-1990 specifies that the range for this parameter is related to the value of xstInstanceCfgBridgeMaxAge. The granularity of this timer is specified by 802.1D-1990 to be 1 second.

For the RST protocol, the value used by the Port Transmit state machine to limit the maximum transmission rate.

For RST protocol, this indicates the type of spanning tree path cost mode used by the switch. The mode applies to all instances of the Spanning Tree protocol running on the switch. When the value of this MIB object is changed, the path cost of all ports will be reassigned to the default path cost values based on the new spanning tree path cost mode and the ports' speed. When the value of this MIB object is set to long(2), the xstInstancePortPathCost MIB object must be used in order to retrieve/configure the spanning tree port path cost as a 32 bit value. The set operation on dot1dStpPortPathCost in the BRIDGE-MIB will be rejected. While retrieving the value of dot1dStpPortPathCost, the maximum value of 65535 will be returned if the value of xstInstancePortPathCost for the same instance exceeds 65535. When the value of this MIB object is set to short(1), the dot1dStpPortPathCost in the BRIDGE-MIB must be used. Enumeration: 'short': 1, 'long': 2.

The extension table for dot1dStpPortEntry to provide additional Spanning Tree information and configuration.

The conceptual row for xstInstancePortTable.

Defines the priority used for this port in the Spanning Tree Algorithm. If the path cost for all ports on a switch is the same, the port with the highest priority (i.e., lowest value) will be configured as an active link in the Spanning Tree. This makes a port with higher priority less likely to be blocked if the Spanning Tree Algorithm is detecting network loops. Where more than one port is assigned the highest priority, the port with lowest numeric identifier will be enabled.

The port's current state as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame: discarding(1) Port receives configuration messages, but does not forward packets. learning(2) Port has transmitted configuration messages for an interval set by the Forward Delay parameter without receiving contradictory information. Port address table is cleared, and the port begins learning addresses. forwarding(3) Port forwards packets, and continues learning addresses. For ports which are disabled (see xstInstancePortEnable), this object will have a value of discarding(1). Enumeration: 'discarding': 1, 'forwarding': 3, 'learning': 2.

The enabled/disabled status of the port.

The pathcost of the RST in the range 1 to 200000000. This parameter is used to determine the best path between devices. Therefore, lower values should be assigned to ports attached to faster media, and higher values assigned to ports with slower media. (Path cost takes precedence over port priority).

The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached.

The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs.

The Bridge Identifier of the bridge which this port considers to be the Designated Bridge for this port's segment.

The Port Identifier of the port on the Designated Bridge for this port's segment.

The number of times this port has transitioned from the Learning state to the Forwarding state.

The role of the port in the RST protocol: (1) The port has no role within the spanning tree (2) The port is part of the active topology connecting the bridge to the root bridge (i.e., root port) (3) The port is connecting a LAN through the bridge to the root bridge (i.e., designated port) (4) The port may provide connectivity if other bridges, bridge ports, or LANs fail or are removed. (5) The port provides backup if other bridges, bridge ports, or LANs fail or are removed. Enumeration: 'disabled': 1, 'designated': 3, 'alternate': 4, 'root': 2, 'backup': 5.

Name of op-code file for start-up.

Name of configuration file for start-up.

Setting this object to warmBoot(2) causes the device to reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. Setting this object to coldBoot(3) causes the device to reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered. When the device is running normally, this variable has a value of running(1). Enumeration: 'running': 1, 'coldBoot': 3, 'warmBoot': 2.

Table for port mirroring, enabling a port to be mirrored to/from another port. Not all ports cannot be mirrored and limitations may apply as to which ports can be used as either source or destination ports.

The conceptual row of mirrorTable.

The destination port interface for mirrored packets. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

The source port interface for mirrored packets. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

If this value is rx(1), receive packets will be mirrored. If this value is tx(2), transmit packets will be mirrored. If this value is both(3), both receive and transmit packets will be mirrored. Enumeration: 'both': 3, 'rx': 1, 'tx': 2.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry.

Parameter to enable or disable IGMP snooping on the device. When enabled, the device will examine IGMP packets and set up filters for IGMP ports.

Enables (disables) whether the switch acts as an IGMP Querier.

The query count from a querier, during which a response is expected from an endstation. If a querier has sent a number of counts defined by igmpSnoopQueryCount, but an endstation has not responded, a countdown timer is started using the time defined by igmpSnoopQueryMaxResponseTime. If the countdown finishes, and the endstation still has not responded, then that endstation is deemed to have left the multicast group.

The interval (in seconds) between IGMP host-query messages sent by the switch.

The time after a query, during which a response is expected from an endstation. If a querier has sent a number of queries defined by igmpSnoopQueryCount, but an endstation has not responded, a countdown timer is started using an initial value set by igmpSnoopQueryMaxResponseTime. If the countdown finishes, and the endstation still has not responded, then that the endstation is deemed to have left the multicast group.

Sets the time (in seconds) the switch waits after the previous querier has stopped querying before the router port (which received Query packets from previous querier) expires.

IGMP Version snooped

Table for current router ports.

Entry for current router ports.

The interface identified by a particular value of this index is the same interface as identified by the same value of dot1qVlanIndex in the Q-BRIDGE-MIB. The entry will only appear here after a configure to igmpSnoopRouterStaticTable.

The set of ports which are current router ports, including static router ports. Please refer to igmpSnoopRouterStaticTable.

The set of ports which are static router ports.

Table for static router ports.

Entry for static router ports.

The interface identified by a particular value of this index is the same interface as identified by the same value of dot1qVlanIndex in the Q-BRIDGE-MIB. The entry will only appear here after a configure to igmpSnoopRouterStaticTable.

The set of ports which are static router ports.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry.

Table for current multicast addresses.

Entry for current multicast addresses.

The interface identified by a particular value of this index is the same interface as identified by the same value of dot1qVlanIndex in the Q-BRIDGE-MIB. The entry will only appear here after a configure to igmpSnoopMulticastStaticTable.

IP address of multicast group.

The set of ports which are members of a multicast group, including static members. Please refer to igmpSnoopMulticastStaticTable.

The set of ports which are static members.

Table for static multicast addresses.

Entry for static multicast addresses.

The interface identified by a particular value of this index is the same interface as identified by the same value of dot1qVlanIndex in the Q-BRIDGE-MIB. The entry will only appear here after a configure to igmpSnoopMulticastStaticTable.

IP address of multicast group.

The set of ports which are members.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry.

A table of netConfigEntries.

A set of configuration parameters for a particular network interface on this device. If the device has no network interface, this table is empty. The index is composed of the ifIndex assigned to the corresponding interface.

The VLAN interface being used by this table entry. Only the VLAN interfaces which have an IP configured will appear in the table.

The IP address of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask are 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails, before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device).

The subnet mask of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask are 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails, before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device).

Whether this is a primary interface. Enumeration: 'primary': 1, 'secondary': 2.

Whether this is an unnumbered interface. Enumeration: 'unnumbered': 1, 'notUnnumbered': 2.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

The IP Address of the default gateway. If this value is undefined or unknown, it shall have the value 0.0.0.0.

Whether HTTP is enabled.

The port number for HTTP.

When set to restart(1) the DHCP server will restart. When read, this value always returns noRestart(2). Enumeration: 'noRestart': 2, 'restart': 1.

Whether HTTPS is enabled.

The port number for HTTPS.

Table to manage the control of broadcast storms for ports.

The conceptual row of bcastStormTable.

The port and the trunk (including trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Whether broadcast storm protection is enabled.

Sample type. If this is pkt-rate(1), then bcastStormPktRate is used to specify the broadcast storm threshold. If this is octet-rate(2), then bcastStormOctetRate determines the broadcast storm threshold. If this is percent(3), then bcastStormPercent determines the threshold. Enumeration: 'percent': 3, 'octet-rate': 2, 'pkt-rate': 1.

Broadcast storm threshold as packets per second. If this entry is for a trunk, this is the value for each member port.

Broadcast storm threshold as octets per second. If this entry is for a trunk, this is the value for each member port.

Broadcast storm threshold as percentage of bandwidth.

Table for VLAN configuration.

Entry for VLAN configuration.

Based on dot1qVlanIndex in the Q-BRIDGE-MIB. This table has only one entry - the entry for the VLAN of the management interface.

Method to get the IP address. Enumeration: 'dhcp': 3, 'user': 1, 'bootp': 2.

Table for port configuration in VLAN.

Entry for port configuration in VLAN.

The port and the trunk (excluding trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of dot1qPvid in the Q-BRIDGE-MIB.

This variable sets the 802.1Q VLAN mode. Setting it to hybrid(1) sets a hybrid link. Setting it to dot1qTrunk(2) sets a trunk link. Setting it to access(3) sets an access link. Enumeration: 'access': 3, 'dot1qTrunk': 2, 'hybrid': 1.

Selects whether no frame priority mapping, IP ToS precedence mapping or DSCP mapping is performed. Enumeration: 'disabled': 1, 'dscp': 3, 'precedence': 2.

Table for IP precedence priority mapping.

Entry for IP precedence priority mapping.

The port and the trunk (excluding trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Value of IP ToS Precedence as specified in the packet header.

Class of Service (CoS) as defined by dot1dTrafficClassPriority in the P-BRIDGE-MIB. The IP ToS precedence value in the same table row will be mapped to this CoS. This CoS is then further mapped to the hardware queue according to dot1dTrafficClassTable.

Enables the IP Precedence settings of a port to be restored to their default values. To reset the settings of a port, assign prioIpPrecRestoreDefault to the value of ifIndex defined by the ifIndex in the IF-MIB. For example, If 1 is written to it, then the IP priorities of port 1 will be restored to default. When read, this object always returns 0.

Table for IP DSCP priority mapping.

Entry for IP DSCP priority mapping.

The port and the trunk (excluding trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Value of IP DSCP as specified in the packet header.

Class of Service as defined by dot1dTrafficClassPriority in the P-BRIDGE-MIB. The prioIpDscpValue value in the same table row will be mapped to this Class of Service (COS). This CoS is then further mapped to the hardware queue according to dot1dTrafficClassTable.

Enables the IP DSCP settings of a port to be reset to their defaults. To reset the IP DSCP settings of a port, assign the value of the relevant ifIndex defined by the ifIndex in the IF-MIB. For example, assigning the value 1 will result in the IP DSCP settings of port 1 being restored to their default. When read, this object always returns 0.

Whether IP Port priority look-up is enabled.

Table for IP port priority mapping.

Entry for IP port priority mapping.

The port and the trunk (excluding trunk member) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

IP port for this value.

Class of service for this entry.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry.

Action to copy IP Precedence settings from a source port to many destination ports. The first four octets represent an integer for the source port, in high-to-low (big-endian) order. Starting from the 5th octet is destination port list in a form described by PortList in the Q-BRIDGE-MIB. Writing this object will perform copy. Reading this object will always get a zero-length octet string.

Action to copy IP DSCP settings from a source port to many destination ports. The first four octets represent an integer for the source port, in high-to-low (big-endian) order. Starting from the 5th octet is destination port list in a form described by PortList in the Q-BRIDGE-MIB. Writing this object will perform copy. Reading this object will always get a zero-length octet string.

Action to copy IP Port settings from a source port to many destination ports. The first four octets represent an integer for the source port, in high-to-low (big-endian) order. Starting from the 5th octet is destination port list in a form described by PortList in the Q-BRIDGE-MIB. Writing this object will perform copy. Reading this object will always get a zero-length octet string.

Table for weighted round robin (WRR).

Entry for weighted round robin (WRR).

Traffic class for this entry, as defined in dot1dTrafficClass in the P-BRIDGE-MIB. The actual maximum depends on the hardware, and is equal to dot1dPortNumTrafficClasses-1.

Weight for this entry.

A list of trap destination entries.

A destination entry describes the destination IP address, the community string and SNMP version to use when sending a trap.

The address to send traps.

A community to which this destination address belongs.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry.

Determines the version of the Trap that is to be sent to the trap Receiver. If the value is 1, then a SNMP version 1 trap will be sent and if the value is 2, a SNMP version 2 trap is sent. Enumeration: 'version1': 1, 'version2': 2.

Whether rate limit is enabled.

Table for rate limit of each port.

Entry for rate limit of each port.

The port and the trunk (including trunk member) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Value of the input rate limit. Its unit is megabits per second. For a 100 Mb/s port, the range is 1 to 100. For a 1000 Mb/s port, the range is 1 to 1000.

Value of the output rate limit. Its unit is megabits per second. For a 100 Mb/s port, the range is 1 to 100. For a 1000 Mb/s port, the range is 1 to 1000.

Whether input rate limit is enabled for this port.

Whether output rate limit is enabled for this port.

The marker table.

Entry for marker table.

The interface index of the marker table. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

The name of an ACL. Within a feature the name is unique used to identifies the list to which the entry belongs in the device.

The marker action bit list, in right to left order. for example: 0x3(11 in binary) means dscp(0) and precedence(1) 0x4(100 in binary) means priority(2) Bits: 'priority': 2, 'precedence': 1, 'dscp': 0.

The Dscp value of the marker entry.

The precedence value of the marker entry.

The priority value of the marker entry.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

Table for Acl to Cos Mapping.

Entry for Acl to Cos Mapping.

The port interface of the prioAclToCosMappingEntry. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

The name of an IP ACL. Within a feature the name is unique used to identifies the list to which the entry belongs in the device.

Cos value of the prioAclToCosMappingTable.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

The Port Security(MAC binding) Table

The entry of portSecPortTable

The port and the trunk (excluding trunk members) interface of the portTable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex in the IF-MIB.

Set enabled(1) to enable port security and set disabled(2) to disable port security.

The corresponding actions that will take place when a port is under intruded, when this variable is set to none(1), no action will perform, when this variable is set to trap(2), a swPortSecurityTrap trap will send, when this variable is set to shutdown(3), the port will shutdown, when this variable is set to trapAndShutdown(4), a swPortSecurityTrap will send and the port will shutdown. Enumeration: 'none': 1, 'trap': 2, 'shutdown': 3, 'trapAndShutdown': 4.

The maximun number of MAC addresses that will be learned and locked. When we change the value of this variable, if the portSecPortStatus is enabled, we will discard all secure MAC and begin to learn again, until the number of MAC has reached this value, and only the secure MAC addresses can enter this port. If the portSecPortStatus is disabled, we will begin to learn the MAC, and auto enabled the portSecPortStatus when the MAC has reached this value.

IP address of RADIUS server.

IP port number of RADIUS server.

Key for RADIUS. This variable can only be set. When this variable is read, it always returns a zero-length string.

Maximum number of retransmissions for RADIUS.

Timeout for RADIUS.

IP address of TACACS server.

IP port number of TACACS server.

The encryption key used to authenticate logon access for the client using TACAS. Do not use blank spaces in the string. This variable can only be set. When this variable is read, it always returns a zero-length string.

The status of Secure Shell Server, set this value to 1 to enable SSH server, set this value to 2 to disable the SSH server.

The major version of the SSH Server.

The minor version of the SSH Server.

The time interval that the router waits for the SSH client to respond. The range is 1-120.

The number of attempts after which the interface is reset. The range is 1-5.

The table for Secure Shell Connection.

The conceptual row for sshConnInfoTable.

The connection ID of the Secure Shell Connection.

The SSH major version.

The SSH minor version.

The encryption type of the SSH. none(1) mean no encryption , des(2) mean using DES encryption, tribeDes mean using 3DES encryption. Enumeration: 'none': 1, 'des': 2, 'tribeDes': 3.

The SSH connection State. negotiationStart(1) mean the SSH is in its negotiation start state, authenticationStart(2) mean the SSH is in authentication start state, sessionStart(3) mean the SSH is in session start State. Enumeration: 'negotiationStart': 1, 'authenticationStart': 2, 'sessionStart': 3.

The user name of the connection.

Set the variable to disconnect to disconnect the connection, when read, this variable always return noDisconnect(1). Enumeration: 'noDisconnect': 1, 'disconnect': 2.

The conceptual table of all of aclIpAceEntry

The conceptual row for aclIpAceTable.

The name of an ACL. Within a feature the name is unique used to identifies the list to which the entry belongs in the device

The unique index of an ACE within an ACL

Specifies the IP precedence value

the aclIpAceAction of aces which have the same aclIpAceName must be the same Enumeration: 'deny': 2, 'permit': 1.

The specified source IP address. The packet's source address is AND-ed with the value of aclIpAceSourceIpAddrBitmask and then compared against the value of this object.

The specified source IP address mask

The specified destination IP address. The packet's destination address is AND-ed with the value of aclIpAceDestIpAddrBitmask and then compared against the value of this object

The specified destination IP address mask

The protocol number field in the IP header used to indicate the higher layer protocol as specified in RFC 1700. A value value of 0 matches every IP packet. the object=256, means 'any' For example : 0 is IP, 1 is ICMP, 2 is IGMP, 4 is IP in IP encapsulation, 6 is TCP, 9 is IGRP, 17 is UDP, 47 is GRE, 50 is ESP, 51 is AH, 88 is IGRP, 89 is OSPF, 94 is KA9Q/NOS compatible IP over IP, 103 is PIMv2, 108 is PCP.

Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

Indicates how a the control flags of TCP packet's to be compared to be compared. aceIpControlCode is AND-ed with aceIpControlCodeBitmask

Indicates how a the control flags of TCP packet's to be compared to be compared. it can be used to check multiple flags of the FIN, SYN, RST, PSH, ACK, URG by sum of FIN=1, SYN=2, RST=4, PSH=8, ACK=16, URG=32

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

The conceptual table of all of aclMacAceEntry

The conceptual row for aclMacAceTable.

The name of an ACL. Within a feature the name is unique used to identifies the list to which the entry belongs in the device

The unique index of an ACE within an ACL

Specifies the IP precedence value

the aclMacAceAction of aces which have the same aclMacAceName must be the same Enumeration: 'deny': 2, 'permit': 1.

used to check the packet format of the packets Enumeration: 'untagged802Dot3': 3, 'tagggedEth2': 4, 'any': 1, 'untagged-Eth2': 2, 'tagged802Dot3': 5.

Indicates the 48 bits destination MAC address. The specified source mac of the packet The packet's source mac address is AND-ed with the value of aceMacSourceMacAddrBitmask and then compared against the value of this object.

The specified source mac address mask.

Indicates the 48 bits destination MAC address. The specified destination mac of the packet The packet's destination mac address is AND-ed with the value of aceMacDestMacAddrBitmask and then compared against the value of this object.

The specified destination mac address mask.

Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

the conceptual table of aclAclGroupEntry

The conceptual row for aclAclGroupTable.

the interface number specified the ACL bining to.

specified the ingress ip acl(standard or extended) binding to the interface.

specified the egress ip acl(standard or extended) binding to the interface.

specified the ingress mac acl binding to the interface.

specified the egress mac acl binding to the interface.

the conceptual table of aclIngressIpMaskEntry

The conceptual row for aclIngressIpMaskTable.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

the conceptual table of aclEgressIpMaskEntry

The conceptual row for aclEgressIpMaskTable.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

the conceptual table of aclIngressMacMaskEntry

The conceptual row for aclIngressMacMaskTable.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

the conceptual table of aclEgressMacMaskEntry

The conceptual row for aclEgressMacMaskTable.

The status of this conceptual row entry. This object isused to manage the creation and deletion of conceptual rows. The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). For detail description of this object, please ref to SNMPv2-TC MIB.

Whether the system log is enabled.

Severity level for logging to flash.

Severity level for logging to RAM.

Number of data bits. Enumeration: 'databits8': 2, 'databits7': 1.

Define the generation of a parity bit. Enumeration: 'partyEven': 2, 'partyOdd': 3, 'partyNone': 1.

Baud rate. Valid values are 115200, 57600, 38400, 19200, and 9600. Enumeration: 'baudRate57600': 4, 'baudRate115200': 5, 'baudRate19200': 2, 'baudRate38400': 3, 'baudRate9600': 1.

The stop Bits of the console, valid value is stopbits1(1) or stopbits2(2) Enumeration: 'stopbits1': 1, 'stopbits2': 2.

In serial console, use the consoleExecTimeout variable to set the interval that the EXEC command interpreter waits until user input is detected, set the value to 0 to disable it.

The number of failed console logon attempts that may be made before the system will not accept a further attempt for the time specified by consoleSilentTime. A value of 0 disables the functionality.

The length of time that the management console is inaccessible for after the number of failed logon attempts has reached consolePasswordThreshold. A value of 0 disables the functionality.

Specifies the interval that the system waits for user input before terminating the current telnet session.

The number of failed telnet logon attempts that may be made before the system will not accept a further attempt to logon with telnet.

Set enabled(1) to enable the SNTP, set disabled(2) to disable the SNTP.

Service mode. Enumeration: 'unicast': 1, 'broadcast': 2, 'anycast': 3.

Polling interval.

Table for SNTP servers

Entry for SNTP servers.

The index of a server. This table has fixed size.

The IP address of a server. Valid IP addresses must occupy contiguous indexes. All IP addresses after the last valid index is 0.

It is a text string in the following form, based on Unix: 'Mmm _d hh:mm:ss yyyy'. 'Mmm' is the first three letters of the English name of the month. '_d' is the day of month. A single-digit day is preceded by the space. 'hh:mm:ss' is a 24-hour representations of hours, minutes, and seconds. A single-digit hour is preceded by a zero. 'yyyy' is the four-digit year. An example is: 'Jan 1 02:03:04 2002'.

It is a text string in the following form: '[s]hh:mm'. '[s]' is a plus-or-minus sign. For UTC, this is omitted. For a positive offset, this is '+'. For a negative offset, this is '-'. 'hh:mm' in the hour and minute offset from UTC. A single-digit hour is preceded by a zero.

The name of the time zone.

The Copy Operation in which we want to perform to the fileCopyDestOperType, this operation is similar to the CLI command 'copy fileCopySrcOperType fileCopyDestOperType'. file(1) means we want to perform the 'copy file fileCopyDestType' operation, runningCfg(2) means we want to perform the 'copy running-config fileCopyDestOperType' operation, startUpCfg(3) means we want to perform the 'copy startup-config fileCopyDestOperType' operation, tftp(4) means we want to perform the 'copy tftp fileCopyDestOperType' operation, unit(5) is only available in stacking system, in which we can copy files from one unit to another unit and it means we want to perform the 'copy unit fileCopyDestOperType' operation. The possible permutations is as follow: (1)copy file file (2)copy file runningCfg (3) copy file startUpCfg (4)copy file tftp (5) copy file unit(for stacking system only) (6)copy runningCfg file (7)copy runningCfg startUpCfg (8)copy runningCfg tftp (9)copy startupCfg file (10)copy startupCfg runningCfg (11)copy startupCfg tftp (12)copy tftp file (13)copy tftp runningCfg (14)copy tftp startUpCfg (15)copy unit file. Enumeration: 'unit': 5, 'tftp': 4, 'runningCfg': 2, 'startUpCfg': 3, 'file': 1.

The source file name for fileCopyMgt when a copy operation is next requested via this MIB. This value is set to the zero length string when no file name has been specified. Note: if the fileCopySrcOperType is runningCfg(2) or startUpCfg(3), this variable can be ignored.

The Copy Operation in which we want to perform from the fileCopySrcOperType, this operation is similar to the CLI command 'copy fileCopySrcOperType fileCopyDestOperType'. file(1) means we want to perform the 'copy fileCopySrcType file ' operation, runningCfg(2) means we want to perform the 'copy fileCopySrcOperType running-config ' operation, startUpCfg(3) means we want to perform the 'copy fileCopySrcOperType startup-config ' operation, tftp(4) means we want to perform the 'copy fileCopySrcOperType tftp' operation, unit(5) is only available in stacking system, in which we can copy files from one unit to another unit and it means we want to perform the 'copy fileCopySrcOperType unit' operation. The possible permutations is as follow: (1)copy file file (2)copy file runningCfg (3) copy file startUpCfg (4)copy file tftp (5) copy file unit(for stacking system only) (6)copy runningCfg file (7)copy runningCfg startUpCfg (8)copy runningCfg tftp (9)copy startupCfg file (10)copy startupCfg runningCfg (11)copy startupCfg tftp (12)copy tftp file (13)copy tftp runningCfg (14)copy tftp startUpCfg (15)copy unit file. Enumeration: 'unit': 5, 'tftp': 4, 'runningCfg': 2, 'startUpCfg': 3, 'file': 1.

The destination file name for fileCopyMgt when a copy operation is next requested via this MIB. This value is set to the zero length string when no file name has been specified. Note: if the fileCopyDestOperType is runningCfg(2) or startupCfg(3), this variable can be ignored.

Type of file to copy in fileCopyMgt. If the fileCopySrcOperType or fileCopyDestOperType is either runningCfg(2) or startupCfg(3), this variable can be ignored. If the fileCopySrcOperType or fileCopyDestOperType is unit(5), this variable cannot be set to bootRom(3). Enumeration: 'config': 2, 'opcode': 1, 'bootRom': 3.

The IP address of the TFTP server for transfer when a download is next requested via this MIB. This value is set to '0.0.0.0' when no IP address has been specified. If neither fileCopySrcOperType nor fileCopyDestOperType is tftp(4), this variable can be ignored.

Specify the unit of the switch for stackable device when performing the 'copy unit file' or 'copy file unit' action, If neither fileCopySrcOperType nor fileCopyDestOperType is unit(5), this variable can be ignored.

Setting this object to copy(2) to begin the copy Operation. Enumeration: 'notCopying': 1, 'copy': 2.

The status of the last copy procedure, if any. This object will have a value of downloadStatusUnknown(2) if no copy operation has been performed. Enumeration: 'fileCopyTftpSocketBindError': 13, 'fileCopyTftpSocketOpenError': 12, 'fileCopyTftpAccessViolation': 3, 'fileCopyBusy': 17, 'fileCopyTftpSendError': 10, 'fileCopyWriteFlashError': 27, 'fileCopyTftpCompleted': 15, 'fileCopyImageTypeError': 23, 'fileCopyHeaderChecksumError': 24, 'fileCopyUnknown': 18, 'fileCopyTftpUndefError': 1, 'fileCopyParaError': 16, 'fileCopyTftpUnkownTransferId': 6, 'fileCopyWriteFlashFinish': 26, 'fileCopyReadFileError': 19, 'fileCopyTftpUserCancel': 14, 'fileCopyTftpReceiverError': 11, 'fileCopyWriteFlashProgramming': 28, 'fileCopyTftpTimeout': 9, 'fileCopyTftpFileNotFound': 2, 'fileCopyTftpIllegalOperation': 5, 'fileCopyTftpNoSuchUser': 8, 'fileCopySuccess': 30, 'fileCopyTftpDiskFull': 4, 'fileCopyMagicWordError': 22, 'fileCopyImageChecksumError': 25, 'fileCopyTftpFileExisted': 7, 'fileCopyError': 29, 'fileCopyCompleted': 31, 'fileCopyFileSizeExceed': 21, 'fileCopySetStartupError': 20.

The tftp error message, this value is meaningful only when the fileCopyStatus is fileCopyTftpUndefError(1).

The IP address or DNS of the TFTP server for transfer when a download is next requested via this MIB. This value is set to '0.0.0.0' when no IP address has been specified. If neither fileCopySrcOperType nor fileCopyDestOperType is tftp(4), this variable can be ignored.

This table contain the information of the file system, we can also perform the delete, set startup file operation.

A conceptually row for fileInfoTable.

The unit of the switch in a stacking system, in a non-stacking system, it value is always 1.

The file Name of the file System in the device.

The file type of the file System in the device. Enumeration: 'certificate': 8, 'postlog': 6, 'diag': 1, 'private': 7, 'syslog': 3, 'webarchive': 9, 'cmdlog': 4, 'runtime': 2, 'config': 5.

This flag indicate whether this file is a startup file, Setting this object to truth(1) to indicate this is a startup file, setting this object to false(2) is a invalid operation.

The sizes( in bytes) of the file.

The creation time of the file.

Writing this object to delete(2) to delete a file, when read, this always return noDelete(1). Enumeration: 'noDelete': 1, 'delete': 2.

This trap is sent when the power state changes.