HP 3000 Manuals HP 3000 Manuals
Configuring an Adjacent MTA You need to configure each adjacent MTA to which the local MTA establishes a connection. A maximum of 200 adjacent MTAs, HP X.400/HP Desk Nodes (if you are using HP X.400 with HP Desk),and API clients can be configured. To configure an adjacent MTA, * Select the ADJMTA item from the Configure X.400 Menu. This displays the Configure Adjacent MTAs screen.Figure 7-1. Configure Adjacent MTAs Screen
NOTE If you are configuring X.400 for the first time,this screen does not display any adjacent MTAs. If you are reconfiguring,this screen displays a list of adjacent MTAs which has already been configured.
The fields on the screen are: Adjacent MTA Mnemonic Name Display. Only the first 16 characters of the name displays. Output Queue Display. This directory name is automatically assigned when the MTA is first configured. The full directory name is /usr/spool/x400/oq/ output queue. Country Display. The country where the adjacent MTA's network is located. See Appendix C for a list of country codes. ADMD (Administration Management Domain) Display. See Appendix D for a list of ADMDs. PRMD (Private Management Domain) Display. If you need to scroll the screen, * Press the Page Down key to scroll forward for additional entries, or * Press the Page Up key to scroll to the previous screen. To add, modify, or delete an adjacent MTA, * Press the Action Menu key to display the Action Menu so you can select Add Adjacent MTA, Modify Adjacent MTA, or Delete Adjacent MTA. Adding an Adjacent MTA To add an adjacent MTA, * Select the Add Adjacent MTA item from the Configure Adjacent MTAs Action Menu. This displays the Add Adjacent MTA screen.Figure 7-2. Add Adjacent MTA Screen The fields on the screen are: Adjacent MTA Mnemonic Name Required. Unique name that is a printable string of up to 32 characters. If passwords are used, the adjacent MTA name entered here must be the same name used by the adjacent MTA. If the adjacent MTA name contains nonprintable characters, configure a mnemonic name with printable characters in this field. Then, configure the name with nonprintable characters in the MTA Name expected in connect indication from adjacent MTA field of the Alternate MTA Names window (press the Action Menu key to select Alternate MTA Names). Output Queue Display. This directory name is automatically assigned when the MTA is first configured. Country Code Required. The country where the remote MTA's network is located. See Appendix C for a list of country codes. Administration Domain Name Optional. Your local MTA must also be connected to this ADMD since mail transferred between your local MTA and the adjacent MTA transfers through this ADMD. If this remote MTA does not use public X.400 services to transfer mail to the local MTA (i.e. PRMD to PRMD connection), then leave this field blank. This field is a printable string of up to 16 characters. Private Domain Name Optional. If the adjacent MTA is an MTA within a public X.400 network (i.e., ADMD), then leave this field blank. This field is a printable string of up to 16 characters. Incoming Password Optional. This password is used for security. Enter the password that the adjacent MTA sends to the local MTA when requesting a connection. The local MTA then matches this password with the configured password. If the password does not match the configured password, there is no connection. This is a string of up to 64 characters in length and is case-sensitive. There is no default value. If no password is required, leave this field blank. If an incoming password is configured and if the the "MTA Name expected..." field of the Alternate MTA Names window is not configured, the Adjacent MTA Mnemonic Name entered in the first field is also verified against the MTA name that is sent by the adjacent MTA. If an incoming password is configured and if the MTA Name expected ... field of the Alternate MTA Names window is configured, the MTA Name expected... field is verified against the MTA name that is sent by the adjacent MTA. Outgoing Password Optional. This password is used for security. Enter the password that the local MTA sends to the adjacent MTA when requesting a connection. This is a string of up to 64 characters in length and is case-sensitive. There is no default value. If no password is required, leave this field blank. If an outgoing password is configured, the adjacent MTA also verifies the local MTA Name (entered on the Configure Local MTA screen) that is sent by the local MTA. If the MTA Name to send to adjacent MTA in a connect request field of the Alternate MTA Names window is configured, the MTA Name to send..., instead of the Local MTA name, is sent by the local MTA. Profile Supported Required. Default: NIST84 . The profile type to which this adjacent MTA conforms. The local MTA must know to which profile the adjacent MTA conforms in order to interoperate with that adjacent MTA. To select a new value for this field, press the Help key. Your choices are: EWOS88 (1988 X.400, Europe), NIST88 (1988 X.400, U.S.A.), NIST84 (1984 X.400, U.S.A.), CEN41201 (1984 X.400 for PRMD to PRMD connections, Europe), and CEN41202 (1984 X.400 for ADMD to PRMD connections, Europe). If either CEN41201 or CEN41202 is selected, the local MTA does not include internal trace records in messages sent to this adjacent MTA. RTS Recovery? (y/n) Required. Default: n. Enter y to cause the RTS, when acting as initiator, to try and recover a session connection (that has been aborted) at the latest confirmed Minor Synchronization Point for the message being transferred. Enter n to cause the RTS to try and re-establish a session connection (that has been aborted) from the beginning of the message being transferred. Send 8883 as P1 protocol id? (y/n) Required. Default: n. Enter y to cause a protocol ID with the value 8883 to be sent to the adjacent RTS instead of the value 1. The CEN41201 Functional Specification requires 8883 to be sent while the NIST Implementor's Agreement and the CEN41202 Functional Specification require 1. This parameter is included for flexibility. Use unstructured SCID? (y/n) Required. Default: n. Enter y to indicate that the components of the session connection identifier (SCID) used by the RTS should be encoded as separate components rather than a sequence, and that the additional reference information parameter should be encoded as a T.61 string rather than as implicit. When the fields on this screen are correctly defined, * Press the Action Menu key to select Network Address, RTS Limits, Transfer Time, or Alternate MTA Names from the Action Menu. The Network Address, including TSAP and NSAP, must be added. * Press the Perform Task key. The Adjacent MTA Route Reminder window displays to remind you to add a route to the adjacent MTA if you want messages routed to the adjacent MTA. Press the Confirm key if you want to add a route now (the Add Route screen displays). And, after pressing the Exit Task key in the Add Route screen, the Add Adjacent MTA screen displays. Press the Cancel key if you want to add a route later.
NOTE If you press the Perform Task key to add the adjacent MTA to the configurationand the network addressing information was not entered, a message displays that you must enter the Network Address. The RTS Limits, Transfer Time, and Alternate MTA Names are optional. If you press the Perform Task key to add the adjacent MTA to the configuration and an SSAP value was configured, a warning message displays reminding you that the SSAP field should be left blank unless this adjacent MTA is U.S. GOSIP compliant and must have an SSAP value configured.
Network Address Information Window. Select the Network Address item from the Action Menu to display the Network Address Information window.Figure 7-3. Network Address Information Window The fields on this window are: Is TSAP HEX or ASCII Required if TSAP value is entered. Enter H if (H/A)? the TSAP address is to be entered in the HEX format, or A for the ASCII format. If there is a TSAP address displayed in the next field, this field displays the format of the TSAP. If you change the format, the displayed TSAP address converts to the new format. A TSAP value in ASCII format is converted to its HEX format by concatenating the hexadecimal ASCII codes of the characters. For example, the HEX format of the ASCII TSAP value MHS is 4D4853. This is obtained by concatenating the hexadecimal ASCII code for M (4D), the hexadecimal ASCII code for H (48), and the hexadecimal ASCII code for S (53). If the present TSAP is in HEX and the ASCII equivalent contains unprintable characters, then the TSAP value does not convert into ASCII when you enter A. You need to erase the TSAP value in the next field before you can enter A in this field. TSAP (Transport Selector): Optional. The Transport Service Access Point (or transport selector) that identifies the X.400 MHS on the adjacent MTA. Within a network, the MHS may be one of several services available to the user/subscriber. To specify a NULL TSAP, leave this field blank. The previous field indicates the format of this TSAP address. If this field is HEX, it can contain up to 32 hexadecimal digits, must have an even number of digits, and can contain spaces to make the field easier to read. If this field is ASCII, it can contain up to 16 characters (spaces are valid characters). Is SSAP HEX or ASCII Required if SSAP value is entered. Enter H if (H/A)? the SSAP address is to be entered in the HEX format, or A for the ASCII format. If there is an SSAP address displayed in the next field, this field displays the format of the SSAP. If you change the format, the displayed SSAP address converts to the new format. An SSAP value in ASCII format is converted to its HEX format by concatenating the hexadecimal ASCII codes of the characters. For example, the HEX format of the ASCII SSAP value MHS is 4D4853. This is obtained by concatenating the hexadecimal ASCII code for M (4D), the hexadecimal ASCII code for H (48), and the hexadecimal ASCII code for S (53). If the present SSAP is in HEX and the ASCII equivalent contains unprintable characters, then the SSAP value does not convert into ASCII when you enter A. You need to erase the SSAP value in the next field before you can enter A in this field. SSAP (Session Selector): Optional. Obtain the SSAP for this adjacent from the administrator of the adjacent MTA. In general, this field should be left blank. The first version of the U.S. GOSIP 1.0 profile (FIPS 146) recommended that the X.400 SSAP value be HEX 02 which conflicted with the CCITT 1984 X.400 standard specifying that the SSAP should always be null. This conflict was resolved in a later version of the U.S. GOSIP profile, but some vendors' GOSIP compliant implementations may not have incorporated the revision. If you are connecting to such an implementation, you may need to enter 02 in HEX here. Configuring an SSAP value may cause problems with other vendors whose X.400 implementations do not allow SSAP values to be entered. Please contact your HP Representative if you have questions or concerns regarding SSAP configuration. If you enter the Session Service Access Point (or session selector), it identifies the X.400 MHS. Within a network, the MHS may be one of several services available to the user/subscriber. The previous field indicates the format of this SSAP address. If this field is HEX, it can contain up to 32 hexadecimal digits, must have an even number of digits, and can contain spaces to make the field easier to read. If this field is ASCII, it can contain up to 16 characters (spaces are valid characters). NSAP (hex): Network Service Access Point. Required. The network address of the adjacent MTA. Typically, the PTTor public carrier assigns the NSAP and the administrator of the adjacent MTA assigns the sub-address of the NSAP. NSAPs for adjacent MTAs accessed through X.25 connections are often their X.121 addresses. The X.121 addresses are already in HEX format. This field must be a hexadecimal value up to 40 digits, can have optional spaces between each pair of HEX digits, and must have an even number of digits. The local RTS uses this NSAP to validate incoming connections from the adjacent RTS if incoming connections from adjacent MTAs that are not configured are not allowed. The adjacent RTS has its own NSAP value in its connection request and, if it does not match a configured NSAP entry, the local RTS refuses the connection unless the "Allow an incoming connection from a non-configured adjacent MTA" on the Local MTA screen is set to y. ______________________________________________ NOTE The NSAPs 5148504C4F4F504241434B and 687072656C6179 are reserved and may not be entered as the NSAP for an adjacent MTA. ______________________________________________ When the fields on this window are correctly defined, * Press the Done key. The window is removed from the screen. * Press the Perform Task key. The Adjacent MTA Route Reminder window displays. RTS Limits Window. Select the RTS Limits item from the Action Menu to display the RTS Limits window.
NOTE It is recommended that you do not change the information on this screen until you have established an initial connection with the adjacent MTA. Once a connection is established, use these fields to fine tune your system.
Figure 7-4. RTS Limits Window The fieldvalues on this window are: Checkpoint Size Required. Default: 5. The number of kilobytes (which may be integers from 0 to 5) of data that is to be sent between each RTS checkpoint. Enter 0 to disable RTS checkpointing. Maximum connection retries Required. Default: 0. The maximum number of attempts that will be made to establish a connection to the adjacent MTA for high, normal, and low priority messages. Specifically, the maximum number of session connect requests that will be sent to the adjacent MTA. When the number of attempts exceed the number defined for the high, normal, or low priority message, the message is sent back to the local MTA and transferred using an alternate route or determined undeliverable. Enter zero to allow an unlimited numberof attempts to be made. If you use alternate routing, enter a number greater than zero, but do not use zero. The number entered can be any numeric value.
NOTE The maximum connection retries limit applies to both the initial connection attempts and the subsequent connect attempts made if the connection goes down after message transfer has begun. Previously, the maximum connection retries limit applied only to initial connection attempts.
Connect refusal grace period Required. Default: 0 hours, 0 minutes, and 0 seconds. If a connection refusal is received (for a reason other than "RTS busy"), the time entered here determines how much time to wait before a connection is tried again. This allows the X.400 administrator time to fix a problem with the adjacent MTA before a message is returned to the local MTA. If the connection is refused again (for a reason other than "RTS busy"), the RTS returns the message to the local MTA. If the time entered is zero and a connection refusal is received (for a reason other than "RTS busy"), the message is immediately returned to the local MTA. The time entered must be in hours, minutes, and seconds using the 24-hour clock.
NOTE If the adjacent RTS is busy or the connection is aborted during message transfer, the local RTS returns the message to the local MTA when either the total number of connection attempts for this message exceeds the number defined for the appropriate message priority, or the maximum time to transfer a message is exceeded. If the maximum connection retries limit is zero, there is no limit to the number of connection attempts and the message is only returned to the local MTA if the maximum time to transfer a message is exceeded. The RTS attempts to establish a connection using the following time intervals: * Retries every 30 seconds for the first ten attempts. * Retries every 5 minutes for the next ten attempts. * Retries every 1 hour for the next ten attempts. * Retries every 5 hours for all remaining attempts.
Maximum time to transfer a message Required. Default: 8 hours for high, 16 for normal, and 24 for low priority messages. The amount of time (in hours and minutes) to be allowed for transferring high, normal, and low priority messages. If the amount of time defined for each type of priority messageexpires before the message has been successfully transferred, the RTS returns the message to the MTA. The message may then be transferred using an alternate route or determined to be undeliverable. If the time entered is zero, the message is not transferred. The time entered must be in hours and minutes using the 24 -hour clock. ______________________________________________ NOTE The configured maximum transfer times for priority messages are only used while the RTS is running. If the system crashes or shuts down, the counters reinitialize to zero when the system restarts. For example, if the time allowed for a message to transfer is 45 minutes and the system crashes before the message is completely transferred, the counters reinitialize to zero when the system restarts. The message has 45 minutes to transfer again. ______________________________________________ When the fields on this screen are correctly defined, * Press the Done key. The window is removed from the screen. * Press the Perform Task key. Transfer Times Window. Select the Transfer Times item from the Action Menu to display the Transfer Times window.
NOTE It is recommended that you do not change the information on this screen until you have established an initial connection with the adjacent MTA. Once a connection is established, use these fields to fine tune your system.
Figure 7-5. Transfer Times Window The Transfer Times window is initially set up to allow message transfer to occur at any time. If you want to allow message transfers to occur at specific times, you need to define the timeranges on this screen. Otherwise, you do not need to define time ranges for message transfers. You can define time ranges for high, normal and low priority messages. A maximum of three time ranges can be defined for each message priority. No two ranges for the same priority should overlap. For each time range defined, you must specify the start time, end time, and frequency. You can define a maximum of six time ranges. The fieldson the window are: Msg Pri For this time range, enter H for high priority, N for normal priority, and L for low priority messages. Start Time Default: 0. The start time (in hours, minutes, and seconds using the 24-hour clock) when messages of the specified priority can be transferred to the adjacent MTA. End Time Default: 24. The end time (in hours, minutes, and seconds using the 24-hour clock) when messages of the specified priority can be transferred to the adjacent MTA. Frequency Default: 1 minute for high, 1 minute for medium, and 10 minutes for low priority messages. How often (in hours, minutes, and seconds using the 24-hour clock) the RTS checks to determine if messages of the specified priority need to be transferred to the adjacent MTA. For example, if you enter 2 hours, 0 minutes, and 0 seconds, the RTS checks every two hours if messages need to be transferred. This allows for messages to be transferred in batch. The minimum frequencyis 15 seconds. When the fields on this screen are correctly defined, * Press the Done key. The window is removed from the screen. * Press the Perform Task key. The adjacent MTA Route Reminder window displays. Alternate MTA Names. Select the Alternate MTA Names item from the Action Menu to display the Alternate MTA Names window.
NOTE Do not enter any information unless the information is necessary to interoperate with the adjacent MTA.
Figure 7-6. Alternate MTA Names Window The Alternate MTA Names window allows you to configure alternate values for MTA names expected in a connect indication or sent out in a connect request. This allows HP's X.400 to interoperate with adjacent MTAs that have unusual name requirements. The fields on this window are: MTA Name expected in Optional. Enter the name that is used instead connect indication from of the Adjacent MTA Mnemonic Name to verify adjacent MTA: the MTA Name and password received in a connect indication from this adjacent MTA, if an incoming password is configured. For example, enter a name if it contains characters that are not allowed in a printable string. This field is a string of up to 32 characters. MTA Name to send to Optional. Enter the name that is used instead adjacent MTA in a of the local MTA Name when sending a connect connect request: request to this adjacent MTA. For example, enter the adjacent MTA name if the adjacent MTA expects the local MTA to send the adjacent MTA name instead of the local MTA name. This name is sent to this adjacent MTA when requesting a connection. This field is a string of up to 32 characters. When the fields on this screen are correctly defined, * Press the Done key. The window is removed from the screen. * Press the Perform Task key. The Adjacent MTA Route Reminder window displays. Modifying an Adjacent MTA To modify an adjacent MTA, * Select the adjacent MTA to be modified from the ADJMTA Configure Adjacent MTAs screen. * Press the Action Menu key. * Select Modify Adjacent MTA item from the ADJMTA Configure Adjacent MTAs Action Menu. This displays the Modify Adjacent MTAscreen.Figure 7-7. Modify Adjacent MTA Screen For a description of the fields, refer to the Add Adjacent MTA screen field descriptions. If you need to modify additional MTA information (Network Address, RTS Limits, Transfer Time, or Alternate MTA Names), * Press the Action Menu key to select Network Address, RTS Limits, Transfer Time, or Alternate MTA Names from the Action Menu. The appropriate window for the selected item to be modified displays. Refer to these windows discussed earlier in this chapter for more information.
NOTE After you modify the additional MTA information for the selected item, press the Done key. The window is removed from the screen.
When the fields on this screen are correctly defined, * Press the Perform Task key to save the datain the configuration file. A confirmation message displays. If an SSAP value was configured, a warning message displays reminding you that the SSAP field should be left blank unless this adjacent MTA is U.S. GOSIP compliant and must have an SSAP value configured. If you need to cancel the data you just typed, * Press the Exit Task key. A confirmation displays asking whether you want to exit without updating the values of the fields. Deleting an Adjacent MTA To delete an adjacent MTA, * Select the adjacent MTA to be deleted from the Configure Adjacent MTAs screen. * Press the Action Menu key. * Select the Delete Adjacent MTA item from the Action Menu. This displays the Delete Adjacent MTA screen.Figure 7-8. Delete Adjacent MTA Screen To deletethe information and all routes defined for the selected adjacent MTA, * Press the Confirm key.
NOTE When deleting an adjacent MTA, the oq directory associated with the adjacent MTA is no longer serviced once the configuration is ENABLED. The oq directory and any message files in it are not deleted. These message files can be viewed and deleted using x4queview. The oq directory can be deleted using the HP-UX command rmdir <directory name>. The oq directory which may contain messages destined to the adjacent MTA is: /usr/spool/x400/oq/<output queue> where <output queue> is displayed on the Configure Adjacent MTA screen. Incoming messages from the adjacent MTA are processed. However, delivery/nondelivery notifications that are to be sent back to the deleted adjacent MTA are discarded.
To cancelthe delete operation, * Press the Cancel key.
![[]](../../pic3k/M011985/FFN173c50.gif)
![[]](../../pic3k/M011985/FFN183c50.gif)
![[]](../../pic3k/M011985/FFN193c50.gif)
![[]](../../pic3k/M011985/FFN203c50.gif)
![[]](../../pic3k/M011985/FFN213c50.gif)
![[]](../../pic3k/M011985/FFN223c50.gif)
![[]](../../pic3k/M011985/FFN233c50.gif)
![[]](../../pic3k/M011985/FFN243c50.gif)