MPLS L2VPN ASR9K and 7600

Am having problem bringing up mpls l2vpn between asr9k and 7609 router . Below is my config. The interfaces are up, the vc working, but can't ping across.
AS9K
interface GigabitEthernet0/2/0/6.609 l2transport
encapsulation dot1q 609
rewrite ingress tag pop 1 symmetric
mtu 1526
pw-class TST
  encapsulation mpls
   transport-mode vlan
xconnect group TST
  p2p TST
   interface GigabitEthernet0/6.609
   neighbor 2.2.2.2  pw-id 609
    pw-class TST
7609
interface gig 3/4.609
encapsulation dot1q 609
xconnect 1.1.1.1 609 encapsulation mpls
***OUTPUT FROM ASR9K********
RP/0/RSP0/CPU0#sh l2vpn xconnect pw-class TST detail 
Group X,X, state is up; Interworking none
  AC: GigabitEthernet0/6.609, state is up
    Type VLAN; Num Ranges: 1
    VLAN ranges: [905, 905]
    MTU 1512; XC ID 0x1040003; interworking none
    Statistics:
      packets: received 735789487, sent 725878036
      bytes: received 405747931393, sent 184926449749
      drops: illegal VLAN 0, illegal length 0
  PW: neighbor 2.2.2.2, PW ID 609, state is up ( established )
    PW class ENS, XC ID 0xc0000003
    Encapsulation MPLS, protocol LDP
    Source address 1.1.1.1
    PW type Ethernet VLAN, control word disabled, interworking none
    PW backup disable delay 0 sec
    Sequencing not set
    PW Status TLV in use
      MPLS         Local                          Remote                       
      Label        17442                          847                          
      Group ID     0x80003c0                      0x0                          
      Interface    GigabitEthernet0/6.609     uknown
      MTU          1512                           1512                         
      Control word disabled                       disabled                     
      PW type      Ethernet VLAN                  Ethernet VLAN                
      VCCV CV type 0x2                            0x2                          
                   (LSP ping verification)        (LSP ping verification)      
      VCCV CC type 0x6                            0x6                          
                   (router alert label)           (router alert label)         
                   (TTL expiry)                   (TTL expiry)                 
    Incoming Status (PW Status TLV):
      Status code: 0x0 (Up) in Notification message
    Outgoing Status (PW Status TLV):
      Status code: 0x0 (Up) in Notification message
    MIB cpwVcIndex: 3221225475
    Statistics:
      packets: received 725878036, sent 735789487
      bytes: received 184926449749, sent 405747931393
*******7609 OUTPUT*******
Local interface: Gi1/3.609 up, line protocol up, Eth VLAN 609 up
  Destination address: 1.1.1.1, VC ID: 609, VC status: up
    Output interface: Gi2/4, imposed label stack {0 151644}******************This is my problem no imposed label on 7609
    Preferred path: not configured 
    Default path: active
    Next hop: 10.198.64.21
  Create time: 00:00:16, last status change time: 00:00:16
  Signaling protocol: LDP, peer 1.1.1.1 up
    Targeted Hello: 2.2.2.2(LDP Id) -> 1.1.1.1, LDP is UP
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRru
      Last local dataplane   status rcvd: No fault
      Last local SSS circuit status rcvd: No fault
      Last local SSS circuit status sent: No fault
      Last local  LDP TLV    status sent: No fault
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 505, remote 151644
    Group ID: local 0, remote 134218688
    MTU: local 1508, remote 1508
    Remote interface description: GigabitEthernet0_6_.609
  Sequencing: receive disabled, send disabled
  Control Word: Off (configured: autosense)
  SSO Descriptor: 1.1.1.1/609, local label: 505
    SSM segment/switch IDs: 57633/24673 (used), PWID: 28772
  VC statistics:
    transit packet totals: receive 3, send 0
    transit byte totals:   receive 216, send 0
    transit packet drops:  receive 0, seq error 0, send 0

Hello ogungbenro wale,
Would you be so kind to verify the output form 7600, since the config part does not correspond to VC you provided output for:
interface gig 3/4.609 <=
Local interface: Gi1/3.609 up, line protocol up, Eth VLAN 609 up <=

