- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: PCM 2.2 - Logged Traffic Data CVS?
Switches, Hubs, and Modems
1755669
Members
4416
Online
108837
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО06-07-2007 03:35 AM
тАО06-07-2007 03:35 AM
I've had a look at some of the data logged by Traffic Monitor but the CVS file is a little awkward to make sense of (no column headings). Is there a way of parsing this file to obtain some more useful information?
Regards
Jason
Regards
Jason
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2007 04:23 AM
тАО06-07-2007 04:23 AM
Solution
Jason,
Here is an example of a row from the TrafficDataLog.csv file.
"2007 Jun 1, 13:26:26:625",[host001.boneyard.rose.hp.com(150.2.51.1): A11, 00:15:60:f9:93:f5, A11, 11, , 11, 100000000, FullDuplex, ManualOn, NoViolation, 04/23/07 01:54:35p, 0.0017978378, 2.5743244, 0.006756757, 0.5067568, 0.0, 04/23/07 01:54:35p, 0.002787081, 3.25, 0.7162162, 0.45945945, 0.0, 04/23/07 01:54:36p, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ICMP 150.2.51.1:0 -> 150.2.51.10:0, , , , , Ethernet 00:08:02:76:41:87:2048, , , , , Ethernet 00:15:60:f9:83:00:2048, , , , , ICMP, , , , , ICMP 150.2.51.1:0 -> 150.2.51.10:0, , , , , Ethernet 00:08:02:76:41:87:2048, , , , , Ethernet 00:15:60:f9:83:00:2048, , , , , ICMP, , , , , , , , , , , , , , ]
Here is a description of each value according to its column position (comma separated CSV):
"LogEntryTimestamp", (for example: 2007 Jun 1, 13:26:26:625)
[
DevicePort, (for example: host001.boneyard.rose.hp.com(150.2.51.1): A11)
PortMAC,
PortName,
PortNumber,
PortFriendlyName,
PortIfIndex,
PortSpeed,
PortDuplex,
LogMode,
ThresholdViolation,
RxStatsTimestamp, (for the following 5 metrics, for example: 04/23/07 01:54:35p)
RxUtilization,
RxFramesPerSecond,
RxBrodcastsPerSecond,
RxMulticastsPerSecond,
RxErrorsPerSecond,
TxStatsTimestamp, (for the following 5 metrics)
TxUtilization,
TxFramesPerSecond,
TxBrodcastsPerSecond,
TxMulticastsPerSecond,
TxErrorsPerSecond,
TopTalkerTimestamp, (for the following top 5 in each category)
RxUtilizationConnections#1, (for example: ICMP 150.2.51.1:0 -> 150.2.51.10:0)
RxUtilizationConnections#2,
RxUtilizationConnections#3,
RxUtilizationConnections#4,
RxUtilizationConnections#5,
RxUtilizationDestinations#1,
RxUtilizationDestinations#2,
RxUtilizationDestinations#3,
RxUtilizationDestinations#4,
RxUtilizationDestinations#5,
RxUtilizationSources#1,
RxUtilizationSources#2,
RxUtilizationSources#3,
RxUtilizationSources#4,
RxUtilizationSources#5,
RxUtilizationProtocols#1,
RxUtilizationProtocols#2,
RxUtilizationProtocols#3,
RxUtilizationProtocols#4,
RxUtilizationProtocols#5,
RxFramesPerSecondConnections#1,
RxFramesPerSecondConnections#2,
RxFramesPerSecondConnections#3,
RxFramesPerSecondConnections#4,
RxFramesPerSecondConnections#5,
RxFramesPerSecondDestinations#1,
RxFramesPerSecondDestinations#2,
RxFramesPerSecondDestinations#3,
RxFramesPerSecondDestinations#4,
RxFramesPerSecondDestinations#5,
RxFramesPerSecondSources#1,
RxFramesPerSecondSources#2,
RxFramesPerSecondSources#3,
RxFramesPerSecondSources#4,
RxFramesPerSecondSources#5,
RxFramesPerSecondProtocols#1,
RxFramesPerSecondProtocols#2,
RxFramesPerSecondProtocols#3,
RxFramesPerSecondProtocols#4,
RxFramesPerSecondProtocols#5,
RxBroadcastsPerSecondConnections#1,
RxBroadcastsPerSecondConnections#2,
RxBroadcastsPerSecondConnections#3,
RxBroadcastsPerSecondConnections#4,
RxBroadcastsPerSecondConnections#5,
RxMulticastsPerSecondConnections#1,
RxMulticastsPerSecondConnections#2,
RxMulticastsPerSecondConnections#3,
RxMulticastsPerSecondConnections#4,
RxMulticastsPerSecondConnections#5,
RxErrorsPerSecondConnections#1,
RxErrorsPerSecondConnections#2,
RxErrorsPerSecondConnections#3,
RxErrorsPerSecondConnections#4,
RxErrorsPerSecondConnections#5,
TxUtilizationConnections#1,
TxUtilizationConnections#2,
TxUtilizationConnections#3,
TxUtilizationConnections#4,
TxUtilizationConnections#5,
TxUtilizationDestinations#1,
TxUtilizationDestinations#2,
TxUtilizationDestinations#3,
TxUtilizationDestinations#4,
TxUtilizationDestinations#5,
TxUtilizationSources#1,
TxUtilizationSources#2,
TxUtilizationSources#3,
TxUtilizationSources#4,
TxUtilizationSources#5,
TxUtilizationProtocols#1,
TxUtilizationProtocols#2,
TxUtilizationProtocols#3,
TxUtilizationProtocols#4,
TxUtilizationProtocols#5,
TxFramesPerSecondConnections#1,
TxFramesPerSecondConnections#2,
TxFramesPerSecondConnections#3,
TxFramesPerSecondConnections#4,
TxFramesPerSecondConnections#5,
TxFramesPerSecondDestinations#1,
TxFramesPerSecondDestinations#2,
TxFramesPerSecondDestinations#3,
TxFramesPerSecondDestinations#4,
TxFramesPerSecondDestinations#5,
TxFramesPerSecondSources#1,
TxFramesPerSecondSources#2,
TxFramesPerSecondSources#3,
TxFramesPerSecondSources#4,
TxFramesPerSecondSources#5,
TxFramesPerSecondProtocols#1,
TxFramesPerSecondProtocols#2,
TxFramesPerSecondProtocols#3,
TxFramesPerSecondProtocols#4,
TxFramesPerSecondProtocols#5,
TxBroadcastsPerSecondConnections#1,
TxBroadcastsPerSecondConnections#2,
TxBroadcastsPerSecondConnections#3,
TxBroadcastsPerSecondConnections#4,
TxBroadcastsPerSecondConnections#5,
TxMulticastsPerSecondConnections#1,
TxMulticastsPerSecondConnections#2,
TxMulticastsPerSecondConnections#3,
TxMulticastsPerSecondConnections#4,
TxMulticastsPerSecondConnections#5,
TxErrorsPerSecondConnections#1,
TxErrorsPerSecondConnections#2,
TxErrorsPerSecondConnections#3,
TxErrorsPerSecondConnections#4,
TxErrorsPerSecondConnections#5
]
This example shows data for a port with sampling enabled but many sampled data fields empty. Of course, for ports where stats are being monitored rather than sampling, *all* of the top talker fields (the ones with "#n" appended above) will be empty since no visibility is provided into the traffic content.
Regards,
SVB
Here is an example of a row from the TrafficDataLog.csv file.
"2007 Jun 1, 13:26:26:625",[host001.boneyard.rose.hp.com(150.2.51.1): A11, 00:15:60:f9:93:f5, A11, 11, , 11, 100000000, FullDuplex, ManualOn, NoViolation, 04/23/07 01:54:35p, 0.0017978378, 2.5743244, 0.006756757, 0.5067568, 0.0, 04/23/07 01:54:35p, 0.002787081, 3.25, 0.7162162, 0.45945945, 0.0, 04/23/07 01:54:36p, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ICMP 150.2.51.1:0 -> 150.2.51.10:0, , , , , Ethernet 00:08:02:76:41:87:2048, , , , , Ethernet 00:15:60:f9:83:00:2048, , , , , ICMP, , , , , ICMP 150.2.51.1:0 -> 150.2.51.10:0, , , , , Ethernet 00:08:02:76:41:87:2048, , , , , Ethernet 00:15:60:f9:83:00:2048, , , , , ICMP, , , , , , , , , , , , , , ]
Here is a description of each value according to its column position (comma separated CSV):
"LogEntryTimestamp", (for example: 2007 Jun 1, 13:26:26:625)
[
DevicePort, (for example: host001.boneyard.rose.hp.com(150.2.51.1): A11)
PortMAC,
PortName,
PortNumber,
PortFriendlyName,
PortIfIndex,
PortSpeed,
PortDuplex,
LogMode,
ThresholdViolation,
RxStatsTimestamp, (for the following 5 metrics, for example: 04/23/07 01:54:35p)
RxUtilization,
RxFramesPerSecond,
RxBrodcastsPerSecond,
RxMulticastsPerSecond,
RxErrorsPerSecond,
TxStatsTimestamp, (for the following 5 metrics)
TxUtilization,
TxFramesPerSecond,
TxBrodcastsPerSecond,
TxMulticastsPerSecond,
TxErrorsPerSecond,
TopTalkerTimestamp, (for the following top 5 in each category)
RxUtilizationConnections#1, (for example: ICMP 150.2.51.1:0 -> 150.2.51.10:0)
RxUtilizationConnections#2,
RxUtilizationConnections#3,
RxUtilizationConnections#4,
RxUtilizationConnections#5,
RxUtilizationDestinations#1,
RxUtilizationDestinations#2,
RxUtilizationDestinations#3,
RxUtilizationDestinations#4,
RxUtilizationDestinations#5,
RxUtilizationSources#1,
RxUtilizationSources#2,
RxUtilizationSources#3,
RxUtilizationSources#4,
RxUtilizationSources#5,
RxUtilizationProtocols#1,
RxUtilizationProtocols#2,
RxUtilizationProtocols#3,
RxUtilizationProtocols#4,
RxUtilizationProtocols#5,
RxFramesPerSecondConnections#1,
RxFramesPerSecondConnections#2,
RxFramesPerSecondConnections#3,
RxFramesPerSecondConnections#4,
RxFramesPerSecondConnections#5,
RxFramesPerSecondDestinations#1,
RxFramesPerSecondDestinations#2,
RxFramesPerSecondDestinations#3,
RxFramesPerSecondDestinations#4,
RxFramesPerSecondDestinations#5,
RxFramesPerSecondSources#1,
RxFramesPerSecondSources#2,
RxFramesPerSecondSources#3,
RxFramesPerSecondSources#4,
RxFramesPerSecondSources#5,
RxFramesPerSecondProtocols#1,
RxFramesPerSecondProtocols#2,
RxFramesPerSecondProtocols#3,
RxFramesPerSecondProtocols#4,
RxFramesPerSecondProtocols#5,
RxBroadcastsPerSecondConnections#1,
RxBroadcastsPerSecondConnections#2,
RxBroadcastsPerSecondConnections#3,
RxBroadcastsPerSecondConnections#4,
RxBroadcastsPerSecondConnections#5,
RxMulticastsPerSecondConnections#1,
RxMulticastsPerSecondConnections#2,
RxMulticastsPerSecondConnections#3,
RxMulticastsPerSecondConnections#4,
RxMulticastsPerSecondConnections#5,
RxErrorsPerSecondConnections#1,
RxErrorsPerSecondConnections#2,
RxErrorsPerSecondConnections#3,
RxErrorsPerSecondConnections#4,
RxErrorsPerSecondConnections#5,
TxUtilizationConnections#1,
TxUtilizationConnections#2,
TxUtilizationConnections#3,
TxUtilizationConnections#4,
TxUtilizationConnections#5,
TxUtilizationDestinations#1,
TxUtilizationDestinations#2,
TxUtilizationDestinations#3,
TxUtilizationDestinations#4,
TxUtilizationDestinations#5,
TxUtilizationSources#1,
TxUtilizationSources#2,
TxUtilizationSources#3,
TxUtilizationSources#4,
TxUtilizationSources#5,
TxUtilizationProtocols#1,
TxUtilizationProtocols#2,
TxUtilizationProtocols#3,
TxUtilizationProtocols#4,
TxUtilizationProtocols#5,
TxFramesPerSecondConnections#1,
TxFramesPerSecondConnections#2,
TxFramesPerSecondConnections#3,
TxFramesPerSecondConnections#4,
TxFramesPerSecondConnections#5,
TxFramesPerSecondDestinations#1,
TxFramesPerSecondDestinations#2,
TxFramesPerSecondDestinations#3,
TxFramesPerSecondDestinations#4,
TxFramesPerSecondDestinations#5,
TxFramesPerSecondSources#1,
TxFramesPerSecondSources#2,
TxFramesPerSecondSources#3,
TxFramesPerSecondSources#4,
TxFramesPerSecondSources#5,
TxFramesPerSecondProtocols#1,
TxFramesPerSecondProtocols#2,
TxFramesPerSecondProtocols#3,
TxFramesPerSecondProtocols#4,
TxFramesPerSecondProtocols#5,
TxBroadcastsPerSecondConnections#1,
TxBroadcastsPerSecondConnections#2,
TxBroadcastsPerSecondConnections#3,
TxBroadcastsPerSecondConnections#4,
TxBroadcastsPerSecondConnections#5,
TxMulticastsPerSecondConnections#1,
TxMulticastsPerSecondConnections#2,
TxMulticastsPerSecondConnections#3,
TxMulticastsPerSecondConnections#4,
TxMulticastsPerSecondConnections#5,
TxErrorsPerSecondConnections#1,
TxErrorsPerSecondConnections#2,
TxErrorsPerSecondConnections#3,
TxErrorsPerSecondConnections#4,
TxErrorsPerSecondConnections#5
]
This example shows data for a port with sampling enabled but many sampled data fields empty. Of course, for ports where stats are being monitored rather than sampling, *all* of the top talker fields (the ones with "#n" appended above) will be empty since no visibility is provided into the traffic content.
Regards,
SVB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2007 07:55 PM
тАО06-07-2007 07:55 PM
Re: PCM 2.2 - Logged Traffic Data CVS?
Thanks Steve, thats great info!
Jas
Jas
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP