ipMcastBoundaryTable

1.3.6.1.2.1.168.1.7.1.1

ipMcastBoundaryIfIndex

INTEGER

not-accessible

The IfIndex value for the interface to which this boundary

applies. Packets with a destination address in the

associated address/mask range will not be forwarded over

this interface.

For IPv4, zone boundaries cut through links. Therefore,

this is an external interface. This may be either a

physical or virtual interface (tunnel, encapsulation, and

so forth.)

For IPv6, zone boundaries cut through nodes. Therefore,

this is a virtual interface within the node. This is not

an external interface, either real or virtual. Packets

crossing this interface neither arrive at nor leave the

node, but only move between zones within the node.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.2

ipMcastBoundaryAddressType

INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)}

not-accessible

A value indicating the address family of the address

contained in ipMcastBoundaryAddress. Legal values

correspond to the subset of address families for which

multicast forwarding is supported.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.3

ipMcastBoundaryAddress

OCTET STRING{(0,255)}

not-accessible

The group address which, when combined with the

corresponding value of ipMcastBoundaryAddressPrefixLength,

identifies the group range for which the scoped boundary

exists. Scoped IPv4 multicast address ranges must be

prefixed by 239.0.0.0/8. Scoped IPv6 multicast address

ranges are FF0x::/16, where x is a valid RFC 4291 multicast

scope.

An IPv6 address prefixed by FF1x::/16 is a non-permanently-

assigned address. An IPv6 address prefixed by FF3x::/16 is

a unicast-prefix-based multicast addresses. A zone boundary

for FF0x::/16 implies an identical boundary for these other

prefixes. No separate FF1x::/16 or FF3x::/16 entries exist

in this table.

This address object is only significant up to

ipMcastBoundaryAddressPrefixLength bits. The remaining

address bits are set to zero. This is especially important

for this index field, which is part of the index of this

entry. Any non-zero bits would signify an entirely

different entry.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.4

ipMcastBoundaryAddressPrefixLength

Unsigned32{(0,2040)}

not-accessible

The length in bits of the mask which when, combined with

the corresponding value of ipMcastBoundaryAddress,

identifies the group range for which the scoped boundary

exists.

The InetAddressType is given by ipMcastBoundaryAddressType.

For values 'ipv4' and 'ipv4z', this object must be in the

range 4..32. For values 'ipv6' and 'ipv6z', this object

must be set to 16.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.5

ipMcastBoundaryTimeStamp

TimeTicks

read-only

The value of sysUpTime at which the multicast boundary

information represented by this entry was learned by the

router.

If this information was present at the most recent re-

initialization of the local management subsystem, then this

object contains a zero value.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.6

ipMcastBoundaryDroppedMcastOctets

Counter64

read-only

The number of octets of multicast packets that have been

dropped as a result of this zone boundary configuration.

Discontinuities in this monotonically increasing value

occur at re-initialization of the management system.

Discontinuities can also occur as a result of boundary

configuration being removed and replaced, which can be

detected by observing the value of

ipMcastBoundaryTimeStamp.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.7

ipMcastBoundaryDroppedMcastPkts

Counter64

read-only

The number of multicast packets that have been dropped as a

result of this zone boundary configuration.

Discontinuities in this monotonically increasing value

occur at re-initialization of the management system.

Discontinuities can also occur as a result of boundary

configuration being removed and replaced, which can be

detected by observing the value of

ipMcastBoundaryTimeStamp.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.8

ipMcastBoundaryStatus

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

read-create

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) without setting

any other columnar objects in this entry.

All writeable objects in this entry can be modified when the

status of this entry is active(1).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.168.1.7.1.9

ipMcastBoundaryStorageType

INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)}

read-create

The storage type for this row. Rows having the value

'permanent' need not allow write-access to any columnar

objects in the row.

This object is implemented as defined in the corresponding MIB files.