Interface Table Extension to the Interface Table High Capacity Counters Interface-Related Traps IF MIB Conformance and Compliance Statements

Size: px
Start display at page:

Download "Interface Table Extension to the Interface Table High Capacity Counters Interface-Related Traps IF MIB Conformance and Compliance Statements"

Transcription

1 CHAPTER 3 This chapter describes the individual MIB objects that comprise the PXM45-specific MIB files. The IF MIB resides in the IF-MIB.my file. This MIB is extracted from RFC 2233 and describes the generic network interface sub-layers. The IF MIB is an updated version of MIB-II s iftable and incorporates the extensions defined in RFC Contents of this chapter include: Interface Index Interface Table Extension to the Interface Table High Capacity Counters Interface-Related Traps IF MIB Conformance and Compliance Statements Interface Index The interface index contains the semantics of the ifindex and is used for any objects defined on other mib modules that need these semantics. The object identifier for each MIB object is listed in Table 3-1. Table 3-1 Interface Index Object Identifiers Name Object Identifier OwnerString InterfaceIndex InterfaceIndexOrZero ifnumber ::= { interfaces 1 } iftablelastchange ::= { ifmibobjects 5 } 3-1

2 Interface Index Chapter 3 The MIB objects are listed in Table 3-2. Table 3-2 Interface Index MIB Objects OwnerString OCTET STRING Uses a model as an administratively-assigned name (SIZE(0..255)) of the resource-owner for this data type. This information is taken from the NVT ASCII character set. It is suggested that this name contains one or more of the following: ASCII form of the manager station s transport address. Management station name (for example, domain name). Network management personnel s name, location, or phone number. In some cases, the agent itself is the owner of an entry. In these cases, start of the string can be the agent substring. InterfaceIndex contains the semantics of ifindex and is used for any syntax defined on other MIB modules that need these semantics. Display Hint: 255a InterfaceIndex Integer32 ( ) Specifies a unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity s network management system to the next re-initialization. Display Hint: d InterfaceIndexOrZero Integer32 ( ) Specifies an extension of the InterfaceIndex convention for this textual convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. The zero value is specific and must therefore be defined as part of the description of any object using this syntax. Examples of the usage of zero include situations when the interface was unknown, or when or all interfaces are referenced. Display Hint: d 3-2

3 Chapter 3 Interface Table Table 3-2 Interface Index MIB Objects (continued) ifnumber Integer32 Determines the number of network interfaces (regardless of their current state) present on this system. iftablelastchange TimeTicks Determines the value sysuptime at the last creation or deletion of an entry in the iftable. If the number of entries are unchanged since the last re-initialization of the local network management subsystem, this contains a zero value. Interface Table The interface table contains information on the entity s interfaces. Each sub-layer below the internetwork layer of a network interface is considered to be an interface. The object identifier for each MIB object is listed in Table 3-3. Table 3-3 Interface Table Object Identifiers Name Object Identifier iftable ::= { interfaces 2 } ifentry ::= { iftable 1 } ifindex ::= { ifentry 1 } ifdescr ::= { ifentry 2 } iftype ::= { ifentry 3 } ifmtu ::= { ifentry 4 } ifspeed ::= { ifentry 5 } ifphysaddress ::= { ifentry 6 } ifadminstatus ::= { ifentry 7 } ifoperstatus ::= { ifentry 8 } iflastchange ::= { ifentry 9 } ifinoctets ::= { ifentry 10 } ifinucastpkts ::= { ifentry 11 } ifinnucastpkts ::= { ifentry 12 } ifindiscards ::= { ifentry 13 } ifinerrors ::= { ifentry 14 } 3-3

4 Interface Table Chapter 3 Table 3-3 Interface Table Object Identifiers (continued) Name Object Identifier ifinunknownprotos ::= { ifentry 15 } ifoutoctets ::= { ifentry 16 } ifoutucastpkts ::= { ifentry 17 } ifoutnucastpkts ::= { ifentry 18 } ifoutdiscards ::= { ifentry 19 } ifouterrors ::= { ifentry 20 } ifoutqlen ::= { ifentry 21 } ifspecific ::= { ifentry 22 } The MIB objects are listed in Table 3-4. Table 3-4 Interface Table MIB Objects iftable Sequence of IfEntry Provides a list of interface entries. The number of entries is given by the value of ifnumber. Max-Access: not-accessible ifentry IfEntry Contains an entry that is used for management information applicable to a particular interface. Max-Access: not-accessible The index contains ifindex. ifindex InterfaceIndex Specifies a unique value, greater than zero, for each interface. It is recommended that values be assigned contiguously starting from one. The value for each interface sub-layer must remain constant from one reinitialization of the entity s network management system to the next reinitialization. Note For the Cisco MGX 8850, the values may not be contiguous and cannot start from one. The ifindex association with a physical interface or a logical interface is found in ifname object. 3-4

5 Chapter 3 Interface Table Table 3-4 Interface Table MIB Objects (continued) ifdescr DisplayString (SIZE (0..255)) Specifies a textual string that contains information about the interface. This string can include the name of the manufacturer, the product name, and the version of the interface hardware and software. An example can be the association of the interface with a physical or logical interface. iftype IANAifType Indicates the type of interface. Additional values for iftype are assigned by the Internet Assigned Numbers Authority (IANA), by updating the syntax of the IANAifType textual convention. ifmtu Integer32 Indicates the size of the largest packet that is sent and received on the interface, specified in octets. For interfaces that are used to transmit network datagrams, this is the largest network datagram sent on the interface. ifspeed Gauge32 Determines an estimate of the interface s current bandwidth in bits per second. For interfaces which do not vary in bandwidth or no accurate estimation is made, ifspeed can indicate the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable, ifspeed can report its maximum value (4,294,967,295). For a sub-layer which has no concept of bandwidth, ifspeed is zero. ifphysaddress PhysAddress Indicates the address of the interface at the protocol sub-layer. For example, an interface can normally contain a Media Access Control (MAC) address. The interface s media-specific MIB must define the bit and byte ordering and the format of the value of this address. For interfaces which do not have such an address (for example, a serial line), ifphysaddress can contain an octet string of zero length. 3-5

6 Interface Table Chapter 3 Table 3-4 Interface Table MIB Objects (continued) ifadminstatus Integer {up (1), ready to pass packets down; (2), testing; (3), in some test mode} Indicates the desired state of the interface. The testing(3) state indicates no operational packets are passed. When a managed system initializes, all interfaces start with ifadminstatus in the down (2) state. As a result of either explicit management action or through configuration information retained by the managed system, ifadminstatus is then changed to either the up(1), testing(3), or remains in the down( 2) state. Max-Access: read-write ifoperstatus Integer {up (1), ready to pass packets; down (2); testing (3), in some test mode; unknown (4), status can not be determined; dormant (5); notpresent (6), some component is missing; lowerlayerdown (7), down due to state of lower-layer interface(s)} Indicates the current operational state of the interface. The testing(3) state indicates that no operational packets are passed. If ifadminstatus is down(2), ifoperstatus is down(2). If ifadminstatus is changed to up(1), ifoperstatus can change to up(1). If the interface is ready to transmit and receive network traffic, it can change to dormant(5) when the interface is waiting for external actions (such as a serial line waiting for an incoming connection). It can remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state. It can remain in the notpresent(6) state if the interface is missing hardware components. iflastchange TimeTicks Indicates the sysuptime value at the time the interface entered the current operational state. If the current state is entered prior to the last reinitialization of the local network management subsystem, this contains a zero value. ifinoctets Counter32 Indicates the total number of octets received on the interface, including framing characters. The discontinued counter value can occur at reinitialization of the management system, and at other times as indicated by the ifcounterdiscontinuitytime value. 3-6

