November 2013 AOS Release 6.4.6.R01 Release Notes
Multicast Features
PIM Startup Delay
In certain networks, when PIM becomes active before the unicast applications like OSPF and BGP,
multicast packet loss may be observed until the unicast routing information is updated. To overcome such
packet loss due to startup latency between the PIM and unicast routing applications, a user-define startup
delay has been introduced in PIM.
This feature enhancement provides the ability to configure the startup delay for PIM neighborship, so that
the PIM neighborship will be formed after the delay value configured . This delay is applicable only when
the switch boots up. A CLI option is added to configure the PIM startup delay, with an appropriate value, 0
being the default. If a startup delay is configured then PIM will not become globally enabled until after the
delay period. This will ensure that none of the PIM interfaces become enabled until after the configured
startup delay.
-> ip pim startup-delay <seconds>
The delay can be configured in the range of 0 to 120. The default value for delay is 0.
Initial Multicast Packet Routing
Multicast is often used for audio\video streaming applications where the first packet may be dropped as it is
used for learning the new flow. However, some multicast applications require the initial packets sent by the
multicast source to be received. The packet buffering functionality can be enabled to prevent those first
multicast packets from being dropped.
Following debug CLIs can be used to modify the default values for packet buffering.
• debug ip set ipedrMaxPacketsPerSgv – to modify the number of packets that can be buffered for a
particular flow. Default value is 4 packets.
• debug ip set ipedrMaxSgv – to modify the number of SGVs that can be buffered. Default value is
16 SGVs.
• debug ip set ipedrMaxBufTimeout - to modify the time up to which buffered packet can be in
IPMS NI. Default value is 10 seconds.
Contact Service and Support before implementing the debug capability on an OmniSwitch.
Multicast Address Boundaries
Multicast boundaries confine multicast addresses to a particular domain. Confining multicast addresses
helps to ensure that multicast data traffic passed within a multicast domain does not conflict with multicast
users outside the domain.
Multicast addresses 239.0.0.0 through 239.255.255.255 have been reserved by the IANA as
administratively scoped addresses for use in private multicast domains. These addresses cannot be used for
any other protocol or network function. Because they are regulated by the IANA, these addresses can
theoretically be used by network administrators without conflicting with networks outside of their multicast
domains. However, to ensure that the addresses used in a private multicast domain do not conflict with
other domains (for example, within the company network or out on the Internet), multicast address
boundaries can be configured.
AOS supports configuration of multicast route boundaries for the entire multicast group including scoped
multicast addresses (224.0.0.0 through 239.255.255.255).
Page 14 of 80 OmniSwitch 6850E/6855/9000E—Release 6.4.6.R01
To Next Page
Loading...
