Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 927 / 974

8-123
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 8 Industry-Standard Management Information Base
IF-MIB
The value of ifIndex corresponding to the lower sub-layer of the relationship, i.e., the sub-layer
which runs 'below' the sub-layer identified by the corresponding instance of ifStackHigherLayer. If
there is no lower sub-layer, then this object has the value 0.
::= { ifStackEntry 2 }
ifStackStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
The status of the relationship between two sub-layers. Changing the value of this object from 'active'
to 'notInService' or 'destroy' will likely have consequences up and down the interface stack. Thus,
write access to this object is likely to be inappropriate for some types of interfaces, and many
implementations will choose not to support write-access for any type of interface.
::= { ifStackEntry 3 }
ifStackLastChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
The value of sysUpTime at the time of the last change of the (whole) interface stack. A change of
the interface stack is defined to be any creation, deletion, or change in value of any instance of
ifStackStatus. If the interface stack has been unchanged since the last re-initialization of the local
network management subsystem, then this object contains a zero value.
::= { ifMIBObjects 6 }
Generic Receive Address Table
This group of objects is mandatory for all types of interfaces which can receive packets/frames addressed
to more than one address. This table replaces the ifExtnsRcvAddr table. The main difference is that this
table makes use of the RowStatus textual convention, while ifExtnsRcvAddr did not.
ifRcvAddressTable OBJECT-TYPE
SYNTAX Sequence of IfRcvAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
This table contains an entry for each address (broadcast, multicast, or uni-cast) for which the system
will receive packets/frames on a particular interface, except as follows:
– For an interface operating in promiscuous mode, entries are only required for those addresses
for which the system would receive frames were it not operating in promiscuous mode.
–
For 802.5 functional addresses, only one entry is required, for the address which has the
functional address bit ANDed with the bit mask of all functional addresses for which the
interface will accept frames.