An entry (conceptual row) describing one of this device's
multicast scope zone boundaries.
OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit.
Parsed from file IPMCAST-MIB.mib
Module: IPMCAST-MIB
ipMcastBoundaryEntry OBJECT-TYPE
SYNTAX IpMcastBoundaryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) describing one of this device\s
multicast scope zone boundaries.
OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit."
REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5"
INDEX { ipMcastBoundaryIfIndex,
ipMcastBoundaryAddressType,
ipMcastBoundaryAddress,
ipMcastBoundaryAddressPrefixLength }
View at oid-info.com
An entry (conceptual row) describing one of this device's
multicast scope zone boundaries.
OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit.
Parsed from file rfc5132-IP-Multicast-IP-MCAST.mib.txt
Company: None
Module: IPMCAST-MIB
An entry (conceptual row) describing one of this device's
multicast scope zone boundaries.
OIDs are limited to 128 sub-identifiers, but this limit
is not enforced by the syntax of this entry. In practice,
this does not present a problem, because IP address types
allowed by conformance statements do not exceed this limit.
ipMcastBoundaryEntry OBJECT-TYPE SYNTAX IpMcastBoundaryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) describing one of this device's multicast scope zone boundaries. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit." REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5" INDEX { ipMcastBoundaryIfIndex, ipMcastBoundaryAddressType, ipMcastBoundaryAddress, ipMcastBoundaryAddressPrefixLength } ::= { ipMcastBoundaryTable 1 }
Automatically extracted from RFC5132
ipMcastBoundaryEntry OBJECT-TYPE SYNTAX IpMcastBoundaryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) describing one of this device's multicast scope zone boundaries. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit." REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5" INDEX { ipMcastBoundaryIfIndex, ipMcastBoundaryAddressType, ipMcastBoundaryAddress, ipMcastBoundaryAddressPrefixLength } ::= { ipMcastBoundaryTable 1 }
ipMcastBoundaryEntry OBJECT-TYPE SYNTAX IpMcastBoundaryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) describing one of this device's multicast scope zone boundaries. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit." REFERENCE "RFC 2365 Section 5, RFC 4007 Section 5" INDEX { ipMcastBoundaryIfIndex, ipMcastBoundaryAddressType, ipMcastBoundaryAddress, ipMcastBoundaryAddressPrefixLength } ::= { ipMcastBoundaryTable 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.168.1.7.1.1 | ipMcastBoundaryIfIndex | 0 | 0 | The IfIndex value for the interface to which this boundary applies. Packets with a destination address in the associated address… |
| 1.3.6.1.2.1.168.1.7.1.2 | ipMcastBoundaryAddressType | 0 | 0 | A value indicating the address family of the address contained in ipMcastBoundaryAddress. Legal values correspond to the subset … |
| 1.3.6.1.2.1.168.1.7.1.3 | ipMcastBoundaryAddress | 0 | 0 | The group address which, when combined with the corresponding value of ipMcastBoundaryAddressPrefixLength, identifies the group r… |
| 1.3.6.1.2.1.168.1.7.1.4 | ipMcastBoundaryAddressPrefixLength | 0 | 0 | The length in bits of the mask which when, combined with the corresponding value of ipMcastBoundaryAddress, identifies the group … |
| 1.3.6.1.2.1.168.1.7.1.5 | ipMcastBoundaryTimeStamp | 0 | 0 | The value of sysUpTime at which the multicast boundary information represented by this entry was learned by the router. If this in… |
| 1.3.6.1.2.1.168.1.7.1.6 | ipMcastBoundaryDroppedMcastOctets | 0 | 0 | The number of octets of multicast packets that have been dropped as a result of this zone boundary configuration. Discontinuities… |
| 1.3.6.1.2.1.168.1.7.1.7 | ipMcastBoundaryDroppedMcastPkts | 0 | 0 | The number of multicast packets that have been dropped as a result of this zone boundary configuration. Discontinuities in this m… |
| 1.3.6.1.2.1.168.1.7.1.8 | ipMcastBoundaryStatus | 0 | 0 | The status of this row, by which rows in this table can be created and destroyed. This status object can be set to active(1) with… |
| 1.3.6.1.2.1.168.1.7.1.9 | ipMcastBoundaryStorageType | 0 | 0 | The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row. |