...
For example, the service header length for 64 bytes long frames (Figure 4b) and 156 bytes frames(Figure 4c) will be the same, but the user data amount will be different. To transmit 138 bytes of user data, three 64 bytes frames or one 156 bytes frame will be required, so in the first case 192 bytes are sent, in the second only 156 bytes. For a link having a fixed throughput, large frames will increase the efficiency by rising the useful throughput of the system, but the latency will also increase. The performance of the Infinet devices in various conditions is shown in the "Performance of the InfiNet Infinet Wireless devices" document.
...
Center |
---|
Internal packet queuing
Parameter | Description | InfiLINK 2x2 / InfiMAN 2x2 | InfiLINK Evolution / InfiMAN Evolution | InfiLINK XG / InfiLINK XG 1000 | Quanta 5 / Quanta 6 / Quanta 70 |
---|
Marking criteria | A criteria that can be used to classify the incoming traffic. | PCAP expressions support (PCAP expressions allow flexible filtering based on any service header field, see the PCAP filters article) | PCAP expressions support (PCAP expressions allow flexible filtering based on any service header field, see the PCAP filters article) | vlan-id | vlan-id | Auto recognition | Protocols for which the family of devices automatically recognizes the priority set in the header and puts the data in the appropriate queue. | RTP 802.1p IPIP/GRE tunnels MPLS DSCP ToS ICMP TCP Ack PPPoE | RTP 802.1p IPIP/GRE tunnels MPLS DSCP ToS ICMP TCP Ack PPPoE | 802.1p | 802.1p | Number of queues | The number of data queues used by the device. | 17 | 17 | 4 | 8 | Queue management | Supported mechanisms for emptying the packets from the queues. | Weighted | Strict Weighted | QoS configuration via Web | Documentation about the traffic prioritization configuration using the Web interface.
| QoS options Traffic Shapping | QoS options Traffic Shaping | Configuring QoS Switch Configuring per-VLAN | Switch settings | QoS configuration via CLI | Documentation about the traffic prioritization configuration using the command line interface.
| qm command | qm command | Commands for switch configuration | - |
Correspondence between the priorities of the standard protocols and the internal priorities used by the InfiLINK 2x2, InfiMAN 2x2, InfiLINK Evolution and InfiMAN 2x2 Evolution families of devicesTraffic class (in accordance with MINT) | InfiLINK 2x2, InfiMAN 2x2, InfiLINK Evolution and InfiMAN Evolution | 802.1p | ToS (Precedence) | DSCP |
---|
Background | 16 | 01 |
|
| Regular best effort | 15 | 00 | 00 | 0 | Business 6 | 14 |
| 01 | 8, 10 | Business 5 | 13 |
|
| 12, 14 | Business 4 | 12 |
| 02 | 16, 18 | Business 3 | 11 |
|
| 20, 22 | Business 2 | 10 |
| 03 | 24, 26 | Business 1 | 9 | 02 |
| 28, 30 | QoS 4 | 8 |
| 04 | 32 | QoS 3 | 7 |
|
| 34 | QoS 2 | 6 |
|
| 36 | QoS 1 | 5 | 03 |
| 38 | Video 2 | 4 | 04 | 05 | 40, 42 | Video 1 | 3 |
|
| 44, 46 | Voice | 2 | 05 | 06 | 48, 50 | Control | 1 | 06 |
| 52, 54 | NetCrit | 0 | 07 | 07 | 56, 58, 60, 62 |
Correspondence table between the priorities of the standard protocols and the internal priorities used by the InfiLINK XG, InfiLINK XG 1000, Quanta 5, Quanta 6 and Quanta 70 families of devicesTraffic class (in accordance with 802.1p) | 802.1p | InfiLINK XG, InfiLINK XG 1000 | Quanta 5, Quanta 6, Quanta 70 |
---|
Background (lowest priority) | 00 | 1 | 0 | Best Effort | 01 | 1 | Excellent Effort | 02 | 2 | 2 | Critical Applications | 03 | 3 | Video | 04 | 3 | 4 | Voice | 05 | 5 | Internetwork Control | 06 | 4 | 6 | Network Control (higher priority) | 07 | 7 |
|
...
Center |
---|
Throughput limitation capabilities in Infinet devices
Parameter | Description | InfiLINK 2x2 / InfiMAN 2x2 | InfiLINK Evolution / InfiMAN Evolution | InfiLINK XG / InfiLINK XG 1000 |
---|
Interface shaping | The throughput limitation capabilities of the device's physical interface. | - | - | | Logical stream shaping | The throughput limitation capability for a traffic stream, filtered according to one or more criteria. | up to 200 logical channels | up to 200 logical channels | - | Traffic directions | Ability to apply limitations to the incoming/outgoing traffic flows. | incoming and outgoing | incoming and outgoing | outgoing | Limitations hierarchy
| The ability to create a system of hierarchical limitations. | up to 200 logical channels, which are the children of the logical classes | up to 200 logical channels, which are the children of the logical classes | - | Logical stream filtering | Criteria used to filter the data streams. | PCAP expressions support (PCAP expressions allow to perform a flexible limitation based on any service header field, see the PCAP filters article) | PCAP expressions support (PCAP expressions allow to perform a flexible limitation based on any service header field, see the PCAP filters article) | - | Traffic shaping in Web | Documentation about throughput limitation settings in the Web interface.
| Traffic shaping | Traffic Shaping | Switch | Traffic shaping in CLI | Documentation about throughput limitation settings via CLI.
| qm command | qm command | Commands for switch configuration |
|
Recommendations for the throughput limitation configuration
...
- RFC 4594.
- RFC 791.
- RFC 1349.
- RFC 2474.
- InfiMONITOR monitoring system.
- InfiLINK 2x2, InfiMAN 2x2 family devices web interface. QoS options.
- InfiLINK 2x2, InfiMAN 2x2 family devices web interface. Traffic shaping.
- InfiLINK Evolution, InfiMAN Evolution family devices web interface. QoS options.
- InfiLINK Evolution, InfiMAN Evolution family devices web interface. Traffic shaping.
- InfiLINK XG, InfiLINK XG 1000 family devices web interface. Configuring QoS.
- Quanta 5, Quanta 6 family devices web interface. Switch settings.
- Quanta 70 family devices web interface. Switch settings.
- QoS configuration in OS WANFleX.