ES4612-MIB: View SNMP OID List / Download MIB

The MIB module for ES4612.

The VLAN on which management is done.

The total number of switches present on this system.

Table of descriptive and status information about switches in this system.

An entry in the table, containing information about a single switch in this system.

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 total port number of this switch (including expansion slot).

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, 'thousandBaseXGbic': 8, 'thousandBaseT': 10, 'other': 2, 'thousandBaseSfp': 12, 'thousandBaseSxMtrjMmf': 7, 'notPresent': 1, 'hundredBaseFxMtrjMmf': 5.

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

Service tag serial-number of the switch.

Model number of the switch.

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

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 swUnitIndex.

1 means internal power. 2 means external power.

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

enable(1) means the Jumbo Frame has enabled, disabled(2) means the Jumbo Frame has disabled. Enumeration: 'disabled': 2, 'enabled': 1.

If this is enabled(1), the MAC address table will age out according to its timer. If this is disabled(2), the MAC address table will not age out.

The table of Fan Status.

A conceptual row of the switchFanTable.

the unit of the switch for stackable device.

The unit number of the fan.

Indicating the status of the fan, 1:ok; 2:failure. Enumeration: 'failure': 2, 'ok': 1.

Table of descriptive and status information about configuration of each switch port (including expansion slot) in this system. This table also contains information about each trunk (similar to Cisco's EtherChannel).

An entry in the table, containing information about configuration in one switch port of the switch.

This is defined as ifIndex in the IF-MIB.

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

Indicates the port type. Enumeration: 'hundredBaseFX': 3, 'thousandBaseGBIC': 7, 'thousandBaseLX': 5, 'hundredBaseTX': 2, 'thousandBaseT': 6, 'other': 1, 'thousandBaseSfp': 8, 'thousandBaseSX': 4.

Set the port speed and duplex mode as follows: 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 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 autonegotiation is enabled. Enumeration: 'disabled': 2, 'enabled': 1.

The operating speed and duplex mode of the switched port. If this index is a trunk, the speed is the speed of its individual members. If this index is a trunk and the result is inconsistent among its member ports, this 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 this index is a trunk and the result is inconsistent among its member ports, 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.

This determines the forced mode of a combo port. For a non-combo port, this variable has a value of none(1), and setting this variable to none(1) has no effect. For a combo port, this has its own valid values not equal to none(1), and setting this variable to none(1) is not allowed. Enumeration: 'copperPreferredAuto': 3, 'sfpPreferredAuto': 5, 'none': 1, 'copperForced': 2, 'sfpForced': 4.

The maximum number for a trunk identifier.

The number of valid trunks.

Table of descriptive and status information about configuration of each trunk, similar to Cisco EtherChannel.

An entry in the table, containing information about configuration in one trunk of the switch.

This object identifies the trunk within the switch for which this entry contains information.

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. Enumeration: 'valid': 1, 'invalid': 2.

Table for LACP port configuration.

Entry for LACP port configuration.

This is defined as ifIndex in the IF-MIB.

Whether 802.3ad LACP is enabled. Enumeration: 'disabled': 2, 'enabled': 1.

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, 802.1w or 802.1s depending on the value specified by staProtocolType.

The conceptual entry of staPortTable.

The port and the trunk (excluding trunk member ports) interface of the staPortTable. The interface identified by a particular value of this index is the same interface as identified by the same value of dot1dStpPort in the BRIDGE-MIB.

Whether fast forwarding is enabled.

When operating in RSTP (version 2) mode, writing true(1) to this object forces this 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 as an edge-port and a value of false(2) indicates that this port should be assumed as 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 are aggregatable, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by management means. Enumeration: 'forceFalse': 1, 'forceTrue': 0, 'auto': 2.

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

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

Per-port spanning tree status. (1) Spanning tree protocol is enabled. (2) Spanning tree protocol is disabled.

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 that the Rapid Spanning Tree Protocol is as specified in IEEE 802.1w, and the value 'mstp(3)' indicates that the Multiple Spanning Tree Protocol is as specified in IEEE 802.1s. New values may be defined in the future as new or updated versions of the protocol become available. Enumeration: 'mstp': 3, 'stp': 1, 'rstp': 2.

The value used by the Port Transmit state machine to limit the maximum transmission rate.

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 BRIDGE-MIB will be rejected. While 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 BRIDGE-MIB must be used.

The name of the Multiple Spanning Tree region.

The Revision number of the Multiple Spanning Tree region.

The max hop number counts of the Multiple Spanning Tree region.

This table is used to configure the property of a specific instance in Multiple Spanning Tree or Rapid Spanning Tree. If Rapid Spanning Tree protocol is in use, the mstInstanceEditIndex is always 0.

A conceptual row containing the property of the RST or MST instance.

An arbitrary integer within the range from 1 to the value of the maximum instance that uniquely identifies a spanning tree instance.

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 a second) since the last topology change detected by the bridge entity in RST or MST.

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

The bridge identifier of the root of the spanning tree as determined by the Multiple Spanning Tree Protocol. (802.1s) or 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 or MST.

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

