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).

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;
             }
         }
     }
}

• 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.

This is expected behavior and working as designed. The workaround is to enable no-cspf for the LSP or inter-domain under protocols MPLS.