HPE Community
Web and Unmanaged
1753758 Members
4658 Online
108799 Solutions
New Discussion

Problems when connecting Clients in 1810G24/48 Enviorment

 
pelzi71
Occasional Contributor

‎06-23-2014 12:50 AM - last edited on ‎06-29-2014 05:50 PM by

‎06-23-2014 12:50 AM - last edited on ‎06-29-2014 05:50 PM by

Problems when connecting Clients in 1810G24/48 Enviorment

Hello,

 

we have in our company a network build on 3 1810G24 a 1810G48 and a dlink 1248T switch.

 

All switches a connected to the 1818G48 with 2 trunked ports.

 

My problem is that sometimes, when I try to move a client from a dlink to the a hp network port, the client can not communicate.


At first it looks normal, the network interface on the client is activated and windows shows a connected network.

 

But the client can't get a IP-address from the dhcp-server and if I switch to static ip there is nothing to ping on the net.

 

If I move back the client to the dlink switch the connection ist established soon with no error and the client gets an ip from dhcp.

 

But my dlink switch has all ports in use now and I need to connect more clients to the hp switches.

 

All my servers are connected to the 1810G48, there is no vlan or anything compicated in the setup on the switches, flow control is enabled on all the ports.

 

There is nothing to see in the logfile of the hp switch. I flashed the switches to the latest firmware because there was I problem in the older ones I read in the release notes.

 

IP Communication (CR_0000131152) - Some clients connected directly to the switch become unable to communicate
on the network. When this happens, the switch log shows Unable to delete FDB entry messages.

 

It seems the problem is not solved, only the message is removed.

 

 

What happens on the hp switches? Can you provide me furthe assistance?

 

P.S. This thread has been moved from  Switches, Hubs, Modems (Legacy ITRC forum) to  Web and Unmanaged. -HP Forum Moderator

0 Kudos
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.