The maximum age of Multiple Spanning Tree Protocol ( 802.1s ) or Rapid Spanning Tree Protocol ( 802.1w ) 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 specific 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 or MST.

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 RST or MST 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 or MST 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 RST or MST protocol,the time (in hundredths of a 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 RST or MST protocol, the time (in hundredths of a 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 RST or MST protocol, the value used by the port transmit state machine to limit the maximum transmission rate.

For RST or MST 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 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 BRIDGE-MIB must be used.

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

The conceptual row for xstInstancePortTable.

The instance of the MSTP.

The port and the trunk (excluding trunk member ports) interface of the mstInstancePortTable. The interface identified by a particular value of this index is the same interface as identified by the same value of dot1dStpPort in the BRIDGE-MIB.

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 or MST 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 or MST 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. (6) For MST protocol only, indicates whether this instance is in a master role. Enumeration: 'backup': 5, 'alternate': 4, 'designated': 3, 'disabled': 1, 'master': 6, 'root': 2.

The Multiple Spanning Tree region instance vlan configuration table. Please read the actual instance vlan mapped in the mstInstanceOperTable.

A conceptual row containing the status of the MSTP instance.

An arbitrary integer within the range from 1 to the value of the maximum instance that uniquely identifies a spanning tree instance.

A string of octets containing one bit per VLAN. The first octet corresponds to VLANs with vlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc., The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'. To create a row, write any of mstInstanceEditVlansMap, mstInstanceEditVlansMap2k, mstInstanceEditVlansMap3k or mstInstanceEditVlansMap4k, to a non-empty list. To destroy a row, write all of these four variables to an empty list.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 1024 through 2047. The first octet corresponds to VLANs with vlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'. To create a row, write any of mstInstanceEditVlansMap, mstInstanceEditVlansMap2k, mstInstanceEditVlansMap3k or mstInstanceEditVlansMap4k, to a non-empty list. To destroy a row, write all of these four variables to an empty list.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 2048 through 3071. The first octet corresponds to VLANs with vlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'. To create a row, write any of mstInstanceEditVlansMap, mstInstanceEditVlansMap2k, mstInstanceEditVlansMap3k or mstInstanceEditVlansMap4k, to a non-empty list. To destroy a row, write all of these four variables to an empty list.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 3072 through 4095. The first octet corresponds to VLANs with vlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'. To create a row, write any of mstInstanceEditVlansMap, mstInstanceEditVlansMap2k, mstInstanceEditVlansMap3k or mstInstanceEditVlansMap4k, to a non-empty list. To destroy a row, write all of these four variables to an empty list.

The remaining hop count for this MST instance.

The Multiple Spanning Tree region instance vlan mapped table.

A conceptual row containing the status of the MSTP instance.

An arbitrary integer within the range from 1 to the value of the maximum instance that uniquely identifies a spanning tree instance.

A string of octets containing one bit per VLAN. The first octet corresponds to VLANs with vlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc., The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 1024 through 2047. The first octet corresponds to VLANs with vlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 2048 through 3071. The first octet corresponds to VLANs with vlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'.

A string of octets containing one bit per VLAN for VLANS with vlanIndex values of 3072 through 4095. The first octet corresponds to VLANs with vlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value vlanIndex in that octet. For each VLAN, if it is mapped to this MSTP instance, then the bit corresponding to that VLAN is set to '1'.

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 restart the application software with current configuration parameters saved in non-volatile memory. Setting this object to coldBoot(3) causes the device to reinitialize configuration parameters in non-volatile memory to default values and restart the application software. When the device is running normally, this variable has a value of running(1). Enumeration: 'running': 1, 'coldBoot': 3, 'warmBoot': 2.

Table of descriptive and status information about switches in this system.

An entry in the table, containing information about a single switch in this system.

Destination port for mirrored packets. This is defined as ifIndex in the IF-MIB.

Source port for mirrored packets. This is defined as 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. Enumeration: 'both': 3, 'rx': 1, 'tx': 2.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

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. Enumeration: 'disabled': 2, 'enabled': 1.

Whether to act as querier. Enumeration: 'disabled': 2, 'enabled': 1.

Maximum number of queries that have not been heard on the system before the system starts taking action to solicit reports.

Query interval.

Timeout value (seconds) between IGMP reports received on a port for an IP Multicast Address that can pass before the system sends an IGMP Query out the port and removes it from the list.

Query time-out.

Version.

Table for current router ports.

Entry for current router ports.

This is defined as dot1qVlanIndex in the Q-BRIDGE-MIB.

The set of ports which are current router ports. Within this list, some router ports are 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.

This is defined as dot1qVlanIndex in the Q-BRIDGE-MIB.

The set of ports which are static router ports.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

Table for current multicast addresses.

Entry for current multicast addresses.

This is defined as dot1qVlanIndex in the Q-BRIDGE-MIB.

IP address of multicast group.

The set of ports which are members.

The set of ports which are static members.

Table for static multicast addresses.

Entry for static multicast addresses.

This is defined as dot1qVlanIndex in the Q-BRIDGE-MIB.

IP address of multicast group.

The set of ports which are members.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

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. Enumeration: 'disabled': 2, 'enabled': 1.

The port number for HTTP.

Write it to restart(1) to restart DHCP. When read, this value always returns noRestart(2). Enumeration: 'noRestart': 2, 'restart': 1.

Whether HTTPS is enabled.

The port number for HTTPS.

Table for DHCP client information listed by interface. Depending on the nature of the product, this table may have only one entry(e.g. for the management VLAN), or may have many entries(e.g. for all ports, or for all static VLANs).

Entry for DHCP client information listed by interface.

This is defined by ifIndex in the IF-MIB.(static vlan if index)

Whether the Client ID is in text mode or in Hex mode. Enumeration: 'text': 2, 'hex': 3, 'notSpecify': 1.

The value that the DHCP client sets in the client_id option of DHCPDISCOVER and DHCPREQUEST messages. This value may be used by DHCP servers to uniquely identify the client.

The role of DHCP Relay Agent is to forward requests and replies between server and client when they are not in the same subnet. To enable DHCP Relay service user needs to specify Relay Server ip address and then restart DHCP Relay. This Table is to specify Relay Server ip address, the maximum numbers of server ip address user can specify is 5. To Restart DHCP Relay, please use the dhcpRelayRestart variable.

A conceptual row of dhcpRelayServerAddrTable.

The VLAN interface being used by this table entry.

The Index of the Relay server IP address.

The IP address of the relay server.

Set to restart(1) to restart DCHP Relay. Always get noRestart(2) when you read this variable. Enumeration: 'noRestart': 2, 'restart': 1.

A dhcp pool is a collection of user configuration such as option config-lease time or dns-server IPs, a network address for network pool, or a host IP plus a hardware address pair for host pool. However, a dhcp pool only can either be a network pool or a host pool, or none of them (such as that pool only containing option config no network address config or a host ip config as well)

A conceptual row of dhcpPoolTable.

PoolName, simply specify a string which string size NO MORE THAN 8

Pool Type: notSpecify(1); netWork(2);host(3) Enumeration: 'host': 3, 'netWork': 2, 'notSpecify': 1.

Pool Address

Subnet Mask

Hardware type: notSpecify(1); ethernet(2); ieee802(3); fddi(4) Enumeration: 'ethernet': 2, 'ieee802': 3, 'notSpecify': 1, 'fddi': 4.

MAC address

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

This is the Option table of the dhcpPoolTable, user can specify Options configuration in this table

A conceptual row of dhcpPoolOptionTable.

PoolName, simply specify a string which string size NO MORE THAN 8

Specifies the IP address of the next server in the boot process, which is typically a Trivial File Transfer Protocol(TFTP) server. One IP address is required.

Specifies the NetBIOS node type. Valid types are: none(1) b-node(2) - Broadcast p-node(3) - Peer-to-peer m-node(4) - Mixed h-node(5) - Hybrid. Enumeration: 'm-node': 4, 'none': 1, 'p-node': 3, 'b-node': 2, 'h-node': 5.

Specifies the domain name string.

To specify the name of the default boot image.

To configure the duration of the lease of an IP address that is assigned from a DHCP Server to a DHCP client.

Set this variable to text(2) of hex(3) to specify the mode of the Client Id, which is useful for CLI to determine the display way of the Client Id. You will get default value 'notSpecify(1)'when this variable had never been set. Setting this to notSpecify(1) is a invalid operation. Enumeration: 'text': 2, 'hex': 3, 'notSpecify': 1.

Content of Client Id. You MUST specify the dhcpPoolOptionCidMode before setting this variable.

To specify the DNS IP servers available to a DHCP client, you can specify up to two addresses for each DHCP pool.

A conceptual row of dhcpPoolOptionDnsSerTable.

PoolName, simply specify a string which string size NO MORE THAN 8

Index of the DNS server.

Ip address of the DNS server.

Specifices the default router list for a DHCP Client, you can specify up to two addresses for each DHCP pool.

A conceptual row of dhcpPoolOptDefaultRouterTable.

PoolName, simply specify a string which string size NO MORE THAN 8

Index of the default router.

Specifies the IP address of a router. One IP address is required.

To configure the NetBIOS WINS name servers that are available to DHCP clients. You can specify up to eight addressed for each DHCP pool.

A conceptual row of dhcpPoolOptNetbiosServerTable.

PoolName, simply specify a string which string size NO MORE THAN 8

Index of the Netbios name Server.

Specifies the IP address of the NetBIOS WINS name server. One IP address is required.

To specify IP addresses that a DHCP Server shuld not assign to DHCP clients.

A conceptual row of dhcpServerExcludedIpAddrTable.

The excluded IP address, or first IP address in an excluded address range.

The last IP address in the excluded address range.

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

To configure the address bindings on the DHCP server.

A conceptual row of dhcpServerLeaseBindingTable.

The IP address of the host as recorded on the DHCP Server.

The MAC address of the host as recorded on the DHCP Server.

The lease expiration date of the IP address of the host.

Show current system real time in sec.

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

Setting this to 1 to enable the dhcp server service. Setting this to 2 to disable the dhcp server service.

A table of iPAddrEntry.

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 IP address of this Net interface. The default value for this object is 0.0.0.0. If either the IPAddrIPAddress or IPAddrSubnetMask is 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 IPAddrIPAddress or IPAddrSubnetMask 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 VLAN interface being used by this table entry. Only the VLAN interfaces which have an IP configured will appear in the table.

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 a detailed description of this object, please refer to SNMPv2-TC MIB.

Table of descriptive and status information about configuration of each switch ports(including expansion slot) in this system.

An entry in the table, containing information about configuration in one switch port of the switch.

This is defined as ifIndex in the IF-MIB.

Whether broadcast storm protection is enabled. Enumeration: 'disabled': 2, 'enabled': 1.

Sample type. If this is pkt-rate(1), then bcastStormPktRate is valid. If this is octet-rate(2), then bcastStormOctetRate is valid. If this is percent(3), then bcastStormPercent is valid. Enumeration: 'percent': 3, 'octet-rate': 2, 'pkt-rate': 1.

Broadcast storm threshold as packets per second.

Broadcast storm threshold as octets per second.

Broadcast storm threshold as percentage of bandwidth.

Table for VLAN configuration.

Entry for VLAN configuration.

Same is 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.

This is defined as ifIndex in the IF-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. Enumeration: 'dot1qTrunk': 2, 'hybrid': 1.

Whether IP precedence or DSCP look-up is enabled. Enumeration: 'disabled': 1, 'dscp': 3, 'precedence': 2.

Table for IP precedence priority mapping.

Entry for IP precendence priority mapping.

This is defined as ifIndex in the IF-MIB.

Precedence value for this entry.

Class of service for this entry.

This object is to restore IP Precedence settings of a port to default. To do this, write it to the value of ifIndex defined by the ifIndex in the IF-MIB. When read, this object always returns 0.

Table for IP DSCP priority mapping.

Entry for IP DSCP priority mapping.

This is defined as ifIndex in the IF-MIB.

DSCP value for this entry.

Class of service for this entry.

This object is to restore IP DSCP settings of a port to default. To do this, write it to the value of ifIndex defined by the ifIndex in the IF-MIB. 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.

The global status for the prioQueue. wrr(1),strict(2) Enumeration: 'strict': 2, 'wrr': 1.

Table for per port weighted round robin (WRR).

Entry for per port weighted round robin (WRR).

The port interface of the prioWrrPortEntry. 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.

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.

This entry includes a destination IP address to which to send traps for this community.

The address to send traps.

A community to which this destination address belongs.

Writing this to valid(1) creates an entry. Writing this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

This variables represent the version of the Trap we wish to send to trap Receiver. If the value is 1, mean we wish to send Version 1 trap. If the value is 2, mean we wish to send version 2 trap. If the value is 3, mean we wish to send version 3 trap. Enumeration: 'version1': 1, 'version2': 2, 'version3': 3.

Determines the UDP port number of the trap that is to be sent to the trap Receiver.

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 marker conceptual row entry. This object is used to manage creation, deletion and modification of rows in this table. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Once a row becomes active, value in any other column within such row cannot be modified. ip ace created by SNMP basically belong to ip extended ACL. Valid values are: active(1); notInService(2); notReady(3); createAndGo(4); createAndWait(5); destroy(6). Set this value to createAndGo(4) to ceate a new entry and make it active at once, set to createAndWait(5) means create a new entry but not active now, set to destroy(6) to delete an entry You may get one of the following value when you try to read this variable: active(1); notInService(2); notReady(3) representing the current status of this entry

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 acl to cos mapping conceptual row entry. This object is used to manage creation, deletion and modification of rows in this table. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Once a row becomes active, value in any other column within such row cannot be modified. ip ace created by SNMP basically belong to ip extended ACL. Valid values are: active(1); notInService(2); notReady(3); createAndGo(4); createAndWait(5); destroy(6). Set this value to createAndGo(4) to ceate a new entry and make it active at once, set to createAndWait(5) means create a new entry but not active now, set to destroy(6) to delete an entry You may get one of the following value when you try to read this variable: active(1); notInService(2); notReady(3) representing the current status of this entry.

The Port Security(MAC bindind) 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 written. 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.

Key for TACACS.

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 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 variables to disconnect to disconnect the connection, when read, this variables always return noDisconnect(1). Enumeration: 'noDisconnect': 1, 'disconnect': 2.

The encryption type of the SSH.

The SSH server key size.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of RSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshRsaHostKey1: part 1 of the RSA host key (1-128) sshRsaHostKey2: part 2 of the RSA host key (129-256) sshRsaHostKey3: part 3 of the RSA host key (257-384) sshRsaHostKey4: part 4 of the RSA host key (385-512) sshRsaHostKey5: part 5 of the RSA host key (513-640) sshRsaHostKey6: part 6 of the RSA host key (641-768) sshRsaHostKey7: part 7 of the RSA host key (769-896) sshRsaHostKey8: part 8 of the RSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshRsaHostKey1, and a string which length is 1 in sshRsaHostKey2, moreover, sshRsaHostKey3 to sshRsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

The total length of DSA host key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshDsaHostKey1: part 1 of the DSA host key (1-128) sshDsaHostKey2: part 2 of the DSA host key (129-256) sshDsaHostKey3: part 3 of the DSA host key (257-384) sshDsaHostKey4: part 4 of the DSA host key (385-512) sshDsaHostKey5: part 5 of the DSA host key (513-640) sshDsaHostKey6: part 6 of the DSA host key (641-768) sshDsaHostKey7: part 7 of the DSA host key (769-896) sshDsaHostKey8: part 8 of the DSA host key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshDsaHostKey1, and a string which length is 1 in sshDsaHostKey2, moreover, sshDsaHostKey3 to sshDsaHostKey8 will all got zero-length string.

This variable is for host key generating. For the set behavior: set it to genRsaKey(2) to generate the RSA host key, genDsaKey(3) to generate the DSA host key, if genBothKeys(4) is set, both RSA and DSA host key are generated. For the get behavior: you will get genRsaKey(2), genDsaKey(3) or genBothKeys(4) when the key gen action is in progress. otherwise, you will get noGen(1). Enumeration: 'genBothKeys': 4, 'genRsaKey': 2, 'noGen': 1, 'genDsaKey': 3.

The result of the last KeyGen status. if no Key gen action has been perform you will get unknown(1) status. Enumeration: 'unknown': 1, 'success': 2, 'failure': 3.

To save host key from memory to flash. For the set behavior: set it to save(2) to perform the save operation. For the get behavior: you will get save(1) when the save action is in progress. otherwise, you will get noSave(1). Enumeration: 'noSave': 1, 'save': 2.

The result of the last savekey status. if no save action has been perform you will get unknown(1) status. Enumeration: 'unknown': 1, 'success': 2, 'failure': 3.

To delete the host key. For the set behavior: set it to delRsaKey(2) to delete the RSA host key, delDsaKey(3) to delete the DSA host key, or delBothKeys(4) to delete both RSA and DSA host key. For the get behavior: you will get delRsaKey(2), delDsaKey(3) or delBothKeys(4) when the delete operation is in progress. otherwise, you will get noDel(1). Enumeration: 'delRsaKey': 2, 'noDel': 1, 'delBothKeys': 4, 'delDsaKey': 3.

The conceptual table of all of sshUserEntry

The conceptual row for sshUserTable.

User Name.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of RSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the RSA user key (1-128) sshUserRsaKey2: part 2 of the RSA user key (129-256) sshUserRsaKey3: part 3 of the RSA user key (257-384) sshUserRsaKey4: part 4 of the RSA user key (385-512) sshUserRsaKey5: part 5 of the RSA user key (513-640) sshUserRsaKey6: part 6 of the RSA user key (641-768) sshUserRsaKey7: part 7 of the RSA user key (769-896) sshUserRsaKey8: part 8 of the RSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserRsaKey1, and a string which length is 1 in sshUserRsaKey2, moreover, sshUserRsaKey3 to sshUserRsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

The total length of DSA user key is 1024 characters, it is divided into 8 parts and store in 8 separated mib variables as below: sshUserRsaKey1: part 1 of the DSA user key (1-128) sshUserRsaKey2: part 2 of the DSA user key (129-256) sshUserRsaKey3: part 3 of the DSA user key (257-384) sshUserRsaKey4: part 4 of the DSA user key (385-512) sshUserRsaKey5: part 5 of the DSA user key (513-640) sshUserRsaKey6: part 6 of the DSA user key (641-768) sshUserRsaKey7: part 7 of the DSA user key (769-896) sshUserRsaKey8: part 8 of the DSA user key (897-1024) Please note that if the key string is less then 1024 characters, the remaining part of the string will filled by zero-length string. for example, if the length of the key is 129, we will get a string which length is 128 in sshUserDsaKey1, and a string which length is 1 in sshUserDsaKey2, moreover, sshUserDsaKey3 to sshUserDsaKey8 will all got zero-length string.

To delete the user key. For the set behavior: set it to delRsaKey(2) to delete the RSA user key, delDsaKey(3) to delete the DSA user key, or delBothKeys(4) to delete both RSA and DSA user key. For the get behavior: you will get delRsaKey(2), delDsaKey(3) or delBothKeys(4) when the delete operation is in progress. otherwise, you will get noDel(1). Enumeration: 'delRsaKey': 2, 'noDel': 1, 'delBothKeys': 4, 'delDsaKey': 3.

The conceptual table of all of aclIpAceEntry.

The conceptual row for aclIpAceTable.

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

The unique index of an ACE within an ACL.

Specifies the IP precedence value to be matched against. This object cannot not be configured when the status of the entry, aclIpAceStatus, is active(1).

Indicates the action to be taken if a packet matches this ACE. This object cannot not be configured when the status of the entry, aclIpAceStatus, is active(1). 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. This object cannot be configured when the status of the entry, aclIpAceStatus, is active(1).

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

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.

Specifies the IP precedence value to be matched against. This object cannot be configured when the status of the entry, aclIpAceStatus, is active(1). The value of this object is ignored whenever the value of aclIpAcePrec object is 8.

Specifies the IP ToS facility value to be matched against. This object cannot be configured when the status of the entry, aclIpAceStatus, is active(1). The value of this object is ignored whenever the value of aclIpAcePrec object is 9.

Specifies the DSCP value to be matched against. This object cannot be configured when the status of the entry, aclIpAceStatus, is active(1). The value of this object is ignored whenever the value of aclIpAcePrec object is 64.

Indicates how a packet's source TCP/UDP port number is to be compared. noOperator(1), which is the default value, means no comparison is to be made with the source TCP/UDP port number. Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

If the aclIpAceSourcePortOp is range(3), this indicates the lower bound of the TCP/UDP port number value range.

If the aclIpAceSourcePortOp is range(3), this indicates the upper bound of the TCP/UDP port number value range.

If the aclIpAceSourcePortOp is equal(2), this indicates the bitmask of the aclIpAceMinSourcePort.

Indicates how a packet's destination TCP/UDP port number is to be compared. noOperator(1), which is the default value, means that no comparison is to be made with the destination TCP/UDP port number. Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

If the aclIpAceDestPortOp is range(3), this indicates the lower bound of the TCP/UDP port number value range.

If the aclIpAceDestPortOp is range(3), this indicates the upper bound of the TCP/UDP port number value range.

If the aclIpAceDestPortOp is equal(2), this indicates the bitmask of the aclIpAceMinDestPort.

Indicates how the control flags of TCP packets are to be compared. aceIpControlCode is AND-ed with aceIpControlCodeBitmask.

Indicates how the control flags of TCP packets are to be compared. It can be used to check multiple flags of the FIN, SYN, RST, PSH, ACK, URG by the 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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of all of aclMacAceEntry.

The conceptual row for aclMacAceTable.

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

The unique index of an ACE within an ACL.

Specifies the entry's precedence.

Indicates the action to be taken if a packet matches this ACE. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1). Enumeration: 'deny': 2, 'permit': 1.

Used to check the packet format of the packets. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1). Enumeration: 'untagged802Dot3': 3, 'tagggedEth2': 4, 'any': 1, 'untagged-Eth2': 2, 'tagged802Dot3': 5.

