|
|
The DLSw+ RSVP Bandwidth Reservation feature allows DLSw+ to reserve network bandwidth for the DLSw+ TCP connection between DLSw+ peers.
Although it has been possible to reserve bandwidth for a particular existing DLSw+ peer connection through the RSVP command line interface (CLI) support in Cisco IOS software, the CLI required prior knowledge of the TCP ports for which the reservation was being made. Because DLSw+ used one well-known port and one randomly assigned port, the reservation could not be made until after the peer connection was active.
The DLSw+ RSVP Bandwidth Reservation feature permits new DLSw+ peer connections to request bandwidth reservations automatically upon connection, thereby removing the need for user intervention after the peer is connected. This feature ensures the reservation survives a network or device failure and that the DLSw+ traffic carried over a TCP connection is not affected by congestion.
Resource Reservation Protocol (RSVP)---IETF standard for allowing applications to request specific Quality of Service (QOS) for specific flows (as specified in RFC 2205).
The DLSw+ RSVP Bandwidth Reservation feature is supported on the following platforms:
No MIBs are supported by this feature.
The DLSw+ RSVP Bandwidth Reservation feature supports the following RFCs:
The user specifies the amount of RSVP reserved bandwidth for DLSw+ in the following ways:
In any of these situations, the user turns off RSVP by setting the average-bit-rate or maximum-burst values to 0.
Because RSVP requires both a sender and a receiver, the DLSw+ RSVP Bandwidth Reservation feature must be implemented on both devices of a DLSw+ connection. However, RSVP does not need to be configured on all devices that are in the IP routed path between two DLSw+ peers. In this type of configuration the devices in the middle must support only IP RSVP; they do not need to be configured for the new DLSw+ RSVP Bandwidth Reservation feature or of DLSw+. The devices between the peers prioritize the IP packets belonging to the DLSw+ session according to the IP TOS settings. If, however, the devices in the middle do not support IP RSVP, end-to-end bandwidth is not guaranteed.
In the case of priority peers, RSVP bandwidth reservation is done only for the highest priority connection to the peer (TCP port 2065). If the user configures priority queuing and RSVP on the same peer, the user must ensure that the RSVP designated traffic is assigned to the highest priority TCP peer connection.
If the users change the average-bit-rate or maximum-burst settings without removing the existing RSVP bandwidth reservation, a message warns the users that they are removing the existing reservation and that they need to request a new reservation with new values.
Issuing the dlsw rsvp command enables the DLSw+ RSVP Bandwidth Reservation feature on the router and sets the RSVP parameters for all of its peer connections.
To enable the DLSw+ RSVP Bandwidth Reservation feature, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
Enable DLSw+ RSVP Bandwidth Reservation feature on the local peer. |
After RSVP is globally enabled, the user must enable RSVP on specific peers. The user can retain the average-bit-rate and maximum-burst values set in the dlsw rsvp command or the user can override these values for any particular peer connection (remote, promiscuous, or peer-on-demand) by configuring the dlsw remote peer, dlsw prom-peer-defaults, or dlsw peer-on-demand-defaults command.
To enable RSVP support for a remote peer connection, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
dlsw remote peer [rsvp {global | [average-bit-rate maximum burst]}] | Configures RSVP parameters for a specific peer connection. |
To enable RSVP support for a promiscuous peer connection, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
dlsw prom-peer-defaults [rsvp {global | learn | [average-bit-rate maximum burst]}] | Configures RSVP parameters for this promiscuous peer's connection. |
To enable RSVP support for a peer-on-demand connection, use the following command in global configuration mode
| Command | Purpose |
|---|---|
dlsw peer-on-demand-defaults [global | average-bit-rate maximum burst] | Configures RSVP parameters for this peer-on-demand peer's connection. |
To verify that the RSVP PATH messages for DLSw+ are sent and that the feature is working correctly, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
Verifies that the RSVP PATH messages for DLSw+ are being sent. |
To verify whether the RSVP RESV messages for DLSw+ are sent all the way through the RSVP network to the remote peer, issue the following command in global configuration mode:
| Command | Purpose |
|---|---|
Verifies that the RSVP RESV messages for DLSw+ are being sent. |
To verify that the RSVP bandwidth reservations are in place for the DLSw+ peers, issue the following command in global configuration mode:
| Command | Purpose |
|---|---|
Verifies that the RSVP reservations are configured for a peer. |
To disable the DLSw+ RSVP Bandwidth Reservation feature for all peers, issue the following command in global configuration mode:
| Command | Purpose |
|---|---|
Disables the DLSw+ RSVP Bandwidth Reservation feature. |
Setting the average-bit-rate and maximum burst values to 0 in the dlsw remote peer tcp, dlsw prom-peer defaults, and dlsw peer-on-demand defaults commands turns off RSVP for a particular peer connection.
Figure 1 shows a DLSw+ network with the DLSw+ RSVP Bandwidth Reservation feature configured.
DLSWRTR 1 and DLSWRTR 2 are configured for the DLSw+ RSVP Bandwidth Reservation feature with an average bit rate of 40 and a maximum-burst rate of 10.
dlsw local-peer peer id 10.2.17.1 dlsw remote-peer 0 tcp 10.2.24.3 dlsw rsvp 40 10
dlsw local-peer peer id 10.2.24.3 dlsw remote-peer 0 tcp 10.2.17.1 dlsw rsvp 40 10
The following output of the show ip rsvp sender command on the DLSWRTR2 verifies that PATH messages are being sent from DLSWRTR2:
DLSWRTR2#show ip rsvp sender To From Pro DPort Sport Prev Hop I/F BPS Bytes 10.2.17.1 10.2.24.3 TCP 2065 11003 10K 28K 10.2.24.3 10.2.17.1 TCP 11003 2065 10.2.17.1 Et1/1 10K 28K
The following output of the show ip rsvp req command on the DLSWRTR2 verifies that RESV messages are being sent from DLSWRTR2:
DLSWRTR2#show ip rsvp req To From Pro DPort Sport Next Hop I/F Fi Serv BPS Bytes 10.2.24.3 10.2.17.1 TCP 11003 2065 10.2.17.1 Et1/1 FF RATE 10K 28K
If the IP cloud is able to guarantee the bandwidth requested and the show ip rsvp sender and show ip rsvp req commands are successful, issue the show ip rsvp res command to verify that a reservation was made from DLSWRTR1 to DLSWRTR2:
DLSWRTR2#show ip rsvp rese To From Pro DPort Sport Next Hop I/F Fi Serv BPS Bytes 10.2.17.1 10.2.24.3 TCP 2065 11003 10.2.17.1 Et1/1 FF RATE 10K 28K 10.2.24.3 10.2.17.1 TCP 11003 2065 FF RATE 10K 28K
Figure 2 shows a DLSw+ border peer network configured with DLSw+ RSVP.
The following example configures DLSWRTR1 to send PATH messages at rates of 40 Kbps and 10KBps and DLSWRTR2 to send PATH messages at rates of
dlsw local-peer peer-id 10.2.17.1 group 1 promiscuous dlsw rsvp default dlsw remote-peer 0 tcp 10.3.15.2 dlsw peer-on-demand-defaults rsvp 40 10
dlsw local-peer peer-id 10.3.15.2 group 1 border promiscuous dlsw remote-peer 0 tcp 10.3.16.2
dlsw local-peer peer-id 10.3.16.2 group 2 border promiscuous dlsw remote-peer 0 tcp 10.3.15.2
dlsw local-peer peer-id 10.14.25.2 group 2 promiscuous dlsw rsvp default dlsw remote-peer 0 tcp 10.3.16.2
The following output of the show ip rsvp sender command on DLSWRTR2 verifies that PATH messages are being sent from DLSWRTR2:
DLSWRT2#show ip rsvp sender To From Pro DPort Sport Prev Hop I/F BPS Bytes 10.2.17.1 10.14.25.2 TCP 2065 11003 10K 28K 10.14.25.2 10.2.17.1 TCP 11003 2065 10.2.17.1 Et1/1 10K 28K
The following output of the show ip rsvp request command on DLSWRTR2 verifies that RESV messages are being sent from DLSWRTR 2:
DLSWRT2#show ip rsvp req To From Pro DPort Sport Next Hop I/F Fi Serv BPS Bytes 10.14.25.2 10.2.17.1 TCP 11003 2065 10.2.17.1 Et1/1 FF RATE 10K 28K
The following output of the show ip rsvp res command on the DLSWRTR1 verifies that the RSVP reservation was successful:
DLSWRTR1#show ip rsvp rese To From Pro DPort Sport Next Hop I/F Fi Serv BPS Bytes 10.2.17.1 10.14.25.2 TCP 2065 11003 10.14.25.2 Et1/1 FF RATE 10K 28K 10.14.25.2 10.2.17.1 TCP 11003 2065 FF RATE 10K 28K
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
fst | (Optional) Use FST encapsulation for all peers-on-demand established by this router. |
bytes-netbios-out bytes-list-name | (Optional) Configures NetBIOS bytes output filtering for peer-on-demand peers. The bytes-list-name is the name of the previously defined NetBIOS bytes access list filter. |
cost cost | (Optional) Specifies the cost to reach peer-on-demand peer. The valid range is 1 to 5. The default cost is 3. |
dest-mac destination-mac- address | (Optional) Specifies the exclusive destination MAC address for peer-on-demand peers. |
dmac-output-list access- list-number | (Optional) Specifies the filter output destination MAC addresses. |
rsvp global | (Optional) Sets the RSVP parameters to the global values specified in the dlsw rsvp command. |
rsvp average-bit-rate | (Optional) Average bit rate kilobits per second to reserve up to 75 percent of total bits on the interface. The valid range is 0 to 4,294,967. |
rsvp maximum-burst | (Optional) Maximum burst size (kilobytes of data in queue). The valid range is 0 to 4,294,967. |
host-netbios-out host-list-name | (Optional) Configures NetBIOS host output filtering for peer-on-demand peers. The host-list-name is the name of the previously defined NetBIOS host access list filter. |
inactivity minutes | (Optional) Configures the length of time after the peer's circuit count is 0 that the peer-on-demand is disconnected. The valid range is 0 to1440 seconds. The default is 600 seconds. |
keepalive seconds | (Optional) Configures the peer-on-demand keepalive interval. The valid range is 0 to 1200 seconds. The default is 30 seconds. |
lf size | (Optional) Largest frame size for this remote peer. Valid maximum frame sizes are the following: |
lsap-output-list list | (Optional) Configures local service access point (LSAP) output filtering for peer-on-demand peers. Valid numbers are in the range 200 to 299. |
port-list port-list-number | (Optional) Configures a port list for peer-on-demand peers. Valid numbers are in the range 0 to 4095. |
priority | (Optional) Configures prioritization for peer-on-demand peers. The default state is off. |
tcp-queue-max | (Optional) Configures the maximum output TCP queue size for peer-on-demand peers. |
The default peer-on-demand transport is TCP.
Global configuration
This command first appeared in Cisco IOS Release 11.0.
Setting the average-bit-rate and maximum burst values to 0 disables the RSVP bandwidth reservation for the peer connections.
The following example configures FST for peer-on-demand transport:
dlsw peer-on-demand-defaults fst
dlsw prom-peer-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost]
[dest-mac destination-mac-address] [dmac-output-list access-list-number]
[host-netbios-out host-list-name] [keepalive seconds] [lf size]
[lsap-output-list list] [rsvp {global | learn | [average-bit-rate
maximum burst]}] [tcp-queue-max size]
no dlsw prom-peer-defaults [fst] [bytes-netbios-out bytes-list-name] [cost cost]
[dest-mac destination-mac-address] [dmac-output-list access-list-number]
[host-netbios-out host-list-name] [keepalive seconds] [lf size]
[lsap-output-list list] [rsvp {global | learn | [average-bit-rate
maximum burst]}] [tcp-queue-max size]
fst | (Optional) Use FST encapsulation for all promiscuous peers established by this router. |
bytes-netbios-out bytes-list-name | (Optional) Configures NetBIOS bytes output filtering for promiscuous peers. The bytes-list-name is the name of the previously defined NetBIOS bytes access list filter. |
cost cost | (Optional) Specifies the cost to reach promiscuous peers. The valid range is 1 to 5. The default cost is 3. |
dest-mac destination-mac-address | (Optional) Specifies the exclusive destination MAC address for promiscuous peers. |
dmac-output-list access-list-number | (Optional) Specifies the filter output destination MAC addresses. |
host-netbios-out host-list-name | (Optional) Configures NetBIOS host output filtering for promiscuous peers. The host-list-name is the name of the previously defined NetBIOS host access list filter. |
keepalive seconds | (Optional) Configures the promiscuous keepalive interval. The valid range is 0 to 1200 seconds. The default is 30 seconds. |
lf size | (Optional) Largest frame size for this promiscuous peer. Valid maximum frame sizes are the following: |
lsap-output-list list | (Optional) Configures LSAP output filtering for promiscuous peers. Valid numbers are 200 to 299. |
rsvp global | (Optional) Sets the RSVP parameters to the global values. |
rsvp learn | (Optional) Configures RSVP parameters (average-bit-rate and maximum burst rate) to be those of the remote peer to which the promiscuous peer is connecting. |
average-bit-rate | (Optional) Configures RSVP parameters for this peer connection, which are different from the global values. Average bit rate (kilobits per second) to reserve up to 75 percent of the total bits on the interface. The valid range is 0 to 4,294,967. |
maximum-burst | (Optional) Maximum burst size (kilobytes of data in queue). The valid range is 0 to 4,294,967. |
tcp-queue-max size | (Optional) Configures the maximum output TCP queue size for promiscuous peers. |
The default promiscuous peer transport is TCP.
Global configuration
This command first appeared in Cisco IOS Release 11.0.
A promiscuous peer is a peer not configured as a remote peer on this DLSw+ device, but which initiated a peer connection that was accepted because promiscuous peering was enabled.
Setting the average-bit-rate and maximum burst values to 0 disables the RSVP bandwidth reservation for non-configured remote peers.
The following example configures the cost for promiscuous peers:
dlsw prom-peer-defaults cost 4
Use the dlsw remote-peer tcp global configuration command to identify the IP address of a peer with which to exchange traffic using TCP. Use the no form of this command to remove a remote peer.
dlsw remote-peer list-number tcp ip-address [backup-peer [ip-address | frame-relay
list-number | Remote peer ring group list number. The default ring group list number is 0. Otherwise, this value must match the number you specify with the dlsw ring-list, dlsw port-list, or dlsw bgroup-list command. |
tcp ip-address | IP address of the remote peer with which the router is to communicate. |
backup-peer ip-address | (Optional) IP address of the existing TCP/FST peer for which this peer is the backup peer. |
backup-peer frame-relay interface serial number dlci-number | (Optional) Serial interface and DLCI number of the existing Direct/LLC2 Frame Relay peer for which this peer is the backup peer. |
backup-peer interface name | (Optional) Interface name of the existing direct peer for which this peer is the backup peer. |
bytes-netbios-out bytes-list-name | (Optional) Configures NetBIOS bytes output filtering for this peer. The bytes-list-name argument is the name of the previously defined NetBIOS bytes access list filter. |
cost cost | (Optional) Cost to reach this remote peer. The valid range is 1 to 5. |
dest-mac mac-address | (Optional) Permits the TCP connection to be established only when there is an explorer frame destined for the specified 48-bit MAC address (written in dotted triplet form). |
dmac-output-list access-list-number | (Optional) Establishes TCP connection to be established only when the explorer frame passes the specified access list. The access-list-number is the list number specified in an access-list command. |
host-netbios-out host-list-name | (Optional) Configures NetBIOS host output filtering for this peer. The host-list-name is the name of the previously defined NetBIOS host access list filter. |
inactivity minutes | (Optional) Length of time a connection is idle before closing the dynamic remote peer connection. The valid range is 1 to 300 minutes. The default is 5 minutes. |
dynamic | (Optional) Establishes TCP connection only when there is DLSw+ data to send. |
keepalive seconds | Keepalive interval for this remote peer. The range is 0 to 1200 seconds. |
lf size | (Optional) Largest frame size, in bytes, this local peer will use on a circuit to avoid segmented frames. Valid sizes are 516, 1470, 1500, 2052, 4472, 8144, 11407, 11454, and 17800 bytes. |
linger minutes | (Optional) Configures length of time the backup peer remains connected after the primary peer connection is reestablished. The valid range is 1 to 300 minutes. The default is 5 minutes. |
lsap-output-list list | (Optional) Filters output IEEE 802.5 encapsulated packets. Valid access list numbers are in the range 200 to 299. |
no-llc minutes | (Optional) Configures the length of time a remote peer remains connected after all LLC2 connections are gone. The valid range is 1 to 300 minutes. The default is 5 minutes. |
passive | (Optional) Designates this remote peer as passive. |
priority | (Optional) Enables prioritization features for this remote peer. Valid TCP port numbers are the following: · High: 2065 · Medium: 1981 · Normal: 1982 · Low: 1983 |
rif-passthru virtual-ring-number | (Optional) Configures the remote peer as RIF-Passthru. The virtual-ring-number value is the same number as the ring number value assigned in the source-bridge ring-group commands of the DLSw+ Passthru peers. |
rsvp global | (Optional) Configures the RSVP parameters for this specific peer back to the global values. |
rsvp average-bit-rate | (Optional) Configures RSVP parameters for this peer, which are different from the global values. Average bit rate (kilobits per second) reserves up to 75 percent of the total bits on the interface. Range is 0 to 4,294,967. |
rsvp maximum burst | (Optional) Maximum burst size (kilobytes of data in queue). Range is 0 to 4,294,967. |
tcp-queue-max size | (Optional) Maximum output TCP queue size for this remote peer. The valid maximum TCP queue size is a number in the range 10 to 2000. |
timeout seconds | (Optional) Configures the retransmit time limit for TCP. The valid range is 5 to 1200 seconds. The default is 90 seconds. |
No peer IP address is identified.
The linger option is inactive. If the linger option is added with no minutes specified, the default is 5 minutes.
The dynamic option is not on by default. If the dynamic option is added without either the inactivity or no-llc argument specified, the default is to terminate the TCP connection to the remote peer after 5 minutes of no active LLC2 connection.
Global configuration
This command first appeared in Cisco IOS Release 10.3. The following keywords and arguments first appeared in Cisco IOS Release 11.1: dynamic, inactivity minutes, linger minutes, no-llc minutes and timeout seconds. The following keywords and arguments first appeared in Cisco IOS Release 11.2: dest-mac mac-address, dmac-output-list access-list-number, linger minutes.
SNA Dial-on-Demand Routing allows switched links to be closed during idle periods. To enable this feature, set the keepalive option to 0 and configure the timeout option. When the dynamic option is configured, the keepalive option is automatically set to 0.
To enhance DDR cost savings, configure the TCP connection to a remote peer to be dynamically established (that is, established only when there is DLSw data to send). You can also configure the TCP connection to terminate after a specified period of idle time on the peer or after a specified period of no active LLC sessions on the peer.
You cannot use both no-llc and inactivity in a command specifying a dynamic peer.
When you need to permit access to a single MAC address, the dest-mac option is an easier option than the dmac-output-list option.
Use the linger option to specify that a backup peer will remain connected for a specified period of time after the primary connection is gone.
When the priority option on the dlsw remote-peer command is configured, DLSw+ automatically activates four TCP ports to that remote peer (ports 2065, 1981, 1982, and 1983) and assigns traffic to specific ports. Furthermore, if APPN is running with DLSw+ and you specify the priority option on the dlsw remote-peer command, then the SNA TOS maps APPN COS to TCP TOS and will preserve the APPN COS characteristics throughout the network.
The rif passthru option works only on Token Ring LANs via SRB. Other LAN types, such as SDLC and QLLC, are not supported. The RIF passthru feature is supported with TCP encapsulation and it disables local acknowledgment.
The following features are not supported with the DLSw+ RIF Passthru feature:
Setting the average-bit-rate or maximum burst rate to 0 turns off RSVP for this peer.
The following example specifies a TCP encapsulation connection for remote peer transport:
dlsw remote-peer 0 tcp 10.2.17.8
The following example specifies a TCP peer as backup to a primary FST peer:
dlsw remote-peer 0 fst 10.2.18.9 dlsw remote-peer 0 tcp 10.2.17.8 backup-peer 10.2.18.9
Use the dlsw rsvp global configuration command to enable the DLSw+ RSVP Bandwidth Reservation feature on the local peer. Use the no form of this command to disable the DLSw+ RSVP Bandwidth Reservation feature for all peers in the router.
dlsw rsvp {default | [average-bit-rate maximum burst]}
default | (Optional) Sets the average bit rate to 10 Kbps and the maximum burst rate to 28 KBps. |
average-bit-rate | (Optional) Average bit rate (kilobits per second) to reserve up to 75 percent of the total bits on the interface. The valid range is 1 to 4,294,967. |
maximum burst | (Optional) Maximum burst size (kilobytes of data in queue). The valid range is 1 to 4,294,967. |
The default values for the average-bit-rate and maximum burst rate are 10 Kbps and 28 KBps, respectively.
Global configuration
This command first appeared in Cisco IOS Release 12.0(3)T.
The DLSw+ RSVP Bandwidth Reservation feature does not require that all peers in a network have RSVP configured. However, the feature does require that the end peer devices are configured with RSVP and that all devices in the middle are IP RSVP capable.
The default value assumes that the DLSw+ peer is connected via a 56 Kbps link. If this is not the case, then the default values will likely not produce optimal results. Even if the line speed is 56 Kbps, the default values (10 Kbps average-bit-rate and 28 KBps maximum burst rate) may not be optimal in a particular network environment and should be changed accordingly.
The following example configures the DLSw+ RSVP Bandwidth Reservation feature with an average-bit-rate of 10 Kbps and a maximum-burst rate of 28 KBps:
dlsw rsvp default
dlsw peer-on-demand-defaults
dlsw prom-peer defaults
dlsw remote-peer tcp
show ip rsvp sender
show ip rsvp req
show ip rsvp res
Posted: Thu Feb 25 15:09:30 PST 1999
Copyright 1989-1999©Cisco Systems Inc.