MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 168 (ipMcastMIB). 1 (ipMcast). 5 (ipMcastRouteTable). 1 (ipMcastRouteEntry). 22 (ipMcastRouteDifferentInIfOctets)
OID : 1.3.6.1.2.1.168.1.5.1.22
TXT : iso. org. dod. internet. mgmt. mib-2. ipMcastMIB. ipMcast. ipMcastRouteTable. ipMcastRouteEntry. ipMcastRouteDifferentInIfOctets
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.168.1.5.1.22
Module IPMCAST-MIB (ietf)
NomipMcastRouteDifferentInIfOctets
Accesreadonly
Statuscurrent
DescriptionThe number of octets contained in IP datagrams that this router has received from these sources and addressed to this multicast group address, which were dropped because they were received on an unexpected interface. For RPF checking protocols (such as PIM-SM), these packets arrived on interfaces other than ipMcastRouteInIfIndex, and were dropped because of this failed RPF check. (RPF paths are 'Reverse Path Forwarding' paths; the unicast routes to the expected origin of multicast data flows). Other protocols may drop packets on an incoming interface check for different reasons (for example, BIDIR-PIM performs a DF check on receipt of packets). All packets dropped as a result of an incoming interface check are counted here. If this counter increases rapidly, this indicates a problem. A significant quantity of multicast data is arriving at this router on unexpected interfaces, and is not being forwarded. For guidance, if the rate of increase of this counter exceeds 1% of the rate of increase of ipMcastRouteOctets, then there are multicast routing problems that require investigation. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
SyntaxeCounter64 (SNMPv2-SMI)
Module IPMCAST-MIB (Alcatel)
NomipMcastRouteDifferentInIfOctets
Accesreadonly
Statuscurrent
DescriptionThe number of octets contained in IP datagrams that this router has received from these sources and addressed to this multicast group address, which were dropped because they were received on an unexpected interface. For RPF checking protocols (such as PIM-SM), these packets arrived on interfaces other than ipMcastRouteInIfIndex, and were dropped because of this failed RPF check. (RPF paths are 'Reverse Path Forwarding' paths; the unicast routes to the expected origin of multicast data flows). Other protocols may drop packets on an incoming interface check for different reasons (for example, BIDIR-PIM performs a DF check on receipt of packets). All packets dropped as a result of an incoming interface check are counted here. If this counter increases rapidly, this indicates a problem. A significant quantity of multicast data is arriving at this router on unexpected interfaces, and is not being forwarded. For guidance, if the rate of increase of this counter exceeds 1% of the rate of increase of ipMcastRouteOctets, then there are multicast routing problems that require investigation. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
SyntaxeCounter64 (SNMPv2-SMI)