OID | 1.3.6.1.2.1.168.1.4.1.2 |
Module | IPMCAST-MIB (ietf) |
Nom | ipMcastSsmRangeAddress |
Acces | noaccess |
Status | current |
Description | The multicast group address which, when combined with
ipMcastSsmRangePrefixLength, gives the group prefix for this
SSM range. The InetAddressType is given by
ipMcastSsmRangeAddressType.
This address object is only significant up to
ipMcastSsmRangePrefixLength 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.
For IPv6 SSM address ranges, only ranges prefixed by
FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291
multicast address scope. The syntax of the address range is
given by RFC 3306, Sections 4 and 7.
For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this
SSM range entry applies only within the given zone. Zone
index zero is not valid in this table.
If non-global scope SSM range entries are present, then
consistent ipMcastBoundaryTable entries are required on
routers at the zone boundary. |
Syntaxe | InetAddress (INET-ADDRESS-MIB) |
Module | IPMCAST-MIB (Alcatel) |
Nom | ipMcastSsmRangeAddress |
Acces | noaccess |
Status | current |
Description | The multicast group address which, when combined with
ipMcastSsmRangePrefixLength, gives the group prefix for this
SSM range. The InetAddressType is given by
ipMcastSsmRangeAddressType.
This address object is only significant up to
ipMcastSsmRangePrefixLength 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.
For IPv6 SSM address ranges, only ranges prefixed by
FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291
multicast address scope. The syntax of the address range is
given by RFC 3306, Sections 4 and 7.
For addresses of type ipv4z or ipv6z, the appended zone
index is significant even though it lies beyond the prefix
length. The use of these address types indicate that this
SSM range entry applies only within the given zone. Zone
index zero is not valid in this table.
If non-global scope SSM range entries are present, then
consistent ipMcastBoundaryTable entries are required on
routers at the zone boundary. |
Syntaxe | InetAddress (INET-ADDRESS-MIB) |