Administering page two of Survivable Processor screen

Last Updated : Oct 05, 2015 |
Prolog information
Metadata
Keywords:
Use page two of the Survivable Processor screen if you have a CMS connecting to the Processor Ethernet interface of the server that you identified in page one. If the CMS was administered in the Survivable Processor - Processor Channels screen the system will automatically display on page two of the Survivable Processor screen. You cannot add an adjunct in this screen. The adjunct must be administered in the Survivable Processor - Processor Channels screen first.
  1. The Proc Channel field displays the processor channel used for this link when it was administered in the Survivable Processor - Processor Channels screen.
  2. Enter one of the following values in the Enable field:
    • Enter n (no) if this processor channel is disabled on the survivable remote server or the survivable core server.
    • Enter I (inherit) if this link is to be inherited by the survivable remote server or survivable core server. You must use the inherit option in the following scenario, where the main server connects to the adjuncts using the main servers Processor Ethernet interface and you want the survivable remote server or survivable core server to connect to the adjunct using their Processor Ethernet interface.
    • Enter o (over-ride) to over-ride the processor channel information sent in the file sync from the main server. The over-ride option causes the near-end (server’s end of the link) address of the link to change to a p when the translations are sent from the main server to the survivable remote server or the survivable core server. Generally you would want the over-ride option when an adjunct connects to the main server and you want the adjunct to connect to the survivable remote server or the Processor Ethernet interface of the survivable core server.
      When you enter o in the Enable field, you can enter the processor-channel information for the survivable remote server or the survivable core server in the remaining fields.
  3. The Appl field identifies the server application type/adjunct connection used on this channel.
  4. The Mode field identifies if the IP session is passive (client) or active (server). Valid entries are
  5. for server, or blank.
  6. The Interface Link field identifies the physical link carrying this processor (virtual) channel. Yap’ in this field indicates that the physical link is the Processor Ethernet interface.
  7. For TCP/IP, interface channel numbers are in the range of 5000-64500. The value 5001 is recommended for CMS.
  8. The Destination Node field identifies the adjunct at the far end of this link. Enter an adjunct name or leave this field blank for services local to this server.
  9. The Destination Port field identifies the port number of the destination. The number 0 means any port can be used. Valid entries are
  10. through
  11. In the Session Local and Session Remote field the Local and Remote Session is an integer from
  12. .
    13. ADDITIONAL INFORMATION:
    For each connection, the Local Session number on this switch must equal to the Remote Session number on the remote switch and vise versa. It is allowed, and sometimes convenient, to use the same number for the Local and Remote Session numbers for two or more connections.