7 Chapter 3 Interface Table Table 3-4 Interface Table MIB Objects (continued) ifinucastpkts Counter32 Indicates the number of packets delivered by this sub-layer to a higher sub-layer. The packets were not addressed to a multicast or broadcast address at this sub-layer. The discontinued counter value can occur at reinitialization of the management system, and at other times as indicated by the ifcounterdiscontinuitytime value. ifinnucastpkts Counter32 Indicates the number of packets that are delivered by this sub-layer to a higher sub-layer. They are addressed to a multicast or broadcast address at this sub-layer. The discontinued counter values can occur at reinitialization of the management system, and at other times as indicated by the ifcounterdiscontinuitytime value. This is deprecated in favor of ifinmulticastpkts and ifinbroadcastpkts. Status: deprecated ifindiscards Counter32 Indicates the number of inbound packets that are chosen to be discarded even though no errors are detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet can be to free up buffer space. The discontinued counter values can occur at reinitialization of the management system, and at other times as indicated by the ifcounterdiscontinuitytime value. ifinerrors Counter32 Indicates the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol for packet-oriented interfaces. For character-oriented or fixed-length interfaces, the number of inbound transmission units contained errors that prevented them from being delivered to a higher-layer protocol. The discontinued counter values can occur at reinitialization of the management system, and at other times as indicated by the ifcounterdiscontinuitytime value. 3-7

8 Interface Table Chapter 3 Table 3-4 Interface Table MIB Objects (continued) ifinunknownprotos Counter32 Indicates the number of packets received through the interface, which are discarded because of an unknown or unsupported protocol for packet-oriented interfaces. For character-oriented or fixed-length interfaces that support protocol multiplexing, this object indicates the number of transmission units received through the interface. These units were discarded because of an unknown or unsupported protocol. For an interface that does not support protocol multiplexing, this counter is always zero. The discontinued counter value can occur at reinitialization of the management system and at other times as indicated by the ifcounterdiscontinuitytime value. ifoutoctets Counter32 Indicates the number of octets transmitted out of the interface, including framing characters. The discontinued counter value can occur at reinitialization of the management system, and at other times indicated by the ifcounterdiscontinuitytime value. ifoutucastpkts Counter32 Indicates the number of packets that are requested for transmission by higher-level protocols. These packets are not addressed to a multicast or broadcast address at this sub-layer. The number includes those that are discarded or not sent. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifoutnucastpkts Counter32 Indicates the number of packets that are requested for transmission by higher-level protocols, which are addressed to a multicast or broadcast address at this sub-layer. The number includes those that are discarded or not sent. The discontinued counter value can occur at re-initialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. This is deprecated in favor of ifoutmulticastpkts and ifoutbroadcastpkts. Status: deprecated 3-8

9 Chapter 3 Interface Table Table 3-4 Interface Table MIB Objects (continued) ifoutdiscards Counter32 Indicates the number of outbound packets chosen to be discarded, even though no errors have been detected to prevent their transmission. One possible reason for discarding such a packet can be to free up buffer space. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifouterrors Counter32 Indicates the number of outbound packets that cannot be transmitted because of errors for packet-oriented interfaces. For character-oriented or fixed-length interfaces, this object indicates the number of outbound transmission units that can not be transmitted because of errors. The discontinued counter value can occur at re-nitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifoutqlen Gauge32 Indicates the length of the output packet queue (in packets). Status: deprecated ifspecific IDENTIFIER Refers to MIB definitions specific to the particular media being used to realize the interface. It is recommended that this value points to an instance of a MIB in the media-specific MIB. The pointer can have the semantics associated with the Instance Pointer textual convention defined in RFC In fact, it is recommended that the media-specific MIB specify what value ifspecific can take for values of iftype. If no MIB definitions specific to the particular media are available, the value is set to the IDENTIFIER { 0 0 }. Status: deprecated 3-9

10 Extension to the Interface Table Chapter 3 Extension to the Interface Table The object identifier for each MIB object is listed in Table 3-5. Note This table replaces the ifextnstable table. Table 3-5 Extension to the Interface Table Object Identifiers Name Object Identifier ifxtable ::= { ifmibobjects 1 } ifxentry ::= { ifxtable 1 } ifname ::= { ifxentry 1 } ifinmulticastpkts ::= { ifxentry 2 } ifinbroadcastpkts ::= { ifxentry 3 } ifoutmulticastpkts ::= { ifxentry 4 } ifoutbroadcastpkts ::= { ifxentry 5 } The MIB objects are listed in Table 3-6. Table 3-6 Extension to the Interface Table MIB Objects ifxtable SEQUENCE Lists the interface entries. The number of entries given by the value of OF IfXEntry ifnumber. This table contains additional entries for the interface table. Max-Access: not-accessible ifxentry IfXEntry Contains additional management information applicable to a particular interface for this entry. Max-Access: not-accessible The index contains ifentry. 3-10

11 Chapter 3 Extension to the Interface Table Table 3-6 Extension to the Interface Table MIB Objects (continued) ifname DisplayString Specifies the textual name of the interface. The ifname value is the name of the interface assigned by the local device and is suitable for use in commands entered at the device console. Depending on the interface naming syntax of the device, ifname is a text name such as le0 or a simple port number such as 1. If several entries in the iftable together represent a single interface as named by the device, each has the same value of ifname. Note For an agent that responds to SNMP queries concerning an interface on some other (proxy) device, the ifname value for such an interface is the proxy device local name. If there is no local name, or if ifname is not applicable, this object contains a zero length string. Note For the Cisco MGX 8850, ifname contains the physical or logical association of a name. The actual values depend on the implementation. The following is an example that illustrates the value(s) for the ifname object: ifdescr ifname Remark <string> rs232mp Association of RS232 Maintenance Port Logical Slot 7, Bay 1, Port 1 <string> ethernet Association of Ethernet Port Logical Slot 1, Bay 1, Port 1 <string> slip Association of slip Logical Slot 7, Bay 1 rs232port 2, Interface 1 Physical lines, ATM physical lines, and ATM virtual interfaces are the three conventions used for the ifname object. Physical Lines This format is used for Physical Lines such as SONET, DS3, DS1, and so on forth. The following is an example: <linetype>.<logical-slot>.<bay>.<linenumber> The following are the values for the physical lines: linetype logical-slot Refers to SONET, DS3, DS1, Ethernet, and RS232 Determines the logical slot number of the module. 3-11

12 Extension to the Interface Table Chapter 3 Table 3-6 Extension to the Interface Table MIB Objects (continued) ifname bay Determines the back card number. (continued) linenumber Specifies the physical line number. The following is a SONET physical line example: sonet => sonet, Logical Slot 4, Bay 1, Physical Line 1 The following is a ds physical line example: ds => ds3, Logical Slot 6, Bay 2, Physical Line 3 ATM Physical Interfaces The following is the format used for ATM Physical Interfaces: atm.<logical-slot>.<bay>.<linenumber> The following is the values for the ATM Physical Interfaces: logical-slot bay Determines the logical slot number of the module. Determines the back card number. linenumber Determines the physical line number. The following is is an example of the ATM physical interface: atm => atm, Logical Slot 4, Bay 2, Physical Line 2, ATM Phy 1 atm => atm, Logical Slot 4, Bay 1, IMA Id 2, ATM Phy 2 ATM Virtual Interfaces The following format is used for ATM Virtual Interfaces (atmvirtual): atmvirtual.<logical-slot>.<bay>.<linenumber>.<vi-number>.[<vpi-numb er>] The following are the values for the ATM Virtual Interface: logical-slot Determines the logical slot number of the module. bay Determines the back card number. linenumber/ima-id vi-number vpi-number Specifies the physical line number or Ima ID. Determines the virtual interface number. Determines the VPI number and exists only for virtual trunk. 3-12

13 Chapter 3 Extension to the Interface Table Table 3-6 Extension to the Interface Table MIB Objects (continued) ifname (continued) The following is the first example of the ATM virtual interface: atmvirtual => atmvirtual, Logical Slot 3, Bay 1, Physical Line 2, VI 33 The following is the second example of the ATM virtual interface: atmvirtual => atmvirtual, Logical Slot 3, Bay 1, IMA Id 3, VI 23 The following is the third example of the ATM virtual interface: atmvirtual => atmvirtual, Logical Slot 4, Bay 2, Physical Line 2, VI 34, VPI 2000 ifinmulticast Pkts Counter32 Indicates the number of packets delivered by this sub-layer to a higher sub-layer, which is addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both groups and functional addresses. The discontinued counter value can occur at re-nitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifinbroadcast Pkts Counter32 Indicates the number of packets delivered by this sub-layer to a higher sub-layer. These packets are addressed to a broadcast address.the discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifoutmulticast Pkts Counter32 Indicates the number of packets that higher-level protocols request be transmitted. These packets are addressed to a multicast address, which includes those that are discarded or not sent. Both group and functional addresses are included if requested by a MAC layer protocol. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifoutbroadcast Pkts Counter32 Indicates the number of packets that higher-level protocols requested be transmitted, which are addressed to a broadcast address at this sub-layer. The object includes those that are discarded or not sent. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. 3-13

