Scribd Logo
Upload

Welcome to Scribd!

  • 66 views

    Nokia IP Alert

    Uploaded by

    Kazi Ziaul Hoque
    1) Some Alcatel-Lucent routers were not forwarding all multicast traffic out certain interfaces due to an issue when interfaces were rapidly deleted. 2) This could occur when using CLI commands to quickly shut down and remove an interface, or through service de-provisioning via a management system. 3) The recommended workaround was to clear PIM/IGMP state on affected interfaces before shutting/re-enabling the interfaces.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Nokia IP Alert

    Uploaded by

    Kazi Ziaul Hoque
    66 views2 pages
    1) Some Alcatel-Lucent routers were not forwarding all multicast traffic out certain interfaces due to an issue when interfaces were rapidly deleted. 2) This could occur when using CLI commands to quickly shut down and remove an interface, or through service de-provisioning via a management system. 3) The recommended workaround was to clear PIM/IGMP state on affected interfaces before shutting/re-enabling the interfaces.

    Original Description:

    Nokia Alert

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    1) Some Alcatel-Lucent routers were not forwarding all multicast traffic out certain interfaces due to an issue when interfaces were rapidly deleted. 2) This could occur when using CLI commands to quickly shut down and remove an interface, or through service de-provisioning via a management system. 3) The recommended workaround was to clear PIM/IGMP state on affected interfaces before shutting/re-enabling the interfaces.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    66 views2 pages

    Nokia IP Alert

    Uploaded by

    Kazi Ziaul Hoque
    1) Some Alcatel-Lucent routers were not forwarding all multicast traffic out certain interfaces due to an issue when interfaces were rapidly deleted. 2) This could occur when using CLI commands to quickly shut down and remove an interface, or through service de-provisioning via a management system. 3) The recommended workaround was to clear PIM/IGMP state on affected interfaces before shutting/re-enabling the interfaces.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Alcatel−Lucent Alerts

    15−0576a Multicast traffic not being forwarded onto some outgoing interface(s)

    Type: Maintenance
    Urgency: Medium
    Publish Date: 11 Jun 2015
    Region: ALL
    Expiration: Not applicable
    Product category: Carrier Ethernet IP/MPLS & ATM Networks
    Product line: Multiservice Core Switching Products
    Product: 7710 SR (Service Router)
    Sub−product: ALL
    Version: 11.0, 12.0
    Product category: Carrier Ethernet IP/MPLS & ATM Networks
    Product line: Multiservice Core Switching Products
    Product: 7750 SR (Service Router)
    Sub−product: ALL
    Model: ALL
    Version: 11.0, 12.0, 13.0
    Product category: Carrier Ethernet IP/MPLS & ATM Networks
    Product line: Multiservice Core Switching Products
    Product: 7950 XRS (eXtensible Routing System)
    Model: ALL
    Version: 11.0, 12.0, 13.0

    Overview:
    In SR11.0R1 and onwards, shutting down and deleting an interface rapidly may cause some multicast groups not to be forwarded to other
    interfaces that are part of the PIM/IGMP Outgoing Interface lists (OIF lists) containing the deleted interface. The interface can be removed
    too quickly when using copy/paste with CLI commands to shutdown and remove the interface or through service de−provisioning from 5620
    SAM.

    Impact:
    When the issue is triggered some downstream PIM/IGMP neighbors may not receive requested multicast groups. The affected interface(s)
    is(are) still in the OIF list on the CPM, therefore CLI commands on the node with the issue to show OIFs don't identify the issue is occurring.
    When the issue occurs, upstream nodes and the node with the issue will indicate Multicast is being forwarded when looking at PIM or IGMP
    group. However, downstream nodes will indicate no packets are being forwarded.

    When using PIM, check if PIM is forwarding multicast traffic by using "show router pim group <group address> detail" on upstream and
    downstream nodes. The "Curr Fwding Rate" will identify if multicast is being forwarded.

    The below filter can be used to identify if multicast is actually being forwarded out a specific OIF.

    1. Configure an ip−filter to match suspected group(s):


    ip−filter 123 create
    default−action forward
    entry 10 create
    match

    15−0576a Alcatel−Lucent − Proprietary Page 1 of 2


    Alcatel−Lucent Alerts

    dst−ip <suspected group 1>


    exit
    action forward
    exit
    entry 20 create
    match
    dst−ip <suspected group 2>
    exit
    action forward
    exit
    entry 30 create
    match
    dst−ip <suspected group 3>
    exit
    action forward
    exit
    ...
    exit all

    2. Apply it as an egress filter on the suspected outgoing interface with an issue:

    configure service <service id> interface <interface name> sap <sap−id> egress filter ip 123
    or
    configure router interface <interface name> egress filter ip 123

    3. Check to see if each entry is matched in the IP filter


    show filter ip 123 counters

    Action To Be Taken:
    The recovery workaround is:
    1. clear affected IGMP/PIM group on the affected interfaces, or

    clear router <router> pim database interface <interface name> group <group address>
    or
    clear router <router> igmp database interface <interface name> group <group address>

    2. shut/no shut the affected services or interface

    Preventive Action:
    When deleting an interface used as a PIM/IGMP Outgoing Interface (OIF) from the configuration via CLI commands, introduce a 5 second or
    longer delay between shutting down the interface and performing a "no interface <interface name>". The "sleep 5" CLI command can be
    used to induce the delay.

    When de−provisioning an interface used as a PIM/IGMP Outgoing Interface (OIF) or Multicast service from 5620 SAM, first shut down the
    OIF interface or the service and wait for 5 seconds before deleting the OIF interface or service.

    Solution Availability:
    Target release TBD

    Contact:
    Alcatel−Lucent Technical Support
    Please contact the technical support team for your country. If you are unsure of who that is, you can locate the correct number by using our
    Technical Support phone numbers look−up tool, at
    https://support.alcatel−lucent.com/

    15−0576a Alcatel−Lucent − Proprietary Page 2 of 2

    You might also like