MPLS L3 Route - 7600

Hi,
we have a MPLS L3 between our branches, recently we are facing problem with branches connecivites.
our setup is 7609 router connected to CE 3900 branch router, we are using a Interface Vlan to route behind the CE subnets.
CE using sub interface with 802.1q to interconnect with right vlan on the PE. the issue is that we are able to ping the P2P ip between
PE-CE, while the subnets behind CE including physical CE inside IP is not pingable, some time if we initiate the ping from CE source traffic
from inside interface then, bidirectional communication ping is working for some time then it stop.
correct vrf route and redisirbution already one place, same setup is used for hundred of sites, only new sites getting this issue.
the more interesting thing, while we are unable to ping inside CE IP, some hosts/Servers IP are reachable and work fine.
we try to get any bug that might related to the same issue without any luck.
PE:  CISCO7609
IOS: c7600s72033-advipservicesk9-mz.122-33.SRE5.bin
any help will be appreicated.
Mohamed.

Hi Mohammed
Are you trying to ping from remote side ?
Can you provide interface configuration between CE & PE, and routing protocol configuration between CE & PE
If you have EBGP, have you configured ebgp next-hop-self ?
Did you try to traceroute from both side and see where it's blocking ?
Regards,
Sandip

Similar Messages

  • MPLS-TE on 7600?

    Does anyone have links to MPLS-TE 'tunnel mpls' support for 7600 series? Is the extent of MPLS support in the 7600 limited to MPLS VPN and EoMPLS?
    Thanks,
    Greg

    Mainly looking for the basics right now.
    interface Tunnel14
    ip unnumbered Loopback0
    tunnel destination 36.11.1.17
    tunnel mode mpls traffic-eng
    tunnel mpls traffic-eng autoroute announce
    tunnel mpls traffic-eng autoroute metric absolute 500
    tunnel mpls traffic-eng bandwidth 100
    tunnel mpls traffic-eng priority 2 3
    tunnel mpls traffic-eng affinity 400
    tunnel mpls traffic-eng path-option 1 explicit name 14a
    tunnel mpls traffic-eng path-option 2 explicit name 14b
    ip explicit-path name 14a
    next-address 14.14.14.14
    next-address 15.15.15.15
    ip explicit-path name 14b
    next-address 41.41.41.41
    next-address 51.51.51.51
    Also, I assume fast reroute is not available yet?
    Thanks,
    Greg

  • MPLS VRF Routes Leaking

    I am designing network to deploy MPLS L3 VPN services for 2000+ branch locations of 1 customer.
    Cisco 7600 series router is used as PE along with FWSM that points towards Global Routing Table (Internet Gateway).
    Customer is requiring the access for internet along with VPN services to all the 2000+ locations.
    What is the best solution to prefer that meets the requirements & also avoids the security loopholes ?

    you could do one of the following ways to implement Internet access for L3 MPLS VPN
    1. using a separate PE interface in global routing table: in this case the FWSM and an interface in the PE/PEs will require to be in the the global routing table to have the Internet access and then you can inject that route to the VRF/VRFs
    2. Internet access using route leaking between VRFs and the global route table: by using this method you will need to configure a static default route with a next hop as an Internet gateway in your case the FWSM, reachable through the global routing table, this VRF default route need to be injected/redistributed in  the PE-CE routing (MP-BGP) to provide the outbound Internet connectivity to your  VRFs.
    inbound traffic from Internet will require either NATed VRF or a static routes from the global routing table points to the VRF interface
    3. the other method is the used of shared service: with this method you need to put the Internet service FWSM in its own VRF then you can control the import and export between the Internet VRF and other VRFs through import/export of the VRFs route-target values
    good luck
    if helpful Rate

  • MPLS BGP routes push to DMVPN spokes

    I have an MPLS with BGP. I also have sites that are not connected directly to the MPLS, but have a s2s VPN to hub sites that are connected to the MPLS and that way they access the MPLS resources. I need to communicate the route changes to the MPLS when the DMVPN fails-over to another hub.
    Currently this is my config:
    Datacenter (MPLS only)
    interface GigabitEthernet0/1
    description MPLS
    ip address 192.168.0.34 255.255.255.252
    interface Vlan2
    ip address 192.168.96.2 255.255.255.0
    router bgp 65511
    bgp log-neighbor-changes
    network 192.168.96.0
    neighbor 192.168.0.33 remote-as 65510
    Hub site 1 (MPLS + internet)
    interface Tunnel200
    ip address 10.99.99.1 255.255.255.0
    no ip redirects
    ip mtu 1400
    ip nhrp authentication auth
    ip nhrp map multicast dynamic
    ip nhrp network-id 12345
    ip nhrp holdtime 600
    tunnel source GigabitEthernet0/0
    tunnel mode gre multipoint
    tunnel key 200
    tunnel protection ipsec profile dmvpn
    interface GigabitEthernet0/1
    description MPLS
    ip address 192.168.1.2 255.255.255.0 secondary
    ip address 192.168.0.2 255.255.255.252
    router bgp 65001
    bgp log-neighbor-changes
    network 192.168.1.0
    network 192.168.21.0
    !10.99 clients are DMVPN spokes
    neighbor 10.99.99.3 remote-as 99010
    neighbor 10.99.99.3 route-reflector-client
    neighbor 10.99.99.21 remote-as 99001
    neighbor 10.99.99.21 route-reflector-client
    !as 65000 is the MPLS PE
    neighbor 192.168.0.1 remote-as 65000
    Hub Site 2, has the same configuration, except for local ip address and router BGP ID.
    Spoke site:
    interface Tunnel200
    ip address 10.99.99.3 255.255.255.0
    no ip redirects
    ip mtu 1400
    ip nhrp authentication auth
    ip nhrp map 10.99.99.1 PUBLIC_IP_HUB_1
    ip nhrp map 10.99.99.16 PUBLIC_IP_HUB_2
    ip nhrp network-id 12345
    ip nhrp holdtime 600
    ip nhrp nhs 10.99.99.1 priority 1
    ip nhrp nhs 10.99.99.16 priority 5
    ip nhrp nhs fallback 60
    tunnel source GigabitEthernet0/0
    tunnel mode gre multipoint
    tunnel key 200
    tunnel protection ipsec profile dmvpn
    interface GigabitEthernet0/1
    description Internal
    ip address 192.168.3.1 255.255.255.192
    router bgp 99010
    bgp log-neighbor-changes
    network 192.168.3.0
    neighbor 10.99.99.1 remote-as 65001
    neighbor 10.99.99.16 remote-as 65013
    On this spoke site 
    #sh ip route
    B 192.168.1.0/24 [20/0] via 10.99.99.1, 00:47:01
    which is the HUB network, but the rest of the MPLS routes are not "learned".
    What am I missing?
    Thanks!

    Hi Jon, I've ommited the configuration of the MPLS provider routers in between.  The DC is connected to a router that has the AS 65510.
    DC:CPE---PE:{MPLS}PE---CPE:HUB---{internet}---Spoke
    The DC is ok getting the network information via BGP:
    #sh ip route
    B 192.168.3.0/24 [20/0] via 192.168.0.33, 3d05h
    B 192.168.21.0/24 [20/0] via 192.168.0.33, 3d05h
    #sh ip bgp 192.168.21.0
    BGP routing table entry for 192.168.21.0/24, version 559
    Paths: (1 available, best #1, table default)
    Not advertised to any peer
    Refresh Epoch 1
    65510 3549 6140 3549 65000
    192.168.0.33 from 192.168.0.33 (###.###.###.###)
    Origin IGP, localpref 100, valid, external, best
    #sh ip route 192.168.21.0
    Routing entry for 192.168.21.0/24
    Known via "bgp 65511", distance 20, metric 0
    Tag 65510, type external
    Last update from 192.168.0.33 3d05h ago
    Routing Descriptor Blocks:
    * 192.168.0.33, from 192.168.0.33, 3d05h ago
    Route metric is 0, traffic share count is 1
    AS Hops 5
    Route tag 65510
    MPLS label: none
    Spoke:
    #sh ip bgp
    BGP table version is 494, local router ID is 192.168.21.1
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
    r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
    x best-external, a additional-path, c RIB-compressed,
    Origin codes: i - IGP, e - EGP, ? - incomplete
    RPKI validation codes: V valid, I invalid, N Not found
    Network Next Hop Metric LocPrf Weight Path
    *> 10.0.129.32/27 10.99.99.16 0 65013 65012 3549 ?
    *> 192.168.96.0 10.99.99.16 0 65013 65012 3549 6745 65510 ?
    #sh ip route 192.168.96.0
    Routing entry for 192.168.96.0/24
    Known via "bgp 99001", distance 20, metric 0
    Tag 65013, type external
    Last update from 10.99.99.16 00:02:11 ago
    Routing Descriptor Blocks:
    * 10.99.99.16, from 10.99.99.16, 00:02:11 ago
    Route metric is 0, traffic share count is 1
    AS Hops 5
    Route tag 65013
    MPLS label: none
    #sh ip bgp 192.168.96.0
    BGP routing table entry for 192.168.96.0/24, version 465
    Paths: (1 available, best #1, table default)
    Not advertised to any peer
    Refresh Epoch 2
    65013 65012 3549 6745 65510
    10.99.99.16 from 10.99.99.16 (10.2.16.1)
    Origin incomplete, localpref 100, valid, external, best
    The route is not being updated to the rest of the routers, and the 192.168.21.0 network is still announced via the old route.
    (from spoke)
    ping 192.168.96.2
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.96.2, timeout is 2 seconds:
    Success rate is 0 percent (0/5)
    From DC
    #traceroute 192.168.21.1
    Type escape sequence to abort.
    Tracing the route to 192.168.21.1
    VRF info: (vrf in name/id, vrf out name/id)
    1 192.168.0.33 [AS 65510] 0 msec 0 msec 0 msec
    2 172.50.1.33 [AS 65510] 56 msec 36 msec 36 msec
    3 10.80.1.1 [AS 3549] 44 msec 44 msec 44 msec
    4 10.80.1.2 [AS 3549] 172 msec 172 msec 168 msec
    5 172.50.1.1 [AS 3549] 168 msec 168 msec 172 msec
    6 172.50.1.2 [AS 3549] 180 msec 180 msec 176 msec
    7 192.168.0.2 [AS 65000] 172 msec 172 msec 168 msec <- old route, should be 192.168.0.9
    8 192.168.0.2 [AS 65000] !H * !H

  • MPLS PE/P 7600 or ASR 1000

    hi,
    We are planning to change our 7206VXR as P/PE routers.  Currently we only have 2 nodes that is running on STM-1.  on each node we have 7206VXR NPEG2 that is acting as PE and P router.
    our requirement is getting bigger we will be upgrading our WAN links to STM-4 soon (and to STM-12 in the future) and we will also be adding more nodes.
    I'm confused on what platform would be best for our network, 7600 or  ASR1000......7600???? 7606 or 7604?      ASR 1000???? ASR1004 or ASR 1006.
    I want my router to accomodate the growth in the network.
    I need your advise/expertise on this.
    Thanks in advance....
    Rachelle

    Hi,
    ASR1k runs IOS-XE, which is IOS. It does not run IOS-XR. ASR9k runs IOS-XR.
    The newer platforms, like ASR1k, ASR9k, have more throughput, while 7200 e.g. has a bigger
    range in different kinds of port adaptors. If you only plan to use ethernet interfaces for example, then
    you could only look at the newer platforms like ASR1k, ASR9k, or even 7600 and choose
    a specific model based on the number of ports you'd need.
    Thanks,
    Luc

  • Cell-mode MPLS / IP routing

    I am studying for CCIP and with my limited knowledge of ATM there is something a don't understand.
    When running cell-mode MPLS over an MPLS aware ATM network are the ATM switches acting as layer 3 routers. If so how.

    Hi,
    yes one converts ATM switches into routers, so to say. Data plane will still be ATM cell switching. But the control plane is modified and VC setup is controlled by IP routing and LDP.
    One can add the IP routing and LDP capability by adding software to IOS based ATM switches (like 8540) or by adding a real router as Label switch controller (f.e. 7200/RPM to BPX or MGX).
    Hope this helps
    Martin
    P.S.: please rate all posts.

  • MPLS vs ROUTING

    Guys first of all i am vvv new to this (MPLS) now guys i have read some few articles......plus some few chapters of few books on MPLS......the main theme of MPLS i sthat it is a lable technology send...froward packets on labels rather then plooking the ip address (tradional)........now guys what is th eplus point then.........i mean the only thing which i can see is that routers would not hold routing tables......so whats th emain theme of MPLS.......i mean i didnt get any main different....please help me clearing my concept....thanks alot for looking

    The routers would still hold the IGP routing table. MPLS isn't a routing protocol. There used to be some performance gains because the router did a lookup on the label (32 bits). However that really isn't the case anymore with lookups being done in hardware. If you're running BGP across your network, with MPLS implemented you can remove BGP from you core devices and just have it on the edge devices. The biggest thing with MPLS though is the other services you can offer on the network once MPLS is deployed. You can offer Layer 3 VPNs, Layer 2 VPNs (EoMPLS, VPLS..) and MPLS Traffic Engineering.

  • MPLS : IGP route aggregation and broken LSPs.

    If I do (IGP) route aggregation inside a MPLS domain it would break LSPs created between end-points, I mean ingress-egress points (PEs), that have the node deploying route aggregation is its path.
    Also, LSP creation is topology driven, not traffic driven; and LSPs are created
    among all possible ingress/egress points/options inside a MPLS Domain.
    However as far as I think I know, LSPs are always established between PEs´
    (Edge-LSRs) router-ids, and so the egress PE does Layer 3 forwarding (as result of penultimate hop popping) when routing toward a CE.
    01) Is that right ?
    If so I understand that, if I allocate a CIDR to a PE and all its customers' wans & lans prefixes (or if you prefer, all PE´s connected and static routes) are subnets of this CIDR; the PE IGP could
    advertise to other PEs only one route regarding the whole CIDR instead of all its subnets, without break any LSP that has this PE as one of its endpoints.
    02) Did I make myself clear ?
    03) Is that right ?
    Yours Truly.
    Murilo Pugliese.

    Say you are summarising on Router1 and Router 2 receives the summarized route and router 3 is the loopback you are trying to reach. Router 1 will generate a label for the Summarized route. When the packet comes to router 2 , it will do an IP lookup for router 3 as the label is for the summarised route and hence the LSP breaks.
    Iam sure someone will correct me if iam wrong

  • MPLS Customer router physical interface

    My provider wants to sell me MPLS services but I can't seem to get a straight answer regarding what the physical interface on my customer router needs to be.  Some personnel tell me it will be a normal ethernet connection, other say it'll be a DS3 or T1 connection depending on the speed.
    Please give me some advice on what to expect regarding an MPLS circuit?  Or point me to some good documentation to maybe I can communicate better with the service provider.
    Thank you.

    Hi Tod
    Few points from my side for your query
    Access Link should be considered based on whether we are going for MPLS L3 VPN or MPLS L2 VPN Soilution
    MPLS L3 VPN from my understanding is independent of Access Media but the Access Media will definitely put different hardware requirements for your Customer Edge Router
    The Access Link Type and Bandwidth would vary depending upon the BW requirements for the network. The T1/T3 or a Subrate T3 Access Links would be a choice when we have BW requirements in that range(<45 Megs)
    Using FE as an Acces link would require SP to provide Colocation Services or rather go for spanning a Fiber out from their Colo and deploying Optical Mux at Customer Premises and again suitable for BW requirements more than 45 Megs
    MPLS L2 VPN
    Ethernet is the choice for taking MPLS L2 VPN Services to connect your different branches in a point-to-multipoint fashion using VPLS at SP end.
    You can go through the Cisco Doc - "Layer 3 MPLS VPN Enterprise Consumer Guide" which should help you gain more insight for choosing the PE-CE Routing Protocol and other points to consider for an MPLS L3 VPN Service.
    Thats from my understanding. Hope you will get more good advises on this.
    Regards
    Vaibhava Varma

  • MPLS VPN routes with core IGP costs

    Hi,
    Is there any way to use the IGP cost between PEs, and pass that into the VRF prefixes?
    For example:
    A branch site has 2x CEs (CE-A & CE-B), each with a link to a different PE (PE-A & PE-B). EBGP is used between CE-PE. IBGP Between CE-A & CE-B. CE-C is also connected to PE-B with EBGP.
    Without any manual intervention, the link from CE-A to PE-A and the link from CE-B to PE-B would be equal cost away. In reality it would be preferable (in our case at least) for traffic destined to CE-C to use the CE-B to PE-B link, because it would result in a shorter path in the core.
    I have been looking for a way to use the IGP metric associated with the VRF route next hop. Ideally, I would like to have the option to copy the IGP cost to next hope into the VRF prefix's MED field... or if you're already using MED as a metric then perhaps the option to ADD the IGP cost to next hope to the existing MED value. I was hoping you would be able to do this with an Import Map on the VRF but I can't see a way of acheiving this.
    Is there another way to get this result?
    Thanks,
    Peter

    Hi Giuseppe
    Thanks very much for your response but I think perhaps I did not explain my question correctly...
    What I was trying to acheive was to influence the rouitng at the branch (CE level with the use of MED), rather than at the PE VRF as you have described with Local Preference.
    I would like the branch AS (consisting of CE-A & CE-B) to choose the link between CE-B - PE-B to get to CE-C's networks, because it is directly connected or has an IGP cost of 0.
    I'm aware I can do this on CE-B by identifying the prefixes from that AS and applying a route-map on CE-B, but I was hoping there was a solution that would be more automatic and less admin overhead by being able to copy the IGP cost into the BGP MED field, as this would then be sent to the CE-B. The prefix sent from PE-A to CE-A would have a higher IGP cost and so would send a higher MED. I hope what I'm trying to explain makes sense.
    If this is not possible (I can't find any reference to such a feature...) then are you aware of any other feature that would result in similar behaviour withou having to manually identify prefixes with route maps? The best I can come up with so far is to tag routes into each PE with a community and use a route-map outbound on PE to CE to add a higher MED value to prefixes that do not contain this same community... Or perhaps this can be done with the SOO attribute. The trouble with this method is it only works for PEs with directly connected CEs. It would be nice to leverage the information in the IGP routing table...
    Thanks,
    Peter

  • MPLS PE Route Availability

    Just learning, but from the enterprise perspective, after successfully creating the MPLS VPN from CE-PE-PE-CE is it possible for either CE device to access networks originating on the PE; other than the vrf forwarding interface?
    Thanks In Advance!

    If the configuration allows, only then the CE would be able to access PE networks.
    Regards.

  • Error Update IOS router 7600

    Hi Guys,
    I've trying updating a 7609 cisco router, my actual image that is working is "c7600s72033-advipservices-mz.122-33.SRB5" and I would like to update to "c7600s72033-adventerprisek9-mz.122-33.SRC2". I've followed all the steps to update but when I've reloaded the router happen the error below:
    System Bootstrap, Version 8.4(2) Release
    Copyright (c) 1994-2005 by cisco Systems, Inc.
    Cat6k-Sup720/SP processor with 524288 Kbytes of main memory
    Autoboot executing command: "boot disk0:c7600s72033-adventerprisek9-mz.122-33.SRC2.bin"
    Loading image, please wait ...
    open: file "c7200-atafslib-m" not found
    monlib.open(): Open Error = -1
    loadprog: error - on file open
    cannot load the monitor library "disk0:%c7200-atafslib-m" from device: PCMCIA Disk 0loadprog: error - on file open
    boot: cannot load "disk0:c7600s72033-adventerprisek9-mz.122-33.SRC2.bin"
    Exit at the end of BOOT string
    rommon 1 >
    The error in red I think that is the problem, How could I solve this problem?
    Thanks Guys

    open: file "c7200-atafslib-m" not found
    I think this is a monitor file.  Post the output to the command "dir disk0".  
    cannot load the monitor library "disk0:%c7200-atafslib-m" from device: PCMCIA Disk 0loadprog: error - on file open
    boot: cannot load "disk0:c7600s72033-adventerprisek9-mz.122-33.SRC2.bin"
    This error message is saying that the router cannot see the PCMCIA card or the PCMCIA card currently installed cannot be detected by the line card.
    You can't load the monitor library file because the boot variable string is incorrect.  Look at the highlighted (in RED) above.  The boot variable string found in the configuration has a space, the symbol "%", between the location (or "disk0:") and the filename.  

  • L3 mpls network with out P router, all PE to PE plus daisy chainging

    Guys, is it possible to run a core l3 MPLS network over 7600s and 3800s with out any P routers? The reason i aak is because of the particular situation where we will have to daisy chain PE routers due to lack of fiber.
    any thoughts?

    As martin says absolutley limited problems with this it will work a charm UNTIL yo urun into scaling issues. You are daisy chaining all the PEs which would also suggest to me that you are daisy chaining your RRs. In an mpls network the RR's have enough state to handle to keep them busy enough without also having to deal with passing labels about the network. Also you will have any cisco account team breaking down your door putting the fear of god into you for not having at least 2 P routers ;-). So yes you can indeed run it like you say but the lifetime of your network will be very limited indeed. If your not an SP then dont be concerned - unless you are an enterprise with 10000000s routes then id start to worry. Oh they (cisco) also state that PEs also have enough to do in their life without passing labelled packets about the place. sit and think about what your poor PE is having to do daily it could be 100 vrfs routing tables, which in turn means layer 3 lookups to find out where the packet has to go, qos, multicast, bgp, ospf, rip, eigrp, your own internal IGP, TE tunnels, RSVP - this poor router has enough to do without also adding transit traffic. ;-)

  • Trouble with advertise a route BGP from VRF on Cisco IOS 7600

    Hi
    the diagram especifie the actually operating network
    we try to advertise the network 172.16.161.6 to Nortel devices and Cisco devices on cisco AS 2005 and 64912, if we are staying look the routing table on cisco 7600 the network 172.16.161.6 is know it
    Success rate is 100 percent (5/5), round-trip min/avg/max = 20/24/28 ms
    cisco 7600#trace                            
    cisco 7600#traceroute vrf data 172.16.161.6
    Type escape sequence to abort.
    Tracing the route to 172.16.161.6
      1 189.1.11.5 [MPLS: Labels 581/730 Exp 0] 24 msec 24 msec 24 msec
      2 172.16.12.73 [MPLS: Label 730 Exp 0] 36 msec 28 msec 36 msec
      3 172.16.12.74 20 msec 20 msec 24 msec
      4 172.16.14.10 64 msec 20 msec 20 msec
      5 172.16.19.9 20 msec 24 msec 20 msec
      6 172.16.161.6 24 msec 20 msec 24 msec
    PE_CAR_1#ping vrf data 172.16.161.6     
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 172.16.161.6, timeout is 2 seconds:
    but the devices Nortel on AS 64912 on routing tables don´t know the networ 172.16.161.6
    the difference on cisco 7600 that know both AS 64912 and 2005 is this one:
    configuration on Cisco Router 7600
    router bgp 2006
    bgp router-id 172.16.110.97
    bgp log-neighbor-changes
    bgp graceful-restart restart-time 120
    bgp graceful-restart stalepath-time 360
    bgp graceful-restart
    neighbor 172.16.10.41 remote-as 64912
    neighbor 172.16.10.41 description PP-A6
    neighbor 172.16.11.233 remote-as 64912
    neighbor 172.16.11.233 description PP-2TE2
    neighbor 172.16.12.73 remote-as 2005
    neighbor 172.16.12.73 description PE_MEX_1
    neighbor 172.16.12.73 fall-over bfd
    neighbor 172.16.13.9 remote-as 2005
    neighbor 172.16.13.9 description PE_MEX_3
    neighbor 172.16.13.9 fall-over bfd
    neighbor 172.16.13.77 remote-as 2005
    neighbor 172.16.14.6 remote-as 64512
    neighbor 172.16.14.10 remote-as 64512
    neighbor 172.16.16.26 remote-as 64982
    neighbor 172.16.16.26 description INTERNET-2
    neighbor 172.16.16.30 remote-as 64982
    neighbor 172.16.16.30 description INTERNET-1
    address-family ipv4
      neighbor 172.16.10.41 activate   (conexion to Nortel Devices)
      neighbor 172.16.10.41 route-map AS-PATH-MAN in
      neighbor 172.16.10.41 route-map REDES-WAN->MAN out
      neighbor 172.16.11.233 activate   (conexion to Nortel Devices)
      neighbor 172.16.11.233 route-map AS-PATH-MAN in
      neighbor 172.16.11.233 route-map REDES-WAN->MAN out
      neighbor 172.16.12.73 activate
      neighbor 172.16.12.73 route-map REDES-WAN-PE_MEX_1 in
      neighbor 172.16.12.73 route-map DEFAULT-ROUTE out
      neighbor 172.16.13.9 activate  (conexion to Cisco 7600 Devices)
      neighbor 172.16.13.9 route-map REDES-WAN-PE_MEX_3 in
      neighbor 172.16.13.9 route-map DEFAULT-ROUTE out
      neighbor 172.16.13.77 activate
      neighbor 172.16.13.77 route-map DEFAULT-ROUTE out
      neighbor 172.16.14.6 activate  (conexion to ASR 9000)
      neighbor 172.16.14.6 route-map default out
      neighbor 172.16.14.10 activate (conexion to ASR 9000)
      neighbor 172.16.14.10 route-map default out
    the difference that look it from routes to know Nortel devices an Cisco Devices is the sollow on Cisco 7600
    Cisco 7600#sho ip bgp 150.151.1.250
    BGP routing table entry for 150.151.0.0/16, version 5612717
    Paths: (2 available, best #1, table default)
    Multipath: eBGP
      Advertised to update-groups:
         2          4        
      2005
        172.16.13.9 from 172.16.13.9 (150.220.250.5)
          Origin IGP, localpref 300, valid, external, best
          Community: 100:22
          Extended Community: RT:100:22
      2005
        172.16.12.73 from 172.16.12.73 (150.220.250.1)
          Origin IGP, localpref 260, valid, external
          Community: 100:22
          Extended Community: RT:100:22
    Cisco 7600#sho ip bgp 172.16.161.6
    BGP routing table entry for 172.16.161.6/32, version 6133620
    Paths: (2 available, best #2, table default)
    Multipath: eBGP
      Not advertised to any peer
      64512 64513
        172.16.14.6 from 172.16.14.6 (172.16.14.1)
          Origin incomplete, localpref 100, valid, external, multipath
          Extended Community: RT:64512:64513
      64512 64513
        172.16.14.10 from 172.16.14.10 (172.16.14.2)
          Origin incomplete, localpref 100, valid, external, multipath, best
          Extended Community: RT:64512:64513
    NOT advertised to any peer
    if we looking on ASR the vrf GAT the network is advertised but on vrf CAMPUS not
    RP/0/RSP0/CPU0:ED_MEX_1#sho bgp vrf CAMPUS 172.16.161.6
    Mon May 20 12:58:03.516 UTC
    BGP routing table entry for 172.16.161.6/32, Route Distinguisher: 64512:64513
    Versions:
      Process           bRIB/RIB  SendTblVer
      Speaker                 20          20
        Local Label: 16004
    Last Modified: May 17 17:24:29.877 for 2d19h
    Paths: (1 available, best #1)
      Not advertised to any peer
      Path #1: Received by speaker 0
      Not advertised to any peer
      64513
        172.16.19.5 from 172.16.19.5 (172.16.162.4)
          Origin incomplete, metric 110, localpref 100, valid, external, best, group-best, import-candidate
          Received Path ID 0, Local Path ID 1, version 20
          Extended community: RT:64512:64513
    but the vrf GAT:
    RP/0/RSP0/CPU0:ED_MEX_1#sho bgp vrf GAT 172.16.161.6   
    Mon May 20 12:58:52.909 UTC
    BGP routing table entry for 172.16.161.6/32, Route Distinguisher: 64512:2006
    Versions:
      Process           bRIB/RIB  SendTblVer
      Speaker                 30          30
    Last Modified: May 17 17:24:29.877 for 2d19h
    Paths: (1 available, best #1)
      Advertised to CE peers (in unique update groups):
        172.16.14.5    
      Path #1: Received by speaker 0
      Advertised to CE peers (in unique update groups):
       172.16.14.5    
      64513
        172.16.19.5 from 172.16.19.5 (172.16.162.4)
          Origin incomplete, metric 110, localpref 100, valid, external, best, group-best, import-candidate, imported
          Received Path ID 0, Local Path ID 1, version 30
          Extended community: RT:64512:64513
    Any idea for this trouble, we try to advertise the extend community but nothing.
    the configuration on ASR is the follow:
    router bgp 64512
    bgp router-id 172.16.14.1
    address-family ipv4 unicast
    address-family vpnv4 unicast
    vrf GAT
      rd 64512:2006
      address-family ipv4 unicast
       redistribute connected
       redistribute static
      neighbor 172.16.14.5
       remote-as 2006
       address-family ipv4 unicast
        send-community-ebgp
        route-policy pass-all in
        route-policy pass-all out
        send-extended-community-ebgp
    vrf CAMPUS
      rd 64512:64513
      address-family ipv4 unicast
       redistribute connected
       redistribute static
      neighbor 172.16.19.5
       remote-as 64513
       address-family ipv4 unicast
        route-policy pass-all in
        route-policy pass-all out
    we only put send-extended-community-ebgp only on vrf GAT.
    Best Regards

    Hi Harold thanks for your comment
    We do it your recommendation and put on AS 64912 routes a route-map for identify the traffic IN on interface the finally configuration on cisco 7600 is:
    router bgp 2006
    bgp router-id 172.16.110.97
    bgp log-neighbor-changes
    bgp graceful-restart restart-time 120
    bgp graceful-restart stalepath-time 360
    bgp graceful-restart
    neighbor 172.16.14.6 remote-as 64512
    neighbor 172.16.14.6 description EDGE_MEX_1
    neighbor 172.16.14.10 remote-as 64512
    neighbor 172.16.14.10 description EDGE_MEX_2
    address-family ipv4
      no synchronization
      neighbor 172.16.14.6 route-map REDES_CAMPUS in
      neighbor 172.16.14.6 route-map default out
      neighbor 172.16.14.10 activate
      neighbor 172.16.14.10 route-map REDES_CAMPUS in
      neighbor 172.16.14.10 route-map default out
      neighbor 172.16.16.26 activate
    with the follow route maps:
    ip extcommunity-list standard GAT permit rt 64512:64513
    ip bgp-community new-format
    ip community-list standard REDES-GAT permit 64512:2006
    route-map REDES_CAMPUS permit 430
    match extcommunity GAT
    set local-preference 250
    set community 64512:2006 additive
    set extcommunity rt  64512:64513 additive
    route-map REDES-WAN->MAN permit 1600
    match community REDES-GAT
    with this information the routes advertise on neighbord know the loopback 172.16.161.6
    GW_MEX_2#sho ip bgp neighbors 172.16.11.233 advertised-routes
    BGP table version is 6160029, local router ID is 172.16.110.97
    Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
                  r RIB-failure, S Stale
    Origin codes: i - IGP, e - EGP, ? - incomplete
       Network          Next Hop            Metric LocPrf Weight Path
    *> 1.0.0.1/32       172.16.12.73                  300      0 2005 ?
    *> 1.0.0.2/32       172.16.12.73                  300      0 2005 ?
       Network          Next Hop            Metric LocPrf Weight Path
    *> 172.16.140.72/32 172.16.13.9                   300      0 2005 ?
    *> 172.16.141.22/32 172.16.12.73                  250      0 2005 ?
    *> 172.16.141.61/32 172.16.12.73                  250      0 2005 i
    *> 172.16.141.71/32 172.16.12.73                  250      0 2005 i
    *> 172.16.142.0/27  172.16.13.9                   300      0 2005 ?
    *> 172.16.142.32/27 172.16.13.9                   250      0 2005 ?
    *> 172.16.144.0/27  172.16.13.9                   300      0 2005 ?
    *> 172.16.146.1/32  172.16.13.9                   300      0 2005 65451 i
    *> 172.16.150.0/27  172.16.12.73                  250      0 2005 ?
    *> 172.16.152.0/27  172.16.13.9                   300      0 2005 ?
    *> 172.16.152.32/28 172.16.13.9                   300      0 2005 ?
    *> 172.16.155.1/32  172.16.13.9                   300      0 2005 ?
    *> 172.16.161.1/32  172.16.14.6              0    250      0 64512 ?
    *> 172.16.161.6/32  172.16.14.10             0    250      0 64512 ?
    Thanks for your cooperation
    Best Regards

  • Cisco 7600 in MPLS

    Hello,
    1)
    I have a question regarding Cisco 7600/6500 ( sup720 exactely) in MPLS.
    I've read in documentation and also in some forum posts that "show mpls cef" is not MPLS aware command and should be used only for IP traffic. But still in some Cisco documents you can find that it is recommended on Cisco 7600/6500 for MPLS to use show mls cef instead of show ip cef (wether it is P or PE device in MPLS).
    Does anyone know what is true?
    2)
    Also when load balancing is involved in MPLS with Cisco 7600/6500 (sup720)
    P=======PE (P and PE are 7600 and there are two paralle link with the same cost between them).
    In documentation can be found that in MPLS, CEF is still in charge for load sharing (src-dst IP header based) except for hardware based platforms.
    Since 7600 is hardware based platform does it have some other load sharing method or it is also CEF based?
    Thanks in advance.
    Regards,
    A.

    Hi Prima,
    This question has been already answered several times and the answer is still the same :-) : it's not supported on 7600 platform due to hardware limitation.
    HTH
    Laurent.

Maybe you are looking for