14 High Capacity Counters Chapter 3 High Capacity Counters The high capacity counters are 64 bit versions of the basic iftable counters. They have the same basic semantics as their 32-bit counterparts; their syntax is extended to 64 bits. The object identifier for each MIB object is listed in Table 3-7. Table 3-7 High Capacity Counters Object Identifiers Name Object Identifier ifhcinoctets ::= { ifxentry 6 } ifhcinucastpkts ::= { ifxentry 7 } ifhcinmulticastpkts ::= { ifxentry 8 } ifhcinbroadcastpkts ::= { ifxentry 9 } ifhcoutoctets ::= { ifxentry 10 } ifhcoutucastpkts ::= { ifxentry 11 } ifhcoutmulticastpkts ::= { ifxentry 12 } ifhcoutbroadcastpkts ::= { ifxentry 13 } iflinkupdowntrapenable ::= { ifxentry 14 } ifhighspeed ::= { ifxentry 15 } ifpromiscuousmode ::= { ifxentry 16 } ifconnectorpresent ::= { ifxentry 17 } ifalias ::= { ifxentry 18 } ifcounterdiscontinuitytime ::= { ifxentry 19 } 3-14

15 Chapter 3 High Capacity Counters The MIB objects are listed in Table 3-8. Table 3-8 High Capacity Counters MIB Objects ifhcinoctets Counter64 Indicates the number of octets received on the interface, which includes framing characters. ifhcinoctets is a 64-bit version of ifinoctets. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by ifcounterdiscontinuitytime value. ifhcinucastpkts Counter64 Indicates the number of packets delivered by this sub-layer to a higher sub-layer.these packets are not addressed to a multicast or broadcast address at this sub-layer. This is a 64-bit version of ifinucastpkts. The discontinued counter value can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifhcinmulticastpkts Counter64 Indicates the number of packets delivered by a sub-layer to a higher sub-layer, which are addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both group and functional addresses. This object is a 64-bit version of ifinmulticastpkts. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifhcinbroadcastpkts Counter64 Indicates the number of packets that are delivered by a lower sub-layer to a higher sub-layer, which are addressed to a broadcast address at the lower sub-layer. This is a 64-bit version of ifinbroadcastpkts. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. 3-15

16 High Capacity Counters Chapter 3 Table 3-8 High Capacity Counters MIB Objects (continued) ifhcoutoctets Counter64 Indicates the number of octets transmitted out of the interface that includes framing characters. This is a 64-bit version of ifoutoctets. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifhcoutucastpkts Counter64 Indicates the number of packets that higher-level protocols requested be transmitted, which are not addressed to a multicast or broadcast address at this sub-layer. This includes those packets that are discarded or not sent. This is a 64-bit version of ifoutucastpkts. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifhcoutmulticastpkts Counter64 Indicates the total number of packets that higher-level protocols requested be transmitted, which are addressed to a multicast address at this sub-layer. This includes the packets that are discarded or not sent. For a MAC layer protocol, this includes both group and functional addresses. This is a 64-bit version of ifoutmulticastpkts. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. ifhcoutbroadcastpkts Counter64 Indicates the number of packets that higher-level protocols requested be transmitted, which are addressed to a broadcast address at this sub-layer. This includes those packets that are discarded or not sent. This is a 64-bit version of ifoutbroadcastpkts. The discontinued counter values can occur at reinitialization of the management system, and at other times, as indicated by the ifcounterdiscontinuitytime value. 3-16

17 Chapter 3 High Capacity Counters Table 3-8 High Capacity Counters MIB Objects (continued) iflinkupdowntrapenable Integer { enabled (1), disabled (2) } Indicates whether linkup or linkdown traps can be generated for this interface. By default, this can have the value enabled(1) for interfaces, which do not operate on top of any other interface (as defined in the ifstacktable) and disabled(2) otherwise. Max-Access: read-write ifhighspeed Gauge32 Provides an estimate of the interface current bandwidth in units of 1,000,000 bits per second. If this reports a value of n, the speed of the interface is from n-500,000 to n+499,999. For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, ifhighspeed can contain the nominal bandwidth. For a sub-layer having a defined bandwidth, the value is zero. ifpromiscuousmode Truth Specifies a value of false(2) if the interface accepts only packets or frames that are addressed to this station. It has a value of true(1) when the station accepts all packets or frames transmitted on the media. The value true(1) is valid only on certain types of media. If valid, setting ifpromiscuousmode to a value of true(1) can require the interface to be reset before becoming effective. The value of ifpromiscuousmode does not effect the reception of broadcast and multicast packets or frames by the interface. Max-Access: read-write ifconnectorpresent Truth Specifies the value true(1) if the interface sublayer has a physical connector and the value false(2). 3-17

18 High Capacity Counters Chapter 3 Table 3-8 High Capacity Counters MIB Objects (continued) ifalias DisplayString (SIZE(0..64)) Describes an alias for the interface as specified by a network manager. It provides a non-volatile handle for the interface. On the first instance of an interface, the value of ifalias associated with that interface is the zero-length string. When a value is written into ifalias through a network management set operation, the agent must retain the supplied value in the ifalias instance associated with the same interface. The agent must retain this supplied value for as long as that interface remains instantiated. The duration that the interface remains instantiated includes all reinitializations and reboots of the network management system. It also includes those which result in a change of the interface s ifindex value. An example of the value that a network manager can store in ifalias for a WAN interface is the Telco s circuit number or identifier of the interface. Some agents can support write-access only for interfaces having particular values of iftype. An agent that supports write access to this is required to keep the value in non-volatile storage, but it can limit the length of new values depending on how much storage is occupied by the current values for other interfaces. Max-Access: read-write ifcounterdiscontinuitytime TimeStamp Indicates the sysuptime value on the most recent occasion one 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 contained in the iftable or ifxtable. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, this object contains a zero value. 3-18

19 Chapter 3 Interface-Related Traps Interface-Related Traps The object identifier for each trap is listed in Table 3-9. Table 3-9 Interface-Related Traps Object Identifiers Name Object Identifier linkdown ::= { snmptraps 3 } linkup ::= { snmptraps 4 } The traps are listed n in Table Table 3-10 Interface-Related Traps MIB Objects linkdown {ifindex, ifadminstatus, ifoperstatus} Signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifoperstatus for one of its communication links is about to enter the down state. This can be from any other state except the notpresent state. This previous state is indicated by the included value of ifoperstatus. linkup {ifindex, ifadminstatus, ifoperstatus} Signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifoperstatus for one of its communication links left the down state and transitioned into some other state. This includes any previous state except the notpresent state. This previous state is indicated by the included value of ifoperstatus. IF MIB Conformance and Compliance Statements The information on conformance is specific to SNMPv2. Table 3-11 lists the conformance groups. Table 3-11 IF MIB Conformance Groups Name Object Identifier ifconformance ::= { ifmib 2 } ifgroups ::= { ifconformance 1 } ifcompliances ::= { ifconformance 2 } 3-19

20 IF MIB Conformance and Compliance Statements Chapter 3 IF MIB Conformance Groups The object identifier for each MIB object is listed in Table Note The five groups iffixedlengthgroup, ifpacketgroup, ifhcpacketgroup, ifvhcpacketgroup, and ifrcvaddressgroup are mutually exclusive; only one of these groups is implemented for any interface. Table 3-12 IF MIB Conformance Group Object Identifiers Name Object Identifier iflinkupdowntrapenable ifpromiscuousmode ifstackstatus ifadminstatus ifalias ::= { ifcompliances 2 } ifgeneralinformationgroup ::= { ifgroups 10 } iffixedlengthgroup ::= { ifgroups 2 } ifhcfixedlengthgroup ::= { ifgroups 3 } ifpacketgroup ::= { ifgroups 4 } ifhcpacketgroup ::= { ifgroups 5 } ifvhcpacketgroup ::= { ifgroups 6 } ifrcvaddressgroup ::= { ifgroups 7 } ifstackgroup2 ::= { ifgroups 11 } ifcounterdiscontinuitygroup ::= { ifgroups 13 } 3-20

