Packet Loss

[Prabaharan]

Hii In our organization, we are having Aruba core switch,

and that switch is releasing 192.168.1.1. 10.0.10.1, 10.0.20.1, 10.0.30.1, 10.0.40.1, 10.0.50.1, and more different series.

what is the problem is there is a server called IP 192.168.1.75 pinging is dropping in other ip series, like 10.0.40.1 and other series, But while dropping in other series from 192.168.1.75, There is a no packet loss in 192.168.1.75 between 192.168.1.1 series machines.   

Thanks for advance.

[deanwebb]

Let me see if I understand... by "series", do you mean IP networks? If so, we would say instead of 10.0.10.1 to represent the IP addresses in that range, the CIDR notation that goes 10.0.10.0/24 - refers to 10.0.10.0-10.0.10.255.

And are you saying that hosts in 10.0.40.0/24 have dropped packets when they try to reach 192.168.1.75, but 192.168.1.0/24 hosts reach that server without issue?

If so, then we note that the server is native to the 192.168.1.0/24 range. Does traffic between hosts in that range have to pass through the core switch? If not, then you do have a core switch issue, most likely.

You would want to check on switch health metrics, such as CPU utilization and bandwidth utilization. If those or some other factor are over-used, that could be why the switch is dropping packets: it may not have enough CPU or RAM to handle the load on it.

[Dieselboy]

I think OP means that hosts are getting DHCP leases from networks other than 192.168.1.x

OP, if you are getting leases on 10.x.x.x networks then there is a dhcp server on 10.x.x.x within the broadcast domain.
What you can do to find it is plug in a windows laptop and get it to receive a 10.x.x.x address. When the laptop has one of those addresses, you can run "ipconfig /all" and in the output it will show you the DHCP server IP address.
Then you can run "arp -a" and find out he dhcp servers mac address.
Then if you have a managed switch, you can check the mac address table to figure out where that dhcp server is plugged into on the switch and then physically trace the cable.

If you dont have a managed switch then you could use another PC to view "arp -a" and see if you can find a close match to the mac in the output, that might be the dhcp server.


Some tips for you:
ipconfig /release = release dhcp IP
ipconfig /renew = try to get a new dhcp ip

Those 2 commands will save you unplugging the network cable to get a new ip.


To save having this problem in the future you can get managed switches with dhcp snooping enabled.