You can use the MODIFY-ADDRESS-ASSIGNMENT command to assign IPv6 network domains that can be accessed via a LAN processor.
BCIN for a LAN processor (format 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<processor-name 1..8>
Name of the processor
NAME-OF-ROUTE=
Using NAME-OF-ROUTE, you specify the name of the route that is defined as the new (additional) route to the processor.
NAME-OF-ROUTE= *default
The name of the processor is used as the route name.
NAME-OF-ROUTE=<rout-name 1..8>
Name of the route that is defined as the new (additional) route to the processor.
If there is already an existing route to the processor with the same route name as the name of the processor, the NAME-OF-ROUTE operand must be specified.
GEN=NODE
Using GEN=NODE, you specify that a processor directly accessible via a LAN node is included in the BCAM data structure and activated.
PROFIL= ...
Using PROFILE, you specify which protocol profile is used on the route to the processor.The specification is made by individually entering the Layer 4 protocol, Layer 3 protocol, and Layer 2 protocol to be used (in that order) in the form of a list, where protocols which are not relevant can be omitted.
Profile Layer 4
PROFIL=(TCP,xxx,xxx)
The Layer 4 protocol TCP is used on the route to the processor.
PROFIL=(ISO4,xxx,xxx)
The Layer 4 protocol ISO8073 Class 4 is used on the route to the processor.
Profile Layer 3
PROFIL=(xxx,IP,xxx),...
The Layer 3 protocol IP is used on the route to the processor.
IPADR= *default
The IP address of the processor is obtained from the processor file or the socket host file.
IPADR=<composed-name 7 ..15> / <x-string 1..8> / list-poss (4): <integer 0..255>
Using IPADR, you specify the IP address of the processor.
OWN-IPADR=...
Using OWN-IPADR, you specify the local IP address, with which the host for the processor can be addressed.
OWN-IPADR= *default
The IP address already known for the host is used as the local IP address.
OWN-IPADR=<composed-name 7 ..15> / <x-string 1..8> / list-poss (4): <integer 0..255>
Local IP address, with which the host for the processor can be addressed.
LANADR=...
Using LANADR, you specify the Ethernet address with which the processor is connected to this LAN.
LANADR= *none
The Ethernet address with which the processor is connected to this LAN is dynamically determined (by BCAM).
LANADR=<x-string 1..12>
The Ethernet address with which the processor is connected to this LAN.
SOKHOST=...
Using SOKHOST, you specify the socket host name of the processor.
SOKHOST= *default
The processor name is used as the socket host name.
SOKHOST=<c-string 1..32> / <sokhost-name 1..32>
Socket host name of the processor
USAGE=...
Using USAGE, you define the usage of the route to the processor.
Both values may also be specified as a list (list-poss).
USAGE=ES
The route is used for transport connections to and from the processor.
USAGE=ROUTER
The processor which is accessed via this route is to function as an IP router.
CONFIGURATION=...
The operand specifies whether or not the network configuration for the processor is to be modified using the routing protocol function. The specification is only possible for the processor to which routes with the L3 profile IP, IPv6 or INTF exist.
CONFIGURATION=UPDATE
Route modifications resulting from routing protocol functions lead to modifications to the BCAM routing tables and remain effective for this BCAM session.
CONFIGURATION=PRIMARY
Route modifications resulting from routing protocol functions are canceled, the original configuration information is used again.
CONFIGURATION=NO
Route modifications resulting from routing protocol functions are not permitted.
RARP=...
Using RARP, you specify whether RARP requests from outside may be answered.RARP requests are used to retrieve information about network addressing.
RARP=NO
RARP requests from outside may not be answered.
RARP=YES
RARP requests from outside may be answered.
IP-NET=...
Using IP-NET, you specify which additional IP addresses are accessible via the route to the processor.
IP-NET= *none
No additional IP addresses are accessible via the route to the processor.
IP-NET=*UNKNOWN
All previously unknown IP addresses are accessible via the route to the processor.
IP-NET=<composed-name 7 ..15> / <x-string 1..8> / list-poss (4): <integer 0..255>
Range of IP addresses that are accessible via the route to the processor.
TRANSON-USAGE =
You use TRANSON-USAGE to specify whether the route is used to access a TranSON server.
TRANSON-USAGE = *OFF
The route is not used to access a TranSON server.
TRANSON-USAGE = *ON
The route is used to access a TranSON server, i.e. parallel connections are permitted for NEA applications.
PROFIL=(xxx,IPV6,xxx),...
The Layer 3 protocol IPv6 is used on the route to the processor.
I6-ADDRESS= *default
The IPv6 address of the processor is taken from the processor file or the socket host file.
I6-ADDRESS=<c-string 1..45>
With I6-ADDRESS, you specify the IPv6 address of the processor.
OWN-I6-ADDRESS=...
IN OWN-I6-ADDRESS you enter the local IPv6 address at which the host can be addressed at this LAN together with the IPv6 prefix length.
OWN-I6-ADDRESS= *default
The known IPv6 address of the host is used as the local IP address
OWN-I6-ADDRESS=<c-string 1..49>
Local IPv6 address at which the host can be addressed at this LAN together with the IPv6 prefix length.
(Syntax: IPv6 address/IPv6 prefix length)
LANADR=...
With LANADR you specify the Ethernet address at which the processor is connected to this LAN.
LANADR= *none
The Ethernet address at which the processor is connected to this LAN is dynamically determined (by BCAM).
LANADR=<x-string 1..12>
Ethernet address at which the processor is connected to this LAN.
SOKHOST=...
IN SOKHOST you enter the processor’s socket host name.
SOKHOST= *default
The processor name is used as the socket host name.
SOKHOST=<c-string 1..32> / <sokhost-name 1..32>
Socket host name of the processor
USAGE=...
With USAGE you define the purpose of this route to the processor.
You can also specify both values as a list (list-poss).
USAGE=ES
The route is used for transport connections from and to the processor.
USAGE=ROUTER
The processor accessed via this route acts as an IPv6 router.
CONFIGURATION=...
The operand specifies whether or not the network configuration for the processor can be modified using the routing protocol function. The specification is only possible for processors accessed by routes with the L3 profile IP, IPv6 or INTF.
CONFIGURATION=UPDATE
Route modifications resulting from routing protocol functions lead to modifications to the BCAM routing tables and remain effective for this BCAM session.
CONFIGURATION=PRIMARY
Route modifications resulting from routing protocol functions are canceled. The original configuration information is used again.
CONFIGURATION=NO
Route modifications resulting from routing protocol functions are not permitted.
PROFIL=(xxx,INTF,xxx),...
The Layer 3 protocol ISO8473 Full Internet is to be used on the route to the processor.
INTADR= *default
The ISO Internet address of the processor is obtained from the processor file.
INTADR=<x-string 1..40>
Using INTADR, you specify the ISO Internet address of the processor.
OWN-INTADR=...
Using OWN-INTADR, you specify the local ISO Internet address, with which the host for the processor can be addressed.
OWN-INTADR= *default
The ISO Internet address already known for the host is used as the local ISO Internet address.
OWN-INTADR=<x-string 1..40>
Local ISO Internet address with which the host for the processor can be addressed.
LANADR=...
Using LANADR, you specify the Ethernet address with which the processor is connected to this LAN.
LANADR= *none
The Ethernet address at which the processor is connected to this LAN is dynamically determined (by BCAM).
LANADR=<x-string 1..12>
The Ethernet address at which the processor is connected to this LAN.
USAGE=...
Using USAGE, you define the usage of the route to the processor.
Both values may also be specified as a list (list-poss).
USAGE=ES
The route is used for transport connections to and from the processor.
USAGE=ROUTER
The processor which is accessed via the route functions as an ISO8473 router.
CONFIGURATION=...
The operand specifies whether or not the network configuration is to be modified for the processor using the routing protocol function. The specification is only possible for the processor to which routes with the L3 profile IP, IPv6 or INTF exist.
CONFIGURATION=UPDATE
Route modifications resulting from routing protocol functions lead to modifications to the BCAM routing tables and remain effective for this BCAM session.
CONFIGURATION=PRIMARY
Route modifications resulting from routing protocol functions are canceled. The original configuration information is used again.
CONFIGURATION=NO
Route modifications resulting from routing protocol functions are not permitted.
ISO-NET=...
Using ISO-NET, you specify which additional ISO Internet addresses are accessible via the route to the processor.
ISO-NET= *none
No additional ISO Internet address is accessible via the route to the processor.
ISO-NET=*UNKNOWN
All previously unknown ISO Internet addresses are accessible via the route to the processor.
ISO-NET=<x-string 1..40>
Additional ISO Internet address, which is accessible via the route to the processor.
PROFIL=(xxx,INT0,xxx),...
The Layer 3 protocol ISO8473 Zero Internet is used on the route to the processor.
LANADR=<x-string 1..12>
Using LANADR, you specify the Ethernet address with which the processor is connected to this LAN.
Profile Layer 2
PROFIL=(xxx,xxx,ETHERNET)
In Layer 2, the Ethernet protocol in accordance with RFC 894 is used on the route to the processor.
PROFIL=(xxx,xxx,SNAP)
In Layer 2, the LLC1 SNAP protocol in accordance with RFC 1042 and RFC 1188 is used on the route to the processor.
End of profile dependency
ROUTE=<node-name 1..8>
Using ROUTE, you specify the name of the LAN node via which the processor is accessible.
HOST=...
Using HOST, you specify the name of the host from which the route to the processor leads.
HOST= *default
The name of the default host (host name from the DCSTART or DCOPT command) is used as the host name.
HOST=<host-name 1..8>
Name of the host from which the route to the processor leads.
LINE=...
Using LINE, you specify the name of the line, which is used as the connection to the LAN node, specified by ROUTE, for the route to the processor.
LINE= *default
One of the existing lines to the LAN node is selected at random as the line which is used as the connection to the LAN node for the route to the processor. The LAN is specified via ROUTE.
If more than one line to the LAN node exists, the LINE operand must be specified.
LINE=<line-name 1..8>
Name of the line which is used as the connection to the LAN node, specified using ROUTE, for the route to the processor.
MAXTSDU=<integer 4096..65530>
Using MAXTSDU, you specify the maximum receive message length of the processor.
Default: 4096
ROUTE-SELECT=...
ROUTE-SELECT determines how transport connections are distributed over the routes to a processor when a connection is being established.
ROUTE-SELECT=*SEQUENTIAL-WITH-RETRY
Sequential distribution with repeat selection if the selection of a route fails:
The next route is not tried until the maximum number of transport connections for the previous route has been reached.
ROUTE-SELECT=*SEQUENTIAL
Sequential distribution without repeat selection if the selection of a route fails:
The next route is not tried until the maximum number of transport connections for the previous route has been reached.
ROUTE-SELECT=*BALANCED-WITH-RETRY
Balanced distribution of transport connections across the routes with repeat selection if the selection of a route fails.
ROUTE-SELECT=*BALANCED
Balanced distribution of transport connections across the routes without repeat selection if the selection of a route fails.
ROUTE-SEQUENCE-NUM=0/<integer 0..99>
Route number for route selection. Determines the sequence of routes during route selection.
Default value: 0
MAXNETL=...
Using MAXNETL, you specify which maximum data length may be used on the route to the processor.
MAXNETL=CSMACD
The maximum data length for a CSMA/CD LAN can be used via this route.
MAP=...8i
Using MAP, you specify whether the name of the processor may be used in a mapping definition (BCMAP command).
MAP=YES
The name of the processor can be used in a mapping definition (BCMAP command).
MAP=NO
The name of the processor may not be used in any mapping definition (BCMAP command).
ADM=...
Using ADM, you specify the administration type for the processor.
ADM=BCAM
The processor is administered using BCAM.
ADM=UNKNOWN
The administration type for the processor is unknown.
ACT=...
Using ACT, you specify whether the processor is to be activated.
ACT=YES
The processor is to be activated.
ACT=NO
The processor is not to be activated.
LINK-DOWN=...
The operand specifies whether or not the transport connections of a route are to be shut down in the event of a route failure.
LINK-DOWN=KEEP-CONNECTION
In the event of a route failure, the transport connections assigned to this route are not shut down.
LINK-DOWN=DISCONNECT
In the event of a route failure, all transport connections assigned to this route are shut down.
Command logging
For reasons of compatibility, positive acknowledgments are supplied in news BCA0763, and negative acknowledgments in news BCA0762, followed by the message NBR0740. In addition, for positive acknowledgments, the messages BCA083E, BCA083F and BCA0620 may also 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 |
| BCA0621 | Start-up aborted |
| BCA0768 | Syntax error in command |
| BCA077A | Definition of the route to computer is invalid |
| BCA0833 | Name already defined |
| BCA0814 | BCAM is being terminated abnormally |
| BCA0816 | BCAM is terminating |
| BCA0766 | BCAM is not active |