| Managing the Switch Using SNMP |
|
|
| object identifier, or NULL. NULLs act as place holders reserved for |
| future use. |
Access | This property indicates the level of access to this particular object. |
| Legal values are: |
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). |
The presence of objects, their names, and additional property values are part of 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
Vendors may choose to implement
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,
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
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
GigWorks | Switch Management | |
Installer's/User's Manual |