Port on Summit X440-48t don't work o.k.


Userlevel 1
It's more like weird issue, it first happen like a month ago, the user couldn't get IP address, was the only user on the switch, we change the patch cords, change the vlan to make short it was not a shortage of ip's on that segment (via DHCP), and then it work, but today happen again, even connecting directly to the switch with my laptop, at the end, I connect the user in a different port on the same switch (also tried without Auto option, no success) what do you suggest me to check?

Thanks

p.s. so far is the only user/port with this issue

8 replies

is there an FDB entry on the port?
Userlevel 1
David Coglianese wrote:

is there an FDB entry on the port?

No, because, when I try to check to which port was connected (without following the cable on the rack) I couldn't find it with the show fdb command
David Coglianese wrote:

is there an FDB entry on the port?

So you know the mac of the PC?
You searched the FDB for the mac and could not find it?

If the above are true I would call tac as I have seen that issue before.
Userlevel 1
David Coglianese wrote:

is there an FDB entry on the port?

Yes, I knew the mac, and couldn't find it... So I'll reported to TAC then, just as port in switch not working properly
David Coglianese wrote:

is there an FDB entry on the port?

Yes, we have seen were a port or group of ports on a switch would enter a weird state that kept them from learning mac addresses. As a result they could not forward traffic to the devices connected to them.

Best of luck,
Userlevel 1
David Coglianese wrote:

is there an FDB entry on the port?

Thanks, that what I like about this community! always so helpful !
Userlevel 7
I'd start with wireshark on their PC. Disconnect the network cable, start the wireshark capture, and connect the cable again. This way you can see everything that happens with DHCP/BOOTP.
You could also set a static IP and gateway on the PC to see what's happening.
Userlevel 1
Drew C. wrote:

I'd start with wireshark on their PC. Disconnect the network cable, start the wireshark capture, and connect the cable again. This way you can see everything that happens with DHCP/BOOTP.
You could also set a static IP and gateway on the PC to see what's happening.

I'll do that, I check with two different computers using the same port,and different vlan's, and since the user needed to work I use a different port, I'll do the capture.

thanks

Reply