- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- No vlan headers in sFlow sampled packets
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
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
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
тАО10-29-2009 07:17 AM
тАО10-29-2009 07:17 AM
No vlan headers in sFlow sampled packets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 07:45 AM
тАО10-30-2009 07:45 AM
Re: No vlan headers in sFlow sampled packets
What are you looking at?
Traffic measuring samples is not packet sniffing.
It is management information, not data-traffic.
every packet can hold multiple data samples (for multiple vlan's) and may have multiple vlan-id's/measurement-data in the data section of the packet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 08:08 AM
тАО10-30-2009 08:08 AM
Re: No vlan headers in sFlow sampled packets
Each time I get an sflow sample, I'm looking at the decoded header information. This information IS the TCP Header of the actual data flowing through the switch, It contains SRC and DST MAc Addresses, IP addresses, packet size, etc.
>>>Traffic measuring samples is not packet sniffing.<<<
I'm looking at sflow samples, not counters so yes , it DOES have "sniffed" packet info in it. That's what sflow is for.
>>>It is management information, not data-traffic.<<<
Also not true. a 1/512 sample rate picks 1 out of every 512 samples out of real data flowing through the sampled port and sends it to the sflow collector. One of the sflow v5 data elements is the IP header of the sampled packet.
>>>every packet can hold multiple data samples (for multiple vlan's) and may have multiple vlan-id's/measurement-data in the data section of the packet.<<<
Correct, and sflow tools decode those, giving me access to BGP info, VLAN info, src_ip and dst_ip info, src_port and dst_port, protocol info, etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 04:03 AM
тАО11-02-2009 04:03 AM
Re: No vlan headers in sFlow sampled packets
How to assign points on this new forum? Click the Kudos Star!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 04:10 AM
тАО11-02-2009 04:10 AM
Re: No vlan headers in sFlow sampled packets
How to assign points on this new forum? Click the Kudos Star!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 07:00 AM
тАО11-02-2009 07:00 AM
Re: No vlan headers in sFlow sampled packets
Good point, I considered that shortly after I got started, and set sFlow to sample only the ports in my core switch that are trunked to my aggregation switches, to ensure I was sampling ports that were Tagged in the VLAN. Thanks for the links, I'll check those out.