10-25-2005 02:45 AM - edited 03-03-2019 12:33 AM
Hello all,
First off, I just came to this office and am getting familiar with the network. I came across this Cat4000 that is giving this error message every couple minutes:
Local7.Error 205.110.68.4 594718: Oct 25 14:41:21.120 ba: %STANDBY-3-DIFFVIP1: Vlan1 Group 1 active routers virtual
Local7.Error 205.110.68.4 594719: IP address 172.16.208.1 is different to the locally configured
Local7.Error 205.110.68.4 594720: address 192.168.0.1
I did a "sh vlan" and this is the Vlan 1 configuration:
interface Vlan1
ip address 172.16.208.140 255.255.248.0
no ip redirects
no ip route-cache
no ip mroute-cache
standby 1 ip 192.168.0.1
standby 1 priority 100
standby 1 preempt
Now... I am unfamiliar with the "standby" command, but I know there is no machine on the network with a 192.x address.
And the strange thing is, all 20 something of the VLANs are defined in the "sh run" yet the "sh vtp status" has the Cat4000 as a VTP CLIENT, not SERVER. I managed to find another Cat4000 on the network that was acting as the SERVER and had the VLANs defined there also.
...Help? hah.
Thanx for looking and let me know if I need to provide more info...
Solved! Go to Solution.
10-25-2005 02:56 AM
The standby commands are used to configure HSRP, the Hot Standby Redundancy Protocol:
http://www.cisco.com/en/US/tech/tk648/tk362/tk321/tsd_technology_support_sub-protocol_home.html
It looks indeed as if this is not a correct configuration as one would expect the hsrp-subnet to exist in the network. You might try to remove these commands using the "no " prefix:
no standby 1 ip 192.168.0.1
no standby 1 priority 100
no standby 1 preempt
Regards,
Leo
10-25-2005 03:04 AM
Hello,
Seems there is another switch on your lan configured with an HSRP group 1 with VIP address 172.16.208.1.
Seems there is a config mismatch, looks like the config dump you posted should contain:
standby 1 ip 172.16.208.1
instead of
standby 1 ip 192.168.0.1
(as 172.16.208.0/21 is the vlan1 local subnet, 172.16.208.1 seems more logical).
Posting the other switch's config would help anyway.
and, AFAIK, VTP does not change interface vlan ip nor standby group vips, but only propagates l2 vlan configuration.
Cheers,
10-25-2005 02:56 AM
The standby commands are used to configure HSRP, the Hot Standby Redundancy Protocol:
http://www.cisco.com/en/US/tech/tk648/tk362/tk321/tsd_technology_support_sub-protocol_home.html
It looks indeed as if this is not a correct configuration as one would expect the hsrp-subnet to exist in the network. You might try to remove these commands using the "no " prefix:
no standby 1 ip 192.168.0.1
no standby 1 priority 100
no standby 1 preempt
Regards,
Leo
10-25-2005 02:56 AM
Hi
Standby configs are related to your HSRP configurations and the error messages clearly tells that the virtual ip which is configured in this box is different when compared to the one configured for the group.
in the other box its being configured as 172.16.208.1 but in your box its 192.168.0.1.
i would suggest to change the standby ip to 172.16.208.1 in this box and check out for the logs.
regds
10-25-2005 03:04 AM
Hello,
Seems there is another switch on your lan configured with an HSRP group 1 with VIP address 172.16.208.1.
Seems there is a config mismatch, looks like the config dump you posted should contain:
standby 1 ip 172.16.208.1
instead of
standby 1 ip 192.168.0.1
(as 172.16.208.0/21 is the vlan1 local subnet, 172.16.208.1 seems more logical).
Posting the other switch's config would help anyway.
and, AFAIK, VTP does not change interface vlan ip nor standby group vips, but only propagates l2 vlan configuration.
Cheers,
10-25-2005 03:34 AM
Well,
Thanx much for all the quick responses. Since they were all pretty much dead on and each one helped, I tried to give them all "5" or however you do it. Internet connection is really slow, so I may have missed one.
I changed the "standby 1 ip 172.X..." like someone mentioned and it appears to have worked. I haven't received any more error messages!
Now, I shall create a new post asking about the VTP setup 8)
Look out for a post called "Defining VLANs?"
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: