SUP720 MPLS support only 700 routes per VRF?

In following document i found that SUP720 supporting only 700 router per 1 VRF. Am i right?
http://www.cisco.com/en/US/partner/products/hw/modules/ps4835/products_data_sheet09186a0080159856.html

There is no such thing as a limit of 700 routes per VRF. What is described in this URL is that scalability testing has been performed with 1024 VRFs with 700 routes each (1024*700=716800 routes total).
You could go way beyond 700 routes per VRF if you don't plan to provision that many VRFs.
Let me know if I answered your question,

Similar Messages

  • Maximum number of routes per vrf on SUP720-3BXL

    Hello,
    What are the limits for max number of routes in one vrf on SUP720-3BXL? Thanks for answers.

    Davor,
    The datasheet refers to 1024 VRFs with 700 routes each (tested numbers) but this is just an example as you could, in principal, have any combination of # VRFs * routes/VRF that would equal 700K routes (i.e. 2 VRF * 350K routes or 1 VRF * 700K routes).
    I say in principal because I have never seen a customer requesting the support for that many routes and have never tested it either.
    http://www.cisco.com/en/US/products/hw/modules/ps4835/products_data_sheet09186a0080159856.html
    Hope this helps,

  • MPLS support for 2621XM Router

    Hi ,
    Can anyone suggest me the IOS for 2621XM Router to support the MPLS LDP.
    My router is a Provider edge router.
    My flash is only 32 MB .
    Thanx in advance
    yogesh

    Hi
    You should use  : C2600-spservicesk9-mz
    This IOS is SP Services IOS for 2600 & 2600XM series router which support MPLS .
    http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps5460/prod_bulletin09186a00801af451.html
    Regards
    Chetan Kumar
    http://chetanress.blogspot.com

  • Per VRF label or Per route label

    Folks,
    A few weeks back I saw on some study group somewhere that im on a decent conversation on the downfalls of per vrf labels (juniper) compared to per route label (cisco). Now per route label obviously has its limitations in label consumption but per vrf label threw up a few issues - one of which was something to do with sub optimal routing. Anyone know any downfalls of using per vrf label space?

    Rob,
    One of the disadvantages of per VRF label scheme is that it requires an IP lookup on the edge router. This is due to the fact that if the label is shared among all CEs on a given PE, an IP lookup needs to be done in the VRF to determine which CE we should send the label to.
    Another disavantage would be that you couldn't support CsC using a per VRF label since an IP table lookup is required on the PE, which breaks the end to end LSP.
    On the other hand, you are absolutely right about the increase resources comsumption when a per route label scheme is used. This affects some vendors more than others though.
    Hope this helps,

  • Tacacs per vrf no supported on my router, does a gre tunnel would work?

    Hi,
    Basically the problem is that I am working with old routers, checked already on feature navigator an the following commands are not supported on the router to communicate to a TACACS server that resides on a vrf:
    Configuring Per VRF for TACACS+ Servers: Example
    The following output example shows that the group server tacacs1 has been configured for per VRF AAA services:
    aaa group server tacacs+ tacacs1
    server-private 10.1.1.1 port 19 key cisco
    ip vrf forwarding cisco
    ip tacacs source-interface Loopback0
    ip vrf cisco
    rd 100:1
    interface Loopback0
    ip address 10.0.0.2 255.0.0.0
    ip vrf forwarding cisco
    Basically I can not support all the above, however I was thinking of bypassing the command creating a GRE tunnel, I just need a confirmation if the following would work, if not I would appreciated that someone can point me into a better direction:
    ON BRANCH ROUTER:
    int l0
    ip add 1.1.1.1 255.255.255.0
    no shut
    int tun10
    ip add 2.2.2.1 255.255.255.0
    ip vrf forwarding cisco
    tun so l0
    tun dest [ip add of router directly connected to tacacs server]
    ip tacacs source-interface l0
    tacacs-server host 10.10.10.1
    tacacs-server key 7 cisco
    ON REMOTE ROUTER:
    int l0
    ip add 3.3.3.3 255.255.255.0
    no shut
    int tun10
    ip add 2.2.2.2 255.255.255.0
    ip vrf forwarding cisco
    tunn so l0
    tunn dest [ip add of branch router]
    Attached is some real information, the ip address of the real tacacs server is 10.20.30.61.

    Thanks for the response but I post the question after knowing that, I already checked on Feature Navigator that THIS IS NOT SUPPORTED for my router, at the end of my configuration I am purposing a workaround using a tunnel to bybass the nonsupported configuration.
    My question to you is, does a configuration with gre with vrf can work instead of the nonsupported configuration?
    I know that the alternative is to run Radius but it is more paperwork to do than trying to implement a solution with the current IOS.
    Thanks and sorry if I didn't make self clear at the beginning of my first post.

  • Per VRF Tacacs+ support on 3550EMI

    Trying to get Tacacs+ running on a 3550EMI switch running 12.1(22)EA3 (latest release), without much success due to wht appears to be lack of support for for Per VRF AAA/TACACS+ on the box.
    Checked elsewhere and looks like this feature is only available in some 12.2 and in 12.3T, but does anyone know if vrf-aware TACACS+ it is likely to appear on the 3550EMI or indeed on 12.1? Or does anyone know of a work around? (tried specifying a source-interface but this doesn't work)
    TIA

    This feature was introduced in 12.3(7)T. I guess its not supported on the Switch currently.

  • Tacacs per vrf no supported on MLS C3750G

    HI,
    As i already know the tacacs per vrf not supported  for MLS C3750G and some other old versin of the IOS router or switch, but now i have 2 vrf routing tables configured in my switch is there any work around for this thing to work?? really aprreicated your inputs guys!!!

    Thanks for the response but I post the question after knowing that, I already checked on Feature Navigator that THIS IS NOT SUPPORTED for my router, at the end of my configuration I am purposing a workaround using a tunnel to bybass the nonsupported configuration.
    My question to you is, does a configuration with gre with vrf can work instead of the nonsupported configuration?
    I know that the alternative is to run Radius but it is more paperwork to do than trying to implement a solution with the current IOS.
    Thanks and sorry if I didn't make self clear at the beginning of my first post.

  • I´m doing a design for presale, where I will need a router what support PAT for 500 or a little more of users, it not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

    I´m doing a design for presale, where  I will  need a router what support PAT for 500 or a little more of users, it  not need any more features only static routing and dhcp pool for 500 users, can you help me for know what router recommend?

    What is your WAN speed currently and projected WAN speed in the next 3 years?

  • Per-VRF BGP Dampening

    Does anyone know if it is possible to enable Per-VRF BGP Dampening? I have a router running 12.4(9)T and when I enable BGP dampening within an address-family, it is enabled under all routing contexts and within VPNV4.
    Any ideas?
    Jon

    Hello Jon,
    try to give the command only under the address-family of interest
    it should be supported
    Command Modes
    >>Address family configuration
    Router configuration
    see
    http://www.cisco.com/en/US/docs/ios/iproute/command/reference/irp_bgp1.html#wp1012660
    Sorry, I haven't seen you had already done. This may be a bug in your release.
    As a workaround you could try to use a route-map like in this example:
    Router(config)# router bgp 50000
    Router(config-router)# address-family ipv4
    Router(config-router-af)# bgp dampening route-map BLUE
    Router(config-router-af)# end
    Hope to help
    Giuseppe

  • Policy based routing on VRF interfaces to route traffic through TE Tunnel

    Hi All,
    Is there a method to do policy based routing on VRF interfaces and route data traffic through one TE tunnel and non-data traffic through another TE tunnel.
    The tunnel is already build up with these below config
    interface Tunnel25
    ip unnumbered Loopback0
    tunnel destination 10.250.16.250
    tunnel mode mpls traffic-eng
    tunnel mpls traffic-eng path-option 10 explicit name test
    ip explicit-path name test enable
    next-address x.x.x.x
    next-address y.y.y.y
    router ospf 1
    mpls traffic-eng router-id Loopback0
    mpls traffic-eng area 0
    mpls traffic-eng tunnels
    nterface GigabitEthernet5/2
    mpls traffic-eng tunnels
    mpls ip
    Is there additional config needed to work ,also in the destination end for the return traffic,we want to use the normal PATH --I mean non TE tunnel.
    We tested with the above scenario,but couldn't able to reach the destination.Meantime we had a question,when the packet uses the policy map while ingress,it may not know the associatuion with VRF(Is that right? --If so ,how to make it happen)
    Any help would be really appreciated
    Thanks
    Regards
    Anantha Subramanian Natarajan

    hi Anantha!
    I might not be the right person to comment on your first question. I have not configured MVPNs yet and not very confertable with the topic.
    But I am sure that if you read through the CBTS doc thoroughly, you might be able to derive the answer yourself. One thing I notice is that " a Tunnel will be selected regularly according to the routing process (even isf it is cbts enabled). From the tunnels selected using the regular best path selection, the traffic is mapped to a perticular tunnel in the group if specific class is mapped to that tunnel.
    So a master tunnel can be the only tunnel between the 2 devices over which the routing (bgp next hops) are exchanged and all other tunnels can be members of this tunnel. So your RPF might not fail.
    You might have to explore on this a bit more and read about the co-existance of multicast and TE. This will be the same as that.
    For your second question, the answer would be easy :
    If you want a specific eompls cust to take a particular tunnel/path, just create a seperate pair of loopbacks on the PEs. Make the loopback learnt on the remote PE through the tunnel/path that you want the eompls to take. Then establish the xconnect with this loopback. I am assuming that your question is that a particular eompls session should take a particular path.
    If you meant that certain traffic from the same eompls session take a different path/tunnel, then CBTS will work.
    Regards,
    Niranjan

  • Redundant access from MPLS VPN to global routing table

    Several our customers have MPLS VPNs deployed over our infrastructure. Part of them requires access to Internet (global routing table in our case).
    As I'm not aware of any methods how to dynamicaly import/export routes between VRF/Global routing tables, at the moment there are static routes configured - one inside VRF pointing to global next hop, another one in global routing table, pointing to interface inside VRF.
    Task is to configure redundant access to Internet. By redundancy I mean using several exit points (primary and backup), what physically represents separate boxes.
    Here comes tricky part - both global static routes (on both boxes, meaning) are valid and reachable in all cases - no matter if specific prefix is reachable in VRF or not. What I'd like to achieve is that specific static route becomes valid only if specific prefix is reachable inside VRF. Yea, sounds like dynamic routing :), I know
    OK, hope U got the idea. Any solutions/recommendations ? Running all Internet routing inside VRF isn't an option, at least for now :(

    Hi Andris,
    I did not mean to have a VRF on the CE. The CE would have both PVCs in the global routing table - his ONLY routing table in fact. One PVC would be used to announce routes into the customer specific VPN (VRF configured on the PE). The other PVC would allow for internet access through the PE (global IP routing table on the PE).
    dot1q will be ok as well.
    This way the CE can be a normal BGP peer to the PE, i.e. there is no MPLS VPN involved here. This allows all options of customer-ISP connectivity.
    Example:
    PE config:
    interface Serial0/0
    encapsulation frame-relay
    interface Serial0/0.1 point-to-point
    description customer VPN access
    ip vrf customer
    ip address 10.1.1.1 255.255.255.252
    interface Serial0/0.2 point-to-point
    description customer Internet access
    ip address 192.168.1.1 255.255.255.252
    router rip
    address-family ipv4 vrf customer
    version 2
    network 10.0.0.0
    no auto-summary
    redistribute bgp 65000 metric 5
    router bgp 65000
    neighbor 192.168.1.2 remote-as 65001
    address-family ipv4 vrf customer
    redistribute rip
    CE config:
    interface Serial0/0
    encapsulation frame-relay
    interface Serial0.1 point-to-point
    description VPN access
    ip address 10.1.1.2 255.255.255.252
    interface Serial0.2 point-to-point
    description Internet access
    ip address 192.168.1.2 255.255.255.252
    router bgp 65001
    neighbor 192.168.1.1 remote-as 65000
    router rip
    version 2
    network 10.0.0.0
    no auto-summary
    Of course you can replace RIP with whatever is suitable for you. And don´t sue me when you do not apply required BGP filters for internet access... ;-)
    The other option ("mini internet") would be feasible as well. Just make sure your BGP filters are NEVER messed up and additionally apply a limit on the numbers of prefixes in your VRF mini-internet.
    Regards
    Martin

  • Is possible to configure SLB per VRF??

    I have the Cat6500 with Sup720 and the IOS version 12.2(18)SXF8. From the documentation this software is SLB VRF-aware. But I can not configure SLB per VRF:-( I'm sending you the example of my configuration:
    ip vrf WEB
    rd 100:1
    ip slb probe WEB1 tcp
    port 443
    ip slb serverfarm WEB
    nat server
    probe WEB1
    real 212.67.72.228
    inservice
    real 212.67.72.244
    inservice
    ip slb vserver WEB-HTTPS
    virtual 212.67.72.150 tcp 443
    serverfarm WEB
    sticky 300 netmask 255.255.255.255
    advertise
    inservice
    interface vlan 30
    ip vrf forwarding WEB
    ip address 10.0.0.4 255.255.255.248
    interface vlan 10
    description Servery
    ip vrf forwarding WEB
    ip address 212.67.72.130 255.255.255.128
    interface gi0/1
    description Server WEB1
    switchport
    switchport access vlan 10
    switchport mode access
    no ip address
    spanning-tree portfast
    interface gi0/2
    switchport
    switchport access vlan 30
    switchport mode access
    no ip address
    spanning-tree portfast
    this configuration is functional without VRF, when I used the configuration with VRF - it is not functional:-(
    Can you help me? Thank you.
    Roman

    if the main server is up, the CSS will use it over the sorry_server.
    You can't tell the CSS not to use it if it is UP.
    Therefore, the only solution is to find a way to keep your main server down once it fails a keepalive.
    This can be done with a script that would issue the command 'suspend' once it detects the service missed a keepalive.
    The script can be a tcp keepalive script and instead of returning just a failure one the server is down, the script itself can generate the 'suspend' command.
    So, you then have time to sync your database and when ready you can do an 'active' under the service to start using it again.
    Gilles.

  • Can mpls support multicast?

    Hi,
    Can mpls support multicast packets?
    Meaning, can multicast packets be sent to destinations over mpls network?
    If so, how does it work?
    I read in this forum somewhere that someone mentioned mpls and multicast can co-eixt.
    What exactly does it mean?
    Thanx!

    In the MPLS network you can either use native multicast or you could implement mVPN on the PE routers if you implement MPLS VPN. mVPN uses native multicast in the core to encapsulate the multicast messages coming from a CE router and to forward these messages to PEs containing the same VRF.
    For more information on mVPN, see the following link:
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmltvpn.htm
    Hope this helps,

  • Tacacs per VRF

    Gooday
    Im trying to configure tacacs per Vrf but no luck, i been using docs from cisco, can somebody help me if my config is correct?
    here is my current config
    aaa group server tacacs+ tacacs1
    server-private 183.x.x.x key 7 XXXXXX
    ip vrf forwarding NMS
    ip tacacs source-interface Vlan89
    aaa authentication login default group tacacs+ enable
    aaa authentication enable default group tacacs+ enable
    aaa authorization commands 0 default group tacacs+ none
    aaa authorization commands 1 default group tacacs+ none
    aaa authorization commands 15 default group tacacs+ none
    ip vrf NMS
    description OOB NMS VRF
    rd 110:100
    interface Vlan89
    description to DIA monitoring
    ip vrf forwarding NMS
    ip address 183.109.191.11 255.255.255.0
    end
    ip vrf NMS
    thanks

    thanks Carlos,
    I followed your suggestion, i think there will be only change in the aaa authentication statement,
    I'm very careful on changing the aaa statement, and don't want to change it without your expert advice, the router is located in different country and no one will reboot if i lost the connection
    The first "password" prompt you get is for the local enable password? We might need to enable "Debug aaa authentication" and "debug tacacs" and recreate the issue.
    ans: yes, first it will ask for the local password
    below is the debug
    AAA Authentication debugging is on
    crt-tw1-602#
    *Jan 18 00:39:40: AAA/BIND(00000084): Bind i/f 
    *Jan 18 00:39:40: AAA/AUTHEN/LOGIN (00000084): Pick method list 'default'
    *Jan 18 00:39:45: AAA/AUTHEN/ENABLE(00000084): Processing request action LOGIN
    *Jan 18 00:39:45: AAA/AUTHEN/ENABLE(00000084): Done status GET_PASSWORD
    *Jan 18 00:39:52: AAA/AUTHEN/ENABLE(00000084): Processing request action LOGIN
    *Jan 18 00:39:52: AAA/AUTHEN/ENABLE(00000084): Done status PASS
    *Jan 18 00:39:54: AAA: parse name=tty450 idb type=-1 tty=-1
    *Jan 18 00:39:54: AAA: name=tty450 flags=0x11 type=5 shelf=0 slot=0 adapter=0 port=450 channel=0
    *Jan 18 00:39:54: AAA/MEMORY: create_user (0x62673AC0) user='NULL' ruser='crt-tw1-602' ds0=0 port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=NONE priv=0 initial_task_id='0', vrf= (id=0)
    *Jan 18 00:39:54: AAA/MEMORY: free_user (0x62673AC0) user='NULL' ruser='crt-tw1-602' port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=NONE priv=0 vrf= (id=0)
    *Jan 18 00:39:54: AAA: parse name=tty450 idb type=-1 tty=-1
    *Jan 18 00:39:54: AAA: name=tty450 flags=0x11 type=5 shelf=0 slot=0 adapter=0 port=450 channel=0
    *Jan 18 00:39:54: AAA/MEMORY: create_user (0x7067DF54) user='NULL' ruser='NULL' ds0=0 port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=ENABLE priv=15 initial_task_id='0', vrf= (id=0)
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): port='tty450' list='' action=LOGIN service=ENABLE
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): using "default" list
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:39:54: TAC+: send AUTHEN/START packet ver=192 id=-165001963
    *Jan 18 00:39:54: TAC+: ver=192 id=-165001963 received AUTHEN status = GETUSER
    *Jan 18 00:39:54: AAA/AUTHEN(4129965333): Status=GETUSER
    *Jan 18 00:40:06: AAA/AUTHEN/CONT (4129965333): continue_login (user='(undef)')
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Status=GETUSER
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:40:06: TAC+: send AUTHEN/CONT packet id=-165001963
    *Jan 18 00:40:06: TAC+: ver=192 id=-165001963 received AUTHEN status = GETPASS
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Status=GETPASS
    *Jan 18 00:40:09: AAA/AUTHEN/CONT (4129965333): continue_login (user='lesterm.admin')
    *Jan 18 00:40:09: AAA/AUTHEN(4129965333): Status=GETPASS
    *Jan 18 00:40:09: AAA/AUTHEN(4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:40:09: TAC+: send AUTHEN/CONT packet id=-165001963
    *Jan 18 00:40:10: TAC+: ver=192 id=-165001963 received AUTHEN status = PASS
    *Jan 18 00:40:10: AAA/AUTHEN(4129965333): Status=PASS
    *Jan 18 00:40:10: AAA/MEMORY: free_user (0x7067DF54) user='lesterm.admin' ruser='NULL' port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=ENABLE priv=15 vrf= (id=0)
    crt-tw1-602#
    crt-tw1-602#debug tacacs
    TACACS access control debugging is on
    crt-tw1-602#
    *Jan 18 00:41:44: TPLUS: Queuing AAA Authentication request 133 for processing
    *Jan 18 00:41:44: TPLUS: processing authentication start request id 133
    *Jan 18 00:41:44: TPLUS: Authentication start packet created for 133()
    *Jan 18 00:41:44: TPLUS: Using server 183.111.21.100
    *Jan 18 00:41:44: TPLUS(00000085)/0/NB_WAIT/7050EE30: Started 5 sec timeout
    *Jan 18 00:41:49: TPLUS(00000085)/0/NB_WAIT/7050EE30: timed out
    *Jan 18 00:41:49: TPLUS(00000085)/0/NB_WAIT/7050EE30: timed out, clean up
    *Jan 18 00:41:49: TPLUS(00000085)/0/7050EE30: Processing the reply packet
    *Jan 18 00:41:58: TAC+: no tacacs servers defined in group "tacacs+"
    *Jan 18 00:41:58: TAC+: send AUTHEN/START packet ver=192 id=1096121892
    *Jan 18 00:41:58: TAC+: Using default tacacs server-group "tacacs1" list.
    *Jan 18 00:41:58: TAC+: Opening TCP/IP to 183.111.21.100/49 timeout=5
    *Jan 18 00:41:58: TAC+: Opened TCP/IP handle 0x7065A0B8 to 183.111.21.100/49 using source 183.109.191.11
    *Jan 18 00:41:58: TAC+: 183.111.21.100 (1096121892) AUTHEN/START/LOGIN/ASCII queued
    *Jan 18 00:41:58: TAC+: (1096121892) AUTHEN/START/LOGIN/ASCII processed
    *Jan 18 00:41:58: TAC+: ver=192 id=1096121892 received AUTHEN status = GETUSER
    *Jan 18 00:42:02: TAC+: send AUTHEN/CONT packet id=1096121892
    *Jan 18 00:42:02: TAC+: 183.111.21.100 (1096121892) AUTHEN/CONT queued
    *Jan 18 00:42:02: TAC+: (1096121892) AUTHEN/CONT processed
    *Jan 18 00:42:02: TAC+: ver=192 id=1096121892 received AUTHEN status = GETPASS
    *Jan 18 00:42:09: TAC+: send AUTHEN/CONT packet id=1096121892
    *Jan 18 00:42:09: TAC+: 183.111.21.100 (1096121892) AUTHEN/CONT queued
    *Jan 18 00:42:10: TAC+: (1096121892) AUTHEN/CONT processed
    *Jan 18 00:42:10: TAC+: ver=192 id=1096121892 received AUTHEN status = FAIL
    *Jan 18 00:42:10: TAC+: Closing TCP/IP 0x7065A0B8 connection to 183.111.21.100/49
    *Jan 18 00:42:12: TAC+: no tacacs servers defined in group "tacacs+"
    *Jan 18 00:42:12: TAC+: send AUTHEN/START packet ver=192 id=-1420048987
    *Jan 18 00:42:12: TAC+: Using default tacacs server-group "tacacs1" list.
    *Jan 18 00:42:12: TAC+: Opening TCP/IP to 183.111.21.100/49 timeout=5
    *Jan 18 00:42:12: TAC+: Opened TCP/IP handle 0x62741B98 to 183.111.21.100/49 using source 183.109.191.11
    *Jan 18 00:42:12: TAC+: 183.111.21.100 (2874918309) AUTHEN/START/LOGIN/ASCII queued
    *Jan 18 00:42:12: TAC+: (2874918309) AUTHEN/START/LOGIN/ASCII processed
    *Jan 18 00:42:12: TAC+: ver=192 id=-1420048987 received AUTHEN status = GETUSER
    *Jan 18 00:42:16: TAC+: send AUTHEN/CONT packet id=-1420048987
    *Jan 18 00:42:16: TAC+: 183.111.21.100 (2874918309) AUTHEN/CONT queued
    *Jan 18 00:42:16: TAC+: (2874918309) AUTHEN/CONT processed
    *Jan 18 00:42:16: TAC+: ver=192 id=-1420048987 received AUTHEN status = GETPASS
    *Jan 18 00:42:19: TAC+: send AUTHEN/CONT packet id=-1420048987
    *Jan 18 00:42:19: TAC+: 183.111.21.100 (2874918309) AUTHEN/CONT queued
    *Jan 18 00:42:20: TAC+: (2874918309) AUTHEN/CONT processed
    *Jan 18 00:42:20: TAC+: ver=192 id=-1420048987 received AUTHEN status = PASS
    *Jan 18 00:42:20: TAC+: Closing TCP/IP 0x62741B98 connection to 183.111.21.100/49
    crt-tw1-602#
    crt-tw1-602#
    AAA Authentication debugging is on
    crt-tw1-602#
    *Jan 18 00:39:40: AAA/BIND(00000084): Bind i/f 
    *Jan 18 00:39:40: AAA/AUTHEN/LOGIN (00000084): Pick method list 'default'
    *Jan 18 00:39:45: AAA/AUTHEN/ENABLE(00000084): Processing request action LOGIN
    *Jan 18 00:39:45: AAA/AUTHEN/ENABLE(00000084): Done status GET_PASSWORD
    *Jan 18 00:39:52: AAA/AUTHEN/ENABLE(00000084): Processing request action LOGIN
    *Jan 18 00:39:52: AAA/AUTHEN/ENABLE(00000084): Done status PASS
    *Jan 18 00:39:54: AAA: parse name=tty450 idb type=-1 tty=-1
    *Jan 18 00:39:54: AAA: name=tty450 flags=0x11 type=5 shelf=0 slot=0 adapter=0 port=450 channel=0
    *Jan 18 00:39:54: AAA/MEMORY: create_user (0x62673AC0) user='NULL' ruser='crt-tw1-602' ds0=0 port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=NONE priv=0 initial_task_id='0', vrf= (id=0)
    *Jan 18 00:39:54: AAA/MEMORY: free_user (0x62673AC0) user='NULL' ruser='crt-tw1-602' port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=NONE priv=0 vrf= (id=0)
    *Jan 18 00:39:54: AAA: parse name=tty450 idb type=-1 tty=-1
    *Jan 18 00:39:54: AAA: name=tty450 flags=0x11 type=5 shelf=0 slot=0 adapter=0 port=450 channel=0
    *Jan 18 00:39:54: AAA/MEMORY: create_user (0x7067DF54) user='NULL' ruser='NULL' ds0=0 port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=ENABLE priv=15 initial_task_id='0', vrf= (id=0)
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): port='tty450' list='' action=LOGIN service=ENABLE
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): using "default" list
    *Jan 18 00:39:54: AAA/AUTHEN/START (4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:39:54: TAC+: send AUTHEN/START packet ver=192 id=-165001963
    *Jan 18 00:39:54: TAC+: ver=192 id=-165001963 received AUTHEN status = GETUSER
    *Jan 18 00:39:54: AAA/AUTHEN(4129965333): Status=GETUSER
    *Jan 18 00:40:06: AAA/AUTHEN/CONT (4129965333): continue_login (user='(undef)')
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Status=GETUSER
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:40:06: TAC+: send AUTHEN/CONT packet id=-165001963
    *Jan 18 00:40:06: TAC+: ver=192 id=-165001963 received AUTHEN status = GETPASS
    *Jan 18 00:40:06: AAA/AUTHEN(4129965333): Status=GETPASS
    *Jan 18 00:40:09: AAA/AUTHEN/CONT (4129965333): continue_login (user='lesterm.admin')
    *Jan 18 00:40:09: AAA/AUTHEN(4129965333): Status=GETPASS
    *Jan 18 00:40:09: AAA/AUTHEN(4129965333): Method=tacacs1 (tacacs+)
    *Jan 18 00:40:09: TAC+: send AUTHEN/CONT packet id=-165001963
    *Jan 18 00:40:10: TAC+: ver=192 id=-165001963 received AUTHEN status = PASS
    *Jan 18 00:40:10: AAA/AUTHEN(4129965333): Status=PASS
    *Jan 18 00:40:10: AAA/MEMORY: free_user (0x7067DF54) user='lesterm.admin' ruser='NULL' port='tty450' rem_addr='183.100.2.99' authen_type=ASCII service=ENABLE priv=15 vrf= (id=0)
    crt-tw1-602#
    crt-tw1-602#debug tacacs
    TACACS access control debugging is on
    crt-tw1-602#
    *Jan 18 00:41:44: TPLUS: Queuing AAA Authentication request 133 for processing
    *Jan 18 00:41:44: TPLUS: processing authentication start request id 133
    *Jan 18 00:41:44: TPLUS: Authentication start packet created for 133()
    *Jan 18 00:41:44: TPLUS: Using server 183.111.21.100
    *Jan 18 00:41:44: TPLUS(00000085)/0/NB_WAIT/7050EE30: Started 5 sec timeout
    *Jan 18 00:41:49: TPLUS(00000085)/0/NB_WAIT/7050EE30: timed out
    *Jan 18 00:41:49: TPLUS(00000085)/0/NB_WAIT/7050EE30: timed out, clean up
    *Jan 18 00:41:49: TPLUS(00000085)/0/7050EE30: Processing the reply packet
    *Jan 18 00:41:58: TAC+: no tacacs servers defined in group "tacacs+"
    *Jan 18 00:41:58: TAC+: send AUTHEN/START packet ver=192 id=1096121892
    *Jan 18 00:41:58: TAC+: Using default tacacs server-group "tacacs1" list.
    *Jan 18 00:41:58: TAC+: Opening TCP/IP to 183.111.21.100/49 timeout=5
    *Jan 18 00:41:58: TAC+: Opened TCP/IP handle 0x7065A0B8 to 183.111.21.100/49 using source 183.109.191.11
    *Jan 18 00:41:58: TAC+: 183.111.21.100 (1096121892) AUTHEN/START/LOGIN/ASCII queued
    *Jan 18 00:41:58: TAC+: (1096121892) AUTHEN/START/LOGIN/ASCII processed
    *Jan 18 00:41:58: TAC+: ver=192 id=1096121892 received AUTHEN status = GETUSER
    *Jan 18 00:42:02: TAC+: send AUTHEN/CONT packet id=1096121892
    *Jan 18 00:42:02: TAC+: 183.111.21.100 (1096121892) AUTHEN/CONT queued
    *Jan 18 00:42:02: TAC+: (1096121892) AUTHEN/CONT processed
    *Jan 18 00:42:02: TAC+: ver=192 id=1096121892 received AUTHEN status = GETPASS
    *Jan 18 00:42:09: TAC+: send AUTHEN/CONT packet id=1096121892
    *Jan 18 00:42:09: TAC+: 183.111.21.100 (1096121892) AUTHEN/CONT queued
    *Jan 18 00:42:10: TAC+: (1096121892) AUTHEN/CONT processed
    *Jan 18 00:42:10: TAC+: ver=192 id=1096121892 received AUTHEN status = FAIL
    *Jan 18 00:42:10: TAC+: Closing TCP/IP 0x7065A0B8 connection to 183.111.21.100/49
    *Jan 18 00:42:12: TAC+: no tacacs servers defined in group "tacacs+"
    *Jan 18 00:42:12: TAC+: send AUTHEN/START packet ver=192 id=-1420048987
    *Jan 18 00:42:12: TAC+: Using default tacacs server-group "tacacs1" list.
    *Jan 18 00:42:12: TAC+: Opening TCP/IP to 183.111.21.100/49 timeout=5
    *Jan 18 00:42:12: TAC+: Opened TCP/IP handle 0x62741B98 to 183.111.21.100/49 using source 183.109.191.11
    *Jan 18 00:42:12: TAC+: 183.111.21.100 (2874918309) AUTHEN/START/LOGIN/ASCII queued
    *Jan 18 00:42:12: TAC+: (2874918309) AUTHEN/START/LOGIN/ASCII processed
    *Jan 18 00:42:12: TAC+: ver=192 id=-1420048987 received AUTHEN status = GETUSER
    *Jan 18 00:42:16: TAC+: send AUTHEN/CONT packet id=-1420048987
    *Jan 18 00:42:16: TAC+: 183.111.21.100 (2874918309) AUTHEN/CONT queued
    *Jan 18 00:42:16: TAC+: (2874918309) AUTHEN/CONT processed
    *Jan 18 00:42:16: TAC+: ver=192 id=-1420048987 received AUTHEN status = GETPASS
    *Jan 18 00:42:19: TAC+: send AUTHEN/CONT packet id=-1420048987
    *Jan 18 00:42:19: TAC+: 183.111.21.100 (2874918309) AUTHEN/CONT queued
    *Jan 18 00:42:20: TAC+: (2874918309) AUTHEN/CONT processed
    *Jan 18 00:42:20: TAC+: ver=192 id=-1420048987 received AUTHEN status = PASS
    *Jan 18 00:42:20: TAC+: Closing TCP/IP 0x62741B98 connection to 183.111.21.100/49
    crt-tw1-602#
    crt-tw1-602#

  • Per VRF label

    Hi,
    Would like to know if per VRF label is supported on 7600 platform with SUP7203BXL?If yes can anybody share the config details

    Anup,
    It is currently supported via the following hidden command:
    [no] mpls label mode { vrf | all-vrfs } protocol bgp-vpnv4 { per-prefix|per-vrf}
    Regards,

Maybe you are looking for