Cisco 10000 - Manual (Page 459)

19-41
Cisco 10000 Series Router Software Configuration Guide
OL-2226-23
Chapter 19 Configuring Multilink Point-to-Point Protocol Connections
Verifying and Monitoring MLP Connections
Example 19-11 Sample Output for the show ppp multilink Command
Router# show ppp multilink
Multilink3, bundle name is multilink_name-3
Endpoint discriminator is multilink_name-3
Bundle up for 3d21h, total bandwidth 128, load 1/255
Receive buffer limit 24384 bytes, frag timeout 1000 ms
Bundle is Distributed
0/0 fragments/bytes in reassembly list
1 lost fragments, 1 reordered
0/0 discarded fragments/bytes, 0 lost received
0x831D received sequence, 0x0 sent sequence
C10K Multilink PPP info
Bundle transmit info
send_seq_num 0x0
Bundle reassembly info
expected_seq_num: 0x00831E
Member links: 2 active, 0 inactive (max 10, min not set)
Vi5, since 3d21h, 16 weight, 82 frag size
Vi4, since 3d19h, 16 weight, 82 frag size No inactive multilink interfaces
The following list describes the bundle-level fields and lines in the show ppp multilink command
output:
• Bundle name is name—The bundle identifier for the bundle.
• Bundle up for time—The elapsed time since the bundle first came up.
• load n/255—The traffic load on the bundle as multilink computes loads for bandwidth-on-demand
purposes. This load might count all traffic, or just inbound or outbound traffic, depending on the
configuration.
• Receive buffer limit n bytes—The maximum amount of fragment data that multilink can buffer in
its fragment reassembly engine for each receive class. This amount is derived from the configured
slippage constraints.
• Frag timeout n ms—The maximum amount of time that multilink waits for an expected fragment
before declaring it lost. This limit applies only when fragment loss cannot be detected by other,
faster means such as sequence number-based detection.
• Member links:—The number of active and inactive links currently in the bundle, followed by the
desired minimum and maximum number of links. The actual number might be outside the range.
After all of the bundle parameters display, information about each individual link in the bundle displays.
Extra link-level parameters might be shown after each link in certain circumstances. The following list
describes the individual link parameters:
• Weight—The weight is used for load balancing. Data is distributed between the member links in
proportion to their weight. The weight is proportional to multilink’s notion of the effective
bandwidth of a link. Therefore, multilink effectively distributes data to the links in proportion to
their bandwidth.
The effective bandwidth of a link is the configured bandwidth value, except on asynchronous lines
where multilink uses a value that is 0.8 times the configured bandwidth setting. This exception
occurs because, on an asynchronous line, at best only 8/10 of the raw bandwidth is available for
transmitting real data and the remainder is consumed in framing overhead.
Previously, the weight also controlled the size of the fragments generated for that link. However,
Cisco IOS software now computes a separate fragment size value.
• Frag size—The size of the largest fragment that can be generated for that link. It is the size of the
MLP payload carried by a fragment and does not include MLP headers or link-level framing.