Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[M/T/MX/PTX]The Secondary IP address that is configured on the loopback interface is not advertised in the Traffic Engineering Database (TED)

0

0

Article ID: KB24612 KB Last Updated: 29 Mar 2013Version: 3.0
Summary:
This article describes the issue of the secondary IP, which is configured on the loopback interface, not being advertised in the Traffic Engineering Database (TED).

Symptoms:
When the LSP, which is configured on the primary loopback address, goes down, the LSP configured on the secondary loopback address does not come up. This causes an outage in the network.
interfaces {
     lo0 {
         unit 0 {
             family inet {
                 address 3.3.3.3/32;
                 address 1.1.1.1/32;
             }
         }
     }
}
Cause:
  • The secondary loopback address is not advertised in the TED database.

  • If CSPF is enabled, the ingress router will consult the TED, in which the secondary loopback address is not advertised; so LSP will not come up.
Solution:
This is expected behavior and working as designed. The workaround is to enable no-cspf for the LSP or inter-domain under protocols MPLS.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search