Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Nexus 7010 error port

I use Nexus 7010 on my client.

There is using 48port ethernet module as I/O on slot 1 and 2 and then I add new module 48port ethernet module on slot 7 and 8.

Some port already use for connection to server (end device) on slot 1 and 2. At this time, nexus work properly and I can use unused port, configure it to connected to server.

But after several month, when I want to use the unused port (port that not connected to end device/server), I had problem that every unused can not be used. I used command sh interface on that port and get no trafic that send from this port (Tx zero).

*all used port that already connceted to server work properly.

Simple topology for testing:

Nexus port eth1/5     --------------------------               PC

10.10.10.1/24              connected to          10.10.10.2/24

nexus:

int eth1/5

no switchport

ip add 10.10.10.1 255.255.255.0

no shut

PC:

ip add 10.10.10.2

subnet mask 255.255.255.0

gateway: 10.10.10.1

from this scenario I can't ping from PC to nexus or Nexus to PC. (nexus port status is connected routed and led status green)

I would appreciate it if anyone has same problem and can tell me to solve this problem.

9 REPLIES
Cisco Employee

Nexus 7010 error port

can you please share the output of show interface eth1/5

-Vijay

Silver

Nexus 7010 error port

Budi Afianto wrote:

I use Nexus 7010 on my client.

There is using 48port ethernet module as I/O on slot 1 and 2 and then I add new module 48port ethernet module on slot 7 and 8.

Some port already use for connection to server (end device) on slot 1 and 2. At this time, nexus work properly and I can use unused port, configure it to connected to server.

But after several month, when I want to use the unused port (port that not connected to end device/server), I had problem that every unused can not be used. I used command sh interface on that port and get no trafic that send from this port (Tx zero).

*all used port that already connceted to server work properly.

Simple topology for testing:

Nexus port eth1/5     --------------------------               PC

10.10.10.1/24              connected to          10.10.10.2/24

nexus:

int eth1/5

no switchport

ip add 10.10.10.1 255.255.255.0

no shut

PC:

ip add 10.10.10.2

subnet mask 255.255.255.0

gateway: 10.10.10.1

from this scenario I can't ping from PC to nexus or Nexus to PC. (nexus port status is connected routed and led status green)

I would appreciate it if anyone has same problem and can tell me to solve this problem.

Without knowing more information about your Nexus config, it's impossible to tell.

Can you post the output from the following commands

show run int e1/15

show run int e1/?? <- pick one of your working server-connected interfaces

show int e1/15

Alternately, post a sanitised (passwords removed etc) copy of your entire Nexus config.

Cheers.

New Member

Nexus 7010 error port

Thank for your respons guys..

I am so sory, but I have not full authorization access to get sh run for the device. I only have this note:

sh int status:

---------------------------------------------------------------------------------------------------------

Port          Name               Status    Vlan      Duplex  Speed   Type

----------------------------------------------------------------------------------------------------------

Eth1/5        --                 connected routed        full    1000    10/100/1000

sh run int eth1/5:

int eth1/5

no switchport

ip add 10.10.10.1 255.255.255.0

no shut

Silver

Nexus 7010 error port

Budi Afianto wrote:

Thank for your respons guys..

I am so sory, but I have not full authorization access to get sh run for the device. I only have this note:

sh int status:

---------------------------------------------------------------------------------------------------------

Port          Name               Status    Vlan      Duplex  Speed   Type

----------------------------------------------------------------------------------------------------------

Eth1/5        --                 connected routed        full    1000    10/100/1000

sh run int eth1/5:

int eth1/5

no switchport

ip add 10.10.10.1 255.255.255.0

no shut

Is the PC a Windows box with the firewall enabled, by any chance? The default Windows firewall installation denies PING traffic. From what you've posted I can't see anything which could be causing this not to work.

Cheers.

Nexus 7010 error port

Why is there "no switchport" in int eth1/5?

If the port is for a Server you should configure it as a switchport.

Cisco Employee

Nexus 7010 error port

Thomas

"no switchport" is configured to make the interface routed and to be able to assign an ip address

Darren

Without more information we can only gues possible reasons:

1. configuration issue

2. server issue

3. link issue

can you gater more info from the box:

try to ping from n7k your server using e1/5 as a source address

sh mod

sh int e1/5

sh int e 1/5 counters

sh run int e 1/5

Regards,

Alex

New Member

Nexus 7010 error port

I have solve this problem by Upgrade NX-OS, from

n7000-s1-kickstart.5.1.3.bin to n7000-s1-kickstart.5.0.2a.bin

n7000-s1-dk9.5.1.3.bin ton7000-s1-dk9.5.0.2a.bin

I think this just bugs, maybe because I add new module 48port ethernet module on slot 7 and 8.

Thanks fo support..

Cisco Employee

Nexus 7010 error port

Hi Budi

That was downgrade as 5.0.2a is older that 5.1.3

Probably Feature that contained the bug hasn't been realised in the 5.0.2a version so the bug is also not present.

Regards,

Alex

New Member

Nexus 7010 error port

Sory Alex,

I make mistake when I write, it should be

n7000-s1-kickstart.5.0.2a.bin    to     n7000-s1-kickstart.5.1.3.bin

n7000-s1-dk9.5.0.2a.bin     to    n7000-s1-dk9.5.1.3.bin

So it is upgrade not downgrade.

This is capture running NX-OS at nexus

Software

  BIOS:      version 3.22.0

  kickstart: version 5.1(3)

  system:    version 5.1(3)

  BIOS compile time:       02/20/10

  kickstart image file is: bootflash:///n7000-s1-kickstart.5.1.3.bin

  kickstart compile time:  12/25/2020 12:00:00 [03/11/2011 14:42:56]

  system image file is:    bootflash:///n7000-s1-dk9.5.1.3.bin

  system compile time:     1/21/2011 19:00:00 [03/11/2011 15:37:35]

709
Views
0
Helpful
9
Replies
CreatePlease to create content