21 Chapter 3 IF MIB Conformance and Compliance Statements A list of the MIB objects is listed in Table Table 3-13 IF MIB Conformance Group MIB Objects ifcompliance2e {ifgeneralinformation Specifies the compliance statement for the SNMPv2 Group, ifstackgroup2, entities that have network interfaces. ifcounterdiscontinuity Group} Module: PXM45 The following is the description of each group: iffixedlengthgroup This group is mandatory for all network interfaces which are character-oriented or transmit data in fixed-length transmission units. ifhcfixedlengthgroup This group is mandatory only for those network interfaces which are character-oriented or transmit data in fixed-length transmission units, and for which the value of the corresponding instance of ifspeed is greater than 20 million bits/second. ifpacketgroup This group is mandatory for all network interfaces which are packet-oriented. ifhcpacketgroup This group is mandatory only for those network interfaces which are packet-oriented and for which the value of the corresponding instance of ifspeed is greater than 650 million bits/second. ifrcvaddressgroup The applicability of this group must be defined by the media-specific MIBs. Media-specific MIBs must define the exact meaning, use, and semantics of the addresses in this group. iflinkupdowntrapenable Specifies the write access is not required for this object. Min-Access: read-only ifpromiscuousmode Specifies the write access is not required for this object. Min-Access: read-only ifstackstatus Integer {active(1)} (a subset of RowStatus) Specifies the write access is not required for this object. Only one of the six enumerated values for the RowStatus textual convention need to be supported, specifically; active(1). Min-Access: read-only 3-21

22 IF MIB Conformance and Compliance Statements Chapter 3 Table 3-13 IF MIB Conformance Group MIB Objects (continued) ifadminstatus Integer {up(1), down(2)} Specifies the write access is not required for this object. The value testing(3) is also not supported. Min-Access: read-only ifalias Specifies the write access is not required for this object. Min-Access: read-only ifgeneralinformationgroup iffixedlengthgroup {ifindex, ifdescr, iftype, ifspeed, ifphysaddress, ifadminstatus, ifoperstatus, iflastchange, iflinkupdowntrapenable, ifconnectorpresent, ifhighspeed, ifname, ifnumber, ifalias, iftablelastchange} {ifinoctets, ifoutoctets, ifinunknownprotos, ifinerrors, ifouterrors} Describes a collection of objects that provides information applicable to all network interfaces. Describes a collection of objects that provides information specific to non-high speed character-oriented or fixed-length-transmission network interfaces. Note Non-high speed interfaces are defined as those that transmit and receive at speeds less than or equal to 20 million bits/second. ifhcfixedlengthgroup {ifhcinoctets, ifhcoutoctets, ifinoctets, ifoutoctets, ifinunknownprotos, ifinerrors, ifouterrors } Describes collection of objects that provides information specific to high speed (greater than 20 million bits/second) that are either character-oriented or fixed-length-transmission network interfaces. ifpacketgroup {ifinoctets, ifoutoctets, ifinunknownprotos, ifinerrors, ifouterrors, ifmtu, ifinucastpkts, ifinmulticastpkts, ifinbroadcastpkts, ifindiscards, ifoutucastpkts, ifoutmulticastpkts, ifoutbroadcastpkts, ifoutdiscards, ifpromiscuousmode} Describes a collection of objects that provides information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20 millionbits/second) packet-oriented network interfaces. 3-22

23 Chapter 3 IF MIB Conformance and Compliance Statements Table 3-13 IF MIB Conformance Group MIB Objects (continued) ifhcpacketgroup {ifhcinoctets, ifhcoutoctets, ifinoctets, ifoutoctets, ifinunknownprotos, ifinerrors, ifouterrors, ifmtu, ifinucastpkts, ifinmulticastpkts, ifinbroadcastpkts, ifindiscards, ifoutucastpkts, ifoutmulticastpkts, ifoutbroadcastpkts, ifoutdiscards, ifpromiscuousmode} Describes a collection of objects that provides information specific to high speed (greater than 20 million bits/second but less than or equal to 650 million bits/second) packet-oriented network interfaces. ifvhcpacketgroup ifrcvaddressgroup ifstackgroup2 ifcounterdiscontinuitygroup {ifhcinucastpkts, ifhcinmulticastpkts, ifhcinbroadcastpkts, ifhcoutucastpkts, ifhcoutmulticastpkts, ifhcoutbroadcastpkts, ifhcinoctets, ifhcoutoctets, ifinoctets, ifoutoctets, ifinunknownprotos, ifinerrors, ifouterrors, ifmtu, ifinucastpkts, ifinmulticastpkts, ifinbroadcastpkts, ifindiscards, ifoutucastpkts, ifoutmulticastpkts, ifoutbroadcastpkts, ifoutdiscards, ifpromiscuousmode} {ifrcvaddressstatus, ifrcvaddresstype} {ifstackstatus, ifstacklastchange} {ifcounterdiscontinuity Time} Describes a collection of objects that provides information specific to higher speed (greater than 650 million bits/second) packet-oriented network interfaces. Describes a collection of objects that provides information on the multiple addresses that an interface receives. Describes a collection of objects that provides information on the layering of MIB-II interfaces. Describes a collection of objects that provides information specific to interface counter discontinuities. 3-23

24 IF MIB Conformance and Compliance Statements Chapter

MPLS Enhancements to the Interfaces MIB

MPLS Enhancements to the Interfaces MIB MPLS Enhancements to the Interfaces MIB This document describes the Multiprotocol Label Switching (MPLS) enhancements to the existing interfaces Management Information Base (MIB) (RFC 2233) to support

More information

AVB/AVBTP layering, management objects and data. Draft 0.01 Alan K. Bartky, Bartky Networks

AVB/AVBTP layering, management objects and data. Draft 0.01 Alan K. Bartky, Bartky Networks AVB/AVBTP layering, management objects and data transfer processing study Draft 0.01 Alan K. Bartky, Bartky Networks alan@bartky.net www.bartky.net May 11, 2007 Study for AVB & AVBTP groups 1 Notice of

More information

Using WhatsUp to Access the SNMP Management Information

Using WhatsUp to Access the SNMP Management Information Using WhatsUp to Access the SNMP Management Information Visit Ipswitch official website at http://www.whatsupgold.com/products/download/ to download WhatsUp and run the installation after downloaded. Step

More information

Network Working Group K. McCloghrie Request for Comments: 2863 Systems Obsoletes: 2233 F. Kastenholz Category: Standards Track Networks June 2000

Network Working Group K. McCloghrie Request for Comments: 2863 Systems Obsoletes: 2233 F. Kastenholz Category: Standards Track Networks June 2000 Network Working Group K. McCloghrie Request for Comments: 2863 Cisco Systems Obsoletes: 2233 F. Kastenholz Category: Standards Track Argon Networks June Status of this Memo The Interfaces Group MIB This

More information

November Copyright (C) The Internet Society (1997). All Rights Reserved.

November Copyright (C) The Internet Society (1997). All Rights Reserved. Network Working Group Request for Comments: 2233 Obsoletes: 1573 Category: Standards Track K. McCloghrie Cisco Systems F. Kastenholz FTP Software November 1997 The Interfaces Group MIB using SMIv2 Status

More information

Network Working Group. Category: Standards Track October Definitions of Managed Objects for IEEE Interfaces

Network Working Group. Category: Standards Track October Definitions of Managed Objects for IEEE Interfaces Network Working Group J. Flick Request for Comments: 2020 Hewlett Packard Category: Standards Track October 1996 Definitions of Managed Objects for IEEE 802.12 Interfaces Status of this Memo This document

More information

Category: Standards Track March 1994

Category: Standards Track March 1994 Network Working Group T. Brown, Editor Request for Comments: 1596 Bell Communications Research Category: Standards Track March 1994 Status of this Memo Definitions of Managed Objects for Frame Relay Service

More information

