05-05-2005 05:51 AM
CSS VIPs Redundancy falls over for few seconds every week
Question: Can I change the Max Failures of the Keep alive AUTO_nexthop00001?
We have CSS in Redundant VIP setup.
We using on Active CSS an Critical Server script ap-kal-pinglist name is up_downstream
It seems that the active CSS stops working almost every week now for a few seconds.
APR 22 09:23:20 5/1 1651 NETMAN-2: Enterprise:Service Transition:nexthop00001 -> down
APR 22 09:23:22 5/1 1655 NETMAN-2: Enterprise:Service Transition:up_downstream -> down
APR 22 09:23:27 5/1 1659 VRRP-4: SNMP Trap Vrouter 10.1.114.5 change to state Backup
APR 22 09:23:27 5/1 1660 VRRP-4: Virtual router 2: backup on interface 10.1.114.5
APR 22 09:23:27 5/1 1661 VRRP-4: Master is 10.1.114.6
APR 22 09:23:27 5/1 1662 VRRP-4: SNMP Trap Vrouter 10.1.110.51 change to state Backup
APR 22 09:23:27 5/1 1663 VRRP-4: Virtual router 1: backup on interface 10.1.110.51
APR 22 09:23:27 5/1 1664 VRRP-4: Master is 10.1.110.52
APR 22 09:23:27 5/1 1665 VRRP-4: SNMP Trap Vrouter 10.1.108.5 change to state Backup
APR 22 09:23:27 5/1 1666 VRRP-4: Virtual router 1: backup on interface 10.1.108.5
APR 22 09:23:27 5/1 1667 VRRP-4: Master is 10.1.108.6
APR 22 09:23:28 5/1 1668 IPV4-4: Duplicate IP address detected: 10.1.114.4 00-00-5e-00-01-02
APR 22 09:23:28 5/1 1669 IPV4-4: Incoming CE 0x3001f00, incoming (0 based) SLP 0xc
APR 22 09:23:28 5/1 1670 IPV4-4: Duplicate IP address detected: 10.1.110.6 00-00-5e-00-01-01
APR 22 09:23:28 5/1 1671 IPV4-4: Incoming CE 0x3001f05, incoming (0 based) SLP 0xc
APR 22 09:23:28 5/1 1673 IPV4-4: Duplicate IP address detected: 10.1.108.4 00-00-5e-00-01-01
APR 22 09:23:28 5/1 1674 IPV4-4: Incoming CE 0x3001f01, incoming (0 based) SLP 0xc
APR 22 09:23:37 5/1 1675 VRRP-4: SNMP Trap Vrouter 10.1.114.5 change to state Master
APR 22 09:23:37 5/1 1676 VRRP-4: Virtual router 2: master on interface 10.1.114.5
APR 22 09:23:37 5/1 1677 VRRP-4: SNMP Trap Vrouter 10.1.110.51 change to state Master
APR 22 09:23:37 5/1 1678 VRRP-4: Virtual router 1: master on interface 10.1.110.51
APR 22 09:23:37 5/1 1679 VRRP-4: SNMP Trap Vrouter 10.1.108.5 change to state Master
APR 22 09:23:37 5/1 1680 VRRP-4: Virtual router 1: master on interface 10.1.108.5
So the Next hop auto generated keep alive of de default gateway is down
This triggered the Critical server script up_downstream and the BOX False over.
Sound all very normal but the IP number 10.1.114.1 is available.
CSS-active#sh keepalive AUTO_nexthop00001
Name: AUTO_nexthop00001 Index: 0 State: Alive
Description: Auto generated for service nexthop00001
Address: 10.1.114.1 Port: Any
Type: ICMP
Frequency: 5
Max Failures: 3
Retry Frequency: 5
Dependent Services:
nexthop00001
05-06-2005 04:53 AM
instead of using a script to monitor nexthop0001, why don't you create a service with icmp keepalive so you can control yourself frequency and max failures.
There is no way to change the auto_nexthop00001 max failures.
Gilles.
05-06-2005 06:10 AM
did not suspect the auto_nexthop00001 will automaticly removed, if I create a keepalive services myself.
Thanks a lot!
05-06-2005 12:11 PM
actually, the CSS will keep the auto_nexthop0001.
If you want to get rid of it, you need the command "ip no-implicit-service" and then reboot.
Regards,
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide