Q-Logic MKII-BASE16 Manuel D’Utilisation
GigWorks MkII-16 Switch Model MKII-BASE16
Installer's/User's Manual 59003-01 Rev. A
Installer's/User's Manual 59003-01 Rev. A
Switch Management
3-51
Managing the Switch Using SNMP
object identifier, or NULL. NULLs act as place holders reserved for
future use.
future use.
Access
This property indicates the level of access to this particular object.
Legal values are: read-only, read-write, write-only, and not accessible.
Legal values are: read-only, read-write, write-only, and not accessible.
Status
This property defines the implementation requirement for this object:
mandatory (the managed node must implement this object); optional
(the managed node may implement this object); or obsolete (the
managed node need no longer implement this object).
mandatory (the managed node must implement this object); optional
(the managed node may implement this object); or obsolete (the
managed node need no longer implement this object).
The presence of objects, their names, and additional property values are part of
each MIB specification. Currently, there are three types of MIB specifications:
each MIB specification. Currently, there are three types of MIB specifications:
Standard MIBs
The standard MIB contains a set of objects that are well defined, known, and
accepted by the Internet standards group. There is a generic MIB defined for
managing network nodes. And, there are two versions of this standard MIB called
MIB-I and MIB-II. These MIBs contain standard managed objects that are
grouped into different functional categories.
accepted by the Internet standards group. There is a generic MIB defined for
managing network nodes. And, there are two versions of this standard MIB called
MIB-I and MIB-II. These MIBs contain standard managed objects that are
grouped into different functional categories.
Vendors may choose to implement MIB-I or MIB-II for their agents as well as
their network management software. That means if you use a MIB-I network
management station to query a MIB-II node, you will not get the full range of
possible data. Conversely, if you use a MIB-II network management station to
query a MIB-I node, many of the data displays on the console will read blank or
zero because of the unavailability of the extra objects.
their network management software. That means if you use a MIB-I network
management station to query a MIB-II node, you will not get the full range of
possible data. Conversely, if you use a MIB-II network management station to
query a MIB-I node, many of the data displays on the console will read blank or
zero because of the unavailability of the extra objects.
Experimental MIBs
The experimental MIB contain MIBs that are not in the standard MIBs and are
not part of the private or enterprise MIBs. These MIBs may contain specific
information about other elements of the network and node management. When an
experimental MIB is proven effective and refined, it can be considered a standard
MIB. Some experimental MIBs include: T1 Carrier Objects, Ethernet-like
Objects, Token Ring-like Objects, and FDDI Objects.
not part of the private or enterprise MIBs. These MIBs may contain specific
information about other elements of the network and node management. When an
experimental MIB is proven effective and refined, it can be considered a standard
MIB. Some experimental MIBs include: T1 Carrier Objects, Ethernet-like
Objects, Token Ring-like Objects, and FDDI Objects.
The Fibre Channel Fabric MIB, supported by the GigVision Proxy Agents is an
Experimental MIB (Refer to Appendix D in this manual). Also, the Fibre Channel
Node MIB, supported by the GigVision Sub-agents, is an Experimental MIB
(Refer to Appendix C in this manual)
Experimental MIB (Refer to Appendix D in this manual). Also, the Fibre Channel
Node MIB, supported by the GigVision Sub-agents, is an Experimental MIB
(Refer to Appendix C in this manual)
Enterprise MIBs
Enterprise MIBs are designed by individual companies for their own networking
nodes. For network management software that is not from the enterprise MIB
vendor to read these MIBs, the manager must know the MIB object names to
access them. Often the enterprise MIBs from a vendor are product-line or model
nodes. For network management software that is not from the enterprise MIB
vendor to read these MIBs, the manager must know the MIB object names to
access them. Often the enterprise MIBs from a vendor are product-line or model