Similar Messages

  • MPLS support GEC on 7600 with SUP-720-3BXL ?

    Hi all
    Could someone let me know does 7600 with SUP-720-3BXL support full MPLS, MPLS-TE, QoS, ... on Gigabit Ethernet channel interface ?
    Which port interface (LAN/WAN, ...) does 7600/SUP-720-3BXL support full MPLS features ?
    And does 10GBASE XENPAR Modules support full MPLS features ?
    thanks you

    The Cisco 7200 Series offers numerous LAN and WAN interfaces for diverse connectivity requirements. Modular processors for the Cisco 7200 Series provide flexibility as their need grows. The three onboard Gigabit Ethernet interfaces,in the Cisco 7301 VAM2+ security router bundle provides the same high performance.For further information verify the following URL:
    http://www.cisco.com/en/US/products/hw/routers/ps341/prod_bulletin0900aecd80205255.html

  • MPLS L2VPN

    Hi All,
    Please explain me the difference betwreen AToM,VPLS,L2TPV3 and Pseudowire and routed Pseudowire.
    Thanks in advance
    Thanks,
    Arun Mohan

    Hello Arun,
    A pseudowire is a point-to-point bearer service capable of carrying Layer2 frames across a network between two defined endpoints. A pseudowire can be likened to a direct point-to-point connection between two endpoints - these endpoints consider themselves to be directly interconnected, even though in reality, there is a service provider that interconnects them.
    There are various technologies that can be used to provide pseudowire services. One of them is the Any Transport over MPLS, or more recently, the Pseudo Wire Emulation End to End (PWE3), that uses MPLS labeling to create a label switched path over the provider that will carry the frames between two defined endpoints. AToM an PWE3 depend on MPLS being present and run in the service provider's network. Another technology used to provide pseudowire service is the L2TP protocol which is basically a protocol that encapsulates (tunnels) Layer2 frames into new IP packets that are routed over the service provider's network to the endpoints where they are decapsulated and the tunneled Layer2 frames are forwarded further. L2TP is a pure IP-based solution.
    Frankly, I do not know what a routed pseudowire is. I haven't heard that term before.
    All pseudowire technologies described so far emulate only a point-to-point direct connection. If more than two locations have to be interconnected, more pseudowires are needed. In general, if a full direct connectivity between N locations is necessary, you need to create N*(N-1)/2 pseudowires which is clearly not a scalable approach. Often, however, customers have many locations and request a kind of "Ethernet-alike" connection between them that behaves simply like an Ethernet switch that interconnects all these locations together, allowing immediate direct connectivity between these locations. The pseudowire as a point-to-point service clearly does not fit in here.
    This is where Virtual Private LAN Service comes in. The VPLS allows you to interconnect multiple customer locations using an MPLS-based service provider network that emulates an Ethernet switch interconnecting all customer's locations. Apart from allowing all locations to communicate directly to each other, VPLS also takes care of replicating unknown unicast, multicast and broadcast traffic coming from a particular location to all other customer's locations, like a normal Ethernet switch would. VPLS network itself is based on routers running IP and MPLS and all operations are performed over MPLS label switched paths.
    Best regards,
    Peter

  • (Linecard image not present) at WS-SSC-600 and 7600-SIP-400

    i install two modules WS-SSC-600 and 7600-SIP-400 in slot 5 and 6 in 13-slot chassis and give this output from show power (Linecard image not present)
      for both cards.
    supervisor engine is : VS-S720-10G with sub-module VS-F6K-PFC3CXL and VS-F6K-MSFC3
    IOS : s72033-advipservicesk9-mz.122-33.SXI9
    what that mean and how to fix it ?

    Ok problem solved by upgrade ios to another version but the new image must contains (_wan) in image name for example (
    s72033-advipservicesk9_wan-mz.122-33.SXJ6 ) otherwise the two modules will not powered up.

  • Number of class maps (QOS) supported on 7200 and 7600

    Hi,
    Have few queries on class maps for QOS, putting forward for your comments/inputs.
    1. Want to know if there are any limitation (s) on the number of class maps (to be applied inbound/outbound) that can be configured on the 7200 and 7600 routers.
    2. Is there any imitation on the numbers (of class maps) in general or will it depend on the sum total of BW configured in the classes? I mean which one will be the deciding factor i.e. if the limit is wrt to the configured classes or the number of classes can't go beyond the consolidated bandwidth configured on the interface.
    Kindly share details on the same and if there are any recommendations.
    Thanks! in advance.

    From: http://www.cisco.com/en/US/tech/tk543/tk545/technologies_q_and_a_item09186a00800cdfab.shtml
    "Q. How many classes does a Quality of Service (QoS) policy support?
    A. In Cisco IOS versions earlier than 12.2 you could define a maximum of only 256 classes, and you could define up to 256 classes within each policy if the same classes are reused for different policies. If you have two policies, the total number of classes from both policies should not exceed 256. If a policy includes Class-Based Weighted Fair Queueing (CBWFQ) (meaning it contains a bandwidth [or priority] statement within any of the classes), the total number of classes supported is 64.
    In Cisco IOS versions 12.2(12),12.2(12)T, and 12.2(12)S, this limitation of 256 global class-maps was changed, and it is now possible to configure up to 1024 global class-maps and to use 256 class-maps inside the same policy-map."

  • Connecting OC48 Between ASR9K and ASR1K

    Hi there.
    I don't know the first thing about the  WAN something like POS...
    Now I'm facing some problem with connecting OC48(POS) between ASR9K and ASR1K.
    There are new 9K and new 1K  in same server rack for the test.
    So i tried to test these for connecting OC48
    9K and 1K is directly connected by OC48
    9K : A9K-SIP-700 // SPA-2XOC48POS/RPR    // SFP-OC48-SR
    1K : ASR1000-SIP10 // SPA-1XOC48-POS    // SFP-OC48-SR
    After connecting these two devices directly, ASR1K shows the interface status is up/up 
    but ASR9K ... the interface status is down/down. 
    I didn't configure anything. Do i need to configure something ? 
    When i connected POS port 1 and POS port 2 directly in the same ASR 9K chassis, the interface is up/up
    please help me out 
    Thank you in advance. :)

    exactly, so the transmit side of the 9k needs to be connected to the receive side of the 1k.
    the transmit side of the 1k needs to be connected to the receive side of the 9k.
    download this doc for reference:
    http://www.cisco.com/c/en/us/td/docs/interfaces_modules/shared_port_adapters/install_upgrade/ASR1000/asr_sip_spa_hw/ASRsov.html#pgfId-1136398
    Another link discussing the type of testing you are attempting:
    http://www.cisco.com/c/en/us/support/docs/optical/synchronous-optical-network-sonet/16181-posclocking-16181.html

  • WCCP and 7600 - not redirecting traffic

    I have a Blue Coat SG 210 connected to a 7600(SUP720).  All web traffic is passing thru the 7600, WCCP config between the SG and 7600 are working.  However traffic isn;t being redirected to Blue Coat..any idea why? 
    ip wccp 0 redirect-list BLUE-COAT group-list 90
    Extended IP access list BLUE-COAT
        1 permit tcp host 10.160.161.125 any eq www
        2 permit tcp host 10.160.161.125 any eq 443
        10 permit tcp host 10.160.161.199 any eq www
        20 permit tcp host 10.160.161.199 any eq 443
    Standard IP access list 90
        8 permit 10.148.131.42 (2217 matches)
    interface GigabitEthernet5/1
    ip address 10.148.130.13 255.255.255.252
    ip wccp 0 redirect in (I have tried both in/out)
    ip pim sparse-dense-mode
    ip route-cache flow
    ip ospf network point-to-point
    sh ip wccp
    Global WCCP information:
        Router information:
        Router Identifier:                   10.148.135.253
        Protocol Version:                    2.0
        Service Identifier: 0
        Number of Cache Engines:             1
        Number of routers:                   1
        Total Packets Redirected:            0
        Redirect access-list:                BLUE-COAT
        Total Packets Denied Redirect:       0
        Total Packets Unassigned:            0
        Group access-list:                   90
        Total Messages Denied to Group:      0
        Total Authentication failures:       0
    sh ip wccp 0 detail
    WCCP Cache-Engine information:
        Web Cache ID:          10.148.131.42
        Protocol Version:      2.0
        State:                 Usable
        Redirection:           GRE
        Packet Return:         GRE
        Packets Redirected:    0
        Connect Time:          05:52:10
        Assignment:            MASK
        Mask  SrcAddr    DstAddr    SrcPort DstPort
        0000: 0x0000003F 0x00000000 0x0000  0x0000
        Value SrcAddr    DstAddr    SrcPort DstPort CE-IP
        0000: 0x00000000 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0001: 0x00000001 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0002: 0x00000002 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0003: 0x00000003 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0004: 0x00000004 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0005: 0x00000005 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0006: 0x00000006 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0007: 0x00000007 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0008: 0x00000008 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0009: 0x00000009 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0010: 0x0000000A 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0011: 0x0000000B 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0012: 0x0000000C 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0013: 0x0000000D 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0014: 0x0000000E 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0015: 0x0000000F 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0016: 0x00000010 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0017: 0x00000011 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0018: 0x00000012 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0019: 0x00000013 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0020: 0x00000014 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0021: 0x00000015 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0022: 0x00000016 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0023: 0x00000017 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0024: 0x00000018 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0025: 0x00000019 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0026: 0x0000001A 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0027: 0x0000001B 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0028: 0x0000001C 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0029: 0x0000001D 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0030: 0x0000001E 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
            0031: 0x0000001F 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0032: 0x00000020 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0033: 0x00000021 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0034: 0x00000022 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0035: 0x00000023 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0036: 0x00000024 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0037: 0x00000025 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0038: 0x00000026 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0039: 0x00000027 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0040: 0x00000028 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0041: 0x00000029 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0042: 0x0000002A 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0043: 0x0000002B 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0044: 0x0000002C 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0045: 0x0000002D 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0046: 0x0000002E 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0047: 0x0000002F 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0048: 0x00000030 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0049: 0x00000031 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0050: 0x00000032 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0051: 0x00000033 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0052: 0x00000034 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0053: 0x00000035 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0054: 0x00000036 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0055: 0x00000037 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0056: 0x00000038 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0057: 0x00000039 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0058: 0x0000003A 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0059: 0x0000003B 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0060: 0x0000003C 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0061: 0x0000003D 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0062: 0x0000003E 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)
        0063: 0x0000003F 0x00000000 0x0000  0x0000  0x0A94832A (10.148.131.42)

    Ilir,
    How is this second group of users connected to the ASA?  Their outbound traffic has to be going out the "inside" interface also. If they are on another port on the ASA, WCCP won't catch their traffic. i.e. You can't use the DMZ interface on an ASA and point its web traffic at a WSA that lives inside.
    Ken

  • MPLS TE Bandwidth and Priority

    Hi everybody
    Hopefully, everyone is doing great.  I stumbled upon the following link on MPLS TE bandwidth and priority:
    http://blog.ipexpert.com/2009/05/27/mpls-te-bandwidth-and-priority/
    it was a very good read.  But I am left with one question. How does R2 decide which tunnel to drop? In the example, R2 drops tunnel 1, but how does R2 decide which one to drop?
    Thanks and have a great sunday

    Hi Thanveer
    I hope you are doing fine.  Here is what i found  in a book ( traffic engineering with MPLS by Eric, Ajay, great book, still reading it)
    There are two priorities:
    1) set up priority
    2) hold prioritity
    Based on the book the code works this way
    Imagine we have two tunnels already established and are passing through R3
    t1, set up priority 6 hold priority 5
    t2 set up priority 6 hold priority 4
    Let say R3 just receives a RSVP path  request for  a new tunnel, lets call it tunnel 3 with set up priority 4 hold priority 6. This tunnel requires a bandwidth which R3 can not accommodate without dropping one of the established tunnels.
    Router will take t3's set up priority ( 4) and compares it against the current  established tunnel's hold priorities where lower the number means higher the priority. In our example, set up priority of tunnel 3  is 4 and R3  compares it against both hold priorities of established tunnels. R3 then concludes it has to drop t1 to accommodate t3 ( set up priority of tunnel3 is higher than the hold priority of tunnel1)
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    what is not cleared is how will router 3 behave if all the established tunnels have same hold priority i.e 4 and a request for a new tunnel i.e t3 comes with the set up priority of 4?
    Not sure if R3 just randomly picks any established tunnel and drops it or there is some move involved process that R3 goes through to decide which tunnel gets dropped.
    Lets hope somebody way smarter than me might chime in :)
    Have a great weekend

  • MPLS TE - Link and Node Protection

    Hi Guys,
    Just revisiting an old topic again - MPLS-TE Link and Node Protection.
    Is it enough that the backup path (facility backup as supported by IOS) just merge on any LSR of the protected LSP? It does seem to be that way. For example, consider the following topology -
    R1-------R2-------R3------R4------R6
                |_____R5____|
    The Primary LSP is setup with explicit path R1-R2-R3-R4-R6 and requesting Link-Protection.
    R2 protects the link R2-R3 with a backup LSP which has an explicit path R2-R5-R4. The backup LSP merges on the Primary LSP but R4 is not the next-hop to R2 protecting the primary LSP.
    This works in my testing but my understanding was that for-
    Link Protection - the backup LSP must be terminated on the LSR which is next-hop to the LSR protecting the primary LSP
    Node Protection - the backup LSP must be terminated on the LSR which is next-next-hop to the LSR protecting the primary LSP
    Your thoughts?
    Regards,
    Amit.

    NHOP Versus NNHOP Backup TunnelsMore than one backup tunnel can protect a given LSP, where one backup tunnel terminates at the LSP
    ’sNNHOP, and the other terminates at the LSP
    ’s NHOP. In this case, the router chooses the backup tunnel thatterminates at the NNHOP (that is, FRR prefers NNHOP over NHOP backup tunnels)

  • 7600 platform for MPLS based L2 and L3 services

    Hi,
    We are planning to deploy 7600s (testing to be done) for L2 and L3 services. Has anyone out there found some issues with both the layers functioning in unison on the same.
    Thanks
    Cheers,
    ~sultan

    Hello Charles,
    Thanks for you reply, actually I wanted to know more specific details, like IOS and modules being used by others, which you have stated.
    I am planning to go for SIP-200 and SIP-400 with STM-1 POS, 2xGIG and FE8 modules.
    Services would be EoMPLS, including VPLS and MPLS/BGP IP VPNs.
    Thanks
    Cheers
    ~sultan

  • CRS-X vs ASR9K vs 7600

    Dears
    Was checking specs for new CRS-X and would like your feedback please regarding ASR9K vs CRS-X
    1- Beside CRS multishelf, why would someone prefer CRS-X over ASR9k ?
    ASR9K seems to be more interesting as it provides 440 G/slot however CRS-X provides 400 G/slot. Also I believe they support nearly same range of interfaces types. To me seems reason someone would go to CRS If he already has CRS in network as in this case it would be more economic to just upgrade existing fabric/LC and go to CRS-X instead of getting new HW ASR9k chassis
    What do you think ?
    |||
    2- Also it came to my mind that 12K provides only 10G/slot however 7609 provides 40 G/slot ... So does this means 7600 can be good candidate for 12K replacment espically that XR 12416 provides total capacity of 320 Gbps and 7609 provides 720 Gbps ??
    Many Thanks
    Regards
    Sherif Ismail

    I would talk to your account team about the future hardware and software feature plans for each platform and how that fits in with your requirements. I would not just consider the current system capacties. Things such as power, cooling, the technology used to interconnect the components with the need to keep backwards compatibilty mean each hardware platform has inherent scaling limits.
    The current ASR9922 hardware actually delivers 660Gb/slot with fabric resiliency although there are not currently any linecards that use that much bandwidth. Publically available marketing slides already talk about the ASR being scalable to 1.2Tb/slot.
    Remember that you need a revision B chassis for 400Gb/slot on the CRS. The "legacy" chassis is limited to 200Gb/slot.
    If things like the high availability features in IOS-XR are important to you then a platform like the 7600 with its multilayer switch heritage and which runs IOS might not be suitable.
    You could also consider the recently announced NCS 6000.

  • VPLS between ASR1000 and 7600

    Hello.
    I'm trying to create VPLS between two ASR1004 routers and one 7600 with ES+ card.
    IGP/BGP and LDP connections between all routers are OK.
    Configuration is the following:
    Cisco 7600: (IP 12.12.12.12)
    l2 vfi TEST manual
    vpn id 777
    neighbor 8.8.8.8 encapsulation mpls
    neighbor 2.2.2.2 encapsulation mpls
    interface Vlan777
    no ip address
    xconnect vfi TEST
    end
    interface GigabitEthernet1/12  // Link to switch1
    description LINK to SW1
    switchport
    switchport trunk encapsulation dot1q
    switchport mode trunk
    end
    And the ASR's config: (IP 8.8.8.8/2.2.2.2)
    l2 vfi TEST manual
    vpn id 777
    bridge-domain 777
    neighbor 12.12.12.12 encapsulation mpls
    neighbor 8.8.8.8 encapsulation mpls
    interface GigabitEthernet0/0/0 // Link to switch2
    description DOWNLINK to SW2
    load-interval 30
    speed 1000
    no negotiation auto
    no clns route-cache
    service instance 777 ethernet
    encapsulation dot1q 777
    bridge-domain 777
    Then I created SVI interfaces on both switches, connected to 7600 and ASR1K (SW1 and SW2), but ping between them in the vlan 777 was failed.
    sh xconnect all from the ASR:
    UP pri vfi TEST UP mpls 12.12.12.12:777 UP
    UP pri vfi TEST UP mpls 8.8.8.8:777 UP
    What's wrong in this configuration?

    I've solved the problem.
    Just added
    rewrite ingress tag pop 1 symmetric
    to the CE facing interface
    and also
    mpls no-split-horizon
    to l2 vfi section

  • Cisco huawei mpls l2vpn

    Hi All,
    While i m doing for the remote ldp formation between this devices of cisco 3600 & huawei 5700,
    attached the configs of these 2 nodes.what could be the possible reason for this..
    witch(config-router)#do sh mpls l2 vc
    Local intf     Local circuit              Dest address    VC ID      Status
    Vl2292         Eth VLAN 2292              10.50.1.1       2292       DOWN
    VFI 2293       vfi                        10.50.1.1       2293       DOWN
    Switch(config-router)#do sh mpls l2 vc det
    Local interface: Vl2292 down, line protocol down, Eth VLAN 2292 down
      Destination address: 10.50.1.1, VC ID: 2292, VC status: down
        Last error: Local peer access circuit is down
        Output interface: none, imposed label stack {}
        Preferred path: not configured
        Default path: no route
        No adjacency
      Create time: 04:16:50, last status change time: 04:20:09
        Last label FSM state change time: 04:16:49
      Signaling protocol: LDP, peer unknown
        Targeted Hello: 10.50.2.2(LDP Id) -> 10.50.1.1, LDP is DOWN, no binding
        Graceful restart: not configured and not enabled
        Non stop routing: not configured and not enabled
        Status TLV support (local/remote)   : enabled/None (no remote binding)
    Thanks
    anand

    Hi Nagendra,
    This is directly connected switch for which i ma trying to establish a remote ldp,
    sh mpls interfaces, states the tu1 as down, is there anything wrong in here
    Switch# show mpls interfaces
    Interface              IP            Tunnel   BGP Static Operational
    Vlan21                 Yes (ldp)     No       No  No     Yes
    Tunnel1                Yes           No       No  No     No
    interface Tunnel1
     ip unnumbered Loopback0
     mpls ip
     mpls label protocol ldp
     tunnel destination 10.50.1.1
    end
    also the preferre path in
    pseudowire-class TEST
     ! Incomplete config [Unconfigured or invalid tunnel interface]
     encapsulation mpls
     preferred-path interface Tunnel1 disable-fallback
      ! Incomplete or invalid tunnel interface
    Please suggest on this..
    Thanks
    kumar

  • MPLS L2VPN packet capture

    Hi,
    I want to capture packet on gi0/0 of PE1 in order to show customer that all his traffic is encapsulated and transmitted by L2VPN (ldp signaling) in his lab.
    CE1-----------(g0/1)PE1(g0/0)------------PE2-----------CE2
    PE1 and PE2 are Cisco3945 and L2VPN is working well. I tried cisco RITE(Router IP Traffic Export Packet Capture) feature, but the output was not what I expected. I tried both export mode and capture mode. Only LDP hello message I got, looks like RITE is only interested in IP packet. Monitor session wasn't effective as well because it is not a switch.
    Is there any other way/workaround to capture customer's traffic encapsulated in L2VPN?
    What I did on PE1 when I was trying RITE export mode:
    ip traffic-export profile test
    bidirectional
    interface GigabitEthernet0/2
    mac-address e411.5b44.3a6d
    interface GigabitEthernet0/2
    ip address 10.1.2.1 255.255.255.0
    interface GigabitEthernet0/0
    ip traffic-export apply test
    Gi0/2 connected my PC(10.1.2.2) with wireshark installed.
    Many thanks.
    Regards,
    Jerry Fan

    Thanks Shivlu. I tried, but failed. 'monitor capture' is only interested in ipv4 and ipv6. Maybe the IOS in Cisco3945 isn't same as the IOS in Cat6500 or Cisco7600 or GSR/CSR.
    See following:
    ===================================================================
    Router_MPS_TEST_A#monitor capture ?    
      buffer  Control Capture Buffers
      point   Control Capture Points
    Router_MPS_TEST_A#monitor capture po
    Router_MPS_TEST_A#monitor capture point ?
      associate     Associate capture point with capture buffer
      disassociate  Dis-associate capture point from capture buffer
      ip            IPv4
      ipv6          IPv6
      start         Enable Capture Point
      stop          Disable Capture Point
    Router_MPS_TEST_A#monitor capture point ip ?
      cef               IPv4 CEF
      process-switched  Process switched packets
    Router_MPS_TEST_A#monitor capture point ip p
    Router_MPS_TEST_A#monitor capture point ip process-switched ?
      WORD  Name of the Capture Point
    Router_MPS_TEST_A#monitor capture point ip process-switched test-point ?
      both     Inbound and outbound and packets
      from-us  Packets originating locally
      in       Inbound packets
      out      Outbound packets
    Router_MPS_TEST_A#monitor capture point ip process-switched test-point b
    Router_MPS_TEST_A#monitor capture point ip process-switched test-point both ?
    Router_MPS_TEST_A#monitor capture point ip process-switched test-point both
    ===================================================================
    At last, I have to insert a switch in the middle of two cisco3945 and configured port span. That worked very well. Anyway, many thanks for your advice.
    Jerry Fan

  • MPLS, Summarisation, OSPF and stubby areas

    Since summarisation breaks the LSP and this is not desired in an MPLS VPN network on the core, can it be concludded then that stubby areas can not be used on the service provider core, if he wants to offer MPLS VPN service?.
    Or how does he avoid or workaround the issue of summarisation, small Link State Database and areas on the core.

    You are correct. It is not possible to use stubby areas if you want to deploy MPLS VPN. You can still summarize though as long as you don't summarize the IP addresses assigned to the loopback interfaces. One way to do it is to use a different address range for the loopback interface of all your PEs and to use summarization for all address ranges but this one. This way only the loopback addresses will be advertised as /32 and the rest of your prefixes will be nicely summarized.
    Hope this helps,

Maybe you are looking for

  • CIN pricing procedure steps

    Dear SAP's   Can any one send me the screen shots for Cin pricing procedure configuration on domestic sales, deemed export sales and export sales. my mail id is [email protected] thanks and points will be rewards if useful regards, Reshmi

  • How to know the limit of a column on a page in iSupplier

    Hi All, Suppliers are facing a issue where they are not able to see all invoices for a payment. iSupplier page just shows the first 400-500 invoices and rest are not shown. This page seems to be oracle seeded page, How can I check which element is re

  • What are the best practices for average size of an Adobe PDF file on a Web Server to be downloaded?

    We know at a certain point, an extremely large file can be slow in downloading/accessing from a web site, and lessens the end-user's experience.  How large is too large? What is a good average or suggested size for Adobe PDF files in general? Thank y

  • Keyboard shortcut to delete row or column

    OK, I like how you can add rows by a quick couple of key strokes, is there any to delete a row simply using keystrokes?

  • Scroll panel - two contents hooked to one scroll bar?

    I've got two boes of content (one running text and one a series of images grouped in a vertical fashion). I want these to move simultaneously but one is much longer than the other - and I want them to finish at the same time, the photos correlating t