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é

Similar Messages

  • Interface goes down with mds9140

    Hi
    I've a problem with both MDS 9140. The fc interface goes down and don't go up when I reboot a device connected to them with a fiber. To solved the problem I need to remove the gbic and plug it back again. I use the following version of software
    Software
    BIOS: version 1.0.8
    loader: version 1.1(2)
    kickstart: version 1.2(1a)
    system: version 1.2(1a)
    Fabrice

    It is probably a software defect where if a port is up for over 248 days, Once link is lost, it will not come back w/o a shut/no shut or manual intervention as you describe. This issue is resolved in the 1.3.4b and above code. For a 91xx, this would be a disruptive upgrade. Or, simply issue a shut/no shut on an affected port and you'll be good for another 248 days.

  • OSPF with ipsec VTI interface goes down before dead timer.

    I have a strange issue that OSPF will initially start working, hellos are exchanged both ways but then after about 3 – 6 hellos one of the sides stops getting them and the ipsec VTI tunnel drops on router A even before the dead timer reaches 0. Is this default behavior, when OSPF is over a VTI interface if it doesn’t receive hellos is drops the tunnel?
    I’m at a loss as to what is going on since it looks like only one neighbor stops receiving hellos, router A, for a brief period of time. This VTI tunnel is going over another provider’s FW and they have assured me the tunnel destination/source ips are wide open they also sent me the ACL and I can verify this. The weird thing is if I enable EIGRP it works great with no issues. On router B I am using the same source/ip unnumbered  interface on multiple VTI tunnels to to other destinations but this shouldn’t cause any issues I don’t think. I have never had an issue like this and from what I can tell the router A just stops briefly getting hellos after 3 – 6 initial hellos and drops the protocol on the VTI interface. If I set the dead timer on router A long enough it will stop receiving hellos but stay up and then after a while you get “LOADING to FULL” as the hellos start coming in again.  Again the tunnel goes over a cisco 800 which I have no control over it and a potential FW before that but I saw the ACL and ip is being allowed. I was thinking this could be a trolling issue on the FW but it doesn’t explain why EIGRP works.  FYI I was having a recursive routing issue before but I have since fixed that and the issue still continues.
    ********  it turns out that i was using the same source ip on multiple tunnels. IPsec would get confused with packets coming in and would deliver packets to the wrong tunnel interface. This was solved but using the key command with a different key number on each set of tunnels with the shared profile command
    "If more than one mGRE tunnel is configured on a router that use the same tunnel source address, the shared keyword must be added to the tunnel protection command on all such tunnel interfaces. Each mGRE tunnel interface still requires a unique tunnel key, NHRP network-ID, and IP subnet address. This is common on a branch router when a dual DMVPN cloud topology is deployed. "
    Router A:
    router ospf 1
    router-id 10.213.22.2
    passive-interface default
    network x.x.97.26 0.0.0.0 area 0
    interface Tunnel1
    ip unnumbered GigabitEthernet0/1
    ip virtual-reassembly in
    ip tcp adjust-mss 1398
    ip ospf network point-to-point
    load-interval 30
    tunnel source GigabitEthernet0/1
    tunnel mode ipsec ipv4
    tunnel destination x.x.173.109
    tunnel path-mtu-discovery
    tunnel protection ipsec profile VTI-to-NB
    router B:
    router ospf 1
    router-id 172.17.2.6
    priority 1
    redistribute static subnets route-map Lan-static-RM
    passive-interface default
    no passive-interface Tunnel1
    no passive-interface Tunnel4
    no passive-interface Tunnel5
    network x.x.173.109 0.0.0.0 area 0
    network 172.17.2.6 0.0.0.0 area 0
    network 192.168.1.47 0.0.0.0 area 0
    interface Tunnel4
    ip unnumbered GigabitEthernet0/2
    ip virtual-reassembly in
    ip tcp adjust-mss 1398
    ip ospf network point-to-point
    load-interval 30
    tunnel source GigabitEthernet0/2
    tunnel mode ipsec ipv4
    tunnel destination x.x.97.26
    tunnel path-mtu-discovery
    tunnel protection ipsec profile VTI_NB_to_dorrance_prv
    end
    thanks P

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    I haven't studied your config, but I can tell you I have production environment using OSPF across VTI  (and GRE, and GRE/IPSec and DMVPN) tunnels without issue.  I.e. so OSPF can be okay with VTI tunnels.

  • Redundacy Not happening after interface goes down.

    Dear All,
    I have the set up which I have attached. To brief, I have 2 CSS 11501 in two different locations connected each other via fibre and running redundnacy protocol on the link as heartbeat.
    The problem I am facing is if the interface through which the services are running fails the redundancy is not happening the master remains the master and the standby is standby and we have a services unavailable.
    the configuration is given below
    CSS_ACTIVE# sh run
    !Generated on 03/07/2010 22:26:21
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      username admin des-password lcof1eugqece2afd superuser
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      ip redundancy master
      app
      app session 10.90.1.2
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDBY PORT 9"
      bridge vlan 23
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.20 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.1 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_ACTIVE#  
    CSS_STANDBY# sh run
    !Generated on 03/07/2010 22:31:42
    !Active version: sg0810106
    configure
    !*************************** GLOBAL ***************************
      ip redundancy
      bridge spanning-tree disabled
      arp timeout 1400
      no restrict web-mgmt
      app
      app session 10.90.1.1
      ip route 10.50.3.0 255.255.255.0 10.50.9.1 1
    !************************* INTERFACE *************************
    interface e1
      description "TRUNK "
      trunk
      vlan 11
        default-vlan
      vlan 20
      vlan 21
    interface e9
      description "REDUNDANCY - CSS-STANDY PORT 9"
      bridge vlan 23
    interface Ethernet-Mgmt
      phy 10Mbits-FD
      admin-shutdown
    !************************** CIRCUIT **************************
    circuit VLAN11
      description "MANAGEMENT IP ADDRESS"
      ip address 10.7.10.21 255.255.255.0
    circuit VLAN20
      description "CSS_SERVER_VLAN"
      redundancy
      ip address 10.50.7.4 255.255.255.0
    circuit VLAN21
      description "CSS_CLIENT_VLAN"
      redundancy
      ip address 10.50.9.7 255.255.255.0
    circuit VLAN23
      description "REDUNDANT LINK TO CSS-STANDBY"
      ip address 10.90.1.2 255.255.255.0
        redundancy-protocol
    !************************** SERVICE **************************
    service Web1
      ip address 10.50.7.5
      active
    service Web2
      ip address 10.50.7.6
      active
    !*************************** OWNER ***************************
    owner KIM
      content web
        add service Web1
        add service Web2
        vip address 10.50.9.2
        advanced-balance sticky-srcip
        active
    CSS_STANDBY#
    If the interface e1 fails on active the redundancy is not shifting to standby.

    You have setup box-to-box redundancy.
    This mechanism is very basic and only detects a box failure.  So, as long as the master can send heartbeat through the 'redundancy protocol' interface it will stay master.
    You should use interface/vip redundancy.
    A little bit more complex to configure but much more robust and with more features including interface failure detection.
    http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v8.20_v8.10/configuration/redundancy/guide/VIPRedun.html
    Gilles.

  • Network ce0 interface goes down when reboots  or does not come up

    Hi,
    Have a V440 and on reboot the main ip ce0 is not up. I have to manually go in and ifconfig 192.168.1.3 up
    My hostname.ce0
    192.168.1.3
    # wc /etc/hostname.ce0
    2 1 13 /etc/hostname.ce0
    # ifconfig -a
    lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
    ce0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.3 netmask ffffff00 broadcast 192.168.1.255
    ether 0:3:ba:d5:ba:2b
    ce0:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.76 netmask ffffff00 broadcast 192.168.1.255
    ce0:4: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.72 netmask ffffff00 broadcast 192.168.1.255
    ce0:5: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.66 netmask ffffff00 broadcast 192.168.1.255
    ce0:6: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.47 netmask ffffff00 broadcast 192.168.1.255
    ce0:7: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.42 netmask ffffff00 broadcast 192.168.1.255
    ce0:8: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.69 netmask ffffff00 broadcast 192.168.1.255
    ce0:9: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.88 netmask ffffff00 broadcast 192.168.1.255
    ce0:10: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.45 netmask ffffff00 broadcast 192.168.1.255
    ce0:11: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.90 netmask ffffff00 broadcast 192.168.1.255
    ce0:12: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.98 netmask ffffff00 broadcast 192.168.1.255
    ce0:13: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.73 netmask ffffff00 broadcast 192.168.1.255
    ce0:14: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.87 netmask ffffff00 broadcast 192.168.1.255
    ce0:15: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.48 netmask ffffff00 broadcast 192.168.1.255
    ce0:16: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.103 netmask ffffff00 broadcast 192.168.1.255
    ce0:17: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.44 netmask ffffff00 broadcast 192.168.1.255
    ce0:18: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.78 netmask ffffff00 broadcast 192.168.1.255
    ce0:19: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.46 netmask ffffff00 broadcast 192.168.1.255
    ce0:21: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.56 netmask ffffff00 broadcast 192.168.1.255
    ce0:22: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.77 netmask ffffff00 broadcast 192.168.1.255
    ce0:23: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.80 netmask ffffff00 broadcast 192.168.1.255
    ce0:24: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.83 netmask ffffff00 broadcast 192.168.1.255
    ce0:25: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.84 netmask ffffff00 broadcast 192.168.1.255
    ce0:26: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.67 netmask ffffff00 broadcast 192.168.1.255
    ce0:28: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.41 netmask ffffff00 broadcast 192.168.1.255
    ce0:29: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.64 netmask ffffff00 broadcast 192.168.1.255
    ce0:30: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.57 netmask ffffff00 broadcast 192.168.1.255
    ce0:31: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.71 netmask ffffff00 broadcast 192.168.1.255
    ce0:32: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.86 netmask ffffff00 broadcast 192.168.1.255
    ce0:33: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.59 netmask ffffff00 broadcast 192.168.1.255
    ce0:34: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.65 netmask ffffff00 broadcast 192.168.1.255
    ce0:35: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.104 netmask ffffff00 broadcast 192.168.1.255
    ce0:36: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.97 netmask ffffff00 broadcast 192.168.1.255
    ce0:37: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.70 netmask ffffff00 broadcast 192.168.1.255
    ce0:38: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.74 netmask ffffff00 broadcast 192.168.1.255
    ce0:39: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.79 netmask ffffff00 broadcast 192.168.1.255
    ce0:41: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.68 netmask ffffff00 broadcast 192.168.1.255
    ce0:42: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.43 netmask ffffff00 broadcast 192.168.1.255
    ce0:43: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.85 netmask ffffff00 broadcast 192.168.1.255
    ce0:44: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.105 netmask ffffff00 broadcast 192.168.1.255
    ce0:45: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.60 netmask ffffff00 broadcast 192.168.1.255
    ce0:46: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.82 netmask ffffff00 broadcast 192.168.1.255
    ce0:47: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.96 netmask ffffff00 broadcast 192.168.1.255
    ce0:48: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.94 netmask ffffff00 broadcast 192.168.1.255
    ce0:49: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.81 netmask ffffff00 broadcast 192.168.1.255
    ce0:50: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.106 netmask ffffff00 broadcast 192.168.1.255
    ce0:51: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.53 netmask ffffff00 broadcast 192.168.1.255
    ce0:52: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.91 netmask ffffff00 broadcast 192.168.1.255
    ce0:53: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.49 netmask ffffff00 broadcast 192.168.1.255
    ce0:54: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.63 netmask ffffff00 broadcast 192.168.1.255
    ce0:55: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.102 netmask ffffff00 broadcast 192.168.1.255
    ce0:56: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.62 netmask ffffff00 broadcast 192.168.1.255
    ce0:57: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.107 netmask ffffff00 broadcast 192.168.1.255
    ce0:58: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.130 netmask ffffff00 broadcast 192.168.1.255
    ce0:59: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.131 netmask ffffff00 broadcast 192.168.1.255
    ce0:60: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.132 netmask ffffff00 broadcast 192.168.1.255
    ce0:61: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.134 netmask ffffff00 broadcast 192.168.1.255
    ce0:62: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.135 netmask ffffff00 broadcast 192.168.1.255
    ce0:63: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.136 netmask ffffff00 broadcast 192.168.1.255
    ce0:64: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.138 netmask ffffff00 broadcast 192.168.1.255
    ce0:65: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.139 netmask ffffff00 broadcast 192.168.1.255
    ce0:66: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.140 netmask ffffff00 broadcast 192.168.1.255
    ce0:67: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.141 netmask ffffff00 broadcast 192.168.1.255
    ce0:68: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.142 netmask ffffff00 broadcast 192.168.1.255
    ce0:69: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.143 netmask ffffff00 broadcast 192.168.1.255
    ce0:70: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.145 netmask ffffff00 broadcast 192.168.1.255
    ce0:71: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.146 netmask ffffff00 broadcast 192.168.1.255
    ce0:72: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.147 netmask ffffff00 broadcast 192.168.1.255
    ce0:73: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.151 netmask ffffff00 broadcast 192.168.1.255
    ce0:74: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.152 netmask ffffff00 broadcast 192.168.1.255
    ce0:75: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.153 netmask ffffff00 broadcast 192.168.1.255
    ce0:76: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.154 netmask ffffff00 broadcast 192.168.1.255
    ce0:77: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.155 netmask ffffff00 broadcast 192.168.1.255
    ce0:78: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.156 netmask ffffff00 broadcast 192.168.1.255
    ce0:79: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.157 netmask ffffff00 broadcast 192.168.1.255
    ce0:80: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.158 netmask ffffff00 broadcast 192.168.1.255
    ce0:81: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.189 netmask ffffff00 broadcast 192.168.1.255
    ce0:82: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.211 netmask ffffff00 broadcast 192.168.1.255
    ce0:83: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.212 netmask ffffff00 broadcast 192.168.1.255
    ce0:84: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.213 netmask ffffff00 broadcast 192.168.1.255
    ce0:85: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.214 netmask ffffff00 broadcast 192.168.1.255
    ce0:86: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.215 netmask ffffff00 broadcast 192.168.1.255
    ce0:87: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.216 netmask ffffff00 broadcast 192.168.1.255
    ce0:88: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.217 netmask ffffff00 broadcast 192.168.1.255
    ce0:89: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.218 netmask ffffff00 broadcast 192.168.1.255
    ce0:90: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
    inet 192.168.1.219 netmask ffffff00 broadcast 192.168.1.255
    lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
    inet6 ::1/128
    Any help would be great!
    Thanks
    Marc

    msglobal3 wrote:
    Hi,
    Have a V440 and on reboot the main ip ce0 is not up. I have to manually go in and ifconfig 192.168.1.3 up
    My hostname.ce0
    192.168.1.3
    # wc /etc/hostname.ce0
    2 1 13 /etc/hostname.ce0The 'wc' output shows that you have a blank line in the file.
    Remove that line (so that 'wc' reports only 1 line present) and the interface will be brought up at boot time.
    Darren

  • When log in into CC,  AcrobatX activation goes down

    Hi, I have CS6 with Acrobat X. After I installed Adobe CC (without Acrobat XI) and sign in,activation on Acrobat X goes down. When I hit button Activate I saw the mail adress is not my mail CS6 registration and appears e-mail from Adobe ID for CC.If continue (change mail, enter serial num e.t.c. Acrobat is ok, but CC is signed out). I use older Acrobat beacouse  my Pit stopPro version require AcrobatX. My question is how can I use both products for which I paid?

    Hi stoyand52938926,
    Please let me know if that is not your email id, then what id is being shown while you activate.
    Were you trying to sign in with new id that is not registered at Adobe.com
    Please refer the KB doc link mentioned below to understand more on "sign in" issues while activating:
    Activation & Deactivation Help
    Hope this helps.
    Regards,
    Anubha

  • L2TP script to initiate a router reload when tunnel goes down - working

    Hi,
         Just thought I would post a working EEM script on doing a router reload when the L2TP tunnel goes down....
    I am using a 3825 router to initiate a site-to-site tunnel with a 3rd party vpn service - StrongVPN.  On the odd occasion when the tunnel goes down, the l2tp tunnel state goes to "no session left" and the virtual-ppp1 interface - which is tied to the l2tp vpn - goes down.  Unfortunately, because I have no control on the far end router, the only way to bring it back up is thru a router reload....
    Here you go:
    event manager applet L2TP-DOWN
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to down"
    action 1.0 syslog msg "The L2TP VPN is down"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload in 10" pattern "confirm"
    action 1.3 cli command ""
    action 1.4 syslog msg "EEM scheduled reload in 10 minutes"
    event manager applet L2TP-UP
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to up"
    action 1.0 syslog msg "The L2TP VPN is up"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload cancel"
    Jason

    Hi Arie,
         So, here is the script I am using....
    When the L2TP tunnel goes to "no sessions left", the virtual-ppp1 interface goes down.  That's the typical message I get when it goes down.  So, when I reboot the router, the script shows the message that the virtual-ppp1 interface is up when the L2TP tunnel comes up.  I checked the debugs and that is the behaviour when the tunnel goes up / down...
    Here you go:
    event manager applet L2TP-DOWN
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to down"
    action 1.0 syslog msg "The L2TP VPN is down"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload in 10" pattern "confirm"
    action 1.3 cli command ""
    action 1.4 syslog msg "EEM scheduled reload in 10 minutes"
    event manager applet L2TP-UP
    event syslog pattern "%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-PPP1, changed state to up"
    action 1.0 syslog msg "The L2TP VPN is up"
    action 1.1 cli command "enable"
    action 1.2 cli command "reload cancel"
    Thanks.

  • 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   

  • 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

  • I have a new sound bar that I plug my phone into through the headphone jack. I also have a bluetooth speaker that I want to play through as well. Is there anyway I can play to both devices at once?

    I have a speaker that I am connecting through my headphone jack but I have a bluetooth speaker in another room that I want to play through as well. Is there anyway I can play to both speakers at once? I saw another post on line that suggested going to the Audio MIDI setup and adding additional output devices. The problem is, I see that on my computer but nothing for my iphone. Can this work? I have also seen things for airplay and of course this is all making my mind fuzzy. Help!

    Sure-glad to help you. You will not lose any data by changing synching to MacBook Pro from imac. You have set up Time Machine, right? that's how you'd do your backup, so I was told, and how I do my backup on my mac.  You should be able to set a password for it. Save it.  Your stuff should be saved there. So if you want to make your MacBook Pro your primary computer,  I suppose,  back up your stuff with Time machine, turn off Time machine on the iMac, turn it on on the new MacBook Pro, select the hard drive in your Time Capsule, enter your password, and do a backup from there. It might work, and it might take a while, but it should go. As for clogging the hard drive, I can't say. Depends how much stuff you have, and the hard drive's capacity.  As for moving syncing from your iMac to your macbook pro, should be the same. Your phone uses iTunes to sync and so that data should be in the cloud. You can move your iTunes Library to your new Macbook pro
    you should be able to sync your phone on your new MacBook Pro. Don't know if you can move the older backups yet-maybe try someone else, anyways,
    This handy article from Apple explains how
    How to move your iTunes library to a new computer - Apple Support''
    don't forget to de-authorize your iMac if you don't want to play purchased stuff there
    and re-authorize your new macBook Pro
    time machine is an application, and should be found in the Applications folder. it is built in to OS X, so there is nothing else to buy. double click on it, get it going, choose the Hard drive in your Time capsule/Airport as your backup Time Machine  and go for it.  You should see a circle with an arrow on the top right hand of your screen (the Desktop), next to the bluetooth icon, and just after the wifi and eject key (looks sorta like a clock face). This will do automatic backups  of your stuff.

  • Program becomes active at startup - don't want it to

    I have a program installed by a guy I use to help me with installation of hardware and software on my new IMAC.  He has set up a program which becomes active at startup so if needed he can take control of my system.  I manually turn this off after system starts up but I would like to remove it from the startup process but don't know how to go about doing that.  
    Would appreciate advice as to how this can be done.
    Thanks

    The following is a long shot.  You may or may not have this folder:  Macintosh HD>Library>Startupitems (folder).  Trash the program if it is inside.
    Macintosh HD>System>Library>Startupitems (folder).  Same as above.
    ==============
    If the above does not work, suggest that you have this friend uninstall what ever it was he installed on your computer.  You should then run OS Recovery, repair permissions & restart your comp afterwards.
    Apple has a built in program called Screen Sharing that you both can use.  Suggest that you research the various Knowledge Base Articles regarding it.  Another resource: 
    How to troubleshoot a friend’s Mac from afar: fix your friend’s Apple Mac remotely with Screen Sharing
    Suggest that you check into purchasing OS X Yosemite: The Missing Manual.  Very easy reading & very detailed = non technical.
    on my new IMAC
    FYI only...
    Please read the warranty paperwork that came w/your computer.
    You have 14 days to return the computer w/no questions asked.
    You have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.
    Strongly suggest that you take FULL advantage of the above before it runs out.  Let Apple deal w/the problems & your concerns. It's what you paid them to do.
    *** While under warranty and/or AppeCare, you do not want to do anything that will void out your warranty.  Hopefully, you will consider purchasing AppleCare if you have not already done so.  Home tech support/repairs for iMacs if necessary.***
    GOOD LUCK!

  • Sticky issue when failed server become active

    Hi,
    We are operating the ace(csm) and using the sticky option.
    Assuming that We have two servers with sicky for redundancy and being opreated active - active, 
    I realized that if one server go down and go up, Csm dosen't forword packet to restored server.
    I think it is due to the sticky option. We need csm to play loadbalancing two servers once one is restored immediately.
    Is there anything opinion or solution?
    Thanks,

    If a real goes down (fails probe) then the csm will remove it from service and not send connections to it. The entry will also be removed from the sticky table. When it comes back, it will receive new connections when it is elgible. If all incoming connections match existing sticky entries then it will take time to gather load. If you configure "predictor leastcons" under the serverfarm and limit the sticky life, then it will allow the failed real to recover load quicker. Matthew

  • How long need to wait before apple developer program (personal) become activated?

    Hi,
    I received the payment confirmation email after purchasing the Apple developer program 6 hours ago.
    But the developer program is not activated yet. My apple ID: [email protected]
    How long need to wait before apple developer program (personal) become activated?
    Thanks

    Check your enrollement status by going to https://developer.apple.com/membercenter/
    If you still cant get in after 24 hours contact apple at https://developer.apple.com/contact/

  • ITunes Connect and "contract becoming active" question

    When setting a price for my app, this appears:
    Your contract for this price tier is being reviewed and is not yet active. Your application will be available on the App Store once your contract becomes active.
    Does this mean I am still missing something I am supposed to provide? All the bank and tax, etc., info is in and everything shows green checkmarks.
    Is it just a matter of waiting for Apple to double-check everything I entered?
    How much time does that usually take?
    Thanks!
    doug

    OK. Thanks. I guess it is just a matter of waiting.
    Just when you think everything is done, you run into another hurdle!
    doug

  • One interface of pair goes down

    Hi
    If two interfaces are paired into one group and one interface of pair goes down, will the second interface will be declared as down by IPS?

    Hi,
    I I have a problem connected to this issue.
    I have only one IPS4270-20 with software 7.0(7)E4 and I use 2 IF pairs on it. Both IF pairs are for the same operation, and they were implemented for HA purposes. We have two 6500 chassis in VSS and all of the IPS ports connected to these switches. Gi3/0-Gi3/1 and Gi1/2-Gi3/3 are in pair, and Gi3/0-Gi3/2 are the inbound and Gi3/1-Gi3/3 are the outbound interfaces, so it achieves the hardwer failover requirements. Inbound IFs creat an Etherchannel, and outbound IFs creat an other Etherchannel, so we try to prevent an L2 loop when VSS breaks.
    The issue what I can't solve is the following:
    If I shut down the 6500 IF what is connected to the IPS Gi3/0 I would like Gi3/1 to goes down, but it isn't the case.
    I tried to use LACP in the Etherchannel, so when Gi3/0 goes down, the 6500 port which connected to the IPS Gi3/1 should be removed from the Etherchannel, but it isn't the case also.
    Do you have an idea, what could be the problem, or I should redesign the topology?
    Thanks,
    Miki

Maybe you are looking for