Technical Committee. LAN Emulation Client Management Specification. Version 1.0

Technical Committee. LAN Emulation Client Management Specification. Version 1.0 Technical Committee LAN Emulation Client Management Specification Version 1.0 af-lane-0038.000 September 1995 1 Copyright 1995 The ATM Forum. All Rights Reserved. No part of this publication may be reproduced

More information

Internet Engineering Task Force (IETF) Obsoletes: 7223 March 2018 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Obsoletes: 7223 March 2018 Category: Standards Track ISSN: Internet Engineering Task Force (IETF) M. Bjorklund Request for Comments: 8343 Tail-f Systems Obsoletes: 7223 March 2018 Category: Standards Track ISSN: 2070-1721 Abstract A YANG Data Model for Interface

More information

Network Working Group Request for Comments: J. Lang Sonos, Inc. E. McGinnis Hammerhead Systems January 2006

Network Working Group Request for Comments: J. Lang Sonos, Inc. E. McGinnis Hammerhead Systems January 2006 Network Working Group Request for Comments: 4327 Category: Standards Track M. Dubuc T. Nadeau Cisco Systems J. Lang Sonos, Inc. E. McGinnis Hammerhead Systems January 2006 Link Management Protocol (LMP)

More information

Network Working Group Request for Comments: 4220 Category: Standards Track Cisco Systems J. Lang Sonos, Inc. November 2005

Network Working Group Request for Comments: 4220 Category: Standards Track Cisco Systems J. Lang Sonos, Inc. November 2005 Network Working Group Request for Comments: 4220 Category: Standards Track M. Dubuc Consultant T. Nadeau Cisco Systems J. Lang Sonos, Inc. November 2005 Status of This Memo Traffic Engineering Link Management

More information

SNMP Support on NFVIS

SNMP Support on NFVIS Introduction about SNMP, page 1 SNMP Operations, page 1 SNMP Versions, page 3 SNMP MIB Support, page 4 Configuring SNMP Support, page 6 Introduction about SNMP Simple Network Management Protocol (SNMP)

More information

Network Working Group. August 1999

Network Working Group. August 1999 Network Working Group Request for Comments: 2665 Obsoletes: 2358 Category: Standards Track J. Flick Hewlett-Packard Company J. Johnson RedBack Networks August 1999 Status of this Memo Definitions of Managed

More information

Category: Proposed Standard August Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces

Category: Proposed Standard August Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces Network Working Group M. St. Johns, Ed. Request for Comments: 2670 @Home Network Category: Proposed Standard August 1999 Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant

More information

January Evolution of the Interfaces Group of MIB-II. Status of this Memo

January Evolution of the Interfaces Group of MIB-II. Status of this Memo Network Working Group Request for Comments: 1573 Obsoletes: 1229 Category: Standards Track K. McCloghrie Hughes LAN Systems F. Kastenholz FTP Software January 1994 Status of this Memo Evolution of the

More information

NetScaler SNMP OID Reference

NetScaler SNMP OID Reference NetScaler SNMP OID Reference Jan 10, 2017 A detailed list of the SNMP OIDs that can be used to obtain information from a NetScaler appliance. Generic MIB-II OIDs system snmp interfaces iftable ifmibobjects

More information

HyperText Transfer Protocol. HTTP Commands. HTTP Responses

HyperText Transfer Protocol. HTTP Commands. HTTP Responses Hyper Transfer Protocol HTTP - just a different file transfer protocol Simplified, standard client/server model just one connection for commands and data Data transferred is structured Similar to MIME

More information

Configuring SNMP. Information about SNMP CHAPTER

Configuring SNMP. Information about SNMP CHAPTER CHAPTER 74 This chapter describes how to configure SNMP to monitor the adaptive security appliance and includes the following sections: Information about SNMP, page 74-1 Licensing Requirements for SNMP,

More information

Internet Engineering Task Force (IETF) Y. Zhang, Ed. Fortinet, Inc. May 2010

Internet Engineering Task Force (IETF) Y. Zhang, Ed. Fortinet, Inc. May 2010 Internet Engineering Task Force (IETF) Request for Comments: 5833 Category: Informational ISSN: 2070-1721 Y. Shi, Ed. Hangzhou H3C Tech. Co., Ltd. D. Perkins, Ed. C. Elliott, Ed. Y. Zhang, Ed. Fortinet,

More information

INTERNET NETWORK MANAGEMENT STANDARDS AIKO PRAS UNIVERSITY OF TWENTE THE NETHERLANDS

INTERNET NETWORK MANAGEMENT STANDARDS AIKO PRAS UNIVERSITY OF TWENTE THE NETHERLANDS INTERNET NETWORK MANAGEMENT STANDARDS COURSE PRESENTED AT THE SBRC 97 SÃO CARLOS, BRASIL 19-22 MAY 1997 AIKO PRAS UNIVERSITY OF TWENTE THE NETHERLANDS pras@cs.utwente.nl http://wwwtios.cs.utwente.nl/~pras

More information

Request for Comments: Accton Technology Corporation February Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)

Request for Comments: Accton Technology Corporation February Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP) Network Working Group Request for Comments: 4404 Category: Standards Track R. Natarajan F5 Networks A. Rijhsinghani Accton Technology Corporation February 2006 Definitions of Managed Objects for Fibre

More information

Cisco Systems, Inc 24 February Fibre Channel Management MIB. draft-ietf-ips-fcmgmt-mib-04.txt. Status of this Memo

Cisco Systems, Inc 24 February Fibre Channel Management MIB. draft-ietf-ips-fcmgmt-mib-04.txt. Status of this Memo Internet Draft Keith McCloghrie Cisco Systems, Inc 24 February 2003 Fibre Channel Management MIB draft-ietf-ips-fcmgmt-mib-04.txt Status of this Memo This document is an Internet-Draft and is subject to

More information

Cisco Systems, Inc 10 October Fibre Channel Management MIB. draft-ietf-ips-fcmgmt-mib-03.txt. Status of this Memo

Cisco Systems, Inc 10 October Fibre Channel Management MIB. draft-ietf-ips-fcmgmt-mib-03.txt. Status of this Memo Internet Draft Keith McCloghrie Cisco Systems, Inc 10 October 2002 Fibre Channel Management MIB draft-ietf-ips-fcmgmt-mib-03.txt Status of this Memo This document is an Internet-Draft and is in full conformance

More information

GLOSSARY CHAPTER. Command-Line Interface

GLOSSARY CHAPTER. Command-Line Interface GLOSSARY CHAPTER B Bandwidth The difference between the highest and lowest frequencies available for network signals. The term is also used to describe the rated throughput capacity of a given network

More information

Force10 Networks, Inc. T. Nadeau Cisco Systems, Inc. June 2004

Force10 Networks, Inc. T. Nadeau Cisco Systems, Inc. June 2004 Network Working Group Request for Comments: 3812 Category: Standards Track C. Srinivasan Bloomberg L.P. A. Viswanathan Force10 Networks, Inc. T. Nadeau Cisco Systems, Inc. June 2004 Multiprotocol Label

More information

ITU-T Recommendation Q

ITU-T Recommendation Q - 1 - ITU-T Recommendation Q.3304.2 Resource control protocol no. 4 SNMP Profile Protocol at the Rc interface between a Transport Resource Control Physical Entity (TRC-PE) and a Transport Physical Entity

More information

Internet Engineering Task Force (IETF) Y. Zhang, Ed. Fortinet, Inc. May 2010

Internet Engineering Task Force (IETF) Y. Zhang, Ed. Fortinet, Inc. May 2010 Internet Engineering Task Force (IETF) Request for Comments: 5834 Category: Informational ISSN: 2070-1721 Y. Shi, Ed. Hangzhou H3C Tech. Co., Ltd. D. Perkins, Ed. C. Elliott, Ed. Y. Zhang, Ed. Fortinet,

More information

Brief Introduction to the Internet Standard Management Framework

Brief Introduction to the Internet Standard Management Framework Part 2: Structure of Management Information Version 2 (SMIv2) The SMI is the Data Definition Language, based loosely on an old version of ASN.1 and used to model and define management information to be

More information

Network Working Group. Category: Standards Track Black Storm Networks R. Wheeler DoubleWide Software August 2002

