You use the MODIFY-ROUTE-ATTRIBUTES command to modify route-specific attributes.
The values that can be set with MODIFY-ROUTE-ATTRIBUTES are partly protocol timers. The setting of these protocol timers must be uniform throughout the network and requires a sound knowledge of the relevant standards and networks.
The alias MDRTA exists for MODIFY-ROUTE-ATTRIBUTES in order to support SNMP management. The SDF alias is MDRTA.
The command offers some of the functionality of the MODIFY-ROUTE command.
BS2000 console | BS2000 SDF command | Command/SOF file | SNMP management | Parameter service |
x | x | x | x |
List of valid command sources
MODIFY-ROUTE-ATTRIBUTES / MDRTA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
ROUTE-NAME=...
Name of the route for modification.
The modification of each individual route is logged with message BCA07C2.
If multiple routes are modified then the number of modified routes is logged with message BCA07C1.
ROUTE-NAME=<composed-name 1..8> / <c-string 1..8>
Name of the route for modification.
ROUTE-NAME=*PROCESSOR(...)
All the routes to a processor are modified.
PROCESSOR-NAME=<composed-name 1..8> / <c-string 1..8>
Name of the processor to which the routes lead.
ROUTE-NAME=*IP(...)
The routes defined by the partner IP address are modified.
IP-ADDRESS= <composed-name 7..15> / <x-string 7..8>
Partner IP address of the routes for modification.
ROUTE-NAME=*ISO(...)
The routes defined by the partner ISO Internet address are modified.
ISO-ADDRESS=<x-string1..40>
Partner ISO Internet address of the routes for modification.
ROUTE-NAME=*LAN(...)
The routes defined by the partner LAN address are modified.
LAN-ADDRESS=<x-string 1..12>
Partner LAN address of the routes for modification.
ROUTE-NAME=*IPV6(...)
The routes defined by the partner IPv6 address are modified.
IPV6-ADDRESS=<text 9..45> / <c-string 9..45>
Partner IPv6 address of the routes for modification.
ROUTE-NAME=*ALL
All routes are modified.
The number of routes actually modified is logged in message BCA07C1.
TIMER=...
Timers that are changed.
TIMER=*UNCHANGED
The values for the timers remain unchanged.
TIMER=*PERIODS(...)
Timer time intervals are changed.
WINDOW=...
The time interval of the window timer is changed.
If nothing was sent on a connection during the time interval, an acknowledgment element (AK-TPDU) is sent.
The value is rounded up to a multiple of 2 seconds. The timer has a precision of 2 seconds.
Values which are greater than 180 are changed to 180.
If the value for WINDOW is changed, the maximum for the RETRANSMISSION value (one fifth of the WINDOW value) is also changed.
WINDOW=*UNCHANGED
The time interval of the window timer remains unchanged.
WINDOW=*STD
The time interval of the window timer is changed to the default value (60 seconds).
WINDOW=<integer 2..190>
The time interval of the window timer is changed to the specified value (in seconds).
RETRANSMISSION=...
The time interval of the retransmission timer is changed.
A protocol element which must be acknowledged is retransmitted if it was not acknowledged by the partner transport control during the time interval.
The value is rounded up to a multiple of 2 seconds. The timer has a precision of 2 seconds.
The retransmission timer is only to be changed where absolutely essential.The timer has major effects on the loading of the system and the LAN. It should be noted that changes to WINDOW values also affect RETRANSMISSION!
For WINDOW=*STD, the RETRANSMISSION value is 10.
RETRANSMISSION=*UNCHANGED
The time interval of the retransmission timer remains unchanged.
RETRANSMISSION=*STD
The time interval of the retransmission timer is changed to the default value (10 seconds).
RETRANSMISSION=<integer 2..36>
The time interval of the retransmission timer is changed to the specified value (in seconds).
OPTIONS=...
Options to be changed.
OPTIONS=*UNCHANGED
No options are changed.
OPTIONS=*ROUTING(...)
Routing options are changed.
ARP=...
Specifies if, and how, ARP is used.
ARP=*UNCHANGED
The use of ARP is not changed.
ARP=*QUIET
ARP is used every 2 seconds when a route is used for the first time.
Every 300 seconds, there is a check to determine whether data transmission has taken place within the elapsed time interval. If this is not the case, and if communication associations exist over the route, an ARP request is sent.
ARP=*ON
ARP is used during route activation (every 2 seconds), and ARP requests are sent periodically (every 300 seconds).
ARP=*OFF
ARP is not used.
RARP-REPLIES=...
Specifies whether RARP is supported, i.e. whether incoming RARP requests can be responded to with the corresponding RARP replies.
RARP-REPLIES=*UNCHANGED
Passive RARP support is not changed.
RARP-REPLIES=*ALLOWED
RARP is passively supported.
RARP-REPLIES=*NOT-ALLOWED
RARP is not passively supported.
AUTO-ROUTE-SWITCHING=...
Defines the AUTO-ROUTE-SWITCHING option.
The AUTO-ROUTE-SWITCHING option specifies whether the route’s path definitions can be changed as a result of routing protocol functions.
AUTO-ROUTE-SWITCHING=*UNCHANGED
The AUTO-ROUTE-SWITCHING setting is unchanged.
AUTO-ROUTE-SWITCHING=*ON
The AUTO-ROUTE-SWITCHING option is activated: the route can be modified.
AUTO-ROUTE-SWITCHING=*OFF
The AUTO-ROUTE-SWITCHING option is deactivated: the route cannot be modified.
ROUTE-RESWITCHING=...
Defines the ROUTE-RESWITCHING option.
The ROUTE-RESWITCHING option specifies whether the route can be switched back to the original path definition in the event of reactivation.
ROUTE-RESWITCHING=*UNCHANGED
The ROUTE-RESWITCHING setting is unchanged.
ROUTE-RESWITCHING=*OFF
The ROUTE-RESWITCHING option is deactivated.
ROUTE-RESWITCHING=*ON
The ROUTE-RESWITCHING option is activated.
TRANSON-USAGE=...
Changes the TRANSON-USAGE option.
The TRANSON-USAGE option specifies whether the route is used to access a TranSON server..
TRANSON-USAGE=*UNCHANGED
The TRANSON-USAGE setting is unchanged.
TRANSON-USAGE=*OFF
The TRANSON-USAGE option is deactivated.
TRANSON-USAGE=*ON
The TRANSON-USAGE option is activated.
This function should only be used for individual routes.
ECN=...
Specifies whether or not the Explicit Congestion Notification (ECN) mechanism is supported for the route. ECN is realized through the interaction of IP and TCP protocols. End systems that support this mechanism can be slowed down in heavyload situations by network components, usually routers, to prevent the loss of packets. ECN considerably improves the stability of a network topology and is one of the required standards of the Internet. ECN is defined in RFC 3168. The specification only applies to routes with transport profile TCP/IP.
Although the BCAM transport system has implemented the recovery mechanism described in RFC 3168, it may be necessary to disable ECN support to enable interworking.
ECN=*UNCHANGED
The previous setting remains unchanged.
Default: *ON (after BCAM has started)
ECN=*ON
Explicit Congestion Notification is supported for the specified route.
The ROUTE-NAME=*ALL specification means that Explicit Congestion Notification is supported for all IP routes. This also applies to all IP routes, created as of this point in time.
ECN=*OFF
Explicit Congestion Notification is not supported for the specified route.
The ROUTE-NAME=*ALL specification means that Explicit Congestion Notification is not supported for all IP routes. This also applies to all IP routes, created as of this point in time.
HIGHSPEED-TCP=...
Specifies whether the high-speed TCP functions are supported for the route.
The high-speed TCP mechanisms (Limited Slow-Start, Large Congestion
Windows) can be deactivated.
HIGHSPEED-TCP only achieves optimum results if used in conjunction with DRS-OUTBOUND.
HIGHSPEED-TCP=*UNCHANGED
The previous setting is retained.
Default: *ON (after BCAM has been started)
HIGHSPEED-TCP=*ON
The high-speed TCP mechanisms are supported for the specified route.
The specification ROUTE-NAME=*ALL causes the high-speed TCP mechanisms to be supported for all IP routes. This also applies to IP routes generated as of this time.
HIGHSPEED-TCP=*OFF
The high-speed TCP mechanisms are not supported for the specified route. The specification ROUTE-NAME=*ALL causes the it is not supported for any IP routes. This also applies to IP routes generated as of this time.
DRS-INBOUND=...
Specifies whether inbound dynamic right-sizing is supported on the route (inbound).
The size of the occupied BCAM storage may be considerably greater than in the predecessor version.
DRS-INBOUND=*UNCHANGED
The previous setting is retained.
Default: *ON (after BCAM has been started)
DRS-INBOUND=*ON
Inbound dynamic right-sizing is supported for the specified route. The specification ROUTE-NAME=*ALL means that inbound dynamic right-sizing is supported for all IP routes. This also applies for routes that are created as of this time.
DRS-INBOUND=*OFF
Inbound dynamic right-sizing is not supported for the specified route. The specification ROUTE-NAME=*ALL means that inbound dynamic right-sizing is not supported for all IP routes. This also applies for routes that are created as of this time.
DRS-OUTBOUND=...
Specifies whether outbound dynamic right-sizing is to be supported for the route.
The size of the occupied BCAM storage may be considerably greater than in the predecessor version.
DRS-OUTBOUND only achieves optimum results if used in conjunction with HIGHSPEED-TCP.
DRS-OUTBOUND=*UNCHANGED
The previous setting is retained.
Default: *ON (after BCAM has been started)
DRS-OUTBOUND=*ON
Outbound dynamic right-sizing is supported for the specified route
The specification ROUTE-NAME=*ALL means that outbound dynamic rightsizing is supported for all IP routes. This also applies for routes that are created as of this time.
DRS-OUTBOUND=*OFF
Outbound dynamic right-sizing is not supported for the specified route. The specification ROUTE-NAME=*ALL means that outbound dynamic right-sizing is not supported for all IP routes. This also applies for routes that are created as of this time.
MAX-NSDU-SIZE=...
Changes the maximum NSDU length.
MAX-NSDU-SIZE=*UNCHANGED
The setting for the maximum NSDU length is not changed.
MAX-NSDU-SIZE=<integer 512..65530>
The maximum NSDU length is changed to the specified value (in bytes).
CHECKSUM=...
Specifies whether or not checksum verification is performed for the route when a segment is received. The checksum for the segments for transmission is always calculated and entered in the protocol. This option can be used to improve reception performances.
This specification only applies to routes with the transport profile TCP.
This option should only be used on routes on which there is no risk of data corruption.
The machine-internal connection between BS2000 guest machines on a VM2000 system, for example, is suitable for this.
CHECKSUM=*UNCHANGED
The previous setting is unchanged.
CHECKSUM=*ON
Checksum verification is performed.
CHECKSUM=*OFF
Checksum verification is not performed.
Command logging
Positive acknowledgments are supplied in news BCA0663, and negative acknowledgments in news BCA06B3. If processing is positive the messages BCA07B0, BCA07C1, BCA07C2, and BCA07C3 may also appear. For positive and negative acknowledgments, the message BCA07C4 may appear.
A description of the error messages that may be issued during command processing is provided in the table below.
Command return codes
(SC2) | Maincode | Meaning |
| CMD0001 | Command successfully processed |
| CMD0202 | Error in command |
| BCA06B3 | MODIFY-ROUTES-ATTRIBUTES cancelled |
| BCA07C0 | No route modified |
| BCA0768 | Syntax error in command |
| BCA07A0 | Processor is unknow |
| BCA07A1 | Route is unknown |
| BCA07A9 | Route is not excluded |
| BCA07EE | Command is being executed |
| BCA079F | Address is unknown |
| BCA0814 | BCAM is being terminated abnormally |
| BCA0816 | BCAM is terminating |
| BCA0766 | BCAM is not active |
Examples
Modify route attributes of the route ROUTOTTO:
/MODIFY-ROUTE-ATTRIBUTES ROUTE-NAME=ROUTOTTO, -
/ OPTIONS=*ROUTING(ARP=*QUIET)
/MODIFY-ROUTE-ATTRIBUTES ROUTE-NAME=ROUTOTTO,CHECKSUM=*ON