Information furnished in this guide is believed to be accurate and reliable. However, QLogic Corporation assumes no
responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its
use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications
described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no
representation nor warranty that such applications are suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
Document Revision History
Revision A, April 2008
Revision B, August 2008
Revision C, October 2008
Revision D, September 2011
ChangesPages Affected
Updated to support firmware version 8.0Throughout
Updated format and brandingThroughout
This guide describes the support for Simple Network Management Protocol
(SNMP) used with QLogic switch products. This Simple Network Management
Protocol Reference Guide describes how to use SNMP to manage and monitor
the QLogic switch products.
This guide is organized as follows:
Section 1 provides an overview of SNMP objectives, managers and agents,
traps, Management Information Bases (MIB), and User Datagram Protocol.
Section 2 describes how to configure a QLogic switch using Telnet and the
Enterprise Fabric Suite graphical user interface.
Section 3 describes the Management Information Bases (MIB-II).
Section 4 describes the Fibre Alliance - Management Information Bases
(FA-MIB version 4.0).
Section 5 describes the Fabric Element - Management Information Bases
(FE-MIB).
Section 6 describes the QLOGIC Management Information Bases
(QLOGIC-MIB).
Section 7 describes the Firmware Download Management Information
Bases (FD-MIB).
Intended Audience
This guide is intended for users responsible for the support of SNMP and QLogic
switch configurations.
Related Materials
Refer to your product documentation.
59047-10 Dxxi
Page 22
Preface
Documentation Conventions
Documentation Conventions
This guide uses the following documentation conventions:
NOTE: provides additional information.
CAUTION!
causing damage to data or equipment.
WARNING!!
causing personal injury.
Text in blue font indicates a hyperlink (jump) to a figure, table, or section in
this guide, and links to Web sites are shown in underlined blue
example:
Table 9-2 lists problems related to the user interface and remote agent.
See “Installation Checklist” on page 3-6.
For more information, visit www.qlogic.com
Text in bold font indicates user interface elements such as a menu items,
buttons, check boxes, or column headings. For example:
Click the Start button, point to Programs, point to Accessories, and
Under Notification Options, select the Warning Alarms check box.
Text in Courier font indicates a file name, directory path, or command line
text. For example:
To return to the root directory from anywhere in the file structure:
indicates the presence of a hazard that has the potential of
indicates the presence of a hazard that has the potential of
.
then click Command Prompt.
Type
cd /root and press ENTER.
. For
Enter the following command: sh ./install.bin
Key names and key strokes are indicated with UPPERCASE:
Press CTRL+P.
Press the UP ARROW key.
xxii59047-10 D
Page 23
Text in italics indicates terms, emphasis, variables, or document titles. For
example:
For a complete listing of license agreements, refer to the QLogic
Software End User License Agreement.
What are shortcut keys?
To enter the date type mm/dd/yyyy (where mm is the month, dd is the
day, and yyyy is the year).
Topic titles between quotation marks identify related topics either within this
manual or in the online help, which is also referred to as the help system
throughout this document.
Technical Support
Customers should contact their authorized maintenance provider for technical
support of their QLogic products. QLogic-direct customers may contact QLogic
Technical Support; others will be redirected to their authorized maintenance
provider. Visit the QLogic support Web site listed in Contact Information for the
latest firmware and software updates.
Preface
Technical Support
Training
For details about available service plans, or for information about renewing and
extending your service, visit the Service Program web page at
http://www.qlogic.com/services
QLogic offers training for technical professionals for all iSCSI, InfiniBand, and
Fibre Channel products. From the main QLogic web page at www.qlogic.com
click the Support tab at the top, and then click Training and Certification on the
left. The QLogic Global Training portal offers online courses, certification exams,
and scheduling of in-person training.
Technical Certification courses include installation, maintenance and
troubleshooting QLogic products. Upon demonstrating knowledge using live
equipment, QLogic awards a certificate identifying the student as a certified
professional. You can reach the training professionals at QLogic by e-mail at
training@qlogic.com
.
.
,
59047-10 Dxxiii
Page 24
Preface
Technical Support
Contact Information
QLogic Technical Support for products under warranty is available during local
standard working hours excluding QLogic Observed Holidays. For customers with
extended service, consult your plan for available hours. For Support phone
numbers, see the Contact Support link at support.qlogic.com
Support Headquarters
QLogic Web Site
Technical Support Web Site
.
QLogic Corporation
4601 Dean Lakes Blvd.
Shakopee, MN 55379 USA
www.qlogic.com
http://support.qlogic.com
Technical Support E-mail
Technical Training E-mail
Knowledge Base
The QLogic knowledge base is an extensive collection of QLogic product
information that you can search for specific solutions. We are constantly adding to
the collection of information in our knowledge base to provide answers to your
most urgent questions. Access the knowledge base from the QLogic Support
Center: http://support.qlogic.com.
support@qlogic.com
training@qlogic.com
xxiv59047-10 D
Page 25
1SNMP Overview
Simple Network Management Protocol is the protocol governing network
management and monitoring of network devices. This Simple Network
Management Protocol Reference Guide describes how to use SNMP to manage
and monitor the QLogic switch products. Specifically, this guide describes the
SNMP agent that resides on the switch.
The following topics are covered in this section:
SNMP interface objectives
Manager and agent
Traps
Manage ment information bases (MIBs)
User datagram protocol (UDP)
Numbering system conventions
SNMP Interface Objectives
The objectives of the SNMP Interface are as follows:
Conne ct to the SNMP ag ent that resides on th e switch using a ma nagement
workstation.
Support of Fabric Element Management Information Bases (FE-MIB)
(rfc2837) and Fibre Alliance Management Information Bases (FA-MIB) draft.
Support of version 1 and 2 traps.
The SNMP agent supports SNMPv1and SNMPv2c.
Manager and Agent
The two primary elements of SNMP are:
Manager — the application that runs on the management workstation.
Agent — the daemon application that runs on the switch.
59047-10 D1-1
Page 26
1–SNMP Overview
Workstation with SNMP
Manager Application
Switch with Agent and
Common User Interface API
Ethernet Connection
Traps
The Manager is the application through which the network administrator performs
network management functions. The SNMP agent is the direct interface on the
switch for any SNMP manager connecting to the switch using the SNMP protocol,
as shown in Figure 1-1. The agent will be started by the script file(s) responsible
for switch initialization when the switch powers up or when the switch is reset.
When an SNMP request arrives at the agent, the agent will compose a message
and pass it on to Switch Management to process the message and provide a
response to the agent. The agent then provides a response to the originator of the
SNMP request. The SNMP agent does not have direct access to the internal
database of the switch.
Figure 1-1. SNMP Interface Architecture
Traps
Traps are notification messages sent from the switch to a registered manager
when a change of state occurs within the switch. A change of state can be an
alarm condition or simply a configuration change.
The Fibre Alliance MIB defines a trap table configurable through SNMP. A trap
table may have up to 5 entries, and can be configured using the SNMP Manager
or Enterprise Fabric Suite graphical user interface. The same trap table
information is available to both SNMP Manager and Enterprise Fabric Suite.
A trap event is reported when the incoming error has a severity level less than or
equal to the configured severity level. The trap event types and trap severity levels
are listed in Table 1-1. Refer to Table 4-1 for information on specific traps.
Management information bases (MIBs) define the properties of the managed
object within the device to be managed. Every managed de vice keeps a database
of values for each definition written in the MIB. It is not the actual database itself; it
is implementation dependant. Definition of the MIB conforms to the Structure of
Management Information (SMI) given in Request For Comment (RFC) 1155. The
latest Internet MIB is given in RFC 1213, and is sometimes called MIB-II.
User Datagram Protocol
QLogic switches support the following User Datagram Protocol (UDP) settings:
Agents “listen” on UDP port 161.
Responses are sent back to the originating Network Management St ation
(NMS) port from a dynamic port, although many agents use p ort 161 also for
this target.
The maximum SNMP message size is 65507 octets (maximum UDP
message size).
The minimum receive packet size for SNMP implementations is 484 octets
in length.
Agent and Network Monitoring Systems are responsible for determining
error recovery.
59047-10 D1-3
Page 28
1–SNMP Overview
Numbering System Conventions
Numbering System Conventions
The conventions for numbering systems in this guide are as follows:
This section describes how to configure a QLogic switch to support SNMP. The
following topics are covered:
System specifications and requirements
Configuring a switch using the Telnet command line interface
Configuring a switch using the Enterprise Fabric Suite application
System Specifications and Requirements
QLogic switches support SNMPv1 and SNMPv2c.
Version 1 and 2 traps are supported.
Hardware — one out-of-band Ethernet connection is required.
Software — one switch management software application allows you to:
Monitor and control the switch.
Read, write, and receive trap information, if supported.
Ports on the switch reserved for SNMP:
Port 161 is not configurable, and is used for the standard SNMP
commands.
Port 162 is configurable and is the default port used for traps.
One or more in-band switches can be managed by an out-of-band QLogic
switch acting as a proxy switch.
QLogic can only act as a proxy for other QLogic switches.
QLogic proxy capability can be disabled.
59047-10 D2-1
Page 30
2–Configuring a Switch
Configuring a Switch Using the Command Line Interface
Configuring a Switch Using the Command Line
Interface
The Telnet command line interface offers a convenient way to change SNMP
parameters. SNMP parameter defaults are preset during manufacturing. For
security purposes, these default values should be changed. For specific
information about SNMP parameters, refer to the SNMP Configuration section in
the corresponding QLogic Switch Management User Guide. To configure a switch
using the command line interface, do the following.
2-259047-10 D
Page 31
2–Configuring a Switch
Configuring a Switch Using the Command Line Interface
Press ENTER to accept the default value for each parameter.
SB5600.116.50 (admin) #> set setup snmp
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the attributes
for the category being processed, press 'q' or 'Q' and the ENTER key to do so.
If you wish to terminate the configuration process completely, press 'qq' or
'QQ' and the ENTER key to do so.
SNMP System Configuration - may optionally use 'set setup snmp common'
command.
Current Values:
SnmpEnabled True
Contact <sysContact undefined>
Location <sysLocation undefined>
ReadCommunity public
WriteCommunity private
AuthFailureTrap False
ProxyEnabled True
SNMPv3Enabled False
New Value (press ENTER to not specify value, 'q' to quit):
SnmpEnabled (True / False) :
Contact (string, max=64 chars) :
Location (string, max=64 chars) :
ReadCommunity (string, max=32 chars) :
WriteCommunity (string, max=32 chars) :
AuthFailureTrap (True / False) :
ProxyEnabled (True / False) :
SNMPv3Enabled (True / False) :
SNMP Trap 1 Configuration - may optionally use 'set setup snmp trap 1'
command.
Current Values:
Trap1Enabled False
Trap1Address 10.0.0.254
Trap1Port 5001
Trap1Severity info
Trap1Version 2
Trap1Community public
New Value (press ENTER to not specify value, 'q' to quit):
Trap1Enabled (True / False) :
Trap1Address (hostname, IPv4, or IPv6 Address) :
Trap1Port (decimal value, 1-65535) :
Trap1Severity (select a severity level)
1=unknown 6=warning
59047-10 D2-3
Page 32
2–Configuring a Switch
Configuring a Switch Using the Command Line Interface
SNMP Trap 2 Configuration - may optionally use 'set setup snmp trap 2'
command.
Current Values:
Trap2Enabled False
Trap2Address 10.20.43.231
Trap2Port 162
Trap2Severity info
Trap2Version 2
Trap2Community public
New Value (press ENTER to not specify value, 'q' to quit):
Trap2Enabled (True / False) :
Trap2Address (hostname, IPv4, or IPv6 Address) :
Trap2Port (decimal value, 1-65535) :
Trap2Severity (select a severity level)
1=unknown 6=warning
2=emergency 7=notify
3=alert 8=info
4=critical 9=debug
5=error 10=mark :
Trap2Version (1 / 2) :
Trap2Community (string, max=32 chars) :
SNMP Trap 3 Configuration - may optionally use 'set setup snmp trap 3'
command.
Current Values:
Trap3Enabled False
Trap3Address 10.20.33.231
Trap3Port 162
Trap3Severity warning
Trap3Version 2
Trap3Community public
New Value (press ENTER to not specify value, 'q' to quit):
Trap3Enabled (True / False) :
Trap3Address (hostname, IPv4, or IPv6 Address) :
Trap3Port (decimal value, 1-65535) :
Trap3Severity (select a severity level)
1=unknown 6=warning
2=emergency 7=notify
2-459047-10 D
Page 33
2–Configuring a Switch
Configuring a Switch Using the Command Line Interface
SNMP Trap 4 Configuration - may optionally use 'set setup snmp trap 4'
command.
Current Values:
Trap4Enabled False
Trap4Address 0.0.0.0
Trap4Port 162
Trap4Severity warning
Trap4Version 2
Trap4Community public
New Value (press ENTER to not specify value, 'q' to quit):
Trap4Enabled (True / False) :
Trap4Address (hostname, IPv4, or IPv6 Address) :
Trap4Port (decimal value, 1-65535) :
Trap4Severity (select a severity level)
1=unknown 6=warning
2=emergency 7=notify
3=alert 8=info
4=critical 9=debug
5=error 10=mark :
Trap4Version (1 / 2) :
Trap4Community (string, max=32 chars) :
SNMP Trap 5 Configuration - may optionally use 'set setup snmp trap 5'
command.
Current Values:
Trap5Enabled False
Trap5Address 0.0.0.0
Trap5Port 162
Trap5Severity warning
Trap5Version 2
Trap5Community public
New Value (press ENTER to not specify value, 'q' to quit):
Trap5Enabled (True / False) :
Trap5Address (hostname, IPv4, or IPv6 Address) :
Trap5Port (decimal value, 1-65535) :
Trap5Severity (select a severity level)
1=unknown 6=warning
2=emergency 7=notify
3=alert 8=info
59047-10 D2-5
Page 34
2–Configuring a Switch
Configuring a Switch Using Enterprise Fabric Suite
Do you want to save and activate this snmp setup? (y/n): [n]
SNMP setup NEITHER saved NOR activated.
SB5600.116.50 (admin) #>
Configuring a Switch Using Enterprise Fabric
Suite
To configure a QLogic switch using Enterprise Fabric Suite, use the SNMP
Properties, Switch Properties, and Network Properties dialogs. For specific
information, refer to the Enterprise Fabric Suite User Guide.
2-659047-10 D
Page 35
3MIB-II Objects
This section covers the implementation details for the MIB-II on the QLogic switch.
A MIB defines the properties of the managed object within the device to be
managed. Every managed device keeps a database of values for each definition
written in the MIB. It is not the actual database itself; it is implementation
dependant. Definition of the MIB conforms to the SMI given in RFC 1155. The
latest Internet MIB is given in RFC 1213, and is sometimes called MIB-II.
Groups in MIB-II
Refer the Table 3-1 for the syntax for MIB-II Groups.
Implementation of the System group is mandatory for all systems. If an agent is
not configured to have a value for any of these variables, a string of length 0 is
returned.
59047-10 D3-1
Page 36
3–MIB-II Objects
sysDescr (1.3.6.1.2.1.1.1)
sysDescr (1.3.6.1.2.1.1.1)
A textual description of the entity. This value should include the full name and
version identification of the system's hardware type, operating-system, and
networking software. It is mandatory that this only contain printable American
Standard Code for Information Interchange (ASCII) characters.
5202 = SANbox 5202 FC Switch, QLogic 5600 = SANbox 5600 FC Switch,
QLogic 5602 = SANbox 5602 FC Switch
sysObjectID (1.3.6.1.2.1.1.2)
The vendor's authoritative identification of the network management subsystem
contained in the entity. This value is allocated within the SMI enterprise subtree
(1.3.6.1.4.1) and provides an easy and unambiguous means for determining
`what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was
assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier
1.3.6.1.4.1.1663.1.1.1.1.30, QLogic 5600 = 1.3.6.1.4.1.1663.1.1.1.1.23, and
QLogic 5602 = 1.3.6.1.4.1.1663.1.1.1.1.24
3-259047-10 D
Page 37
3–MIB-II Objects
sysUpTime (1.3.6.1.2.1.1.3)
sysUpTime (1.3.6.1.2.1.1.3)
The time, in hundredths of a second, since the network management portion of
the system was last re-initialized.
SyntaxTimeTicks
Accessread-only
Statusmandatory
Return ValueThe time since the switch was powered on, or last reset (reset, hard reset, o r
hot reset) was executed. For example, 3 days 21 hours, 5 minutes, and
26.84 seconds. The value will roll over after approximately 497 days of
continuous up time.
sysContact (1.3.6.1.2.1.1.4)
The textual identification of the contact person for this managed Node, together
with information on how to contact this person.
SyntaxDisplayString (SIZE (0..255))
Accessread-write
Statusmandatory
Return ValueThe default is: <sysContact undefined>. The string size is limited to a
maximum of 64.
sysName (1.3.6.1.2.1.1.5)
An administratively-assigned name for this managed Node. By convention, this is
the Node's fully-qualified domain name.
SyntaxDisplayString (SIZE (0..255))
Accessread-write
Statusmandatory
Return ValueThe defaults are: QLogic 5200 Series = SANbox, QLogic 5600 Series =
SANbox
59047-10 D3-3
Page 38
3–MIB-II Objects
sysLocation (1.3.6.1.2.1.1.6)
sysLocation (1.3.6.1.2.1.1.6)
The physical location of this Node, such as telephone closet and 3rd floor.
SyntaxDisplayString (SIZE (0..255))
Accessread-write
Statusmandatory
Return ValueThe default is: <sysLocation undefined>. The string size is limited to a
maximum of 64.
sysServices (1.3.6.1.2.1.1.7)
A value that indicates the set of services that this entity primarily offers.The value
is a sum. This sum initially takes the value zero. Then, for each layer L in the
range 1 through 7 that this Node performs transactions for, 2 raised to (L - 1) is
added to the sum. For example, a Node that performs primarily routing functions
would have a value of 4 (2^(3-1)). In contrast, a Node that is a host offering
application services would have a value of 72 (2^(4-1) + 2^(7-1)).
SyntaxINTEGER (0..127)
Accessread-only
Statusmandatory
Return ValueThe default is: 2
3-459047-10 D
Page 39
The Interfaces Group
Implementation of the Interfaces group is mandatory for all systems.
ifNumber (1.3.6.1.2.1.2.1)
The number of network interfaces (regardless of their current state) present on
this system.
SyntaxINTEGER
Accessread-only
Statusmandatory
Return ValueThe default is: 2
3–MIB-II Objects
The Interfaces Group
The Interfaces Table
The Interfaces table contains information on the entity's interfaces. Each interface
is thought of as being attached to a `subnetwork'. This term should not be
confused with `subnet' which refers to an addressing partitioning scheme used in
the Internet suite of protocols.
ifIndex (1.3.6.1.2.1.2.2.1.1)
A unique value for each interface. Its value ranges between 1 and the value of
ifNumber. The value for each interface must remain constant at least from one
re-initialization of the entity's network management system to the next
re-initialization. The range will be non-contiguous.
SyntaxINTEGER
Accessread-only
Statusmandatory
59047-10 D3-5
Page 40
3–MIB-II Objects
ifDescr (1.3.6.1.2.1.2.2.1.2)
ifDescr (1.3.6.1.2.1.2.2.1.2)
A textual string containing information about the interface. This string should
include the name of the manufacturer, the product name, and the version of the
hardware interface.
The type of interface distinguished according to the physical/link protocol(s)
immediately `below' the network layer in the protocol stack.
SyntaxINTEGER
Accessread-only
Statusmandatory
ifMtu (1.3.6.1.2.1.2.2.1.4)
The size of the largest datagram which can be sent/received on the interface,
specified in octets. For interfaces that are used for transmitting network
datagrams, this is the size of the largest network datagram that can be sent on the
interface.
SyntaxINTEGER
Accessread-only
Statusmandatory
3-659047-10 D
Page 41
ifSpeed (1.3.6.1.2.1.2.2.1.5)
An estimate of the interface's current bandwidth in bits per second. For interfaces
that do not vary in bandwidth or for those where no accurate estimation can be
made, this object should contain the nominal bandwidth. If the bandwidth of the
interface is greater than the maximum value reportable by this object, then this
object reports its maximum value (4,294,967,295 ) and ifHighSpeed must be used
to report the interface's speed.
SyntaxGauge
Accessread-only
Statusmandatory
ifPhysAddress (1.3.6.1.2.1.2.2.1.6)
The interface's address at the protocol layer immediately “below” the network
layer in the protocol stack. For interfaces that do not have such an address, such
as a serial line, this object should contain an octet string of zero length.
3–MIB-II Objects
ifSpeed (1.3.6.1.2.1.2.2.1.5)
SyntaxPhysAddress
Accessread-only
Statusmandatory
ifAdminStatus (1.3.6.1.2.1.2.2.1.7)
The desired state of the interface. The testing(3) state indicates that no
operational packets can be passed.
SyntaxINTEGER
Accessread-only
Statusmandatory
Return ValueWrites not supported.
The current operational state of the interface. The testing(3) state indicates that
no operational packets can be passed.
SyntaxINTEGER
Accessread-only
Statusmandatory
ifLastChange (1.3.6.1.2.1.2.2.1.9)
The value of sysUpTime at the time the interface entered its current operational
state. If the current state was entered prior to the last re-initialization of the local
network management subsystem, then this object contains a zero value.
SyntaxTimeTicks
Accessread-only
Statusmandatory
ifInOctets (1.3.6.1.2.1.2.2.1.10)
The total number of octets received on the interface, including framing chara cters.
SyntaxCounter
Accessread-only
Statusmandatory
ifInUcastPkts (1.3.6.1.2.1.2.2.1.11)
The number of subnetwork-unicast packets delivered to a higher-layer protocol.
SyntaxCounter
Accessread-only
Statusmandatory
3-859047-10 D
Page 43
ifInNUcastPkts (1.3.6.1.2.1.2.2.1.12)
The number of non-unicast (that is, subnetwork- broadcast or
subnetwork-multicast) packets delivered to a higher-layer protocol.
SyntaxCounter
Accessread-only
Statusmandatory
ifInDiscards (1.3.6.1.2.1.2.2.1.13)
The number of inbound packets that were chosen to be discarded even though no
errors had been detected to prevent their being deliverable to a higher-layer
protocol. One possible reason for discarding such a packet could be to free up
buffer space.
3–MIB-II Objects
ifInNUcastPkts (1.3.6.1.2.1.2.2.1.12)
SyntaxCounter
Accessread-only
Statusmandatory
ifInErrors (1.3.6.1.2.1.2.2.1.14)
The number of inbound packets that cont a ined errors pr eventing them from being
deliverable to a higher-layer protocol.
SyntaxCounter
Accessread-only
Statusmandatory
ifInUnknownProtos (1.3.6.1.2.1.2.2.1.15)
The number of packets received from the interface that were discarded because
of an unknown or unsupported protocol.
The total number of octets transmitted out of the interface, including framing
characters.
SyntaxCounter
Accessread-only
Statusmandatory
ifOutUcastPkts (1.3.6.1.2.1.2.2.1.17)
The total number of packets that higher level protocols requested be transmitted
to a subnetwork unicast address, including those that were discarded or not sent.
SyntaxCounter
Accessread-only
Statusmandatory
ifOutNUcastPkts (1.3.6.1.2.1.2.2.1.18)
The total number of packets that higher level protocols requested be transmitted
to a non-unicast (subnetwork broadcast or subnetwork multicast) address,
including those that were discarded or not sent.
SyntaxCounter
Accessread-only
Statusmandatory
ifOutDiscards (1.3.6.1.2.1.2.2.1.19)
The number of outbound packets that were chosen to be discarded even though
no errors had been detected to prevent their being transmitted. One possible
reason for discarding such a packet could be to free up buffer space.
SyntaxCounter
Accessread-only
Statusmandatory
3-1059047-10 D
Page 45
ifOutErrors (1.3.6.1.2.1.2.2.1.20)
The number of outbound packets that could not be transmitted because of errors.
SyntaxCounter
Accessread-only
Statusmandatory
ifOutQLen (1.3.6.1.2.1.2.2.1.21)
The length (in packets) of the output packet queue.
SyntaxGauge
Accessread-only
3–MIB-II Objects
ifOutErrors (1.3.6.1.2.1.2.2.1.20)
Statusmandatory
ifSpecific (1.3.6.1.2.1.2.2.1.22)
A reference to MIB definitions specific to the particular media being used to realize
the interface. For example, if the interface is realized by an Ethernet, then the
value of this object refers to a document that defines objects specific to Ethernet.
If this information is not present, its value should be set to the OBJECT
IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any
conformant implementation of ASN.1 (Abstract Syntax Notation) and BER must
be able to generate and recognize this value.
Implementation of the Address Translation group is mandatory for all systems.
However, this group is dep recated by MIB-II. That is, it is being inclu ded solely for
compatibility with MIB-I Nodes, and will most likely be excluded from MIB-III
Nodes. From MIB-II and onwards, each network protocol group contains its own
address translation tables.
The Address Translation group contains one table which is the union across all
interfaces of the translation tables for converting a NetworkAddress (for example ,
an IP address) into a subnetwork-specific address. For lack of a better term, this
document refers to such a subnetwork-specific address as a `physical' address.
Examples of such translation tables are for: broadcast media where ARP is in use,
the translation table is equivalent to the ARP cache, or on an X.25 network where
non-algorithmic translation to X.121 addresses is required. The translation table
contains the NetworkAddress to X.121 address equivalences.
atIfIndex (1.3.6.1.2.1.3.1.1.1)
The interface on which this entry's equivalence is effective. The interface
identified by a particular value of this index is the same interface as identified by
the same value of ifIndex.
SyntaxINTEGER
Accessread-write
Statusdeprecated
3-1259047-10 D
Page 47
atPhysAddress (1.3.6.1.2.1.3.1.1.2)
The media-dependent “physical” address. Setting this object to a null string (one
of zero length) has the effect of invalidating the corresponding entry in the atTable
object. That is, it effectively disassociates the interface identified with the entry
from the mapping identified with the entry. It is an implementation-specific matter
as to whether the agent removes an invalidated entry from the table. Accordingly,
management workstations must be prepared to receive tabular information from
agents that corresponds to entries not currently in use. Proper interpretation of
such entries requires examination of the relevant atPhysAddress object.
Implementation of the IP group is mandatory for all systems.
ipForwarding (1.3.6.1.2.1.4.1)
The indication of whether this entity is acting as an IP Gateway with respect to the
forwarding of datagrams received by, but not addressed to, this entity. IP
Gateways forward datagrams; IP hosts do not (except those source-routed from
the host).
For some managed Nodes, this object may take on only a subset of the values
possible. Accordingly, it is appropriate for an agent to return a “badValue”
response if a management station attempts to change this object to an
inappropriate value.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueReturns forwarding (1). Writes not supported.
ipDefaultTTL (1.3.6.1.2.1.4.2)
The default value inserted into the Time-To-Live field of the IP header of
datagrams originated at this entity whenever a TTL value is not supplied by the
transport layer protocol.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueReturns 64 (0x40). Writes not supported.
3-1459047-10 D
Page 49
ipInReceives (1.3.6.1.2.1.4.3)
The total number of input datagrams received from interfaces, including those
received in error.
SyntaxCounter
Accessread-only
Statusmandatory
ipInHdrErrors (1.3.6.1.2.1.4.4)
The number of input datagrams discarded due to errors in their IP headers. These
include bad checksums, version number mismatch, other format errors,
time-to-live exceeded, and errors discovered in processing their IP options.
SyntaxCounter
3–MIB-II Objects
ipInReceives (1.3.6.1.2.1.4.3)
Accessread-only
Statusmandatory
ipInAddrErrors (1.3.6.1.2.1.4.5)
The number of input datagrams discarded because the IP address in their IP
header's destination field was not a valid address to b e received at this entity. This
count includes invalid addresses (for example, 0.0.0.0) and addresses of
unsupported Classes (for example, Class E). For entities which are not IP
Gateways and therefore do not forward datagrams, this counter includes
datagrams discarded because the destination address was not a local address.
The number of input datagrams for which this entity was not their final IP
destination. As a result, an attempt was made to find a route to forward them to
that final destination. In entities that do not act as IP Gateways, this counter will
include only those packets that were Source Routed from this entity, and the
Source Route option processing was successful.
SyntaxCounter
Accessread-only
Statusmandatory
ipInUnknownProtos (1.3.6.1.2.1.4.7)
The number of locally-addressed datagrams received successfully but discarded
because of an unknown or unsupported protocol.
SyntaxCounter
Accessread-only
Statusmandatory
ipInDiscards (1.3.6.1.2.1.4.8)
The number of input IP datagrams for which no problems were encountered to
prevent their continued processing, but which were discarded (for example, for
lack of buffer space). This counter does not include any datagrams discarded
while awaiting reassembly.
SyntaxCounter
Accessread-only
Statusmandatory
3-1659047-10 D
Page 51
ipInDelivers (1.3.6.1.2.1.4.9)
The total number of input datagrams successfully delivered to IP user protocols
(including ICMP).
SyntaxCounter
Accessread-only
Statusmandatory
ipOutRequests (1.3.6.1.2.1.4.10)
The total number of IP datagrams that local IP user protocols (including ICMP)
supplied to IP in requests for transmission. This counter does not include any
datagrams counted in ipForwDatagrams.
SyntaxCounter
3–MIB-II Objects
ipInDelivers (1.3.6.1.2.1.4.9)
Accessread-only
Statusmandatory
ipOutDiscards (1.3.6.1.2.1.4.11)
The number of output IP datagrams for which no problem was encountered to
prevent their transmission to their destination, but which were discarded (for
example, for lack of buffer space). This co unter would include dat agrams counted
in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
SyntaxCounter
Accessread-only
Statusmandatory
59047-10 D3-17
Page 52
3–MIB-II Objects
ipOutNoRoutes (1.3.6.1.2.1.4.12)
ipOutNoRoutes (1.3.6.1.2.1.4.12)
The number of IP datagrams discarded because no route could be found to
transmit them to their destination. This counter includes any packets counted in
ipForwDatagrams which meet this “no-route” criterion. This includes any
datagrams that a host cannot route because all of its default gateways are down.
SyntaxCounter
Accessread-only
Statusmandatory
ipReasmTimeout (1.3.6.1.2.1.4.13)
The maximum number of seconds which received fragments are held while they
are awaiting reassembly at this entity.
SyntaxINTEGER
Accessread-only
Statusmandatory
ipReasmReqds (1.3.6.1.2.1.4.14)
The number of IP fragments received tha t needed to be reassembled at this entity.
SyntaxCounter
Accessread-only
Statusmandatory
ipReasmOKs (1.3.6.1.2.1.4.15)
The number of IP datagrams successfully reassembled.
SyntaxCounter
Accessread-only
Statusmandatory
3-1859047-10 D
Page 53
ipReasmFails (1.3.6.1.2.1.4.16)
The number of failures detected by the IP reassembly algorithm for example,
timed out, errors). This is not necessarily a count of discarded IP fragments, since
some algorithms (notably the algorithm in RFC 815) can lose track of the number
of fragments by combining them as they are received.
SyntaxCounter
Accessread-only
Statusmandatory
ipFragOKs (1.3.6.1.2.1.4.17)
The number of IP datagrams that have been successfully fragmented at this
entity.
3–MIB-II Objects
ipReasmFails (1.3.6.1.2.1.4.16)
SyntaxCounter
Accessread-only
Statusmandatory
ipFragFails (1.3.6.1.2.1.4.18)
The number of IP datagrams that have been discarded because they needed to
be fragmented at this entity, but could not because their Don't Fragment flag was
set.
SyntaxCounter
Accessread-only
Statusmandatory
59047-10 D3-19
Page 54
3–MIB-II Objects
ipFragCreates (1.3.6.1.2.1.4.19)
ipFragCreates (1.3.6.1.2.1.4.19)
The number of IP datagram fragments that have been generated as a result of
fragmentation at this entity.
SyntaxCounter
Accessread-only
Statusmandatory
The IP Address Table
The IP address table contains this entity's IP addressing information.
ipAdEntAddr (1.3.6.1.2.1.4.20.1.1)
The IP address to which this entry's addressing information pertains.
SyntaxIpAddress
Accessread-only
Statusmandatory
ipAdEntIfIndex (1.3.6.1.2.1.4.20.1.2)
The index value which uniquely identifies the interface to which this entry is
applicable. The interface identified by a particular value of this index is the same
interface as identified by the same value of ifIndex.
SyntaxINTEGER
Accessread-only
Statusmandatory
3-2059047-10 D
Page 55
ipAdEntNetMask (1.3.6.1.2.1.4.20.1.3)
The subnet mask associated with the IP address of this entry. The value of the
mask is an IP address with all the network bits set to 1 and all the hosts bit s set to
0.
SyntaxIpAddress
Accessread-only
Statusmandatory
ipAdEntBcastAddr (1.3.6.1.2.1.4.20.1.4)
The value of the least-significant bit in the IP broadcast address used for sending
datagrams on the (logical) interface associated with the IP address of this entry.
For example, when the Internet standard all-ones broadcast address is used, the
value will be 1. This value applies to both the subnet and network broadcasts
addresses used by the entity on this (logical) interface.
3–MIB-II Objects
ipAdEntNetMask (1.3.6.1.2.1.4.20.1.3)
SyntaxINTEGER
Accessread-only
Statusmandatory
ipAdEntReasmMaxSize (1.3.6.1.2.1.4.20.1.5)
The size of the largest IP datagram which this entity can reassemble from
incoming IP fragmented datagrams received on this interface.
The IP routing table contains an entry for each route presently known to this entity.
ipRouteDest (1.3.6.1.2.1.4.21.1.1)
The destination IP address of this route. An entry with a value of 0.0.0.0 is
considered a default route. Multiple routes to a single destination can appear in
the table, but access to such multiple entries is dependent on the table-access
mechanisms defined by the network management protocol in use.
SyntaxIpAddress
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteIfIndex (1.3.6.1.2.1.4.21.1.2)
The index value which uniquely identifies the local interface through which the
next hop of this route should be reached. The interface identified by a particular
value of this index is the same interface as identified by the same value of ifIndex.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
3-2259047-10 D
Page 57
ipRouteMetric1 (1.3.6.1.2.1.4.21.1.3)
The primary routing metric for this route. The semantics of this metric are
determined by the routing protocol specified in the route's ipRouteProto value. If
this metric is not used, its value should be set to -1.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteMetric2 (1.3.6.1.2.1.4.21.1.4)
An alternate routing metric for this route. The semantics of this metric are
determined by the routing protocol specified in the route's ipRouteProto value. If
this metric is not used, its value should be set to -1.
3–MIB-II Objects
ipRouteMetric1 (1.3.6.1.2.1.4.21.1.3)
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteMetric3 (1.3.6.1.2.1.4.21.1.5)
An alternate routing metric for this route. The semantics of this metric are
determined by the routing protocol specified in the route's ipRouteProto value. If
this metric is not used, its value should be set to -1.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
An alternate routing metric for this route. The semantics of this metric are
determined by the routing protocol specified in the route's ipRouteProto value. If
this metric is not used, its value should be set to -1.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteNextHop (1.3.6.1.2.1.4.21.1.7)
The IP address of the next hop of this route. In the case of a route bound to an
interface which is realized from a broadcast media, the value of this field is the
agent's IP address on that interface.
SyntaxIpAddress
Accessread-write
Statusmandatory
Return ValueWrites not supported.
3-2459047-10 D
Page 59
ipRouteType (1.3.6.1.2.1.4.21.1.8)
The type of route. The values direct(3) and indirect(4) refer to the notion of direct
and indirect routing in the IP architecture. Setting this object to the value invalid(2)
has the effect of invalidating the corresponding entry in the ipRouteTable object.
That is, it effectively disassociates the destinatio n identified with the entry from the
route identified with the entry . It is an imp lementation-specific matter as to whether
the agent removes an invalidated entry from the table. Accordingly, management
stations must be prepared to receive tabular information from agents that
corresponds to entries not currently in use. Proper interpretation of such entries
requires examination of the relevant ipRouteType object.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
3–MIB-II Objects
ipRouteType (1.3.6.1.2.1.4.21.1.8)
ipRouteProto (1.3.6.1.2.1.4.21.1.9)
The routing mechanism through which this route was learned. Inclusion of values
for gateway routing protocols is not intended to imply that hosts should support
those protocols.
SyntaxINTEGER
Accessread-only
Statusmandatory
ipRouteAge (1.3.6.1.2.1.4.21.1.10)
The number of seconds since this route was last updated or otherwise determined
to be correct. No semantics of `too old' can be implied except through knowledge
of the routing protocol by which the route was learned.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
Indicate the mask to be logical-ANDed with the destination address before being
compared to the value in the ipRouteDest field.
SyntaxIpAddress
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteMetric5 (1.3.6.1.2.1.4.21.1.12)
An alternate routing metric for this route. The semantics of this metric are
determined by the routing-protocol specified in the route's ipRouteProto value. If
this metric is not used, its value should be set to -1.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipRouteInfo (1.3.6.1.2.1.4.21.1.13)
A reference to MIB definitions specific to the particular routing protocol which is
responsible for this route, as determined by the value specified in the route's
ipRouteProto value. If this information is not present, its value should be set to the
OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier. Any
conformant implementation of ASN.1 and BER must be able to generate and
recognize this value.
The IP address translation table contain the IpAddress to`physical' address
equivalences. Some interfaces do not use translation tables for determining
address equivalences (for example, DDN-X.25 has an algorithmic method). If all
interfaces are of this type, then the Address Translation t able is empty, that is, has
zero entries.
ipNetToMediaIfIndex (1.3.6.1.2.1.4.22.1.1)
The interface on which this entry's equivalence is effective. The interface
identified by a particular value of this index is the same interface as identified by
the same value of ifIndex.
SyntaxINTEGER
Accessread-write
3–MIB-II Objects
The IP Address Translation Table
Statusmandatory
Return ValueWrites not supported.
ipNetToMediaPhysAddress (1.3.6.1.2.1.4.22.1.2)
The media-dependent `physical' address.
SyntaxPhysAddress
Accessread-write
Statusmandatory
Return ValueWrites not supported.
The IpAddress corresponding to the media-dependent `physical' address.
SyntaxIpAddress
Accessread-write
Statusmandatory
Return ValueWrites not supported.
ipNetToMediaType (1.3.6.1.2.1.4.22.1.4)
The type of mapping. Setting this object to the value invalid(2) has the effect of
invalidating the corresponding entry in the ipNetToMediaTable. That is, it
effectively disassociates the interface identified with the entry from the mapping
identified with the entry. It is an implementation-specific matter as to whether the
agent removes an invalidated entry from the table. Accordingly, management
stations must be prepared to receive tabular information from agents that
corresponds to entries not currently in use. Proper interpretation of such entries
requires examination of the relevant ipNetToMediaType object.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
3-2859047-10 D
Page 63
Additional IP Objects
Following are the additional IP objects.
ipRoutingDiscards (1.3.6.1.2.1.4.23)
The number of routing entries which were chosen to be discarded even though
they are valid. One possible reason for discarding such an entry could be to
free-up buffer space for other routing entries.
SyntaxCounter
Accessread-only
Statusmandatory
The ICMP Group
3–MIB-II Objects
Additional IP Objects
Implementation of the ICMP group is mandatory for all systems.
icmpInMsgs (1.3.6.1.2.1.5.1)
The total number of ICMP messages received by the entity. This counter includes
all those counted by icmpInErrors.
SyntaxCounter
Accessread-only
Statusmandatory
icmpInErrors (1.3.6.1.2.1.5.2)
The number of ICMP messages received by the entity but were determined as
having ICMP-specific errors (such as, bad ICMP checksums, bad length).
The number of ICMP Timestamp Reply messages received.
SyntaxCounter
Accessread-only
Statusmandatory
icmpInAddrMasks (1.3.6.1.2.1.5.12)
The number of ICMP Address Mask Request messages received.
SyntaxCounter
Accessread-only
Statusmandatory
icmpInAddrMaskReps (1.3.6.1.2.1.5.13)
The number of ICMP Address Mask Reply messages received.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutMsgs (1.3.6.1.2.1.5.14)
The total number of ICMP messages which this entity attempted to send. This
counter includes all those counted by icmpOutErrors.
SyntaxCounter
Accessread-only
Statusmandatory
3-3259047-10 D
Page 67
icmpOutErrors (1.3.6.1.2.1.5.15)
The number of ICMP messages which this entity did not send due to problems
discovered within ICMP, such as a lack of buffers. This value should not include
errors discovered outside the ICMP layer such as the inability of IP to route the
resultant datagram. In some implementations, there may be no types of errors
which contribute to this counter's value.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutDestUnreachs (1.3.6.1.2.1.5.16)
The number of ICMP Destination Unreachable messages sent.
3–MIB-II Objects
icmpOutErrors (1.3.6.1.2.1.5.15)
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutTimeExcds (1.3.6.1.2.1.5.17)
The number of ICMP Time Exceeded messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutParmProbs (1.3.6.1.2.1.5.18)
The number of ICMP Parameter Problem messages sent.
The number of ICMP Redirect messages sent. For a host, this object will always
be zero, since hosts do not send redirects.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutEchos (1.3.6.1.2.1.5.21)
The number of ICMP Echo (request) messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutEchoReps (1.3.6.1.2.1.5.22)
The number of ICMP Echo Reply messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
3-3459047-10 D
Page 69
icmpOutTimestamps (1.3.6.1.2.1.5.23)
The number of ICMP Timestamp (request) messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutTimestampReps (1.3.6.1.2.1.5.24)
The number of ICMP Timestamp Reply messages sent.
SyntaxCounter
Accessread-only
3–MIB-II Objects
icmpOutTimestamps (1.3.6.1.2.1.5.23)
Statusmandatory
icmpOutAddrMasks (1.3.6.1.2.1.5.25)
The number of ICMP Address Mask Request messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
icmpOutAddrMaskReps (1.3.6.1.2.1.5.26)
The number of ICMP Address Mask Reply messages sent.
SyntaxCounter
Accessread-only
Statusmandatory
59047-10 D3-35
Page 70
3–MIB-II Objects
The TCP Group
The TCP Group
Implementation of the TCP group is mandatory for all systems that implement the
TCP. Instances of object types that represent information about a particular TCP
connection are transient; they persist only as long as the connection in question.
tcpRtoAlgorithm (1.3.6.1.2.1.6.1)
The algorithm used to determine the timeout value used for retransmitting
unacknowledged octets.
SyntaxINTEGER
Accessread-only
Statusmandatory
tcpRtoMin (1.3.6.1.2.1.6.2)
The minimum value permitted by a TCP implementation for the retransmission
timeout, measured in milliseconds. More refined semantics for object s of this type
depend upon the algorithm used to determine the retransmission timeout. In
particular, when the timeout algorithm is rsre(3), an object of this type has the
semantics of the LBOUND quantity described in RFC 793.
SyntaxINTEGER
Accessread-only
Statusmandatory
tcpRtoMax (1.3.6.1.2.1.6.3)
The maximum value permitted by a TCP implementation for the retransmission
timeout, measured in milliseconds. More refined semantics for object s of this type
depend upon the algorithm used to determine the retransmission timeout. In
particular, when the timeout algorithm is rsre(3), an object of this type has the
semantics of the UBOUND quantity described in RFC 793.
SyntaxINTEGER
Accessread-only
Statusmandatory
3-3659047-10 D
Page 71
tcpMaxConn (1.3.6.1.2.1.6.4)
The limit on the total number of TCP connections the entity can support. In entities
where the maximum number of connections is dynamic, this object should cont ain
the value -1.
SyntaxINTEGER
Accessread-only
Statusmandatory
tcpActiveOpens (1.3.6.1.2.1.6.5)
The number of times TCP connections have made a direct transition to the
SYN-SENT state from the CLOSED state.
SyntaxCounter
3–MIB-II Objects
tcpMaxConn (1.3.6.1.2.1.6.4)
Accessread-only
Statusmandatory
tcpPassiveOpens (1.3.6.1.2.1.6.6)
The number of times TCP connections have made a direct transition to the
SYN-RCVD state from the LISTEN state.
The number of times TCP connections have made a direct transition to the
CLOSED state from either the SYN-SENT st ate or th e SYN-RCVD state, plus the
number of times TCP connections have made a direct transition to the LISTEN
state from the SYN-RCVD state.
SyntaxCounter
Accessread-only
Statusmandatory
tcpEstabResets (1.3.6.1.2.1.6.8)
The number of times TCP connections have made a direct transition to the
CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
SyntaxCounter
Accessread-only
Statusmandatory
tcpCurrEstab (1.3.6.1.2.1.6.9)
The number of TCP connections for which the current state is either
ESTABLISHED or CLOSE-WAIT.
SyntaxGauge
Accessread-only
Statusmandatory
tcpInSegs (1.3.6.1.2.1.6.10)
The total number of segments received, including those received in error. This
count includes segments received on currently established connections.
SyntaxCounter
Accessread-only
Statusmandatory
3-3859047-10 D
Page 73
tcpOutSegs (1.3.6.1.2.1.6.11)
The total number of segments sent including those on current connections, but
excluding those containing only retransmitted octets.
SyntaxCounter
Accessread-only
Statusmandatory
tcpRetransSegs (1.3.6.1.2.1.6.12)
The total number of segments retransmitted. That is, the number of TCP
segments transmitted containing one or more previously transmitted octets.
SyntaxCounter
3–MIB-II Objects
tcpOutSegs (1.3.6.1.2.1.6.11)
Accessread-only
Statusmandatory
59047-10 D3-39
Page 74
3–MIB-II Objects
The TCP Connection Table
The TCP Connection Table
The TCP connection table contains information about this entity's existing TCP
connections.
tcpConnState (1.3.6.1.2.1.6.13.1.1)
The state of this TCP connection. The only value which may be set by a
management station is deleteTCB(12). Accordingly, it is appropriate for an agent
to return a “badValue” response if a management station attempts to set this
object to any other value.
If a management station sets this object to the value deleteTCB(12), then this has
the effect of deleting the TCB (as defined in RFC 793) of the corresponding
connection on the managed Node. The result is an immediate termination of the
connection.
SyntaxINTEGER
Accessread-write
Statusmandatory
Return ValueWrites not supported.
tcpConnLocalAddress (1.3.6.1.2.1.6.13.1.2)
The local IP address for this TCP connection. In the case of a connection in the
listen state which is willing to accept connections for any IP interface associated
with the Node, the value 0.0.0.0 is used.
The total number of UDP datagrams sent from this entity.
SyntaxCounter
Accessread-only
Statusmandatory
The UDP Listener Table
The UDP listener table contains information about this entity's UDP end-point s on
which a local application is currently accepting datagrams.
udpLocalAddress (1.3.6.1.2.1.7.5.1.1)
The local IP address for this UDP listener. In the case of a UDP listener which is
willing to accept datagrams for any IP interface associated with the Node, the
value 0.0.0.0 is used.
Implementation of the EGP group is mandatory for all systems which implement
the EGP.
egpInMsgs (1.3.6.1.2.1.8.1)
The number of EGP messages received without error.
SyntaxCounter
Accessread-only
Statusmandatory
egpInErrors (1.3.6.1.2.1.8.2)
3–MIB-II Objects
The EGP Group
The number of EGP messages received that proved to be in error.
SyntaxCounter
Accessread-only
Statusmandatory
egpOutMsgs (1.3.6.1.2.1.8.3)
The total number of locally generated EGP messages.
SyntaxCounter
Accessread-only
Statusmandatory
59047-10 D3-45
Page 80
3–MIB-II Objects
egpOutErrors (1.3.6.1.2.1.8.4)
egpOutErrors (1.3.6.1.2.1.8.4)
The number of locally generated EGP messages not sent due to resource
limitations within an EGP entity.
SyntaxCounter
Accessread-only
Statusmandatory
The EGP Neighbor Table
The EGP neighbor table contains information about this entity's EGP neighbors.
egpNeighState (1.3.6.1.2.1.8.5.1.1)
The EGP state of the local system with respect to th is entry's EGP neighbor. Each
EGP state is represented by a value that is one greater than the numerical value
associated with the state in RFC 904.
SyntaxINTEGER
Accessread-only
Statusmandatory
egpNeighAddr (1.3.6.1.2.1.8.5.1.2)
The IP address of this entry's EGP neighbor.
SyntaxIpAddress
Accessread-only
Statusmandatory
3-4659047-10 D
Page 81
egpNeighAs (1.3.6.1.2.1.8.5.1.3)
The autonomous system of this EGP peer. Zero should be specified if the
autonomous system number of the neighbor is not yet known.
SyntaxINTEGER
Accessread-only
Statusmandatory
egpNeighInMsgs (1.3.6.1.2.1.8.5.1.4)
The number of EGP messages received without error from this EGP peer.
SyntaxCounter
Accessread-only
3–MIB-II Objects
egpNeighAs (1.3.6.1.2.1.8.5.1.3)
Statusmandatory
egpNeighInErrs (1.3.6.1.2.1.8.5.1.5)
The number of EGP messages received from this EGP peer that proved to be in
error (for example, bad EGP checksum).
SyntaxCounter
Accessread-only
Statusmandatory
egpNeighOutMsgs (1.3.6.1.2.1.8.5.1.6)
The number of locally generated EGP messages to this EGP peer.
A control variable used to trigger operator-initiated Start and Stop events. When
read, this variable always returns the most recent value that
egpNeighEventTrigger was set to. If it has not bee n set since th e last initialization
of the network management subsystem on the Node, it returns a value of “stop”.
When set, this variable causes a S tart or Stop event on the specified neighbor, as
specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to
begin neighbor acquisition and a non-Idle peer to re-initiate neighbor acquisition.
A stop event causes a non-Idle peer to return to the Idle state until a Start event
occurs, either by egpNeighEventTrigger or otherwise.
Based on the transmission media underlying each interface on a system, the
corresponding portion of the Transmission group is mandatory for that system.
When Internet-standard definitions for managing transmission media are defined,
the transmission group is used to provide a prefix for the names of those objects.
Typically, such definitions reside in the experimental portion of the MIB until they
are "proven", then as a part of the Internet standardization process, the definitions
are accordingly elevated and a new object identifier , under the transmission group
is defined. By convention, the name assigned is:
type OBJECT IDENTIFIER ::= { transmission number }.
Where "type" is the symbolic value used for the media in the ifType column of the
ifTable object, and "number" is the actual integer value corresponding to the
symbol.
An index value that uniquely identifies an interface to an ethernet-like medium.
The interface identified by a particular value of this index is the same interface as
identified by the same value of ifIndex.
A count of frames received on a particular interface that are an integral numbe r of
octets in length but do not pass the FCS check. This count does not include
frames received with frame-too-long or frame-too-short error.
A count of frames for which reception on a particular interface fails due to an
internal MAC sublayer receive error.
The precise meaning of the count represented by an instance of this object is
implementation-specific. In particular, an instance of this object may represent a
count of receive errors on a particular interface that are not otherwise counted.
For an interface operating at 10 Gbps, the number of times the re ceiving media is
non-idle (a carrier event) for a period of time equal to or greater than
minFrameSize, and during which there was at least one occurrence of an event
that causes an indication of a receive error.
A count of MAC Control frames transmitted on this interface with an opcode
indicating the PAUSE operation.
Syntaxcounter32
Accessread-only
Statuscurrent
59047-10 D3-53
Page 88
3–MIB-II Objects
The SNMP Group
The SNMP Group
Implementation of the SNMP group is mandatory for all systems which support an
SNMP protocol entity. Some of the objects defined below will be zero-valued in
those SNMP implementations that are optimized to support only those functions
specific to either a management agent or a management station. In particular, it
should be observed that the objects below refer to an SNMP entity, and there may
be several SNMP entities residing on a managed Node.
snmpInPkts (1.3.6.1.2.1.11.1)
The total number of messages delivered to the SNMP entity from the transport
service.
SyntaxCounter
Accessread-only
Statusmandatory
snmpOutPkts (1.3.6.1.2.1.11.2)
The total number of SNMP messages passed from the SNMP protocol entity to
the transport service.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInBadVersions (1.3.6.1.2.1.11.3)
The total number of SNMP messages delivered to the SNMP protocol entity and
were for an unsupported SNMP version.
SyntaxCounter
Accessread-only
Statusmandatory
3-5459047-10 D
Page 89
snmpInBadCommunityNames (1.3.6.1.2.1.11.4)
snmpInBadCommunityNames (1.3.6.1.2.1.11.4)
The total number of SNMP messages delivered to the SNMP protocol entity wh ich
used a SNMP community name not known to the entity.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInBadCommunityUses (1.3.6.1.2.1.11.5)
The total number of SNMP messages delivered to the SNMP protocol entity wh ich
represented an SNMP operation which was not allowed by the SNMP community
named in the message.
SyntaxCounter
3–MIB-II Objects
Accessread-only
Statusmandatory
snmpInASNParseErrs (1.3.6.1.2.1.11.6)
The total number of ASN.1 or BER errors encountered by the SNMP protocol
entity when decoding received SNMP messages.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInTooBigs (1.3.6.1.2.1.11.8)
The total number of SNMP PDUs delivered to the SNMP protocol entity and for
which the value of the error-status field is “tooBig”.
The total number of SNMP PDUs delivered to the SNMP protocol entity and for
which the value of the error-status field is "NoSuchName".
SyntaxCounter
Accessread-only
Statusmandatory
snmpInBadValues (1.3.6.1.2.1.11.10)
The total number of SNMP PDUs delivered to the SNMP protocol entity and for
which the value of the error-status field is “badValue”.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInReadOnlys (1.3.6.1.2.1.11.11)
The total number valid SNMP PDUs delivered to the SNMP protocol entity and for
which the value of the error-status field is “readOnly”. It should be noted that it is a
protocol error to generate an SNMP PDU which contains the value ”readOnly” in
the error-status field, as such, this object is provided as a means of detecting
incorrect implementations of the SNMP.
SyntaxCounter
Accessread-only
Statusmandatory
3-5659047-10 D
Page 91
snmpInGenErrs (1.3.6.1.2.1.11.12)
The total number of SNMP PDUs delivered to the SNMP protocol entity and for
which the value of the error-status field is “genErr”.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInTotalReqVars (1.3.6.1.2.1.11.13)
The total number of MIB objects retrieved successfully by the SNMP protocol
entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
SyntaxCounter
3–MIB-II Objects
snmpInGenErrs (1.3.6.1.2.1.11.12)
Accessread-only
Statusmandatory
snmpInTotalSetVars (1.3.6.1.2.1.11.14)
The total number of MIB objects altered successfully by the SNMP protocol entity
as the result of receiving valid SNMP Set-Request PDUs.
SyntaxCounter
Accessread-only
Statusmandatory
snmpInGetRequests (1.3.6.1.2.1.11.15)
The total number of SNMP Get-Request PDUs accepted and processed by the
SNMP protocol entity.
The total number of SNMP Get-Request PDUs generated by the SNMP protocol
entity.
SyntaxCounter
Accessread-only
Statusmandatory
snmpOutGetNexts (1.3.6.1.2.1.11.26)
The total number of SNMP Get-Next PDUs generated by the SNMP protocol
entity.
SyntaxCounter
Accessread-only
Statusmandatory
snmpOutSetRequests (1.3.6.1.2.1.11.27)
The total number of SNMP Set-Request PDUs generated by the SNMP protocol
entity.
SyntaxCounter
Accessread-only
Statusmandatory
snmpOutGetResponses (1.3.6.1.2.1.11.28)
The total number of SNMP Get-Response PDUs generated by the SNMP protocol
entity.
SyntaxCounter
Accessread-only
Statusmandatory
3-6059047-10 D
Page 95
snmpOutTraps (1.3.6.1.2.1.11.29)
The total number of SNMP Trap PDUs generated by the SNMP protocol entity.
SyntaxCounter
Accessread-only
Statusmandatory
snmpEnableAuthenTraps (1.3.6.1.2.1.11.30)
Indicates whether the SNMP agent process is permitted to generate
authentication-failure traps. The value of this object overrides any configuration
information; as such, it provides a means whereby all authentication-failure traps
may be disabled.
It is strongly recommended that this object be stored in non-volatile memory so
that it remains constant between re-initializations of the network management
system.
The textual name of the interface. The value of this object should be the name of
the interface as assigned by the local device. If there is no local name, or this
object is otherwise not applicable, then this object contains a zero-length string.
Syntax DisplayString
Access read-only
Status current
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which
were addressed to a multicast address at this sub-layer . For a MAC layer protocol,
this includes both Group and Functional addresses.
Syntax Counter32
Access read-only
Status current
ifInBroadcastPkts (1.3.6.1.2.1.31.1.1.1.3)
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which
were addressed to a broadcast address at this sub-layer.
Syntax Counter32
Access read-only
Status current
ifOutMulticastPkts (1.3.6.1.2.1.31.1.1.1.4)
The total number of packets that higher-level protocols requested be transmitted,
and which were addressed to a multicast address at this sub-layer, including
those that were discarded or not sent. For a MAC layer protocol, this includes both
Group and Functional addresses.
Syntax Counter32
Accessread-only
Statuscurrent
3-6259047-10 D
Page 97
ifOutBroadcastPkts (1.3.6.1.2.1.31.1.1.1.5)
The total number of packets that higher-level protocols requested be transmitted,
and which were addressed to a broadcast address at this sub-layer, including
those that were discarded or not sent.
SyntaxCounter32
Accessread-only
Statuscurrent
ifHighSpeed (1.3.6.1.2.1.31.1.1.1.15)
An estimate of the interface's current bandwidth in units of 1,000,000 bits per
second. If this object reports a value of `n' then the speed of the interface is
somewhere in the range of `n-500,000' to `n+499,999'. For interfaces which do not
vary in bandwidth or for those where no accurate estimation can be made, this
object should contain the nominal bandwidth. For a sub-layer which has no
concept of bandwidth, this object should be zero.
3–MIB-II Objects
ifOutBroadcastPkts (1.3.6.1.2.1.31.1.1.1.5)
Syntax Gauge32
Accessread-only
Statuscurrent
ifPromiscuousMode (1.3.6.1.2.1.31.1.1.1.16)
This object has a value of false(2) if this interface only accepts packets/frames
that are addressed to this station. This object has a value of true(1) when the
station accepts all packets/frames transmitted on the media.
The value of sysUpTime on the most recent occasion at which any on e or more of
this interface's counters suffered a discontinuity. The relevant counters are the
specific instances associated with this interface of any Counter32 or Counter64
object contained in the ifTable or ifXTable. If no such discontinuities have occurred
since the last re-initialization of the local management subsystem, then this object
contains a zero value.
SyntaxTimeStamp
Accessread-only
Statuscurrent
3-6459047-10 D
Page 99
ifTableLastChange (1.3.6.1.2.1.31.5)
The value of sysUpTime at the time of the last creation or deletion of an entry in
the ifTable. If the number of entries has been unchanged since the last
re-initialization of the local network management subsystem, then this object
contains a zero value.