Network Working Group. Category: Standards Track Black Storm Networks R. Wheeler DoubleWide Software August 2002 Network Working Group Request for Comments: 3371 Category: Standards Track E. Caves Occam Networks P. Calhoun Black Storm Networks R. Wheeler DoubleWide Software August 2002 Layer Two Tunneling Protocol

More information

ehealth Integration for Lucent Application Brief

ehealth Integration for Lucent Application Brief ehealth Integration for Lucent Application Brief May 1, 2002 Version 7 Prepared By: 3 rd Party Integration Team Copyright 2001 Concord Communications, Inc. 600 Nickerson Rd. Marlborough, MA 01752 All Rights

More information

Cisco Enterprise MIB Objects

Cisco Enterprise MIB Objects CHAPTER 3 This chapter describes the common MIB objects used for Cisco enterprise that are used for AXSM, AXSME, PXM1E, PXM45, SRM, SRM-E, FRSM12, RPM-XF, and RPM-PRR. Contents of this chapter include:

More information

Network Working Group Request for Comments: K. Rehbehn Megisto Systems, Inc. December 2000

Network Working Group Request for Comments: K. Rehbehn Megisto Systems, Inc. December 2000 Network Working Group Request for Comments: 3020 Category: Standards Track P. Pate B. Lynch Overture Networks K. Rehbehn Megisto Systems, Inc. December 2000 Status of this Memo Definitions of Managed Objects

More information

Critical Application MIBs

Critical Application MIBs CHAPTER 5 This chapter provides a set of objects used for managing critical application processes. Critical application MIBs are represented by a string containing the full path to the binary as well as

More information

SNMP. Agenda. Network Management Basics SNMP. RMON SNMPv2 Product Examples L64 - SNMP. Simple Network Management Protocol. Basics SMI MIB.

SNMP. Agenda. Network Management Basics SNMP. RMON SNMPv2 Product Examples L64 - SNMP. Simple Network Management Protocol. Basics SMI MIB. SNMP Simple Network Management Protocol Agenda Network Management Basics SNMP Basics SMI MIB RMON SNMPv2 Product Examples SNMP, v4.0 2 Page 64-1 What is it? A network management should... automate the

More information

SNMP Server Commands

SNMP Server Commands SNMP Server Commands This chapter describes the Cisco IOS XR software commands used to configure and monitor the Simple Network Management Protocol (SNMP) for network monitoring and management. For detailed

More information

Monitor Device and Network Health and Performance

Monitor Device and Network Health and Performance Monitor Device and Network Health and Performance This chapter contains the following topics: How Device Health and Performance Is Monitored: Monitoring Policies, on page 1 Set Up Basic Device Health Monitoring,

More information

Periodic MIB Data Collection and Transfer Mechanism

Periodic MIB Data Collection and Transfer Mechanism Periodic MIB Data Collection and Transfer Mechanism The Periodic MIB Data Collection and Transfer Mechanism feature provides the ability to periodically transfer selected MIB data from Cisco IOS XE-based

More information

Network Working Group. Obsoletes: R. Abbi Alcatel USA December 2005

Network Working Group. Obsoletes: R. Abbi Alcatel USA December 2005 Network Working Group Request for Comments: 4319 Obsoletes: 3276 Category: Standards Track C. Sikes Zhone Technologies, Inc. B. Ray PESA Switching Systems, Inc. R. Abbi Alcatel USA December 2005 Definitions

More information

A. Kessler Cisco Systems December 2007

A. Kessler Cisco Systems December 2007 Network Working Group Request for Comments: 5132 Obsoletes: 2932 Category: Standards Track D. McWalter Data Connection Ltd D. Thaler Microsoft Corporation A. Kessler Cisco Systems December 2007 IP Multicast

More information

SNMP Server Commands

SNMP Server Commands SNMP Server Commands This chapter describes the Cisco IOS XR software commands used to configure and monitor the Simple Network Management Protocol (SNMP) for network monitoring and management. For detailed

More information

-- extracted from rfc2515.txt -- at Mon Nov 15 17:11: ATM-MIB DEFINITIONS ::= BEGIN

-- extracted from rfc2515.txt -- at Mon Nov 15 17:11: ATM-MIB DEFINITIONS ::= BEGIN -- extracted from rfc2515.txt -- at Mon Nov 15 17:11:39 1999 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, -TYPE, Counter32, Integer32, IpAddress, mib-2 FROM SNMPv2-SMI DisplayString, RowStatus, TruthValue

More information

Network Working Group Request for Comments: 2320 Category: Standards Track Bay Networks, Inc. K. White IBM Corp. T. Kuo Bay Networks, Inc.

Network Working Group Request for Comments: 2320 Category: Standards Track Bay Networks, Inc. K. White IBM Corp. T. Kuo Bay Networks, Inc. Network Working Group Request for Comments: 2320 Category: Standards Track M. Greene Xedia Corp. J. Luciani Bay Networks, Inc. K. White IBM Corp. T. Kuo Bay Networks, Inc. April 1998 Status of this Memo

More information

Request for Comments: Category: Standards Track December 1994

Request for Comments: Category: Standards Track December 1994 Network Working Group K. McCloghrie Request for Comments: 1748 E. Decker Obsoletes: 1743, 1231 cisco Systems, Inc. Category: Standards Track December 1994 Status of this Memo IEEE 802.5 MIB using SMIv2

More information

This chapter provides information to configure sflow.

This chapter provides information to configure sflow. sflow In This Chapter This chapter provides information to configure sflow. Topics in this chapter include: sflow Overview on page 530 sflow Features on page 531 sflow Counter Polling Architecture on page

More information

GLOSSARY. Cisco Assigned Numbers Authority. The central clearing house for allocation of unique names and numbers that are embedded in Cisco software.

GLOSSARY. Cisco Assigned Numbers Authority. The central clearing house for allocation of unique names and numbers that are embedded in Cisco software. GLOSSARY B Bandwidth Broadcast storm The difference between the highest and lowest frequencies available for network signals. The term is also used to describe the rated throughput capacity of a given

More information

ATM Interface Configuration Parameters Table. ATM Interface Configuration Parameters Table Object Identifiers

ATM Interface Configuration Parameters Table. ATM Interface Configuration Parameters Table Object Identifiers CHAPTER 3 This chapter describes the individual Management Information Base (MIB) objects that comprise the ATM MIB file. The ATM MIB resides in the ATM-MIB.my file. Contents of this chapter include: ATM

More information

CHAPTER. Introduction

CHAPTER. Introduction CHAPTER 1 Network management takes place between two major types of systems: those in control, called managing systems, and those observed and controlled, called managed systems. The most common managing

More information

CISCO ENTITY FRU CONTROL MIB File

CISCO ENTITY FRU CONTROL MIB File CHAPTER 4 This chapter describes the individual MIB objects that comprise the PXM45-specific MIB files. The CISCO ENTITY Field Replaceable Unit (FRU) Control MIB resides in the ENTITY-MIB.my file. The

More information

Configuring Performance Monitoring, RMON, OTN, and Port Provisioning

Configuring Performance Monitoring, RMON, OTN, and Port Provisioning Configuring Performance Monitoring, RMON, OTN, and Port Provisioning This chapter describes performance monitoring, RMON, and OTN, port provisioning and the configuration procedures. Understanding Performance

More information

Information for the Internet. Jurgen Schonwalder and Frank Strau. Technical University Braunschweig. Bultenweg 74/75, Braunschweig, Germany,

Information for the Internet. Jurgen Schonwalder and Frank Strau. Technical University Braunschweig. Bultenweg 74/75, Braunschweig, Germany, Next Generation Structure of Management Information for the Internet Jurgen Schonwalder and Frank Strau Technical University Braunschweig Bultenweg 74/75, 38106 Braunschweig, Germany, fschoenw straussg@ibr.cs.tu-bs.de

More information

WIPIPE-MIB DEFINITIONS ::= BEGIN. -- WiPipe MIB Release Copyright by CradlePoint, Inc. All rights reserved

WIPIPE-MIB DEFINITIONS ::= BEGIN. -- WiPipe MIB Release Copyright by CradlePoint, Inc. All rights reserved WIPIPE-MIB DEFINITIONS ::= BEGIN -- WiPipe MIB Release 1.4 -- Copyright 2008-2011 by CradlePoint, Inc. All rights reserved -- This Specification is supplied "AS IS", CradlePoint makes no warranty, -- either

