If an end system is not already known in BCAM, BCAM checks in several steps how a processor and route name can be assigned to an IP/IPv6 address:
- If the partner end system is included in the ISAM file derived from the processor file, the name written there should be used. This ISAM file contains the information from the processor file, as well as the entries from the FQDN file, which were specified with an IP/IPv6 address.
If the partner end system is included in the socket host file and its socket host name is shorter than 9 characters, the name is inherited from the socket host name.
- If the partner end system is included in the FQDN file (without IP/IPv6 address), the name stored there is used. This case only applies if there is an entry in the DNS for the partner end system, LWRESD is started and the use of DNS is enabled, as well as allowed for the partner end system.
If there exists an entry in the DNS for the partner end system, LWRESD is started and the use of DNS is activated, as well as allowed for the partner end system, the name is built from the first 8 characters of the DNS name .
If a name, that is not yet assigned in BCAM, is found in this way, this name is used as the processor name as well as the route name. Otherwise, an artificial name is generated for the partner end system which has been created.
The following rules apply to the artificially generated processor and/or route names:
- If a derived DNS name is used according to the above criteria, but it already exists as a processor name, the dynamic name
@@xxxxxx (000001 <= xxxxxx <= 999999)
is used as processor and route name instead. If no name was found according to the above criteria, or if the found name already exists, the dynamic name
##xxxxxx (000001 <= xxxxxx <= 999999)
is used as processor and route name.If a name was found according to the above criteria and could be used as processor name, but is already taken as route name in BCAM, or if only a route to an already known computer is created by AEC, the dynamic name
#$xxxxxx (000001 <= xxxxxx <= 999999)
will be used as route name.
This processor or route name can be used to address (e.g. deactivate) the corresponding end system by means of BCAM commands. The relevant extensions can be displayed, for example, using the command SHOW-ROUTE or SHOW-ROUTE-ATTRIBUTES.
Relation of AEC with the processor/FQDN file and DNS usage
Note: Without consideration of the IP range table and the socket host file | FQDN entry with IP/IPv6 address, | FQDN entry without IP/IPv6 address, No entry in processor file | FQDN entry with/without IP/IPv6 address, Entry in processor file | No FQDN entry, no entry in processor file |
An entry exists in the DNS for the partner end system, LWRESD is started and the use of DNS is activated, as well as permitted for the partner end system | ||||
AEC with ACCESS=READ | Processor name from FQDN file | Processor name from FQDN file | Processor name from processor file | Processor name is derived from DNS name |
AEC with ACCESS=ALLOW | Processor name from FQDN file | Processor name from FQDN file | Processor name from processor file | Processor name is derived from DNS name |
| There is no entry in the DNS for the partner end system, LWRESD is not running or the use of DNS is deactivated or prohibited for the partner end system | ||||
AEC with ACCESS=READ | Processor name from FQDN file | Connection not possible, end system in BCAM firewall | Processor name from processor file | Connection not possible, end system in BCAM firewall |
AEC with ACCESS=ALLOW | Processor name from FQDN file | Dynamic processor name (##xxxxxx) | Processor name from processor file | Dynamic processor name (##xxxxxx) |
Note:
If there is an entry with the same IP or IPv6 address in both the processor and FQDN file, they must match; otherwise, an error will be detected.