Hide Navigation Pane
Show Navigation Pane
Feedback
Download
SHA1
Verifying the Link Services intelligent queuing Interface Configuration
To verify a link services configuration, perform the following tasks:
- Displaying Multilink Bundle Configurations
- Displaying Link Services CoS Configurations
- Verifying Link Services Interface Statistics
- Verifying Link Services CoS
Displaying Multilink Bundle Configurations
Purpose
Verify the multilink bundle configuration.
Action
Enter the show interfaces command.
The sample output in this section displays the multilink bundle configurations provided in Configuring MLPPP Bundles and LFI on Serial Links.
 | Note: The MLFR FRF.15 and MLFR FRF.16 configurations are not displayed in this section, but you can display MLFR configurations in the same manner. |
[edit]user@R0# show interfacesinterfaces {lsq-0/0/0 {per-unit-scheduler;unit 0 {encapsulation multilink-ppp;fragment-threshold 128;family inet {address 10.0.0.10/24;}}}ge-0/0/1 {unit 0 {family inet {address 192.1.1.1/24;}}}se-1/0/0 {per-unit-scheduler;dce-options {clocking-mode dce;clocking-rate 2.0mhz;}unit 0 {family mlppp {bundle lsq-0/0/0.0;}}}se-1/0/1 {per-unit-scheduler;dce-options {clocking-mode dce;clocking-rate 2.0mhz;}unit 0 {family mlppp {bundle lsq-0/0/0.0;}}}}
Meaning
Verify that the output shows the intended multilink bundle configurations.
Displaying Link Services CoS Configurations
Purpose
Displaying the CoS configurations on the link services interface.
Action
Enter the show class-of-service command.
The sample output in this section displays the CoS configurations provided in Configuring MLPPP Bundles and LFI on Serial Links.
[edit]user@R0# show class-of-serviceclassifiers {inet-precedence classify_input {forwarding-class DATA {loss-priority low code-points 000;}forwarding-class VOICE {loss-priority low code-points 010;}}}forwarding-classes {queue 0 DATA;queue 2 VOICE;queue 3 NC;}interfaces {ls-0/0/0 {unit 0 {scheduler-map s_map;fragmentation-maps fm;}}ge-0/0/1 {unit 0 {classifiers {inet-precedence classify_input}}}se-1/0/0 {unit 0 {scheduler-map s_map;shaping-rate 2000000;}}se-1/0/1 {unit 0 {scheduler-map s_map;shaping-rate 2000000;}}}scheduler-maps {s_map {forwarding-class DATA scheduler DATA;forwarding-class VOICE scheduler VOICE;forwarding-class NC scheduler NC;}}schedulers {DATA {transmit-rate percent 49;buffer-size percent 49;}VOICE {transmit-rate percent 50;buffer-size percent 5;priority high;}NC {transmit-rate percent 1;buffer-size percent 1;priority high;}}fragmentation-maps fm {forwarding-class {VOICE {no-fragmentation;}}}
Meaning
Verify that the output shows the intended CoS configurations.
Verifying Link Services Interface Statistics
Purpose
Verify the link services interface statistics.
Action
The sample output provided in this section is based on the configurations provided in Configuring MLPPP Bundles and LFI on Serial Links. To verify that the constituent links are added to the bundle correctly and the packets are fragmented and transmitted correctly, take the following actions:
- On Device R0 and Device R1, the two J Series devices used in this example, configure MLPPP and LFI as described in Configuring MLPPP Bundles and LFI on Serial Links.
- From the CLI, enter the ping command to verify that a connection is established between R0 and R1.
- Transmit 10 data packets, 200 bytes each, from R0 to R1.
- On R0, from the CLI, enter the show interfaces interface-name statistics command.
Sample Output
user@R0> show interfaces lsq-0/0/0 statistics
detailPhysical interface: lsq-0/0/0, Enabled, Physical link is Up
Interface index: 134, SNMP ifIndex: 29, Generation: 135
Link-level type: LinkService, MTU: 1504
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps
Last flapped : 2006-06-23 11:36:23 PDT (03:38:43 ago)
Statistics last cleared: 2006-06-23 15:13:12 PDT (00:01:54 ago)
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 1820 0 bps
Input packets: 0 0 pps
Output packets: 10 0 pps
...
Egress queues: 8 supported, 8 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 DATA 10 10 0
1 expedited-fo 0 0 0
2 VOICE 0 0 0
3 NC 0 0 0
Logical interface lsq-0/0/0.0 (Index 67) (SNMP ifIndex 41) (Generation 133)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: Multilink-PPP
Bandwidth: 16mbps
Bundle options:
...
Drop timer period 0
Sequence number format long (24 bits)
Fragmentation threshold 128
Links needed to sustain bundle 1
Interleave fragments Enabled
Bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
...
Statistics Frames fps Bytes bps
Bundle:
Fragments:
Input : 0 0 0 0
Output: 20 0 1920 0
Packets:
Input : 0 0 0 0
Output: 10 0 1820 0
Link:
se-1/0/0.0
Input : 0 0 0 0
Output: 10 0 1320 0
se-1/0/1.0
Input : 0 0 0 0
Output: 10 0 600 0
...
Destination: 10.0.0.9/24, Local: 10.0.0.10, Broadcast: Unspecified, Generation:144
Meaning
This output shows a summary of interface information. Verify the following information:
- Physical interface—The physical interface
is Enabled. If the interface is shown as Disabled, do either of the following:
- In the CLI configuration editor, delete the disable statement at the [edit interfaces interface-name] level of the configuration hierarchy.
- In the J-Web configuration editor, clear the Disable check box on the Interfaces>interface-name page.
- Physical link—The physical link is Up. A link state of Down indicates a problem with the interface module, interface port, or physical connection (link-layer errors).
- Last flapped—The Last Flapped time is an expected value. The Last Flapped time indicates the last time the physical interface became unavailable and then available again. Unexpected flapping indicates likely link-layer errors.
- Traffic statistics—Number and rate of bytes and packets received and transmitted on the interface. Verify that the number of inbound and outbound bytes and packets match the expected throughput for the physical interface. To clear the statistics and see only new changes, use the clear interfaces statistics interface-name command.
- Queue counters—Name and number of queues are as configured. This sample output shows that 10 data packets were transmitted and no packets were dropped.
- Logical interface—Name of the multilink bundle you configured—lsq-0/0/0.0.
- Bundle options—Fragmentation threshold is correctly configured, and fragment interleaving is enabled.
- Bundle errors—Any packets and fragments dropped by the bundle.
- Statistics—The fragments and packets are
received and transmitted correctly by the device. All references to
traffic direction (input or output) are defined with respect to the
device. Input fragments received by the device are assembled into
input packets. Output packets are segmented into output fragments
for transmission out of the device.
In this example, 10 data packets of 200 bytes were transmitted. Because the fragmentation threshold is set to 128 bytes, all data packets were fragmented into two fragments. The sample output shows that 10 packets and 20 fragments were transmitted correctly.
- Link—The constituent links are added to this bundle and are receiving and transmitting fragments and packets correctly. The combined number of fragments transmitted on the constituent links must be equal to the number of fragments transmitted from the bundle. This sample output shows that the bundle transmitted 20 fragments and the two constituent links se-1/0/0.0 and se-1/0/1.0.0 correctly transmitted 10+10=20 fragments.
- Destination and Local—IP address of the remote side of the multilink bundle and the local side of the multilink bundle. This sample output shows that the destination address is the address on R1 and the local address is the address on R0.
Related Topics
For a complete description of show interfaces output, see the Junos Interfaces Command Reference.
Verifying Link Services CoS
Purpose
Verify CoS configurations on the link services interface.
Action
From the CLI, enter the following commands:
- show class-of-service interface interface-name
- show class-of-service classifier name classifier-name
- show class-of-service scheduler-map scheduler-map-name
The sample output provided in this section is based on the configurations provided in Configuring MLPPP Bundles and LFI on Serial Links.
Sample Output
user@R0> show class-of-service interface
lsq-0/0/0Physical interface: lsq-0/0/0, Index: 136
Queues supported: 8, Queues in use: 4
Scheduler map: [default], Index: 2
Input scheduler map: [default], Index: 3
Chassis scheduler map: [default-chassis], Index: 4
Logical interface: lsq-0/0/0.0, Index: 69
Object Name Type Index
Scheduler-map s_map Output 16206
Classifier ipprec-compatibility ip 12user@R0> show class-of-service interface
ge-0/0/1Physical interface: ge-0/0/1, Index: 140
Queues supported: 8, Queues in use: 4
Scheduler map: [default], Index: 2
Input scheduler map: [default], Index: 3
Logical interface: ge-0/0/1.0, Index: 68
Object Name Type Index
Classifier classfy_input ip 4330user@R0> show class-of-service classifier
name classify_inputClassifier: classfy_input, Code point type: inet-precedence, Index: 4330
Code point Forwarding class Loss priority
000 DATA low
010 VOICE low
user@R0> show class-of-service scheduler-map
s_mapScheduler map: s_map, Index: 16206
Scheduler: DATA, Forwarding class: DATA, Index: 3810
Transmit rate: 49 percent, Rate Limit: none, Buffer size: 49 percent, Priority:low
Drop profiles:
Loss priority Protocol Index Name
Low any 1 [default-drop-profile]
Medium low any 1 [default-drop-profile]
Medium high any 1 [default-drop-profile]
High any 1 [default-drop-profile]
Scheduler: VOICE, Forwarding class: VOICE, Index: 43363
Transmit rate: 50 percent, Rate Limit: none, Buffer size: 5 percent, Priority:high
Drop profiles:
Loss priority Protocol Index Name
Low any 1 [default-drop-profile]
Medium low any 1 [default-drop-profile]
Medium high any 1 [default-drop-profile]
High any 1 [default-drop-profile]
Scheduler: NC, Forwarding class: NC, Index: 2435
Transmit rate: 1 percent, Rate Limit: none, Buffer size: 1 percent, Priority:high
Drop profiles:
Loss priority Protocol Index Name
Low any 1 [default-drop-profile]
Medium low any 1 [default-drop-profile]
Medium high any 1 [default-drop-profile]
High any 1 [default-drop-profile]
Meaning
These output examples show a summary of configured CoS components. Verify the following information:
- Logical Interface—Name of the multilink bundle and the CoS components applied to the bundle. The sample output shows that the multilink bundle is lsq-0/0/0.0, and the CoS scheduler-map s_map is applied to it.
- Classifier—Code points, forwarding classes, and loss priorities assigned to the classifier. The sample output shows that a default classifier, ipprec-compatibility, was applied to the lsq-0/0/0 interface and the classifier classify_input was applied to the ge-0/0/1 interface.
- Scheduler—Transmit rate, buffer size, priority, and loss priority assigned to each scheduler. The sample output displays the data, voice, and network control schedulers with all the configured values.
Related Topics
For complete descriptions of show class-of-service commands and output, see the Junos System Basics and Services Command Reference.
