[mpls-linux-general] regarding traffic engg...

[<fr...@hs...>]

Hi James,
              first of all let me take the opportunity to appreciate the efforts
 put in implementing
              mpls.

     Actually we want to simulate the traffic Engineering by setting up
   two LSP's between same HOST and DESTINATION. We want to do with transport
   layer port.

     For same DESTINATION , based on Tranport Layer port, we are trying
   to set up two LSP's.

    Actually here the problem is , for same fec, whichever binding info
   is given last is remaining in the
     rt->u.dst.dst_proto_data[AUX_PROTO_DATA_MPLS] =
     res->proto_data[AUX_PROTO_DATA_MPLS];
     /* from route.c file : function :rt_set_nexthop    */
     I think due to this limitation, it is getting the recently configured
   NHLFE info , for same FEC's.

mplsadm -v -A -B -O gen:20:eth1:ipv4:192.168.210.1 -f 192.168.206.12/32
mplsadm -v -A -B -O gen:21:ppp0:ipv4:192.168.210.1 -f 192.168.206.12/32

    In the above case , for FEC 192.168.206.12 , it is always going through
 ppp0 interface.

    I have a doubt that information about "eth1" for 192.168.206.12/32 might
  be overlapping with "ppp0". as i noticed so many times , it is always going
  through  "ppp0".

    If i do it in reverse order , it is doing vice versa.
    You are using platform based labelspace, for that can't we bind the same FEC
  to two different interfaces?

    can't we have  more than one NHLFE for same FEC ?
Please guide in this regard.

   Thanks in advance......

Best Regards,
Faisal Rehman.


********************************************************************************
"This message is proprietary to Hughes Software Systmes Limited (HSS) and/or its
customers and intended solely for the use of the individual or organisation to
whom it is addressed. It may contain  privileged or confidential information.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transimitted by this email including
damage from virus."
********************************************************************************