Routing

I'm trying to setup and l2circuit between Juniper PE routers mapped to an LSP to force the traffic via a specific path. The LSPs are up however I'm getting a CF status on the one PE and OL status on the other PE. Checking the ldp database I can see that in the one direction I have a lable produced but not in the other direction.

I enabled traceoptions for the l2circuit and see the VC is being torn down 

Can anyone shed light on what this is or on where I can find documentation pertaining to deciphering the traceoptions?

Thanks

Hi,

The status "CF" is usually associated with bandwidth constraint configured under l2circuit.

This state is shown up when the required bandwidth configured under l2circuit connection is not available in LSP bandwidth.

i would suggest you to check if the bandwidth as provisioned in l2circuit is available in the LSP. I have provided a sample ouput for the same as below:

Please note, even if you don't configure bandwidth parameter in LSP, then l2circuit would show up as "CF".

For more details please visit

http://www.juniper.net/techpubs/en_US/junos10.4/topics/usage-guidelines/vpns-configuring-bandwidth-allocation-and-call-admission-control-in-layer-2-circuits.html

Hope this helps

If you like this, Kudos would be appreciated.

Regards

Surya Prakash

suryak@r1# run show l2circuit connections                              
Layer-2 Circuit Connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NP -- interface h/w not present   
MM -- mtu mismatch               Dn -- down                       
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down    
CM -- control-word mismatch      Up -- operational                
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          IB -- TDM incompatible bitrate
NC -- intf encaps not CCC/TCC    TM -- TDM misconfiguration
BK -- Backup Connection          ST -- Standby Connection
CB -- rcvd cell-bundle size bad  SP -- Static Pseudowire
LD -- local site signaled down   RS -- remote site standby
RD -- remote site signaled down  XX -- unknown

Legend for interface status  
Up -- operational            
Dn -- down                   
Neighbor: 8.8.8.8
    Interface                 Type  St     Time last up          # Up trans
    ge-2/1/0.0(vc 10)         rmt   CF     Apr  5 02:09:38 2011           1 << Status is CF
      Remote PE: 8.8.8.8, Negotiated control-word: Yes (Null)
      Incoming label: 301888, Outgoing label: 301792
      Negotiated PW status TLV: No
      Local interface: ge-2/1/0.0, Status: Up, Encapsulation: ETHERNET
      VC bandwidth: 100bps                                                <<<< BW is 100bps




suryak@r1# run show mpls lsp detail                                    
Ingress LSP: 1 sessions

8.8.8.8
  From: 2.2.2.2, State: Up, ActiveRoute: 0, LSPname: lsp2
  ActivePath:  (primary)
  LSPtype: Static Configured
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary                    State: Up
    Priorities: 7 0
    Bandwidth: 10bps                              <<<< LSP BW is only 10bps
    SmartOptimizeTimer: 180
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 3)
 10.8.2.2 S 10.8.3.2 S 20.8.3.2 S
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          10.8.2.2 10.8.3.2 20.8.3.2
Total 1 displayed, Up 1, Down 0
           


After changing the LSP bandwidth to 150bps

[edit]
suryak@r1# run show mpls lsp detail                                     
Ingress LSP: 1 sessions

8.8.8.8
  From: 2.2.2.2, State: Up, ActiveRoute: 0, LSPname: lsp2
  ActivePath:  (primary)
  LSPtype: Static Configured
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary                    State: Up
    Priorities: 7 0
    Bandwidth: 150bps                                           <<<< LSP BW is only 150bps    
    SmartOptimizeTimer: 180
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 3)
 10.8.2.2 S 10.8.3.2 S 20.8.3.2 S
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
          10.8.2.2 10.8.3.2 20.8.3.2
Total 1 displayed, Up 1, Down 0



[edit]
suryak@r1# run show l2circuit connections                               
Layer-2 Circuit Connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NP -- interface h/w not present   
MM -- mtu mismatch               Dn -- down                       
EM -- encapsulation mismatch     VC-Dn -- Virtual circuit Down    
CM -- control-word mismatch      Up -- operational                
VM -- vlan id mismatch           CF -- Call admission control failure
OL -- no outgoing label          IB -- TDM incompatible bitrate
NC -- intf encaps not CCC/TCC    TM -- TDM misconfiguration
BK -- Backup Connection          ST -- Standby Connection
CB -- rcvd cell-bundle size bad  SP -- Static Pseudowire
LD -- local site signaled down   RS -- remote site standby
RD -- remote site signaled down  XX -- unknown

