- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Monitoring fabric traffic?
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
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
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
тАО11-03-2010 09:13 AM
тАО11-03-2010 09:13 AM
How do you all monitor traffic across your fabric? Do you just use the performance monitor within Brocade switch viewer?
What about EVAperf? If so, how?
Any other suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2010 12:28 PM
тАО11-03-2010 12:28 PM
Re: Monitoring fabric traffic?
It's better for archiving past performance and not real time.
For real time, I just use the Performance Monitor on brocades' the web GUI.
So, your backups that go over iSCSI are fast, but the ones over the fabric are slow? I mean, are these the same boxes that you're backing up over the network and fabric, or different boxes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2010 12:43 PM
тАО11-03-2010 12:43 PM
Re: Monitoring fabric traffic?
The backups are going to MSL tape libraries, that are zoned.
Traffic seems to go fast over ethernet, but not always over fibre.
It's the same server having the problem with its backups.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2010 07:18 PM
тАО11-03-2010 07:18 PM
SolutionIn the recent versions of Fabric OS, the command bottleneckmon has been included to monitor fabric bottlenecks.
Instead of pondering over Fabric performance which is usually not the root cause, check these factors
1. Errors on relevant ports with
porterrshow
fabriclog -s
portstats64show
2. Check if there is a possibility of ISL oversubscription. If its too grave then you will see errors in errshow -r
Try connecting the MSL port to the same switch as the host or maybe the adjacent port for better locality.
3. Check windows error logs for any errors, specifically errors related to the HBA driver or the SCSI driver.
4. You could try zoning the tape drive to just one HBA to test things.
5. Fix the switch port speed and the HBA speed to the desired and possible level.
I can think of these for now. Since backup over network is fine, I would not doubt the EVA for now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 05:56 AM
тАО11-04-2010 05:56 AM
Re: Monitoring fabric traffic?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 12:28 PM
тАО11-04-2010 12:28 PM
Re: Monitoring fabric traffic?
this is how i did the previous time :
open the switch console , one of the tabs (if i remem. correctly , it's view tab) you would have the option to monitor the traffic real time,port wise(this will vary based on your fabric set up)
On servers , you could install tcpdump , use command line option of tcpdump to monitor traffic and dump to file and connection from lan card of server and DP server.
start the DP backup.
I rememeber , when i did this test previous time i saw most of the backup traffic on lan card only.
Regards ,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 12:41 PM
тАО11-04-2010 12:41 PM
Re: Monitoring fabric traffic?
Connect via telnet to the relevant brocadeswitches. (know upfront on which port of which sanswitch ,the server is connected, on which port(s) of which servers the fc tapedrives are connected and via which interswitchlinks the sanswitches are connected)
And then see with portperfshow on the different brocadeswitches, how the traffic flows from the server to the fc tapedrives and hopefully together with the information of PP BIJU KRISHNAN response, this will give some ideas. ;)
Greetz,
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 12:42 PM
тАО11-04-2010 12:42 PM
Re: Monitoring fabric traffic?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2010 10:12 AM
тАО11-05-2010 10:12 AM
Re: Monitoring fabric traffic?
However I have a question about "fabriclog -s". How do you capture that data? It scrolls continuously when you run the command, so I tried redirecting it to a file, but no luck ("cannot redirect output"). Also, how would you get the data off of the Brocade? I tried to ftp to my Brocade and can't do it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2010 10:12 AM
тАО11-05-2010 10:12 AM