[c-nsp] Nexus HSRP issues

[Raph Skrzypaszek]

Agreed, we are using a Nexus 5548 with a Layer 3 module in our DC and HSRP works fine.

Raph

On 10/08/2013, at 6:39 AM, Lars Christensen <perseusdk at gmail.com> wrote:

> Hi,
> 
> The Nexus 5000 series does not support L3, and therefore it doesn't support HSRP.
> 
> If you'll want to use the 5000 series for layer 3, you would need the 5500 series with the L3 module.
> 
> Lars Christensen
> CCIE #20292
> 
> 
> Den 09/08/2013 kl. 15.33 skrev Christian Kildau <ckildau at plusline.de>:
> 
>> sw2# sh run int vlan200
>> 
>> !Command: show running-config interface Vlan200
>> !Time: Fri Aug  9 13:32:04 2013
>> 
>> version 5.2(1)N1(5)
>> 
>> interface Vlan200
>> no shutdown
>> description vlan fuer HNAS 10.8.200.0/24 - HSRP 10.8.200.1
>> no ip redirects
>> ip address 10.8.200.3/24
>> hsrp version 2
>> hsrp 1
>>   preempt
>>   ip 10.8.200.1
>> 
>> sw1# ping 10.8.200.3
>> PING 10.8.200.3 (10.8.200.3): 56 data bytes
>> 64 bytes from 10.8.200.3: icmp_seq=0 ttl=254 time=2.524 ms
>> 64 bytes from 10.8.200.3: icmp_seq=1 ttl=254 time=0.954 ms
>> 64 bytes from 10.8.200.3: icmp_seq=2 ttl=254 time=0.854 ms
>> 64 bytes from 10.8.200.3: icmp_seq=3 ttl=254 time=1.138 ms
>> 64 bytes from 10.8.200.3: icmp_seq=4 ttl=254 time=0.875 ms
>> 
>> --- 10.8.200.3 ping statistics ---
>> 5 packets transmitted, 5 packets received, 0.00% packet loss
>> round-trip min/avg/max = 0.854/1.268/2.524 ms
>> 
>> 
>> 
>> 
>> Am 09.08.2013 um 14:30 schrieb Rati Berikaant Jokhadze:
>> 
>>> Hi ,
>>> 
>>> Please share us SW2 int vlan200 config.
>>> 
>>> and ping result from sw1 to sw2
>>> 
>>> On 08/09/2013 03:52 PM, Christian Kildau wrote:
>>>> Hi Cisco-NSP,
>>>> 
>>>> we're having some very strange issues while adding HSRP to our Nexus 5020 where both HSRP peers are up, but don't recognize each other, thus causing some issues.
>>>> 
>>>> Our config is pretty simple, running 4 VLANs and VPC. VPC is up and the Trunks are running fine.
>>>> 
>>>> We now added some SVIs for L3 routing which also seems to be working fine.
>>>> But as soon as we add HSRP config as follows:
>>>> 
>>>> interface Vlan200
>>>> no shutdown
>>>> no ip redirects
>>>> ip address 10.8.200.2/24
>>>> hsrp version 2
>>>> hsrp 1
>>>>   preempt
>>>>   priority 110
>>>>   ip 10.8.200.1
>>>> 
>>>> we're facing some very strange issues.
>>>> According to 'debug hsrp engine packet hello' both sides do send HSRP Hello Packets, but the other end never receives them, so both peers are in Active state:
>>>> 
>>>> sw1# sh hsrp group 1 brief
>>>> Interface   Grp Prio P State    Active addr      Standby addr     Group addr
>>>> Vlan200     1   110  P Active   local            unknown          10.8.200.1
>>>> (conf)
>>>> sw2# sh hsrp group 1 brief
>>>> Interface   Grp Prio P State    Active addr      Standby addr     Group addr
>>>> Vlan200     1   100  P Active   local            unknown          10.8.200.1
>>>> (conf)
>>>> 
>>>> What could cause this?
>>>> 
>>>> Thanks for any hint!
>>>> 
>>>> Kind Regards
>>>> Christian
>>>> 
>>>> P.S.
>>>> features are enabled of course ;-)
>>>> _______________________________________________
>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>> 
>> 
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/