HSRP track interface (ASR9k v4.2.3)

Hi all,
I was trying to configure the track interface command within hsrp, and when I apply the command the priority group decrement immediately.
Before of apply the configuration:
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh hsrp bvi 600
Thu Sep 12 14:04:07.548 UTC
                       P indicates configured to preempt.
                       |
Interface      Grp Pri P State   Active addr     Standby addr   Group addr   
BV600            1 110 P Active  local           200.10.10.3    200.10.10.1
Then, I apply track interface:
router hsrp
interface BVI600
  address-family ipv4
   hsrp 1 version 1
    timers 1 3
    preempt
    priority 110
    address 200.10.10.1
    track GigabitEthernet0/3/0/26 20
And priority decrement:
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh hsrp bvi 600
Thu Sep 12 14:05:20.302 UTC
                       P indicates configured to preempt.
                       |
Interface      Grp Pri P State   Active addr     Standby addr   Group addr   
BV600            1  90 P Standby 200.10.10.3     local          200.10.10.1 
Why priority decrement if the interface is always up?
Regards.

No. That´s why I am asking why the priority decrement if the interface is always UP.
Look:
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh inter gi 0/3/0/26
Fri Sep 13 10:41:55.907 UTC
GigabitEthernet0/3/0/26 is up, line protocol is up
Without track command:
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh hsrp bvi 600
Fri Sep 13 10:42:30.411 UTC
                       P indicates configured to preempt.
                       |
Interface      Grp Pri P State   Active addr     Standby addr   Group addr    
BV600            1 110 P Active  local           200.10.10.3    200.10.10.1   
After I apply track command:
router hsrp
interface BVI600
  address-family ipv4
   hsrp 1 version 1
    timers 1 3
    preempt
    priority 110
    address 200.10.10.1
    track GigabitEthernet0/3/0/26 20
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh inter gi 0/3/0/26
Fri Sep 13 10:44:28.498 UTC
GigabitEthernet0/3/0/26 is up, line protocol is up
RP/0/RSP0/CPU0:PE1-ASR9010-LAB-MACUL#sh hsrp bvi 600                
Fri Sep 13 10:44:43.139 UTC
                       P indicates configured to preempt.
                       |
Interface      Grp Pri P State   Active addr     Standby addr   Group addr    
BV600            1  90 P Standby 200.10.10.3     local          200.10.10.1   

Similar Messages

  • What is a good multi track interface to use w/ GB

    I use garageband quite frequently and now I want to multitrack. I have always used a tascam 8 track but I am finally making the switch to full computer. My first goal is to record a 3 peice band I am in. So I was thinking a 8 track interface that uses USB possibly. I have a white 09 macbook but I will be upgrading soon if that makes a difference. Also another question which I am wondering is should I even try a different program? Or is GB all I need? I am in Kiel Germany.
    Thanks!
    -c

    Does your macbook have Firewire? If it does then I would suggest you go with a FW interface. The choice of interface depnds on how you decide to record your band, ie one member at a time or all simultaniously. Check out the PreSonus line of gear as one option. I use the FireStudio Mobile without a hitch in GB.
    The choice of computer depends on what road blocks you encounter. Depending on your budget, there are RAM and HD upgrades avaliable that you can DIY including SSD. http://www.macsales.com/ The other thing you may find with your macbook is screen real estate or lack thereof.
    GB is a very capable program, however, there are some workflow issues that may not suit you. The beauty of GB is that it is not bloated. I think you will find initially setting up your recording environment and collecting gear to be more of an issue that which program to use.

  • Two Mics using Audio Buddy and Fast Track Interface

    Hey,
    the problem i am having is that i am trying to have both mics being used to record at the same time. both are plugged into the AudioBuddy pre-amp, which is plugged into the fast track interface, which is connected to the computer. in logic, i have two different audio tracks opened, one with input one, and the other with input two, but i can only get pick-up from one mic. suggestions?
    thanks

    NewSouth wrote:
    Hey,
    the problem i am having is that i am trying to have both mics being used to record at the same time. both are plugged into the AudioBuddy pre-amp, which is plugged into the fast track interface, which is connected to the computer. in logic, i have two different audio tracks opened, one with input one, and the other with input two, but i can only get pick-up from one mic. suggestions?
    thanks
    Are you getting signal at the Audio Buddy (green leds both light up)?
    On the Fast Track interface, I see only ONE mic input and ONE 1/4" input. In their website, I see that it is a SWITCHABLE INPUT.
    http://www.m-audio.com/products/en_us/FastTrackUSB.html
    " switchable instrument/line input (1/4”) "
    This means you can only record ONE input at a time, not both at the same time.
    You will need a larger interface in order to record two or more signals at once.
    Cheers

  • Question: ACE FT Track Interface

    Hi all,
    I have two ACE appliances installed with HA configuration. I have 5 vlans (Vlan1, Vlan2, Vlan3, Vlan4 and Vlan5) come from 1 trunk interface. I have 1 ADMIN context and 1 PRODUCTION context. I have configured FT Interface, FT Group and FT Peer in ADMIN context only. I have allocate Vlan1 in ADMIN Context only and assign VLAN2, VLAN3, VLAN4 and VLAN5 for PRODUCTION context. The L3 Interface of VLAN2, VLAN3, VLAN4 and VLAN5 are all configured in PRODUCTION context.
    My question is how can I track the interface for VLAN2, VLAN3, VLAN4 and VLAN5? Should I configure FT Track Interface in ADMIN context or configure FT Track Interface in PRODUCTION context so that any VLAN interface down will trigger the failover.
    Appreciate who can help me on this question. Thanks

    The FT group can't be configured in a non-Admin context.
    switch/User2(config)# ft gr?
    % invalid command
    All FT groups MUST be configued in Admin and allocated in Admin to a context.
    ft group 112
    peer 1
    peer priority 90
    associate-context User2
    inservice
    switch/Admin#
    The only FT commands inside a context are :
    switch/User2(config)# ft ?
    auto-sync Enable auto sync
    track Configure Fault Tolerance tracking for switchover
    switch/User2(config)# ft
    And, yes, if tracking configured in a context will reduce priority to its associated group configured in Admin.
    Gilles.

  • HSRP both become active once tracked interface goes down

    Hi team,
    I was doing a fail-over testing for several sites for a customer.(dual CE router setup)
    I have two routers 08R & 09R with following HSRP config.
    with this configuration 08R is active & 09R is secondary.. all good
    but when I shutdown the Serial link on active router(08R). both become active and standby unknown
    they can ping each other, checked ARP table, all good.
    also removed track statement on backup router (09R) but no joy...
    put the debug on
    Please advise.
    08R#sh run int f0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30  <---hsrp ip
    standby 1 priority 105<------------------- when s0/0/0 down, becomes 95
    standby 1 preempt
    standby 1 track Serial0/0/0.100
    09R#sh run int f0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 priority 101  <-------
    standby 1 preempt
    standby 1 track Serial0/1/0:0.100<-----------also tracking its own serial interface (removed this as its not required but still not working)
    Debug on 08R
    Jun 25 08:51:33.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30  <---sending hellos with lower priority 95, no in pkts
    Jun 25 08:51:36.554 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:51:37.978 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Debug on 09R
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:00.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  in  10.58.0.29 Active  pri 95 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Coup   out 10.58.0.31 Active  pri 101 vIP 10.58.0.30
    Jun 25 08:52:03.542 GMT: HSRP: Fa0/0 Grp 1 Hello  out 10.58.0.31 Active  pri 101 vIP 10.58.0.30

    Try this:
    Router 08R Configuration
    track 100 interface Serial0/0/0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.29 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 105
    standby 1 track 100 decrement 10
    Router 09R Configuration
    track 100 interface Serial0/1/0:0.100 ip routing
    interface FastEthernet0/0
    ip address 10.58.0.31 255.255.255.0
    standby 1 ip 10.58.0.30
    standby 1 preempt
    standby 1 priority 101
    standby 1 track 100 decrement 10
    Ref.: CCO
    /André

  • Hsrp track 2 LAN

    hallo , i have a question if my configuration for dual HSRP is correct, and if the HSRP failover works with nat
    thank you
    ROUTER 1
    ========
    track 10 interface GigabitEthernet0/1 line-protocol
    track 20 interface GigabitEthernet0/0 line-protocol
    interface GigabitEthernet0/0
    ip address 172.16.1.11 255.255.0.0
    ip nat inside
    ip virtual-reassembly
    duplex auto
    speed auto
    standby 10 ip 172.16.1.10
    standby 10 priority 110
    standby 10 preempt
    standby 10 authentication
    standby 10 track 10 decrement 20
    interface GigabitEthernet0/1
    ip address 87.248.47.37 255.255.255.224
    ip access-group 116 in
    ip nat outside
    ip virtual-reassembly
    duplex auto
    speed auto
    standby 20 ip 87.248.47.36
    standby 20 priority 110
    standby 20 preempt
    standby 20 authentication
    standby 20 track 20 decrement 20
    ROUTER 2
    ========
    track 10 interface GigabitEthernet0/1 line-protocol
    track 20 interface GigabitEthernet0/0 line-protocol
    interface GigabitEthernet0/0
    ip address 172.16.1.12 255.255.0.0
    ip nat inside
    ip virtual-reassembly
    duplex auto
    speed auto
    standby 10 ip 172.16.1.10
    standby 10 priority 95
    standby 10 preempt
    standby 10 authentication
    standby 10 track 10 decrement 20
    interface GigabitEthernet0/1
    ip address 87.248.47.38 255.255.255.224
    ip access-group 116 in
    ip nat outside
    ip virtual-reassembly
    duplex auto
    speed auto
    standby 20 ip 87.248.47.36
    standby 20 priority 95
    standby 20 preempt
    standby 20 authentication
    standby 20 track 20 decrement 20
    FOR ANY ROUTER
    ==============
    ip forward-protocol nd
    ip nat pool xxx
    ip nat inside source list 56 pool .... overload
    ip nat inside source static a.a.a.a b.b.b.b
    ip route x.x.x.x 255.255.252.0 87.248.47.xx
    ip route y.y.y.y 255.255.255.255 87.248.47.xx
    access-list 56 permit any
    access-list 116 permit tcp host ..............
    access-list 116 permit ......................
    access-list 116 deny  ip any any

    I do not see anything that is "incorrect" in the syntax of this config for HSRP. I will comment that you may not get the results that you expect if you track the line protocol of the GigEthernet interfaces, especially on the LAN side. Since the router connections are through a switch it is quite possible that you will lose the ability to communicate between HSRP peers but that the interface line protocol will stay up on the active router. I will also question if the connections on G0/1 are really through a router how you will get both interfaces into the same subnet. It is not an issue on router 1 or router 2 but how does the other router have 2 routed ports in the same subnet?
    I am slightly confused about your second question. You seem to be asking does HSRP work when you are running NAT. I can not think of anything about NAT that would impact HSRP failover. But if your question is really about whether running NAT is impacted when you run HSRP then I believe that the answer is that if traffic has been running through router 1 and a set of translations have been built on router 1 and then you failover to router 2 then there will not be the same set of translations on that router. So there would be some impact on traffic in that case.
    HTH
    Rick

  • HSRP Interface Tracking Question

    I have a pair of 7206 routers for Internet access.  The Internet was provided over OC3, and used interface POS1/0.  I just upgraded the Internet to Ethernet so now the interface is GigabitEthernet 0/3.
    I just discovered that there there is another interface that uses POS1/0 as an HSRP tracking interface.  So my question is:   Can I just remove the old tracking interface and add the new one? Or is there another prefered method to do this?
    My current HSRP interface:
    interface GigabitEthernet0/1.21
     description INET
     encapsulation dot1Q 21
     ip address x.x.x.x 255.255.255.240
     ip broadcast-address x.x.x.x
     no ip redirects
     ip accounting output-packets
     ip flow ingress
     ip nbar protocol-discovery
     no snmp trap link-status
     standby 1 ip x.x.x.x
     standby 1 priority 105
     standby 1 preempt
     standby 1 track POS1/0
    Thanks!
    Ray

    Ray
    While it is correct that you can just change the HRP interface to track the Ethernet interface be aware that it may not work quite the same way. With POS and most serial interface implementations if communications with the peer is lost then the loss of keepalives will change the interface state to line protocol down and that is what the interface tracking is looking for. However with an Ethernet interface if you lose communication with the peer the interface may still be in a line protocol up state. In that circumstance interface tracking will not detect the problem.
    HTH
    Rick

  • HSRP / interface tracking and not only…

    Hi All,
    HSRP provides nice feature of tracking an “external” interface, while taking decision with regard to active HSRP router election.
    What I would like to ask you is as follows:
    In my network all routing decisions are based on Layer2 protocol (NSAP addresses in ATM). On a top of this, I have pure IP network without any dynamic routing protocol (neither OSPF nor BGP is not supported on ATM boxes). Now I would like to bring ATM interface down for a gateway, which does not work as an active HSRP router.
    As I mentioned before Layer2 takes a decision for traffic a traffic flow. I’m afraid under certain circumstances traffic may hit ATM interface attached the standby router. So what next? Won’t be properly routed via HSRP pair. Is my understanding correct?
    I would like to have activated only one ATM interface running on active HSRP router, on the standby line protocol should be down. When HSRP re-election process takes place, newly activated router becomes active and in the first order changes protocol line to active. Is that possible?
    Just as a last remark, ATM interfaces are monitored (tracked) only. Standby group is configured on Ethernet ports.
    Regards,
    Artur

    Hello Artur,
    HSRP 'tracking' feature is solely to take down the 'HSRP STATUS' to up or down and it has no bearing on the actual line protocol state of the interface.
    So if you desire that HSRP should bring down the ATM interface, then that is not possible. HSRP tracking would only change the 'priority' of that interface and not bring it down/up.
    Let me know if i understood and answered your question correctly,

  • HSRP Interface Tracking on ATM Sub-Interface?

    I want to enable HSRP interface tracking to monitor an ATM sub-interface. As I understand it, when using the (standby 1 track <interface>) command, the HSRP group priority will be decremented only if the line protocol goes down on the interface being tracked. For this reason I need to track an ATM sub-interface (i.e. atm1/0.77). I am wondering if this will work properly. Has anyone ever used this configuration successfully?

    Hi Friend,
    I find no reason why it should not work?
    When it work for serial subinterface and frame relay interfces it should also work for atm subinterface.
    I have implemented in serial subinterface.
    Yes it should work fine. Go ahead and implement and update the status.
    Regards,
    Ankur

  • Nexus 5548UP - HSRP and vPC, tracking required?

    Hi,
    We've got two Nexus 5548UPs that are vPC and HSRP peers.
    I've had some feedback that I should incorporate the tracking function to close the vPC down in the case of a layer 3 problem, the thing is I'm not sure it's required. I can see in this article it recommends implementing tracking when your L2 peer-link and L3 interfaces are on the same module (which it is in my case).. http://www.cisco.com/en/US/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
    But in this article it says not to use tracking.. http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/design_guide_c07-625857.pdf
    Any one got any real world experience and can offer some feedback.. I don't mind putting it in just want to understand why.
    Thanks,
    Nick.

    Hi Nick
    there is two tracking can be use din nexus enviroment
    HSRP tracking and vPC tracking
    for using one line card for the vPC peer link vPC tracking is recomnded
    HSRP tracking is used to track L3 uplinks to the core
    Using vPC with HSRP/VRRP object tracking may leads to traffic blackholing in case object tracking is triggered
    its better to use separate L3 inter switch link instead of using HSRP tracking
    hope this help

  • ACE to track user interface

    Hello,
    Just a few questions on a HA lab to track the user interface. If i configure the primary ACE in the admin-context like this:
    ft interface vlan 402    ---->>> FT VLAN
      ip address <primary_ip>
      peer ip address <secondary_ip>
      no shutdown
    ft peer 1
      heartbeat interval 300
      heartbeat count 10
      ft-interface vlan 402
    ft group 4     --->> group associated to user-context Juniper
       peer 1
       priority 200     --->>> primary is 200 and secondary is 100
       associate-context Juniper
       inservice
    and in the user-context of the primary ACE:
    ft track interface vlan202   ---->>> VLAN 202 is where VIPs are configured in the Juniper user-context
      track-interface vlan 202
    peer track-interface vlan 202
      priority 110
    peer priority 100
    1.- the command "peer-track interface" is useful in case the primary ACE and secondary ACE are not connected on vlan 202 via the same single switch? i guess without this command the secondary wouldnt track the user interface 202.
    2.- Do i need to specify "peer priority 100" in  the user context for the secondary ACE? Is it used to set the priority of the secondary once the primary becomes standby? Default is 100 for secondary so i think its not useful.
    3.- Can i configure preempt delay in ACE?
    Thanks,
    Giulio.

    Hi Giulio
    Could you please check 'ft group 4' configuration on your standby ACE?
    Probably, you configure 'priority 105' on standby too. If so, please change configuration
    from 'priority 105' to 'peer priority 105' on standby ACE.
    # active admin context
    ft group 4
      peer 1
      priority 105
      associate-context Juniper
      inservice
    # standby admin context
    ft group 4
      peer 1
      peer priority 105  <<==
      associate-context Juniper
      inservice
    I checked your configuration and found you configured ft group for Juniper context only.
    This means Admin context is not sync'ed. (I was misled into thinking that your admin
    context is also sync'ed.)
    If ft group for admin context is configured, you configure 'priority 105' on active admin context
    only since 'priority 105' configuration is automatically converted to 'peer priority 105' and set
    to standby ACE.
    However, if ft group for admin context is not configured, your should configure both active and
    standby ACE manually. Furthermore, you have to convert them by hand.
    Since admin context of my ACE appliance is synced as below, I only configured 'ft group 4'
    on active ACE. (Standby ACE was automatically set 'peer priority 105'.)
    This behavior is same with module and appliance.
    # my ace appliance configuration
    ACE4710a/Admin# sh run ft | b group
    Generating configuration....
    ft group 1
      peer 1
      priority 105
      associate-context Admin
      inservice
    ft group 4
      peer 1
      priority 105
      associate-context test
      inservice
    ACE4710a/Admin# sh ft gr sum
    FT Group                     : 1
    Configured Status            : in-service
    Maintenance mode             : MAINT_MODE_OFF
    My State                     : FSM_FT_STATE_ACTIVE
    My Config Priority           : 105
    My Net Priority              : 105
    My Preempt                   : Enabled
    Peer State                   : FSM_FT_STATE_STANDBY_HOT
    Peer Config Priority         : 100
    Peer Net Priority            : 100
    Peer Preempt                 : Enabled
    Peer Id                      : 1
    No. of Contexts              : 1
    FT Group                     : 4
    Configured Status            : in-service
    Maintenance mode             : MAINT_MODE_OFF
    My State                     : FSM_FT_STATE_ACTIVE
    My Config Priority           : 105
    My Net Priority              : 105
    My Preempt                   : Enabled
    Peer State                   : FSM_FT_STATE_STANDBY_HOT
    Peer Config Priority         : 100
    Peer Net Priority            : 100
    Peer Preempt                 : Enabled
    Peer Id                      : 1
    No. of Contexts              : 1
    ACE4710a/Admin#
    Regards,
    Yuji

  • Is it an HSRP Bug?

    Hi,
    I have implemented HSRP betwen Cisco 1841 & Cisco 1700. and used Standby Track command.
    1841>
    interface FastEthernet0/0
    ip address 10.4.0.2 255.255.252.0
    duplex auto
    speed auto
    standby 1 ip 10.4.0.1
    standby 1 priority 254
    standby 1 preempt
    standby 1 track Serial0/0/0 100
    1751>
    interface FastEthernet0/0
    ip address 10.4.0.3 255.255.252.0
    duplex auto
    speed auto
    standby 1 ip 10.4.0.1
    standby 1 priority 250
    The show standby Command on 1841 is as follows:
    1841#show standby
    FastEthernet0/0 - Group 1
    State is Active
    4 state changes, last state change 01:49:46
    Virtual IP address is 10.4.0.1
    Active virtual MAC address is 0000.0c07.ac01
    Local virtual MAC address is 0000.0c07.ac01 (v1 default)
    Hello time 3 sec, hold time 10 sec
    Next hello sent in 0.244 secs
    Preemption enabled
    Active router is local
    Standby router is 10.4.0.3, priority 250 (expires in 8.108 sec)
    Priority 154 (configured 254)
    Track interface Serial0/0/0 state Down decrement 100
    IP redundancy name is "hsrp-Fa0/0-1" (default)
    YB-MUMNP-P-1841#
    I have made the serial 0/0/0 link down (not by Serial Shutdown command, but by switching off the link)
    If you see, the priority of the 1841 router is 154, as compared to 250 of 1751,
    Yet 1841 is Active router.
    Is there somethin i hv missed, or the router is misbehaving?
    rgds
    Sumedh

    Hi amit,
    I was having the same dilemna while preparing for my BCMSN - CCNP exam :) Consider this scenario
    Router A with HSRP priority 50 with no preempt configured
    Router B with HSRP priority 25 with preempt enabled.
    Assume router A is the first HSRP router on the LAN segment it becomes the default active forwarder and begins forwarding data. Now router B comes up and since it has preempt configured, it will preempt router A. However since it has lesser priority it will fail.
    Assume router A fails (i.e the hold down timer expires after not recieving 3 consecutive hellos) now router B becomes the default active forwarder.
    So far so good.
    If router A comes back online, it will start sending hellos, but since it is NOT configured with the preempt command, router A will not set the preempt flag and hence router B will continue being the active forwarder until the time it actually goes down or an administrator manually does the needful.
    Now if Router A was configured with standby preempt, Router A would correctly set the preempt flag and since it has higher priority it would correctly be set as the active forwarder once again
    Hope I understood your problem correctly and gave the right explanation.

  • ACE redundancy tracking and failure detection

    Hello,
    I have configured redundancy on a pair of ACEs, and looking now for the most approriate method of failure detection.
    In the admin guide, 3 possible methodes are explained: host tracking, interface tracking and HSRP group tracking.
    I don't have HSRP configured on the Supervisors in the ACEs chassis, the default gateway is on other chassis, so HSRP tracking is not an option.
    The ACEs are configured in routed mode.
    I have 1 VLAN with all VIPs, and 4 server VLANs.
    There are 2 contexts active.
    I was thinking of tracking all 5 VLAN interfaces + tracking the default gateway on client side.
    Would this be a good approach?
    thanks in advance for your input.

    Hi ,
    The ACE supports a maximum of 4,093 VLANs per system and a maximum of 1,024 shared VLANs per system.
    Alos note that the ACE supports a maximum of 8,192 interfaces per system that include VLANs, shared VLANs, and BVI interfaces.
    Regards,
    Sachin

  • HSRP preempt

    Hi,
    I would need some advise to clarify on the following HSRP preempt concept. Please let me know if the following is correct.
    1) both active and standby routers NOT configured with HSRP preempt. When active router goes down, standby will NOT take over due to NO HSRP preempt configured.
    2) both active and standby routers configured with HSRP preempt. When active router goes down, standby will take over as the active. When the active goes down again, the standby will take over as active. However, there will be a short downtime during the HSRP transition states. How long is the transition state?
    3) only standby router configured with HSRP preempt. When active router goes down, standby will take over to become the active. However, when the active router goes down again, the standby router will NOT take over as the active due to NO HSRP preempt configured.
    Thanks
    Christina

    Christina
    1) Not correct. If both routers do not include preempt and the active router goes down then the standby router WILL take over as the active. Preempt is not an issue here. If the currently active router goes down and if there is a standby then the standby will take over as active. In a failure situation the standby will take over without consideration of preempt.
    2) I am not entirely clear what you are describing when you say the active goes down and then when the active goes down again. So let me re-phrase it in terms of rtrA and rtrB. Assume that rtrA has a higher priority and becomes active and rtrB is standby. Then rtrA goes down. rtrB then becomes active. At that point I do not follow your scenario. I am not sure whether you assume that rtrA comes back into service or if you assume that there is rtrC which became standby.
    If rtrA comes into service again and it has higher priority and it has preempt then rtrA becomes active and rtrB returns to standby. This is because preempt on rtrA allows it to displace rtrB. There is some very brief period of transition. I am not sure how long but I know it is quite short.
    If rtrB became active and there is rtrC who becomes standby and then rtrB fails then rtrC becomes active and there is no period of interruption.
    3)I have the same problem with this description. You describe active and standby, you assume that the active fails, and then you assume that the active fails again without specifying whether the original active router came back in service again.
    So let me go back to my example of rtrA and rtrB. Assume that rtrA has higher priority and becomes active and does not have preempt. Assume that rtrB has lower priority and does have preempt. Then rtrA goes down. rtrB becomes active. (Note that this really has nothing to do with preempt - rtrB takes over because the active failed.) If rtrA comes into service then it is in the HSRP group and it has higher priority but it does not become active because it does not have preempt.
    Preempt really has to do with enabling a router that has higher priority but is not active to displace the current active router. Preempt is a factor when some router attempts to displace the current active router. It is not a factor when the active router fails.
    Let me describe another example. Assume rtrA has priority of 105 and rtrB has priority of 100. So rtrA becomes the active router. Then assume that rtrA is tracking interface serial0/0 and the interface goes down. Now rtrA has priority 95 and rtrB has priority 100. Will rtrB become active? With preempt configured it will and without prempt configured it will not.
    HTH
    Rick

  • ACE - FT tracking

    Existng setup:
    SW-Dist1 SW-Dist2
    | |
    SW1 SW2
    ACE 1 --- ACE2
    Active
    C1
    C2
    C3
    where C1-3 are contexts, all contexts are active in ACE1.
    These ACE are modules in 6504 switches.
    SW1 and SW2 respectively.
    SW1 and SW2 are trunked to Distribution Switches via port channels.
    Requirement is to implement failover by tracking uplink port-channel availability.
    How to achieve this? Any help is much appreciated.

    With ACE you have 3 tracking options
    you can track host (an ip), track an Interface and an HSRP group.
    Tracking interface option is applicable for VLAN interfaces only. It cannot track port channel/ physical interface.
    In your case the best option would be to track HSRP group configured on the uplink devices.
    More details at
    http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A2/configuration/administration/guide/redundcy.html#wp1024578
    Syed Iftekhar Ahmed

Maybe you are looking for