Indicates the 48-bit 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. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

The specified source MAC address mask. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

Indicates the 48-bit 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. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

The specified destination MAC address mask. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

Indicates how a packet's vid is to be compared. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1). Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

Indicates the lower bound of the vid value range if the aclMacAceVidOp is range(3). This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

The bitmask of vid if the aclMacAceVidOp is equal, default value is 0xfff.

Indicates the upper bound of the vid value range if the aclMacAceVidOp is range(3). This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

Indicates how a packet's ethertype is to be compared. This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1). Enumeration: 'range': 3, 'equal': 2, 'noOperator': 1.

The bitmask of vid if the aclMacAceVidOp is equal(2) , default value is 0xFFFF.

Indicates the lower bound of the vid value range if the aclMacAceEtherTypeOp is range(3). This object cannot be configured when the status of the entry, aclMacAceStatus, is active(1).

Indicates the upper bound of the vid value range if the aclMacAceEtherTypeOp is range(3). This object cannot be configured when the status of the entry, aclMacAceStatus, is active(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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of aclAclGroupEntry.

The conceptual row for aclAclGroupTable.

The interface number specifying the ACL binding to.

Specifies the ingress IP ACL(standard or extended) binding to the interface.

Specifies the egress IP ACL(standard or extended) binding to the interface.

Specifies the ingress MAC ACL binding to the interface.

Specifies the egress MAC ACL binding to the interface.

The conceptual table of aclIngressIpMaskEntry.

The conceptual row for aclIngressIpMaskTable.

Indicates the bitmask of the source IP address. The relative bitmask must be created before the ACE binds to the interface. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates whether to check the IP precedence against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates whether to check the IP ToS facility against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates whether to check the IP DSCP against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates whether to check the IP precednce against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates whether to check the IP protocol against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates the source IP bitmask to check against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates the destination IP bitmask to check against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates the source port bitmask to check against the TCP/UDP packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates the destination port bitmask to check against the TCP/UDP packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(1).

Indicates the control code bitmask to check against the TCP packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressIpMaskStatus, is active(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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of aclEgressIpMaskEntry.

The conceptual row for aclEgressIpMaskTable.

The index of a mask entry within a mask table.

The created precedence of an mask entry within the mask table.

Indicates whether to check the IP ToS facility against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates whether to check the IP DSCP against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates whether to check the IP precedence against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates whether to check the IP protocol against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates the source IP bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates the destination IP bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates the source port bitmask to check against the TCP/UDP packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates the destination port bitmask to check against the TCP/UDP packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(1).

Indicates the control code bitmask to check against the TCP packets. The relative bitmask must be created before the ACE binds to the interface in egress direction. This object cannot be configured when the status of the entry, aclEgressIpMaskStatus, is active(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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of aclIngressMacMaskEntry.

The conceptual row for aclIngressMacMaskTable.

The index of an mask entry within an ingress mask table.

The created order of an mask entry within an ingress mask table.

Indicates the source MAC bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressMacMaskStatus, is active(1).

Indicates the destination MAC bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressMacMaskStatus, is active(1).

Indicates the vid bitmask to check against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressMacMaskStatus, is active(1).

Indicates the ethertype bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressMacMaskStatus, is active(1).

Indicates whether to check the packet format against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclIngressMacMaskStatus, is active(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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of aclEgressMacMaskEntry.

The conceptual row for aclEgressMacMaskTable.

The index of a mask entry within an egress mask table.

The created precedence of a mask entry within an egress mask table.

Indicates the source MAC bitmask to check against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclEgressMacMaskStatus, is active(1).

Indicates the destination MAC bitmask to check against the packets, The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclEgressMacMaskStatus, is active(1).

Indicates the vid bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclEgressMacMaskStatus, is active(1).

Indicates the ethertype bitmask to check against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclEgressMacMaskStatus, is active(1).

Indicates whether to check the packet format against the packets. The relative bitmask must be created before the ACE binds to the interface in ingress direction. This object cannot be configured when the status of the entry, aclEgressMacMaskStatus, is active(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 a detailed description of this object, please refer to SNMPv2-TC MIB.

A list of IP address entries.

This entry includes an IP address range which the system will allow them to connect to this device through SNMP.

The start-ip-address.

The end-ip-address.

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

A list of IP address entries.

This entry includes an IP address range which the system will allow them to connect to this device through SNMP.

The start-ip-address.

The end-ip-address.

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

A list of IP address entries.

This entry includes an IP address range which the system will allow them to connect to this device through SNMP.

The start-ip-address.

The end-ip-address.

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

To delete all dynamic entries in the ARP cache, write this variable to delete(1). Writing this variable to noDelete(2) has no effect on the device. When read, this variable always returns noDelete(2). Enumeration: 'noDelete': 2, 'delete': 1.

The timeout is provided for entries in the ARP Cache. It's for dynamic mapping only. Static mapping by creating a entry that associates a logical address with a physical address is never age out.

The number of ARP Request packets sent by the ARP process.

The number of ARP Request packets received by the ARP process.

The number of ARP Reply packets sent by the ARP process.

The number of ARP Reply packets received by the ARP process.

A list of Proxy ARP status. This table has entries for all static VLANs.

An entry in the table, containing information about Proxy ARP configuration.

This is defined as a VLAN interface. A routing interface is a VLAN binds a IP subnet.

Enable or Disable Proxy ARP process on an interface

The update time in seconds controls the advertising of regular update messages. The real working model, while using this timer, the time should be offset by a small random time (+/- 0 to 5 seconds each time it is set.

The timeout timer in seconds governs the validity of a route. It is initialized when a route is established, and any time an update message is received for the route. If the setting time elapses from the last time the timrout was initialized, the route is considered to have expired, and the hop count of the route is set to infinite. It should be at least three times the value of update timer.

When the information about a route becomes invalid, the system should not immediately purge that route from its table. Instead, it continues to advertise the route with a metric of infinite. At the same time, the garbage-collection timer is set for that route. When the count reaches zero, the route is purged from the the table. This timer allows neighbors to become aware of the invalidity of a route prior to purging.

Enable or Disable RIP routing process on a system.

To specify a RIP version used globally by the rourter. Enumeration: 'rip2': 3, 'rip1': 2, 'byInterface': 1.

A list of RIP instability preventing status

An entry in the table, containing information about RIP instability preventing configuration. The ifIndex index is a VLAN's ifIndex

This is defined as a VLAN interface. A routing interface is a VLAN binds a IP subnet.

Enable or Disable RIP Poison Reverse on an interface Enumeration: 'none': 3, 'splitHorizon': 1, 'poisonReverse': 2.

Write it to reset(1), the following objects in RFC 1724 should be reset: 1. Global Counters: 'rip2GlobalRouteChanges', 'rip2GlobalQueries'. 2. Interface Status Table, for each 'rip2IfStatAddress': 'rip2IfStatRcvBadPackets', 'rip2IfStatRcvBadRoutes', 'rip2IfStatSendUpdates' 3. Peer Table, for each 'rip2PeerAddress' and 'rip2PeerDomain', 'rip2PeerRcvBadPackets', 'rip2PeerRcvBadRoutes' When read it, this value always is noReset(2). Enumeration: 'reset': 1, 'noReset': 2.

The RIP Network address.

Set this variable to create or destroy a RIP network address.

Set router ID automatically or manually. Enumeration: 'auto': 1, 'manual': 2.

Enable or disable rfc1583 compatibility.

Set the reference bandwith of auto cost, the unit is Mbps.

Enable or disable ASBR to generate a default external route into an OSPF domain if the default route already exists.

If enabled, always advertises the default route regardless of whether the default route exists. Enumeration: 'always': 1, 'notAlways': 2.

External link type associated with the default route advertised into the OSPF routing domain. Enumeration: 'type1': 1, 'type2': 2.

Metric used for generating the default route.

Sets the hold time between two consecutive SPF calculations.

Sets the delay time to calculate SPF Delay time, in seconds, between when OSPF receives a topology change and when it starts an SPF calculation.

Records the OSPF area numbers.

A conceptually table for ospfNssaEntry.

A conceptually row for ospfNssaTable.

The 32-bit identifier for the NSSA. On creation, this can be derived from the instance.

Enabled or disabled to import routes only into the normal areas, but not into the NSSA area.

Enable or disable to generate a Type 7 default into the NSSA area.

The status of this conceptual row entry. This object is used 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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of all of ospfRedistributeEntry.

The conceptual row for ospfRedistributeTable.

Protocol ID. Static is not supported now. Enumeration: 'connected': 3, 'static': 2, 'rip': 1.

Metric type. Enumeration: 'type1': 1, 'type2': 2.

Metric value.

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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of all of ospfSummaryAddressEntry.

The conceptual row for ospfSummaryAddressTable.

Summary address.

Summary mask.

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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The conceptual table of all of ospfNetworkAreaAddressEntry.

The conceptual row for ospfNetworkAreaAddressTable.

NetworkArea address.

NetworkArea mask.

NetworkArea area ID.

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 a detailed description of this object, please refer to SNMPv2-TC MIB.

The router's DVMRP version information. Similar to sysDescr in MIB-II, this is a free-form field which can be used to display vendor-specific information.

The number of entries in the routing table. This can be used to monitor the routing table size.

The number of entries in the routing table with non infinite metrics. This can be used to detect network partitions by observing the ratio of reachable routes to total routes.

The (conceptual) table listing the router's multicast- capable interfaces.

An entry (conceptual row) in the dvmrpInterfaceTable. This row augments ipMRouteInterfaceEntry in the IP Multicast MIB, where the threshold object resides.

The ifIndex value of the interface for which DVMRP is enabled.

The IP address this system will use as a source address on this interface. On unnumbered interfaces, it must be the same value as dvmrpInterfaceLocalAddress for some interface on the system.

The distance metric for this interface which is used to calculate distance vectors.

The status of this entry. Creating the entry enables DVMRP on the virtual interface; destroying the entry or setting it to notInService disables DVMRP on the virtual interface.

The number of DVMRP messages received on the interface by the DVMRP process which were subsequently discarded as invalid (e.g. invalid packet format, or a route report from an unknown neighbor).

The number of routes, in valid DVMRP packets, which were ignored because the entry was invalid.

The number of routes, in DVMRP Report packets, which have been sent on this interface. Together with dvmrpNeighborRcvRoutes at a peer, this object is useful for detecting routes being lost.

The (shared) key for authenticating neighbors on this interface. This object is intended solely for the purpose of setting the interface key, and MUST be accessible only via requests using both authentication and privacy. The agent MAY report an empty string in response to get, get- next, get-bulk requests.

The highest version number of all known interface keys for this interface used for authenticating neighbors.

The generation identifier for the interface. This is used by neighboring routers to detect whether the DVMRP routing table should be resent.

The (conceptual) table listing the router's DVMRP neighbors, as discovered by receiving DVMRP messages.

An entry (conceptual row) in the dvmrpNeighborTable.

The value of ifIndex for the virtual interface used to reach this DVMRP neighbor.

The IP address of the DVMRP neighbor for which this entry contains information.

The time since this DVMRP neighbor (last) became a neighbor of the local router.

The minimum time remaining before this DVMRP neighbor will be aged out.

The neighboring router's generation identifier.

The neighboring router's major DVMRP version number.

The neighboring router's minor DVMRP version number.

This object describes the neighboring router's capabilities. The leaf bit indicates that the neighbor has only one interface with neighbors. The prune bit indicates that the neighbor supports pruning. The generationID bit indicates that the neighbor sends its generationID in Probe messages. The mtrace bit indicates that the neighbor can handle mtrace requests. Bits: 'mtrace': 3, 'leaf': 0, 'prune': 1, 'generationID': 2.

The total number of routes received in valid DVMRP packets received from this neighbor. This can be used to diagnose problems such as unicast route injection, as well as giving an indication of the level of DVMRP route exchange activity.

The number of packet received from this neighbor which were discarded as invalid.

The number of routes, in valid DVMRP packets received from this neighbor, which were ignored because the entry was invalid.

State of the neighbor adjacency. Enumeration: 'active': 2, 'down': 4, 'ignoring': 3, 'oneway': 1.

The table of routes learned through DVMRP route exchange.

An entry (conceptual row) containing the multicast routing information used by DVMRP in place of the unicast routing information.

The network address which when combined with the corresponding value of dvmrpRouteSourceMask identifies the sources for which this entry contains multicast routing information.

The network mask which when combined with the corresponding value of dvmrpRouteSource identifies the sources for which this entry contains multicast routing information.

The address of the upstream neighbor (e.g., RPF neighbor) from which IP datagrams from these sources are received.

The value of ifIndex for the interface on which IP datagrams sent by these sources are received. A value of 0 typically means the route is an aggregate for which no next- hop interface exists.

The distance in hops to the source subnet.

The minimum amount of time remaining before this entry will be aged out.

The time since the route represented by this entry was learned by the router.

The (conceptual) table containing information on the next hops on outgoing interfaces for routing IP multicast datagrams.

An entry (conceptual row) in the list of next hops on outgoing interfaces to which IP multicast datagrams from particular sources are routed.

The network address which when combined with the corresponding value of dvmrpRouteNextHopSourceMask identifies the sources for which this entry specifies a next hop on an outgoing interface.

The network mask which when combined with the corresponding value of dvmrpRouteNextHopSource identifies the sources for which this entry specifies a next hop on an outgoing interface.

The ifIndex value of the interface for the outgoing interface for this next hop.

Type is leaf if no downstream dependent neighbors exist on the outgoing virtual interface. Otherwise, type is branch. Enumeration: 'leaf': 1, 'branch': 2.

The (conceptual) table listing the router's upstream prune state.

An entry (conceptual row) in the dvmrpPruneTable.

The group address which has been pruned.

The address of the source or source network which has been pruned.

The address of the source or source network which has been pruned. The mask must either be all 1's, or else dvmrpPruneSource and dvmrpPruneSourceMask must match dvmrpRouteSource and dvmrpRouteSourceMask for some entry in the dvmrpRouteTable.

The amount of time remaining before this prune should expire at the upstream neighbor. This value should be the minimum of the default prune lifetime and the remaining prune lifetimes of the local router's downstream neighbors, if any.

This entity's IP Extension Routing table.

A particular route to a particular destina- tion, under a particular policy.

The destination IP address of this route. This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteMask object is not equal to x.

Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipCidrRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipCidrRouteMask by reference to the IP Ad- dress Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteDest object is not equal to ipCidrRoute- Dest.

The policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30

On remote routes, the address of the next sys- tem en route; Otherwise, 0.0.0.0.

The OSPF SubType, when the ipCidrRouteProto in IP-FORWARD MIB is ospf(13), this object has value (2)-(7), otherwises, this object will always show none(1). Enumeration: 'none': 1, 'ospfNssa2': 5, 'ospfIntra': 3, 'ospfNssa1': 4, 'ospfInter': 2, 'ospfType1': 6, 'ospfType2': 7.

Whether system log is enabled. Enumeration: 'disabled': 2, 'enabled': 1.

Severity level for logging to flash.

Severity level for logging to RAM.

Whether the remote log system is enabled.

Severity level for remote log.

The FacilityType for remote log. Enumeration: 'localUse3': 19, 'localUse2': 18, 'localUse1': 17, 'localUse0': 16, 'localUse7': 23, 'localUse6': 22, 'localUse5': 21, 'localUse4': 20.

A Table for storing the remote log Server list.

A conceptually row for remoteLogServerTable.

The IP address of the remote log Server.

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

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

specify the SMTP minimum severity level to send the event message.

SMTP source email address, the sender's mail address that appears in the 'From' field of the mail.

The table of SMTP server Ip. The maximum servers to be added is 3.

A conceptual row of the smtpServerIpTable.

SMTP mail servers IP address.

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

The table of the destination e-mail address. The maximum numbers of destination email address to be added is 5.

A conceptual row of the smtpDestEMailTable.

SMTP destination e-mail address.

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

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

Define the generation of a parity bit. Enumeration: 'partyEven': 2, 'partyOdd': 3, 'partyNone': 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 variables to set the interval that the EXEC command interpreter waits until user input is detected, set the value to 0 to disable it.

In serial console, use the consolePasswordThreshold variabes to set the password intrusion threshold, which limits the number of failed logon attempts allowed. Set it value to 0 to disable it.

In Console, Use the consoleSilentTime variable to set the amount of time the management console is inaccessible after the number of unsuccessful logon attempts exceeds the threshold set by the password-thresh command. Set it to 0 to disable it.

Baud rate. Valid values are 2400, 4800, 9600, 19200, 38400, 57600, 115200. Setting this variable to 0 means autobaud. Please read the actual baud rate in the consoleOperBaudRate variable.

The baud rate currently in use.

In a telnet session, to set the interval that the EXEC command interpreter waits until user input is detected, use the telnetExecTimeout variables.

In a telnet session, use the consolePasswordThreshold variabes to set the password intrusion threshold, which limits the number of failed logon attempts allowed. Set it value to 0 to disable it.

To enable or disable the telnet function. Any new telnet request will be rejected and all current telnet sessions will be terminated if this status is set to disabled(2).

The telnet session port number.

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

Service mode. Enumeration: 'unicast': 1, '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 avaiable 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 permuations 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 varible 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 avaiable 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 permuations 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 varible can be ignored.

Type of file to copy in fileCopyMgt. If the fileCopySrcOperType or fileCopyDestOperType is either runningCfg(2) or startupCfg(3), this varible can be ignored. If the fileCopySrcOperType or fileCopyDestOperType is unit(5), this varibles 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 messge, this value is meaningful only when the fileCopyStatus is fileCopyTftpUndefError(1).

This table contain the information of the file system, we can also perfrom 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.

To enable the IP Domain Naming System (DNS)-based host name-to-address translation

To define a default domain name to complete unqualified host names (names without a dotted-decimal domain name)

This table is used to define static host name-to-address mapping.

A conceptual row for the dnsHostTable.

The DNS Host name.

The secondary index of this dnsHostTable, representing the sequence of the dnsHostIp.

The DNS Host IP.

This table display the alias of the host name

A conceptually row for dnsAliasTable.

Host Name

Alias

This table define a list of default domain names to complete unqualified host names

A conceptually row for dnsDomainListTable.

Domain Name

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

To specify the address of one or more name servers to use for name and address resolution

A conceptually row for dnsNameServerTable.

Ip address of name server

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

To display the RRs in DNS cache

A conceptually row for dnsCacheTable.

The sequence number of the entry

Always get 4, means this record is unreliable

Cache Type: address(1); cname(2). Enumeration: 'cname': 2, 'address': 1.

Cache Ip

Cache Ttl

Cache domain

The amount of time in minutes a row in cHsrpGrpTable can remain in a state other than active before being timed out.

A table containing information on each HSRP group for each interface.

Information about an HSRP group. Management applications use cHsrpGrpRowStatus to control entry modification, creation and deletion. Setting cHsrpGrpRowStatus to 'active' causes the router to communicate using HSRP. The value of cHsrpGrpRowStatus may be set to 'destroy' at any time. Entries may not be created via SNMP without explicitly setting cHsrpGrpRowStatus to either 'createAndGo' or 'createAndWait'. Entries can be created and modified via the management protocol or by the device's local management interface. A management application wishing to create an entry should choose the ifIndex of the interface which is to be added as part of an HSRP group. Also, a cHsrpGrpNumber should be chosen. A group number is unique only amongst the groups on a particular interface. The value of the group number appears in packets which are transmitted and received on a LAN segment to which the router is connected. The application must select the group number as explained in the description for cHsrpGrpNumber. If the row is not active, and a local management interface command modifies that row, the row may transition to active state. A row which is not in active state will timeout after a configurable period (five minutes by default). This timeout period can be changed by setting cHsrpConfigTimeout.

This object along with the ifIndex of a particular interface uniquely identifies an HSRP group. Group numbers 0,1 and 2 are the only valid group numbers for TokenRing interfaces. For other media types, numbers range from 0 to 255. Each interface has its own set of group numbers. There's no relationship between the groups configured on different interfaces. Using a group number on one interface doesn't preclude using the same group number on a different interface. For example, there can be a group 1 on an Ethernet and a group 1 on Token Ring. More details can be found from RFC 2281.

This is an unencrypted authentication string which is carried in all HSRP messages. An authentication string mismatch prevents a router interface from learning the designated IP address or HSRP timer values from other HSRP-enabled routers with the same group number. The function of this object is not to supply any sort of security-like authentication but rather to confirm that what's happening is what's intended. In other words, this is meant for sanity checking only.

The cHsrpGrpPriority helps to select the active and the standby routers. The router with the highest priority is selected as the active router. In the priority range of 0 to 255, 0 is the lowest priority and 255 is the highest priority. If two (or more) routers in a group have the same priority, the one with the highest ip address of the interface is the active router. When the active router fails to send a Hello message within a configurable period of time, the standby router with the highest priority becomes the active router. A router with highest priority will only attempt to overthrow a lower priority active router if it is configured to preempt. But, if there is more than one router which is not active, the highest priority non-active router becomes the standby router.

This object, if TRUE, indicates that the current router should attempt to overthrow a lower priority active router and attempt to become the active router. If this object is FALSE, the router will become the active router only if there is no such router (or if an active router fails).

This delay is the time difference between a router power up and the time it can actually start preempting the currently active router. When a router first comes up, it doesn't have a complete routing table. If it's configured to preempt, then it will become the Active router, but it will not be able to provide adequate routing services. The solution to this is to allow for a configurable delay before the router actually preempts the currently active router.

HSRP routers learn a group's Hellotime or Holdtime from hello messages. The Hellotime is used to determine the frequency of generating hello messages when this router becomes the active or standby router. The Holdtime is the interval between the receipt of a Hello message and the presumption that the sending router has failed. If this object is TRUE, the cHsrpGrpConfiguredHelloTime and cHsrpGrpConfiguredHoldTime will be used. If it is FALSE, the Hellotime and Holdtime values are learned.

If cHsrpGrpUseConfiguredTimers is true, cHsrpGrpConfiguredHelloTime is used when this router is an active router. Otherwise, the Hellotime learned from the current active router is used. All routers on a particular LAN segment must use the same Hellotime.

If cHsrpGrpUseConfiguredTimers is true, cHsrpGrpConfiguredHoldTime is used when this router is an active router. Otherwise, the Holdtime learned from the current active router is used. All routers on a particular LAN segment should use the same Holdtime. Also, the Holdtime should be at least three times the value of the Hellotime and must be greater than the Hellotime.

If the Hellotime is not configured on a router, it can be learned from the Hello messages from active router, provided the Hello message is authenticated. If the Hellotime is not learned from a Hello message from the active router and it is not manually configured, a default value of 3 seconds is recommended.

If the Holdtime is not configured on a router, it can be learned from the Hello message from the active router. Holdtime should be learned only if the Hello message is authenticated. If the Holdtime is not learned and it is not manually configured, a default value of 10 seconds is recommended.

This is the primary virtual IP address used by this group. If this address is configured (i.e a non zero ip address), this value is used. Otherwise, the agent will attempt to discover the virtual address through a discovery process (which scans the hello messages).

If this object is TRUE, cHsrpGrpVirtualIpAddr was a configured one. Otherwise, it indicates that cHsrpGrpVirtualIpAddr was a learned one.

Ip Address of the currently active router for this group.

Ip Address of the currently standby router for this group.

The current HSRP state of this group on this interface.

Mac Addresses used are as specified in RFC 2281. For ethernet and fddi interfaces, a MAC address will be in the range 00:00:0c:07:ac:00 through 00:00:0c:07:ac:ff. The last octet is the hexadecimal equivalent of cHsrpGrpNumber (0-255). Some Ethernet and FDDI interfaces allow a unicast MAC address for each HSRP group. Certain Ethernet chipsets(LANCE Ethernet, VGANYLAN and QUICC Ethernet) only support a single Unicast Mac Address. In this case, only one HSRP group is allowed. For TokenRing interfaces, the following three MAC addresses are permitted (functional addresses): C0:00:00:01:00:00 C0:00:00:02:00:00 C0:00:00:04:00:00.

The control that allows modification, creation, and deletion of entries. For detailed rules see the DESCRIPTION for cHsrpGrpEntry.

A table containing information about tracked interfaces per HSRP group.

The cHsrpExtIfTrackedEntry allows an HSRP group interface to track one or more interfaces. Weight(priority) is given to each and every interface tracked. When a tracked interface is unavailable, the HSRP priority of the router is decreased. i.e cHsrpGrpPriority value assigned to an HSRP group will reduce by the value assigned to cHsrpExtIfTrackedPriority. This reduces the likelihood of a router with a failed key interface becoming the active router. Setting cHsrpExtIfTrackedRowStatus to active starts the tracking of cHsrpExtIfTracked by the HSRP group. The value of cHsrpExtIfTrackedRowStatus may be set to destroy at any time. Entries may not be created via SNMP without explicitly setting cHsrpExtIfTrackedRowStatus to either 'createAndGo' or 'createAndWait'. Entries can be created and modified via the management protocol or by the device's local management interface. If the row is not active, and a local management interface command modifies that row, the row may transition to active state. A row entry in the cHsrpExtIfTrackedTable can not be created unless the corresponding row in the cHsrpGrpTable has been created. If that corresponding row in cHsrpGrpTable is deleted, the interfaces it tracks also get deleted. A row which is not in active state will timeout after a configurable period (five minutes by default). This timeout period can be changed by setting cHsrpConfigTimeout.

Index into the cHsrpExtIfTrackedTable for the corresponding { ifIndex, cHsrpGrpNumber } pair i.e for an HSRP group. This is the ifIndex of the tracked interface.

Priority of the tracked interface for the corresponding { ifIndex, cHsrpGrpNumber } pair. In the range of 0 to 255, 0 is the lowest priority and 255 is the highest. When a tracked interface is unavailable, the cHsrpGrpPriority of the router is decreased by the value of this object instance (If the cHsrpGrpPriority is less than the cHsrpExtIfTrackedPriority, then the HSRP priority becomes 0). This allows a standby router to be configured with a priority such that if the currently active router's priority is lowered because the tracked interface goes down, the standby router can takeover.

The control that allows modification, creation, and deletion of entries. For detailed rules see the DESCRIPTION for cHsrpExtIfTrackedEntry.

A table containing information about secondary HSRP IP Addresses per interface and group.

The CHsrpExtSecAddrEntry allows creation of secondary IP Addresses for each cHsrpGrpEntry row. Secondary addresses can be added by setting cHsrpExtSecAddrRowStatus to be active. The value of cHsrpExtSecAddrRowStatus may be set to destroy at any time. Entries may not be created via SNMP without explicitly setting cHsrpExtSecAddrRowStatus to either 'createAndGo' or 'createAndWait'. Entries can be created and modified via the management protocol or by the device's local management interface. If the row is not active, and a local management interface command modifies that row, the row may transition to active state. A row which is not in active state will timeout after a configurable period (five minutes by default). This timeout period can be changed by setting cHsrpConfigTimeout. Before creation of a cHsrpExtSecAddrEntry row, either cHsrpGrpConfiguredVirtualIpAddr or cHsrpGrpLearnedVirtualIpAddr must have a valid IP Address. This is because a secondary ip address cannot be created unless the primary ip address has already been set. To create a new cHsrpExtSecAddrEntry row, a management station should choose the ifIndex of the interface which is to be added as part of an HSRP group. Also, an HSRP group number and a cHsrpExtSecAddrAddress should be chosen. Deleting a {ifIndex, cHsrpGrpNumber} row in the cHsrpGrpTable will delete all corresponding rows in the cHsrpExtSecAddrTable. Deleting a primary address value in the cHsrpGrpEntry row will delete all secondary addresses for the same {ifIndex, cHsrpGrpNumber} pair.

A secondary IpAddress for the {ifIndex, cHsrpGrpNumber} pair. As explained in the DESCRIPTION for cHsrpExtSecAddrEntry, a primary address must exist before a secondary address for the same {ifIndex, cHsrpGrpNumber} pair can be created.

The control that allows modification, creation, and deletion of entries. For detailed rules see the DESCRIPTION for cHsrpExtSecAddrEntry.

Parameter to enable or disable MVR(Multicast VLAN Registration) on the device. NOTE: IGMP Snooping must be enabled first before enabling MVR and MVR will be disabled when IGMP Snooping is disabled.

To set VLAN for MVR.The VLAN identified by a particular value of this index is the same VLAN as identified by the same value of dot1qVlanIndex in the Q-BRIDGE-MIB.

The maximum number of MVR groups.

The current number of MVR groups.

The start of a contiguous range of MVR group addresses.

The range count for configuring MVR group addresses.

Sets the configure action for a contiguous range of MVR group addresses. The start addresses is the current value of mvrGroupsCtlId and the range count is the current value of mvrGroupsCtlCount. Set this object to create(2) to create MVR group addresses. Set this object to destory(3) to delete MVR group addresses. When the action is complete, this object becomes noAction(1). Enumeration: 'create': 1, 'destory': 2, 'noAction': 0.

The table for configuring the MVR group.

The entry for configuring the MVR group.

The multicast address of the MVR group.

To indicate if the group has a member or not. If there are no members, the status is inactive(2); otherwise the status is active(1). Enumeration: 'active': 1, 'inactive': 2.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

The table for configuring the static members of the MVR group.

The entry for configuring the static members of the MVR group.

The multicast address of the MVR group.

The set of ports configured by management in this entry. Ports entered in this list will be the static members of this MVR group.

Setting this to valid(1) creates an entry. Setting this to invalid(2) destroys an entry. Enumeration: 'valid': 1, 'invalid': 2.

The table for the current members of the MVR group.

The entry for the current members of the MVR group.