reason for L3 not ready in nexus 5596

[karthick raja]

we need a help with this issue,

we have configured VpC between two Nexus 5596, for Vpc-Keep-alive-link we configured L3 interface with 1G (GLC-T) ,it shows the below status message "L3 not Ready" with interface LED glows in Yellow in color. is this a physical layer problem

Ethernet      VLAN     Type Mode         Status                    Reason                     Speed            Po Ch

Eth1/17       --              eth               routed down           L3 not ready               1000(D)            --

Eth1/18       1              eth                access down          SFP not inserted            10G(D)             --

Eth1/19       1              eth                access down          SFP not inserted            10G(D)             --

Eth1/20       1              eth                access down          SFP not inserted            10G(D)              --

Eth1/21       1              eth                access down          SFP not inserted            10G(D)              --

switch-1

vrf context vpc-keepalive

int eth 1/17

no switchport

vrf member vpc-keepalive

ip add 172.19.24.1 255.255.255.252

speed 1000

no shut

vpc domain 50

peer-keepalive destination 172.19.24.2 source 172.19.24.1 vrf vpc-keepalive

ip arp synchronize

role priority 8192

switch-2

vrf context vpc-keepalive

int eth 1/17

no switchport

vrf member vpc-keepalive

ip add 172.19.24.2 255.255.255.252

speed 1000

no shut

vpc domain 50

peer-keepalive destination 172.19.24.1 source 172.19.24.2 vrf vpc-keepalive

ip arp synchronize

role priority 8192

[Reza Sharifi]

If you look at port e1/17 on each switch and the link light in not green, than you have physical layer issue.  Is the patch cord good?

is the GLC-T working fine?  what is the output of "sh int e1/17 tran"?

HTH

[karthick raja]

As soon i change the interface from L3 to L2 interface it turn's to green colour.

[Reza Sharifi]

Can you add switchport vlan x/x to both switches and try again?

see below example

vrf context vpc_keepalive
interface Ethernet1/31
  switchport access vlan 123
interface Vlan123
  vrf member vpc_keepalive
  ip address 123.1.1.2/30
  no shutdown
vpc domain 1
  peer-keepalive destination 123.1.1.1 source 123.1.1.2 vrf 
vpc_keepalive

[karthick raja]

Thanks for the support. interface is came up but  vpc is not up, could you tell me what is the problem

Show vpc brief output

vPC domain id                   : 50 
Peer status                     : peer link not configured     
vPC keep-alive status           : Suspended (Destination IP not reachable)
Configuration consistency status: failed 
Per-vlan consistency status     : failed                       
Configuration consistency reason: vPC peer-link does not exist 
Type-2 consistency status       : failed 
Type-2 consistency reason       : vPC peer-link does not exist 
vPC role                        : none established             
Number of vPCs configured       : 0  
Peer Gateway                    : Disabled
Dual-active excluded VLANs      : -
Graceful Consistency Check      : Disabled (due to peer configuration)

N5K-AGG-1#

[Oleksandr Nesterov]

Hi Karthik

In your output:

Peer status                     : peer link not configured     

vPC keep-alive status           : Suspended (Destination IP not reachable)

1. check whether you have Port-channel between your n5k configured as vpc peer-link, and it's up

2. check whether you can ping

123.1.1.1 from 123.1.1.2 in vrf vpc_keepalive

HTH,

Alex

[karthick raja]

Thanks Oleksandr Nesterov,

i have not configured vpc peer-link command in the port channel between N5k, i have added the key-word now it is up and running .

[Oleksandr Nesterov]

Hi Karthik

Happy to hear that VPC is up and runnig now

HTH,

Alex

[karthick raja]

Hi  Oleksandr Nesterov, happy new year

thanks for your support ,  all are up and running ,but i dont understand why we got this status message when it was an Routed interface, please help me to understand this.

Ethernet      VLAN     Type Mode         Status                    Reason                     Speed            Po Ch

Eth1/17       --              eth               routed down           L3 not ready               1000(D)            --

[Oleksandr Nesterov]

Hi Karthik

Please check "sh mod" and "sh lic usage".

If L3 module was down or license was absent such behavior might be observed.

HTH,

Alex

[karthick raja]

Hi Oleksandr,

i was in vacation so i didnt reply for this thread , yes you are right i have verified the device with both commands 'show module' & 'show license usage'.

In 5596, L3 (LAN_BASE_LIC) was not there, we installed the license all routing related things started to work.

In 5548, L3 (LAN_BASE_LIC) was there but there is no L3 Daughter card , we cleared the L3 license it rolled back to L2 operatons. we are using 5548 switches mainly for L2 operation so we did not install the L3 daughter card , for all L3 opration redirected towards 5596 like HSRP,inter-vlan routing.

Out of this what i understood ,

If we want to use Nexus 5500 as an L3 switch , we need both(1&2) requirements to be there

1.we need L3 module

2. we need L3 license (LAN_BASE_LIC)

Your show commands helped me to clear the issues, Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!!