Cisco Cisco MDS 9000 NX-OS Software Release 4.2 Referencia técnica

Counter32—A nonnegative integer that increases until it reaches some maximum value. After 
reaching the maximum value, it rolls over to zero. For example, the variable ifInOctets, with a 
Counter32 syntax, counts the number of input octets on an interface.

Gauge32—A nonnegative integer that increases until it reaches some maximum value. After 
reaching the maximum value, it stays fixed (no roll over).

Counter64—A nonnegative 64-bit integer that increases until it reaches some maximum value. After 
reaching the maximum value, it rolls back to zero. Counter64 is used for MIB objects that can reach 
high values in a short period of time (for example, a packet counter for a Gigabit Ethernet port).

Integer32—An integer from -2

32

 to 2

32

-1.

IPAddress—An octet string that represents an IP address. For example, the variable hostConfigAddr 
indicates the IP address of the host that provided the host configuration file for a device.

Timeticks—A nonnegative integer that counts the hundredths of a second that have elapsed since an 
event. For example, the variable loctcpConnElapsed provides the length of time that a TCP 
connection has been established.

The MAX-ACCESS clause identifies the maximum access level for the associated MIB object. This 
clause can represent one of the following five states: read-create, read-write, read-only, 
accessible-for-notify, and not-accessible.

read-create—You can read, modify, or create objects as rows in a table.

read-write—You can read or modify this object.

read-only—You can only read this object.

accessible-for-notify—You cannot read or write to this object. SNMP notifications can send this 
object as part of their event information.

not-accessible—You cannot read or write to this object. Table indices are typically objects that are 
not accessible.

In SNMP, capabilities files provide implementation details for the associated MIB. These files, called 
AGENT-CAPABILITIES, list supported conformance groups and any deviations from the MIB as 
implemented in the associated software version. For instance, the 
CISCO-AAA-SERVER-CAPABILITY provides the implementation details for the 
CISCO-AAA-SERVER-MIB, as implemented in the Cisco MDS NX-OS or SAN-OS.

Capabilities files may have implementation details for more than one software release. You need to 
match your software release to the corresponding AGENT-CAPABILITIES clause in this file.

The Cisco MDS 9000 Family MIB files can be obtained by File Transfer Protocol (FTP) from 

, under Cisco Storage Networking.