Allied Telesis AT-8824 Installationsanleitung Seite 5
- Seite / 202
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Software Version 2.7.5 5
Software Version 2.7.5
C613-10454-00 REV A
MSS Clamping
Maximum Segment Size (MSS) clamping functionality has been introduced to
Point-to-Point Protocol (PPP) to allow the following:
■ User configuration of the MSS clamping value via the command line
interface.
■ A clamping range of 40 - 200 bytes.
Previously, MSS clamping occurred at a fixed value of 120 bytes.
Overview
MSS clamping reserves a set amount of space within a TCP packet for the
header, which in turn limits the amount of space that may be consumed by the
data (payload). Setting the header space value to an appropriate level prevents
packet fragmentation from occurring.
Maximum
Transmission Unit and
Maximum Segment
Size
The Maximum Transmission Unit (MTU) is the maximum number of bytes per
packet that may be transmitted by the network interface. If a single packet
exceeds the MTU, it is divided into smaller packets before being transmitted.
For a TCP packet, the MTU can be illustrated by the following equation:
MTU = Header Size + Maximum Segment Size
where:
■ Header Size is the size of the packet header
■ Maximum Segment Size is the largest amount of TCP data, in bytes, that
the router or switch can transmit or receive in one single data packet.
MTU is set with the set interface mtu command. For more information, see the
Interfaces chapter of the Software Reference.
Data Transmission and
MSS clamping
As packets are sent across various protocols, each protocol adds its own header
and encapsulates the information. This can increase the size of the packet being
transmitted, potentially exceeding the MTU of devices on the TCP/IP link.
When the packet exceeds the defined MTU for an interface, fragmentation
occurs. Packet fragmentation can be costly for the following reasons:
■ decreased throughput, the amount of data transferred or processed in a
specified amount of time
■ networks that are explicitly set to drop fragmented packets suffer
communication loss.
Each TCP device uses its MSS value to communicate the highest allowable
amount of data it can receive. Although devices in a TCP/IP connection
calculate the amount of data to send in a packet based on variables, such as the
current window size and various algorithms, the amount of actual data can
never exceed the MSS of the device the packet is being sent to.
Setting the MSS clamping value at an appropriate limit prevents fragmentation
by reserving a set amount of space within a TCP packet for the header, so that
the packet nver needs to be fragmented at any point in its journey. Allowing
header space, in turn, limits the amount of space that may be consumed by the
data payload.
- Software Version 2.7.5 1
- Overview of New Features 4
- MSS Clamping 5
- 8 MSS Clamping Release Note 8
- Software Version 2.7.5 9 9
- 10 MSS Clamping Release Note 10
- Syntax SHow PPP PPPoe 11
- Command changes 13
- Command Reference Updates 14
- Software Version 2.7.5 15 15
- Command Changes 18
- Syntax SHow IP 21
- DHCP Option 82 Relay 22
- Software Version 2.7.5 25 25
- Syntax SHow BOOTp RELAy 26
- IGMP Enhancements 28
- Filtering and Throttling 29
- Configuring IGMP 30
- IGMP Throttling 31
- Software Version 2.7.5 33 33
- Software Version 2.7.5 35 35
- OSPF Network Types 41
- [{FULl 45
- BGP Enhancements 46
- Automatic Summarising 48
- Aggregating Routes 50
- Software Version 2.7.5 53 53
- Syntax SHow BGP 55
- Syntax SHow BGP PEer[=ipadd] 56
- Software Version 2.7.5 59 59
- Software Version 2.7.5 61 61
- Firewall Enhancements 63
- UDP Port Timeout 65
- Software Version 2.7.5 67 67
- Software Version 2.7.5 73 73
- WAN Load Balancing 74
- VRRP Preemption Delay 75
- Software Version 2.7.5 77 77
- ..3600] [PRIOrity=1..254] 77
- Operating Principles 80
- Load Distribution Methods 81
- 1-4 Release Note 82
- WAN Load Balancing 1-5 83
- Healthcheck 84
- Assigning Weights 85
- Healthchecks 86
- Operation with Firewall 87
- 1-10 Release Note 88
- Before you 89
- Parameter Description 96
- ● eth (such as eth0, eth1) 100
- ● PPP (such as ppp0, ppp1) 100
- C613-10454-00 REV A 101
- Related Commands enable wanlb 109
- Syntax SHow WANLB 112
- Syntax SHow WANLB HEALthcheck 114
- ■ eth (such as eth0, eth1) 122
- ■ PPP (such as ppp0, ppp1) 122
- Filtering IP Routes 123
- 2-2 Release Note 124
- Introduction 125
- Types of Filters 126
- About AS Path Lists 127
- About Route Maps 127
- When to use 128
- About IP Route Filters 129
- Creating Filters 130
- Creating Route Maps for BGP 131
- How to create a route map 132
- ■ exclude the update message 133
- Example comparing 134
- AS path filter and 134
- Matching on 134
- Creating Route Maps for OSPF 138
- Creating IP Route Filters 141
- Applying Filters 142
- Applying AS path 143
- ■ prefix lists 148
- ■ AS path lists 148
- ■ route maps 148
- 2-28 Release Note 150
- [other-options] 150
- Filtering IP Routes 2-29 151
- The filtering 151
- Limitations of route 153
- Interface Routes 154
- Statically-Configured Routes 155
- Configuration Examples 156
- Using a Route Map 157
- Using an AS Path Filter 158
- Using Communities 160
- Command Reference 162
- Parameters for both 173
- Parameters for 173
- Parameters for set 176
- ■ an entire route map 181
- [PREfix=ipadd] 182
Verwandte Produkte und Handbücher für Netzwerk-Switches Allied Telesis AT-8824
(179 Seiten)
(32 Seiten)© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.115 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern