Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
For questions about Internet Protocol Flow Information Export (IPFIX), where it is an IETF protocol that was created based on the need for a common, universal standard of export for Internet Protocol flow information from routers, probes and other devices. See RFC 3917, 7011, 7015 and 5103.
1
vote
ipfix - variance of size packets in a flow
RMON can show the number of frames by size class, e.g. for HP Provision switches show rmon statistics <portno>:
Status and Counters - Port Counters for port 24
Drop events : 0 …
1
vote
Accepted
IPFIX vlanId element in access switchports
If there's no explicit VLAN tag (802.1Q), vlanId is the VLAN ID associated with an untagged frame for the ingress port.
0
votes
Accepted
Best practices to build network flow monitoring
IPFIX support is still somewhat scarce. sFlow support across device vendors is broader, so that might be the most promising path. …
0
votes
Identifying Application Information and MAC Addresses Using IPFIX Data
That isn't usually done on the IPFIX exporter but further up in the workflow. … . - isn't defined by IPFIX standards. The field itself is defined in RFC 6759.
Data link layer (L2) information is not commonly included in IPFIX data. There's a draft RFC 7133. …