Reset Search
 

 

Article

Traffic going from global table to a VRF using MPLS is not forwarded by the MLX correctly

« Go Back

Information

 
TitleTraffic going from global table to a VRF using MPLS is not forwarded by the MLX correctly
Symptoms
  • Unable to connect to addresses outside of the VRF if they originate in the global table of the PE, when traffic originates from connected CE
  • Issue seen when traffic is leaked from default VRF to custom VRF, and then transmitted to the CE via MPLS
  • Captured ingress packets on the CE will not show a MPLS header but a VLAN header
  • Checking CAM and PRAM programming on egress LP of the MLX will show N/A under IFL/VLAN and missing RSVP label
LP-1#sh cam ip 1/1 10.30.0.1/24
LP Index    IP Address         MAC            Age IFL/ Out IF PRAM
   (Hex)                                          VLAN        (Hex)
1  035484(R) 10.30.0.0/24       N/A            Dis N/A  2/11   00020
 
LP-1#dm pram me/1 0x00020 mpls
LABEL OPERATION       0          0=swap_label 1=PHP 2=rsrv 3=NoAction
Insert RSVP label     0          Insert RSVP label into the frame
RSVP Label            0          RSVP label for LDP over RSVP frames>

 
Environment
  • MLX
  • NetIron 5.7 and above (tested)
  • MPLS
Cause
IP PRAM of the egress card is not programmed with the MPLS header
Resolution
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255