More information

GLOSSARY. Authentication, authorization, and accounting. The word alarm represents a condition that causes a trap to be generated.

GLOSSARY. Authentication, authorization, and accounting. The word alarm represents a condition that causes a trap to be generated. GLOSSARY A AAA Alarm Alarm Severity ATM ATM-AAL5 Authentication, authorization, and accounting. The word alarm represents a condition that causes a trap to be generated. Each alarm type defined by a vendor

More information

Request for Comments: 4837 Category: Standards Track July Managed Objects of Ethernet Passive Optical Networks (EPON)

Request for Comments: 4837 Category: Standards Track July Managed Objects of Ethernet Passive Optical Networks (EPON) Network Working Group L. Khermosh Request for Comments: 4837 PMC-SIERRA Category: Standards Track July 2007 Managed Objects of Ethernet Passive Optical Networks (EPON) Status of This Memo This document

More information

For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to

For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. Contents at a Glance About the Author...

More information

Network Working Group. Category: Standards Track June 2007

Network Working Group. Category: Standards Track June 2007 Network Working Group M. Squire Request for Comments: 4878 Hatteras Networks Category: Standards Track June 2007 Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions

More information

January AppleTalk Management Information Base II. Status of this Memo

January AppleTalk Management Information Base II. Status of this Memo Network Working Group Request for Comments: 1742 Obsoletes: 1243 Category: Standards Track S. Waldbusser Carnegie Mellon University K. Frisa FORE Systems, Inc. January 1995 Status of this Memo AppleTalk

More information

MPLS Embedded Management and MIBs Configuration Guide, Cisco IOS XE Everest 16.5

MPLS Embedded Management and MIBs Configuration Guide, Cisco IOS XE Everest 16.5 MPLS Embedded Management and MIBs Configuration Guide, Cisco IOS XE Everest 16.5 First Published: 2012-11-05 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA

More information

Table of Contents 1. DUT and Test Equipments...2

Table of Contents 1. DUT and Test Equipments...2 Table of Contents 1. DUT and Test Equipments...2 1.1 DUT Specification...2 2. Functionality test...4 2.1 Management Interface Evaluation...4 2.2 Firmware Upgrade and Configuration Files Update Test...8

More information

May Management Information Base for Network Management of TCP/IP-based internets: MIB-II

May Management Information Base for Network Management of TCP/IP-based internets: MIB-II Network Working Group Request for Comments: 1158 M. Rose, Editor Performance Systems International May 1990 Management Information Base for Network Management of TCP/IP-based internets: MIB-II 1. Status

More information

action (event) through rising (test threshold)

action (event) through rising (test threshold) action (event) through rising (test threshold) action (event), page 3 add (bulk statistics object), page 5 bandwidth (interface configuration), page 7 buffer-size (bulk statistics), page 10 comparison,

More information

SNMPv2 Object Descriptions

SNMPv2 Object Descriptions CHAPTER 7 This chapter describes the individual MIB objects that comprise SNMPv2. The objects reside in the SNMPv2-MIB.my file. Contents of this chapter include: System Group Object Resource Information

More information

Configuring Interfaces and Circuits

Configuring Interfaces and Circuits CHAPTER 5 This chapter describes how to configure the CSS interfaces and circuits and how to bridge interfaces to Virtual LANs (VLANs). Information in this chapter applies to all CSS models, except where

More information

Request for Comments: October 1996

Request for Comments: October 1996 Network Working Group Request for Comments: 2037 Category: Standards Track K. McCloghrie A. Bierman Cisco Systems October 1996 Entity MIB using SMIv2 Status of this Memo This document specifies an Internet

More information

SNMP Configuration Guide, Cisco IOS Release 12.4T

SNMP Configuration Guide, Cisco IOS Release 12.4T SNMP Configuration Guide, Cisco IOS Release 12.4T Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)

More information

Network Working Group. Category: Standards Track. ArrowPoint Communications A. Sastry. Cisco Systems. September 1997

Network Working Group. Category: Standards Track. ArrowPoint Communications A. Sastry. Cisco Systems. September 1997 Network Working Group Request for Comments: 2213 Category: Standards Track F. Baker Cisco Systems J. Krawczyk ArrowPoint Communications A. Sastry Cisco Systems September 1997 Integrated Services Management

More information

Performance Monitoring

Performance Monitoring 12 CHAPTER Performance Monitoring Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional

More information

Network Service Module Hardware Reference

Network Service Module Hardware Reference Network Service Module Hardware Reference AT-AR040 AT-AR041 AT-AR042 AT-AR048 Network Service Module Hardware Reference AT-AR040 AT-AR041 AT-AR042 AT-AR048 Download the complete document set from www.alliedtelesis.com/support/software

More information

Industriefunkuhren. Technical Manual. LAN Board. Model 7270 ENGLISH. Version:

Industriefunkuhren. Technical Manual. LAN Board. Model 7270 ENGLISH. Version: Industriefunkuhren Technical Manual LAN Board Model 7270 ENGLISH Version: 07.00-08.03.2007 Valid for Devices 7270 with FIRMWARE Version: 07.xx and REMOTE-SOFTWARE Version: 00.00 2 / 42 7270 LAN Board -

More information

Network Working Group. Category: Standards Track Dorado Software A. Huynh Cetus Networks September 2003

Network Working Group. Category: Standards Track Dorado Software A. Huynh Cetus Networks September 2003 Network Working Group Request for Comments: 3591 Category: Standards Track H-K. Lam Lucent Technologies M. Stewart Dorado Software A. Huynh Cetus Networks September 2003 Definitions of Managed Objects

More information

Category: Standards Track March Dial Control Management Information Base using SMIv2

Category: Standards Track March Dial Control Management Information Base using SMIv2 Network Working Group G. Roeck, Editor Request for Comments: 2128 cisco Systems Category: Standards Track March 1997 Status of this Memo Dial Control Management Information Base using SMIv2 This document

More information

SNMP. User s Guide. for 12000/4000 BLCs and Micro DSLAMs. Document No. SNMP-A2-GB April 2005

SNMP. User s Guide. for 12000/4000 BLCs and Micro DSLAMs. Document No. SNMP-A2-GB April 2005 SNMP for 12000/4000 BLCs and Micro DSLAMs User s Guide Document No. SNMP-A2-GB20-00 April 2005 Copyright 2005 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected

More information

Category: Standards Track U. Bonollo NEC Australia September 2009

Category: Standards Track U. Bonollo NEC Australia September 2009 Network Working Group Request for Comments: 5650 Category: Standards Track M. Morgenstern ECI Telecom Ltd. S. Baillie U. Bonollo NEC Australia September 2009 Definitions of Managed Objects for Very High

More information

A Brief Introduction to Internet Network Management. Geoff Huston

A Brief Introduction to Internet Network Management. Geoff Huston A Brief Introduction to Internet Network Management Geoff Huston gih@telstra.net What are we talking about? Network Management Tasks fault management configuration management performance management security

More information

Procket Networks D. Thaler Microsoft October 2000

Procket Networks D. Thaler Microsoft October 2000 Network Working Group Request for Comments: 2932 Category: Standards Track K. McCloghrie cisco Systems D. Farinacci Procket Networks D. Thaler Microsoft October 2000 IPv4 Multicast Routing MIB Status of

More information

Concept SAN Health Status Monitor

Concept SAN Health Status Monitor System and Network Engineering Research Project 2 Concept SAN Health Status Monitor By: Yanick de Jong - yanick.dejong@os3.nl Adriaan van der Zee - adriaan.vanderzee@os3.nl Supervisor (KLM IS): L.H.M.

More information

Pica8 private MIB. March, Version: 2.

Pica8 private MIB. March, Version: 2. March, 2015 Version: 2 www.pica8.com Pica8, Inc. 1032 Elwell Court, Suite 105 Palo Alto, CA. 94303 +1 (650) 614-5838 sales@pica8.com support@pica8.com Copyright 2015 Pica8 Inc. Pica8 is a registered trademark

More information

Monitoring Policies Reference

