topic Re: Performance question? 150 node network with multiple switches... in Operating System - HP-UX

Performance question? 150 node network with multiple switches...

Dale Sullens — Wed, 16 Jul 2003 18:15:59 GMT

I have a 150 node network with approximately 50 workstations and 100 Servers, all on 1 floor with no network segmentation.

The configuration (this was not by design) I am working with consists of a primary 80 Port HP procurve switch with 4 smaller switches at locations of high concentration.
My question is how much of an impact is the overall network performance affected by these "extra" switches?

The building we are in right now only has 1 or 2 network drops per room so I am limited on where I can place my equipment. Hence I may have 1 network cable from the "main" switch feeding 30 Servers...

I would like to have 1 drop per node to the "main" switch. Without some hard facts it will be difficult to convince management to spring for any cabling changes in the building..

Thanks for any advice..

Re: Performance question? 150 node network with multiple switches...

Ron Kinner — Wed, 16 Jul 2003 18:23:42 GMT

It sort of depends on the size of the links between switches and the amount of traffic.

Get mrtg and let it monitor your links between switches. It will show you where the bottlenecks are in pretty graphs which even managers can understand.

people.ee.ethz.ch/~oetiker/webtools/mrtg

It would be interesting to know what level of broadcast traffic you are running into on your network. If these are all Window boxes it could be a considerable proportion of your available bandwidth. Reducing the worthless broadcasts might help. How many of your machines are running netbeui for no reason?

Ron

Re: Performance question? 150 node network with multiple switches...

Steven E. Protter — Wed, 16 Jul 2003 18:28:22 GMT

This kind of setup is surely going to be a drag on performance.

Even a ping request has a lot of workstations to poll to get an answer.

Try pinging the broadcast address and see how long that takes to cycle.

More important, during periods of high network load, bottlenecks can develop.

Toptools, is a good way to monitor the network configuration itself, but it only runs on certain HP hardware.

A traceroute (tracert in windows) command can be used to look for bottlenecks.

Utilization on that server wire may be a problem as well and needs to be looked at.

I'm not familiar with that HP switch, but a modern Cisco Switch to segment the servers and provide a faster Core backbone can really improve performance a lot.

SEP

Re: Performance question? 150 node network with multiple switches...

Dale Sullens — Wed, 16 Jul 2003 18:41:50 GMT

90% of my systems are Windows based.. The remaining are a mix of Unix boxes..
I'll give mrtg a try.

Whats the easiest way to disable Netbeui?

I'm still running a Windows NT4 domain.

Thanks

Re: Performance question? 150 node network with multiple switches...

Ron Kinner — Wed, 16 Jul 2003 19:02:11 GMT

Some switches let you block anything but IP otherwise I think it's probably a one machine at a time thing. You could put a sniffer on it and see if you are getting a lot of netbeui going over the interswitch links. The switches themselves may be able to give you some info on the amount of broadcast traffic which you can commpare to the total number of packets in or out. Some of them allow you to limit the percentage of broadcast traffic.

Ron

Re: Performance question? 150 node network with multiple switches...

Dale Sullens — Wed, 16 Jul 2003 19:17:22 GMT

These switches are pretty low end( except for the main HP pro curve) I would appreciate a recommendation for a network sniffer?

Thanks!

Re: Performance question? 150 node network with multiple switches...

Ron Kinner — Wed, 16 Jul 2003 19:35:13 GMT

tcpdump is what all of the UNIX types like. www.tcpdump.org or get the official HP version form the HP website.

If you are running a Window box you can use either Windump
http://windump.polito.it/install/default.htm
or Snort (www.snort.org). Both require Winpcap to run. Snort's really an intrusion detector but it can do lots of other things.

In etiher case since you are working with switches you will need to tell the switch to let you monitor the traffic on port x by way of port y then you plug your box into port y. Port x should be one of your interswitch links. Probably your core switch would be your best bet.

If you have any trouble getting mrtg to work let me know. You will need to tell it the ip address of the management interface for each switch as well as the community string. If your cheap switches are all connected directly to the big switch then you really only have to monitor the big switch. The big switch may need to know the ip address of the box you are running mrtg on if you have set up security on it.

Ron

Re: Performance question? 150 node network with multiple switches...

Dale Sullens — Thu, 17 Jul 2003 14:28:17 GMT

Thanks Ron.. I will try to give it a shot this week.. Appreciate all of the advice..