Legend for interface status  
Up -- operational            
Dn -- down                   
Neighbor: 8.8.8.8
    Interface                 Type  St     Time last up          # Up trans
    ge-2/1/0.0(vc 10)         rmt   Up     Apr  5 02:16:23 2011    2      <<< Status is Up.
      Remote PE: 8.8.8.8, Negotiated control-word: Yes (Null)
      Incoming label: 301888, Outgoing label: 301792
      Negotiated PW status TLV: No
      Local interface: ge-2/1/0.0, Status: Up, Encapsulation: ETHERNET
      VC bandwidth: 100bps

My LSPs are showing the configured bandwidth for the l2circuit of 155Mbps. The problem I'm seeing is I'm getting no label generated back from the one side. This is the traceoption output from the PE that isn't generating the label.

Apr  5 10:19:45.355406 New policy call for L2CKT from l2ckt.0

Apr  5 10:19:45.355418 [add] l2circuit VC l2ckt_vc_adv_recv (cw-bit 1, encaps ETHERNET, vc-id 1,label 301056, mtu 1540, cb-size 0, no vlan-id, TDM payload size 0 bytes,  TDM bitrate 0 (xDS0)) received from PE 10.0.0.201

Apr  5 10:19:45.355424 [l2ckt_vc_adv_recv] Adv received for active pw from neighbor 10.0.0.201

Apr  5 10:19:45.355432 [l2ckt_vc_adv_recv] Intf ge-3/0/3.0 (VC-ID 1) updated from signalled info: label 301056, encaps ETHERNET, cw-bit 1, mtu 1540, cb-size 0,  TDM payload size 0 (bytes), TDM bitrate 0 (xDS0) no vlan-id

Apr  5 10:19:45.355436 New policy processing complete for L2CKT from l2ckt.0

Apr  5 10:19:45.355442 rt_flash_update_callback: flash l2 circuit (l2circuit.0) done

Apr  5 10:19:45.356316 Route flash received from mpls.0 : New policy

Apr  5 10:19:45.356323        Triggering VC status update timer for intf ge-3/0/3.0

Apr  5 10:19:45.467148 [vc_intf_vc_status_update] Recomputing the status of the VC for interface : ge-3/0/3.0

Apr  5 10:19:45.467186 vc_intf_vc_status_update] interface : ge-3/0/3.0 vc status = intf Up : intf_up = TRUE

Apr  5 10:19:45.467207 [vc_intf_vc_status_update] interface : ge-3/0/3.0 UP adv_down = 0 : vc_down = 0, ccc_up = 1

Apr  5 10:19:45.467212 vc_intf_vc_status_update] interface : ge-3/0/3.0 VC PRESENT

Apr  5 10:19:45.467217  setting vc_down --- why:Apr  5 10:19:45.467221  rt_head_active != vcri_rt

Apr  5 10:19:45.467226 [vc_intf_vc_status_update] interface : ge-3/0/3.0 Done Computing adv, vc down and ccc_up status adv_down = 1, vc_down = 1, ccc_up = 0

Hi,

Can you please share your configs and toplogy?

Regards

Surya Prakash

Hi,

was this ever resolved? Appearently it´s showing up again: https://puck.nether.net/pipermail/juniper-nsp/2013-July/026884.html Any suggestions / observations would be helpful here and for j-nsp ...

Best Regards

Ulf

Hello there,

Jul 24 12:33:40.354196       setting vc_down --- why:
Jul 24 12:33:40.354219       rt_head_active != vcri_rt

This happens when remote/tailend router-id is not reachable via inet.3 table.

Specifically, when tailend router-id is artifically set to an address not present in tthe tailend router at all, or if that address is not covered by IGP and/or LDP and/or RSVP.

For proper L2 circuit functionality (and L3VPN, and L2VPN, and VPLS functionality too) the LER router-id must be same as primary IPv4 address on lo0.0 interface, and lo0.0 must be present in IGP and LDP.

If using RSVP, the lo0.0 primary address must be used to establish the LSPs to.

HTH

Thanks

Alex