|
|
< Free Open Study > |
|
Link ManagerUnderneath a lot of externally visible RSVP and MPLS things is something called the link manager. The link manager's job is to track interface-related stuff with regard to MPLS Traffic Engineering. Specifically, the link manager keeps track of the following:
The link manager isn't really something you can configure. However, it's useful to know it's there. The link manager has several things you can look at, as demonstrated in Example 4-45. Example 4-45 Displaying Link Manager Capabilities
gsr2#show mpls traffic-eng link-management ?
admission-control Link Management admission-control
advertisements Link Management advertisements
bandwidth-allocation Link Management bandwidth-allocation
igp-neighbors Link Management igp-neighbors
interfaces Link Management Traffic Engineering interfaces
statistics Link Management Traffic Engineering statistics
summary Link Management summary
The following sections provide output from each of these commands, along with some comments. Figure 4-43 shows the topology used in the link manager examples. Figure 4-43. Network Topology for the Link Manager Examples
There are 50 2-Mbps tunnels from gsr4 to gsr8 and 50 1-Mbps tunnels from gsr8 to gsr4. All these commands were done on gsr4, so the link manager output is consistent with the other output in this chapter. Most of these commands also take an interface as an optional argument, but the command output doesn't change other than showing you the interface you specify. show mpls traffic-eng link-management admission-control CommandAs Example 4-46 demonstrates, this command shows all the LSPs that the admission control portion of the link manager is aware of. The STATE of Resv Admitted means that a Resv for this tunnel has been sent, and everything is good. There can be other states for LSPs that are in the process of being set up or torn down. In the far-right column, the R means that the bandwidth has been reserved with a Resv. If the display has a tunnel that has an H instead of an R, this indicates that the bandwidth is being held. This means that the router has seen a Path message for a tunnel but has not yet seen the Resv. The G next to the R means that the bandwidth reserved for this tunnel was reserved from the global pool rather than the subpool (see the section "DiffServ-Aware Traffic Engineering (DS-TE)" in Chapter 6). Example 4-46 show mpls traffic-eng link-management admission-control Command Output
gsr5#show mpls traffic-eng link-management admission-control
System Information::
Tunnels Count: 100
Tunnels Selected: 100
TUNNEL ID UP IF DOWN IF PRIORITY STATE BW (kbps)
192.168.1.4 1_16 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 2_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 3_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 4_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 5_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 6_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 7_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 8_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 9_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
192.168.1.4 10_15 PO4/1 PO4/2 7/7 Resv Admitted 2000 RG
...
show mpls traffic-eng link-management advertisements CommandAs demonstrated in Example 4-47, this command shows the information that the link manager floods when it asks the IGP to flood. Information for each link on the router is shown. On Link ID 0 (the link between gsr5 and gsr4), at priority 7, the reservable bandwidth is 66,250 Kbps, whereas it's 116,250 Kbps at every other priority. This is because of the 50 1-Mb tunnels from gsr8 to gsr2; these tunnels all have setup and holding priorities of 7, so tunnels with a better priority see the full 116,250 Kb available to them. The same thing is true on Link ID 1 between gsr5 and gsr6. The 50 2-Mbps tunnels from gsr4 to gsr8 mean that the remaining bandwidth at priority 7 is 16,250 Kbps. Example 4-47 show mpls traffic-eng link-management advertisements Command Output (Continued)gsr5#show mpls traffic-eng link-management advertisements Flooding Status: ready Configured Areas: 3 IGP Area[1] ID:: isis level-1 System Information:: Flooding Protocol: ISIS Header Information:: IGP System ID: 0168.0001.0005.00 MPLS TE Router ID: 192.168.1.5 Flooded Links: 2 Link ID:: 0 Link Subnet Type: Point-to-Point Link IP Address: 192.168.3.5 IGP Neighbor: ID 0168.0001.0004.00, IP 192.168.3.4 TE metric: 10 IGP metric: 10 Physical Bandwidth: 155000 kbits/sec Res. Global BW: 116250 kbits/sec Res. Sub BW: 0 kbits/sec Downstream:: Global Pool Sub Pool ----------- ---------- Reservable Bandwidth[0]: 116250 0 kbits/sec Reservable Bandwidth[1]: 116250 0 kbits/sec Reservable Bandwidth[2]: 116250 0 kbits/sec Reservable Bandwidth[3]: 116250 0 kbits/sec Reservable Bandwidth[4]: 116250 0 kbits/sec Reservable Bandwidth[5]: 116250 0 kbits/sec Reservable Bandwidth[6]: 116250 0 kbits/sec Reservable Bandwidth[7]: 66250 0 kbits/sec Attribute Flags: 0x00000000 Link ID:: 1 Link Subnet Type: Point-to-Point Link IP Address: 192.168.10.5 IGP Neighbor: ID 0168.0001.0006.00, IP 192.168.10.6 TE metric: 10 IGP metric: 10 Physical Bandwidth: 155000 kbits/sec Res. Global BW: 116250 kbits/sec Res. Sub BW: 0 kbits/sec Downstream:: Global Pool Sub Pool ----------- ---------- Reservable Bandwidth[0]: 116250 0 kbits/sec Reservable Bandwidth[1]: 116250 0 kbits/sec Reservable Bandwidth[2]: 116250 0 kbits/sec Reservable Bandwidth[3]: 116250 0 kbits/sec Reservable Bandwidth[4]: 116250 0 kbits/sec Reservable Bandwidth[5]: 116250 0 kbits/sec Reservable Bandwidth[6]: 116250 0 kbits/sec Reservable Bandwidth[7]: 16250 0 kbits/sec Attribute Flags: 0x00000000 show mpls traffic-eng link-management bandwidth-allocation CommandThis command shows a few interesting things. Some of the output, as demonstrated in Example 4-48, is the same as show mpls traffic-eng link-manager advertisements, but not all of it. In particular, the flooding thresholds (discussed in Chapter 3) are displayed, as well as the amount of reserved bandwidth at each priority level. The 50 Mbps and 100 Mbps of reserved bandwidth from the tunnels between gsr4 and gsr8 show up here as well. The BW HELD state is a temporary state that bandwidth is put in when a Path message has been seen for a tunnel, but not a Resv. It's difficult to see values in the BW HELD/TOTALBW HELD columns in the real world, because tunnel setup takes only a few seconds at most. If you see bandwidth constantly in the HELD/TOTAL HELD columns, it's likely an indication of problems. Example 4-48 show mpls traffic-eng link-management bandwidth-allocation Command Outputgsr5#show mpls traffic-eng link-management bandwidth-allocation System Information:: Links Count: 2 Bandwidth Hold Time: max. 15 seconds Link ID:: PO4/1 (192.168.3.5) Link Status: Physical Bandwidth: 155000 kbits/sec Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 43% out) Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out) BW Descriptors: 50 MPLS TE Link State: MPLS TE on, RSVP on, admin-up Inbound Admission: allow-all Outbound Admission: allow-if-room Admin. Weight: 10 (IGP) IGP Neighbor Count: 1 Up Thresholds: 15 30 45 60 75 80 85 90 95 96 97 98 99 100 (default) Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15 (default) Downstream Global Pool Bandwidth Information (kbits/sec): KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED 0 0 0 0 0 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 50000 50000 Downstream Sub Pool Bandwidth Information (kbits/sec): KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED 0 0 0 0 0 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 Link ID:: PO4/2 (192.168.10.5) Link Status: Physical Bandwidth: 155000 kbits/sec Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 86% out) Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out) BW Descriptors: 50 MPLS TE Link State: MPLS TE on, RSVP on, admin-up Inbound Admission: allow-all Outbound Admission: allow-if-room Admin. Weight: 10 (IGP) IGP Neighbor Count: 1 Up Thresholds: 15 30 45 60 75 80 85 90 95 96 97 98 99 100 (default) Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15 (default) Downstream Global Pool Bandwidth Information (kbits/sec): KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED 0 0 0 0 0 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 100000 100000 Downstream Sub Pool Bandwidth Information (kbits/sec): KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED 0 0 0 0 0 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 show mpls traffic-eng link-management igp-neighbors CommandAs the output in Example 4-49 demonstrates, this command just shows what neighbors exist on any links configured for traffic engineering. Information about a TE link is not flooded unless an IGP neighbor exists on that link. If a neighbor doesn't exist to send a Resv to, the rest of the network doesn't need to know about the link. Example 4-49 show mpls traffic-eng link-management igp-neighbors Command Output
gsr5#show mpls traffic-eng link-management igp-neighbors
Link ID:: PO4/1
Neighbor ID: 0168.0001.0004.00 (area: isis level-1, IP: 192.168.3.4)
Link ID:: PO4/2
Neighbor ID: 0168.0001.0006.00 (area: isis level-1, IP: 192.168.10.6)
show mpls traffic-eng link-management interfaces CommandThis command shows much the same information as the other commands. The only difference is that the flooding status for each link is also shown, as demonstrated in Example 4-50. Example 4-50 show mpls traffic-eng link-management interfaces Command Output
gsr5#show mpls traffic-eng link-management interfaces
System Information::
Links Count: 2
Link ID:: PO4/1 (192.168.3.5)
Link Status:
Physical Bandwidth: 155000 kbits/sec
Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 43% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up
Inbound Admission: allow-all
Outbound Admission: allow-if-room
Admin. Weight: 10 (IGP)
IGP Neighbor Count: 1
IGP Neighbor: ID 0168.0001.0004.00, IP 192.168.3.4 (Up)
Flooding Status for each configured area [1]:
IGP Area[1]: isis level-1: flooded
Link ID:: PO4/2 (192.168.10.5)
Link Status:
Physical Bandwidth: 155000 kbits/sec
Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 86% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up
Inbound Admission: allow-all
Outbound Admission: allow-if-room
Admin. Weight: 10 (IGP)
IGP Neighbor Count: 1
IGP Neighbor: ID 0168.0001.0006.00, IP 192.168.10.6 (Up)
Flooding Status for each configured area [1]:
IGP Area[1]: isis level-1: flooded
show mpls traffic-eng link-management statistics CommandAs demonstrated in Example 4-51, this command shows some statistics about RSVP messages sent on each link. Up Path and Up Resv are Path and Resv messages received on the interface (from the upstream router), and Down Path and Down Resv are messages sent on the interface (to the downstream router). Because this router has only two links active in MPLS Traffic Engineering, any message received in Up Path on one link is also counted in Down Path on the other link, and vice versa. This output was taken right after both tunnels came up for the first time. So you see two setup requests (both of which were admitted) on the Up interface and on the Down interface. Example 4-51 show mpls traffic-eng link-management statistics Command Output
gsr5#show mpls traffic-eng link-management statistics
System Information::
LSP Admission Statistics:
Path: 138 setup requests, 138 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
Resv: 138 setup requests, 138 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
Link ID:: PO4/1 (192.168.3.5)
Link Admission Statistics:
Up Path: 50 setup requests, 50 admits, 0 rejects, 0 setup errors
0 tear requests, 0 preempts, 0 tear errors
Up Resv: 50 setup requests, 50 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
Down Path: 88 setup requests, 88 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
Down Resv: 88 setup requests, 88 admits, 0 rejects, 0 setup errors
0 tear requests, 0 preempts, 0 tear errors
Link ID:: PO4/2 (192.168.10.5)
Link Admission Statistics:
Up Path: 88 setup requests, 88 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
Up Resv: 88 setup requests, 88 admits, 0 rejects, 0 setup errors
0 tear requests, 0 preempts, 0 tear errors
Down Path: 50 setup requests, 50 admits, 0 rejects, 0 setup errors
0 tear requests, 0 preempts, 0 tear errors
Down Resv: 50 setup requests, 50 admits, 0 rejects, 0 setup errors
38 tear requests, 0 preempts, 0 tear errors
show mpls traffic-eng link-management summary CommandAs demonstrated in Example 4-52, this command shows a summary of link information. It also has much the same information as other links (commands), but not as much. Example 4-52 show mpls traffic-eng link-management summary Command Output
gsr5#show mpls traffic-eng link-management summary
System Information::
Links Count: 2
Flooding System: enabled
IGP Area ID:: isis level-1
Flooding Protocol: ISIS
Flooding Status: data flooded
Periodic Flooding: enabled (every 180 seconds)
Flooded Links: 2
IGP System ID: 0168.0001.0005.00
MPLS TE Router ID: 192.168.1.5
IGP Neighbors: 2
Link ID:: PO4/1 (192.168.3.5)
Link Status:
Physical Bandwidth: 155000 kbits/sec
Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 43% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up
Inbound Admission: allow-all
Outbound Admission: allow-if-room
Admin. Weight: 10 (IGP)
IGP Neighbor Count: 1
Link ID:: PO4/2 (192.168.10.5)
Link Status:
Physical Bandwidth: 155000 kbits/sec
Max Res Global BW: 116250 kbits/sec (reserved: 0% in, 86% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out)
MPLS TE Link State: MPLS TE on, RSVP on, admin-up
Inbound Admission: allow-all
Outbound Admission: allow-if-room
Admin. Weight: 10 (IGP)
IGP Neighbor Count: 1
|
|
|
< Free Open Study > |
|
