- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Suspect Network Choking
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 03:25 AM
08-31-2004 03:25 AM
Can anybody sugguest how I go about checking the load on the network.
My problem is that every Sat at 10:15 ish users get slow responses retrieving images and Docs over the network and then they stop completley. About 30 mins later they are fine and it rectifies it self. I beleive the network is being chocked at that time. I need to prove that it is the network and whos , our network or the clients network. I have check for any jobs running our end and have sanity check the servers in question.
What can I run at that time to check.
nettl ???
Any sugguestions
Cheers
Rich
Want some points
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 03:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 03:38 AM
08-31-2004 03:38 AM
Re: Suspect Network Choking
How do a full monitor ? Do I select the lan card on the associated server I am on.
I presume this will monitor all traffic to and from the server?
I am not to sure once I have the log file, how to weed out the info I need.
I think nettlfrmt or something like that.
Rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 03:58 AM
08-31-2004 03:58 AM
Re: Suspect Network Choking
Interesting thing about this type of issues is that the network bottleneck could be anywhere starting from within the system, it's interfaces and all the way in the network pipe to the end user.
To eliminate the system problem, I would try setting up a test station within the same network and then try downloading the images and Docs. If the response is slow, then I would look at the local switch and the interface. If the response is normal, then obviously the problem is beyond your local switch.
If it is a patched 11.0 or a 11i, then you can use 'nettladm' to configure nettl. ethereal can be downloaded from our HP's porting center. Both can only give a snapshot of what's happening. Ethereal can also give you the bandwidth utilization. If you have measureware/glance installed, you c an see the network stats like InputPkts/OutputPkts per interface.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 07:13 AM
08-31-2004 07:13 AM
Re: Suspect Network Choking
You dont want to keep nettl running at all time with full logging.
Start the nettl via cron about 1 hour before the time you are interested in and stop the logging about 1 hour after.
You can define the maximum size of the log file in /etc/nettlgen.conf file.
man nettlgen.conf file for more info
nettl -traceon pduin pduout -entity all -file /var/adm/trace
The above nettl command will enable the trace for the in and out PDUs and log the trace in /var/adm/trace.TRCX file
You can use netfmt to view these log files.
-- Sundar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 07:34 AM
08-31-2004 07:34 AM
Re: Suspect Network Choking
As others have noted trying to collect stats on the system can be problematic at best & detrimental at worst. Plus it doesn't really show what's happening on the entire segment anyway.
Best place to collect the network performance stats would be on the first-hop router from this system. If you have a network team request they set up the router to collect these stats on demand - i.e. when the users see the slowdown, the network team should enable the stats collection until a little while after the performance returns to normal. Stats should also be collected - if possible - from the switch the system is directly attached to. This could point out a network config problem that only rears it's head under load. Or even a marginal port/cable/NIC that's fine until the load goes up.
My $0.02,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 01:23 PM
08-31-2004 01:23 PM
Re: Suspect Network Choking
http://mrtg.hdl.com/mrtg.html
Ron
PS. Sounds like some computer is probably doing an automatic backup to a tape drive every Sat at the same time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2004 07:18 PM
08-31-2004 07:18 PM
Re: Suspect Network Choking
It does sound like someone may be doing a backup aty the same time. Hmmmmmmmmmm. Not on the Unix servers though. Might by the clients NT Team.
Cheers
Rich
Have some point for you trouble ;-)