Monitoring Policies Reference The following topics describe the monitoring policies used by Cisco EPN Manager. For information on the supported MIBs and MIB objects, see Cisco Evolved Programmable Network Manager Supported Devices.

More information

Network Management (NETW-1001)

Network Management (NETW-1001) Network Management (NETW-1001) Dr. Mohamed Abdelwahab Saleh IET-Networks, GUC Spring 2017 TOC 1 SNMPv1 Messages 2 SNMP messages Two main purposes: Monitoring and configuration. SNMP version 1 defines five

More information

Appendix A Remote Network Monitoring

Appendix A Remote Network Monitoring Appendix A Remote Network Monitoring This appendix describes the remote monitoring features available on HP products: Viewing System Information You can access software and hardware specifics for an HP

More information

-- extracted from rfc1213.txt -- at Mon Nov 15 17:12: RFC1213-MIB DEFINITIONS ::= BEGIN

-- extracted from rfc1213.txt -- at Mon Nov 15 17:12: RFC1213-MIB DEFINITIONS ::= BEGIN -- extracted from rfc1213.txt -- at Mon Nov 15 17:12:00 1999 DEFINITIONS ::= BEGIN IMPORTS mgmt, NetworkAddress, IpAddress, Counter, Gauge, TimeTicks FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212; -- This

More information

BGP/MPLS Layer 3 VPN Multicast Management Information Base

BGP/MPLS Layer 3 VPN Multicast Management Information Base Internet Engineering Task Force (IETF) H. Tsunoda Request for Comments: 8503 Tohoku Institute of Technology Category: Standards Track December 2018 ISSN: 2070-1721 Abstract BGP/MPLS Layer 3 VPN Multicast

More information

Request for Comments: S. Baillie U. Bonollo NEC Australia November 2006

Request for Comments: S. Baillie U. Bonollo NEC Australia November 2006 Network Working Group Request for Comments: 4706 Category: Standards Track M. Morgenstern M. Dodge ECI Telecom Ltd. S. Baillie U. Bonollo NEC Australia November 2006 Status of This Memo Definitions of

More information

May The Internet-standard Network Management Framework consists of three components. They are:

May The Internet-standard Network Management Framework consists of three components. They are: Network Working Group Request for Comments: 1229 K. McCloghrie, Editor Hughes LAN Systems, Inc. May 1991 Status of this Memo Extensions to the Generic-Interface MIB This RFC contains definitions of managed

More information

Configuring Data Collection Manager

Configuring Data Collection Manager This module describes the configuring of the Data Collection Manager feature. Table 1: Feature History for Release Release 5.2.2 Modification This feature was introduced Data Collection Manager, on page

More information

Category: Standards Track August 2005

Category: Standards Track August 2005 Network Working Group A. Bierman Request for Comments: 4133 K. McCloghrie Obsoletes: 2737 Cisco Systems, Inc. Category: Standards Track August 2005 Status of This Memo Entity MIB (Version 3) This document

More information

Author: Bill Buchanan. Wireless LAN. Unit 3: Wireless Infrastructure

Author: Bill Buchanan. Wireless LAN. Unit 3: Wireless Infrastructure Wireless LAN Unit 3: Wireless Infrastructure Areas covered: Wireless Infrastructures. Basic details on bridging and topologies. Wireless Data Logging and Device Discovery. Details on protocols such as

More information

Using MIBs. Managing Router Physical Entities APPENDIXA

Using MIBs. Managing Router Physical Entities APPENDIXA APPENDIXA This chapter describes how to perform tasks on the Cisco 7200 Router. Managing Router Physical Entities, page A-1 Mapping Information for ENTITY-MIB, page A-2 Generating SNMP Traps, page A-10

More information

MPLS EM MPLS LSR MIB - RFC 3813

MPLS EM MPLS LSR MIB - RFC 3813 MPLS EM MPLS LSR MIB - RFC 3813 First Published: February 19, 2007 Last Updated: February 19, 2007 The MPLS LSR MIB- RFC 3813 (MPLS-LSR-STD-MIB) allows you to use the Simple Network Management Protocol

More information

Metrodata LM1100 User Manual Version 3.9x

Metrodata LM1100 User Manual Version 3.9x LM1100 User Manual www.metrodata.co.uk Metrodata LM1100 User Manual Version 3.9x Metrodata Ltd Fortune House Crabtree Office Village Eversley Way Egham Surrey TW20 8RY United Kingdom tel: +44 (0) 1784

More information

Network Working Group Request for Comments: 4131 Category: Standards Track Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005

Network Working Group Request for Comments: 4131 Category: Standards Track Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005 Network Working Group Request for Comments: 4131 Category: Standards Track S. Green Consultant K. Ozawa Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005 Management Information Base for Data

More information

Intended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt>

Intended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt> NETLMM Working Group INTERNET-DRAFT Intended Status: Proposed Standard Expires: February 19, 2011 Glenn M. Keeni Cyber Solutions Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota ITC

More information

Category: Standards Track July 2002

Category: Standards Track July 2002 Network Working Group A. Bierman Request for Comments: 3287 Cisco Systems, Inc. Category: Standards Track July 2002 Status of this Memo Remote Monitoring MIB Extensions for Differentiated Services This

More information

RMON Configuration Guide, Cisco IOS Release 12.4

RMON Configuration Guide, Cisco IOS Release 12.4 RMON Configuration Guide, Cisco IOS Release 12.4 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax:

More information

Internet Engineering Task Force (IETF) Category: Standards Track

Internet Engineering Task Force (IETF) Category: Standards Track Internet Engineering Task Force (IETF) Request for Comments: 7666 Category: Standards Track ISSN: 2070-1721 H. Asai Univ. of Tokyo M. MacFaden VMware Inc. J. Schoenwaelder Jacobs University K. Shima IIJ

More information

Cisco Nexus 7000 Series NX-OS MIB Quick Reference

Cisco Nexus 7000 Series NX-OS MIB Quick Reference Cisco Nexus 7000 Series NX-OS MIB Quick Reference Date: August, 2013 This document describes the private, or local, Management Information Base (MIB) files for the Cisco NX-OS software. This document provides

More information

RFC1213-MIB DEFINITIONS ::= BEGIN. IMPORTS internet, mgmt FROM RFC1155-SMI; Type definitions -- DisplayString ::= OCTET STRING

RFC1213-MIB DEFINITIONS ::= BEGIN. IMPORTS internet, mgmt FROM RFC1155-SMI; Type definitions -- DisplayString ::= OCTET STRING -- -- RFC1213-MIB.html -- MIB generated by MG-SOFT MIB Explorer Version 1.1 Build 153 -- Wednesday, November 13, 2002 at 12:22:23 -- HTML index: -- RMON2-MIB, RFC1155-SMI, RFC1213-MIB, RMON-MIB, SNMPv2-TC,

More information

Network Working Group. F. Baker Advanced Computer Communications C. Carvalho Advanced Computer Communications April 1992

Network Working Group. F. Baker Advanced Computer Communications C. Carvalho Advanced Computer Communications April 1992 Network Working Group Request for Comments: 1315 C. Brown Wellfleet Communications, Inc. F. Baker Advanced Computer Communications C. Carvalho Advanced Computer Communications April 1992 Status of this

More information

Network Working Group. Category: Standards Track Hewlett-Packard T. McSweeney IBM J. Muchow Qlogic Corp. May 2006

Network Working Group. Category: Standards Track Hewlett-Packard T. McSweeney IBM J. Muchow Qlogic Corp. May 2006 Network Working Group Request for Comments: 4544 Category: Standards Track M. Bakke Cisco Systems M. Krueger Hewlett-Packard T. McSweeney IBM J. Muchow Qlogic Corp. May 2006 Status of This Memo Definitions

More information

Internet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012

Internet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012 Internet Engineering Task Force (IETF) Request for Comments: 6475 Category: Standards Track ISSN: 2070-1721 G. Keeni Cyber Solutions, Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota

More information

Configuring RMON. Understanding RMON CHAPTER

Configuring RMON. Understanding RMON CHAPTER 22 CHAPTER This chapter describes how to configure Remote Network Monitoring (RMON) on your switch. RMON is a standard monitoring specification that defines a set of statistics and functions that can be

More information