H300IP FAQ

H300IP 6.3 Frequently Asked Questions

  1. What is the latest version of H300IP?
    • Refer to the Support Table for the currently supported versions of H300IP; typically the highest release number is the latest version.
  2. Is a software key required?
    • Yes. A software key is required to operate this product. To obtain a key, please contact support. with the following information:
      1. The product - H300IP 6.3
      2. SITEID(s) of the system(s) you are installing to
  3. Can I share an SBCON interface between multiple systems
    • Unisys recommends against sharing an SBCON interface between multiple systems or partitions.  You should use a separate SBCON interface for each host connection to a NESiGate-CA or CO.
  4. How can I achieve full duplex operation in the OS2200?
    • A code change to OS2200 is required for full duplex arbitrary device operation.
      • Note: this patch is REQUIRED if the devices are configured as ARBCU/ARBDEV. If it is missing, I/Os will be VERY slow and no useful work will be possible using the hardware.
      For OS2200 Release SB7.1 (46R7): 
      *IOTBLD
      -10678/49,49
      CUTYPP  ARBCU  +(DF  HNADH,DEVDEP,SINGLE,0)  .   Arbitrary device

      For OS2200 Releases 8.0 (exec 47R1) through 11.0 (47R5D):

      *IOTBLD
      -10631,10631-
      /CUDEP/DEVDEP/

      For OS2200 Release 11.1 (exec 48R1):

      *IOTBLD
      -10905,10631-
      /CUDEP/DEVDEP/
  5. In what order are Netex paths generated by the Netex Configuration Manager?
    • The order in which paths are generated is related to the order in which ADAPTER statements are specified in the NCT. Paths are generated in the following order: For each Local Host ADAPTER (proceeding from last to first), paths are generated to each Remote Host ADAPTER (proceeding from first to last). For example: 
          HOSTA   HOST     TYPE=Linux   MODEL=Fedora
                  ADAPTER  MODEL=N130    NETADDR=02 TO=eth0  
                  ADAPTER  MODEL=N130    NETADDR=03 T0=eth0
          HOSTB   HOST    TYPE=Linux    MODEL=Fedora
                  ADAPTER  MODEL=N130    NETADDR=12 T0=eth0
                  ADAPTER  MODEL=N130    NETADDR=13 T0=eth0

       
        Paths will be generated in the following order:
              Path 1: 03->12
              Path 2: 03->13
              Path 3: 02->12
              Path 4: 02->13

 

 

H300IP 6.1 Frequently Asked Questions

  1. What is the current version of H300IP?
  2. What operating system levels are supported?
    • H300IP/HC 6.1 supports OS2200 29Rx-28R1 (11.1)
  3. Is a software key required?
    • Yes. A software key is required to operate this product. To obtain a key, please contact support.
    • In order to generate your key(s), you must tell us the product, the SITEID of the system(s) you are installing to, whether the system(s) will be connected to DXE or NESiGate or both, and whether you will be using protocol 4 sessions. If you don't know your SITEID you can find it by adding the SYSINFO utility supplied with the product. It is suggested that you email your request to us, with the SYSINFO data and we will return your key(s) via email. (See SUPPORT information above). You may then cut-and-paste the data into the appropriate file, minimizing any transcription errors. Edit the values in the $KEY$ file (see below) in ASCII with no leading spaces, e.g.:
      @ED,IQ NETEX*$KEY$.
      ** Netex key for system ABCD **
      258b773b458b7d12157e4a5c197e51fd
      @eof
  4. Can I share an SBCON interface between multiple systems?
    • Unisys recommends against sharing an SBCON interface between multiple systems or partitions. You should use a separate SBCON interface for each host connection to a NESiGate-CA or NESiGate-CO.
  5. Is there SBCON support for Unisys 2200?
    • Yes, in H300IP/HC Release 5.0 and above.
  6. Why is my transfer rate lower than expected? (ticket 1493)
    • A patch is available for this issue, and a permanent fix is being tested.
  7. Why can I not achieve full duplex operation?
    • A code change to OS2200 is required for full duplex arbitrary device operation.
    • Note: This patch is REQUIRED if the devices are configured as ARBCU/ARBDEV. If it is missing, I/Os will be VERY slow and no useful work will be possible using the hardware.
    • Find the change for your release level:
      1. For SB7.1 (46R7):
        *IOTBLD
        -10678/49,49
            CUTYPP ARBCU +(DF HNADH,DEVDEP,SINGLE,0) . Arbitrary device
      2. For releases 8.0 (exec 47R1) through 11.0 (47R5D), it can be abbreviated:
        *IOTBLD
        -10631,10631-
        /CUDEP/DEVDEP/
      3. For release 11.1 (exec 48R1):
        *IOTBLD
        -10905,10905-
        /CUDEP/DEVDEP/
  8. In what order are Netex paths generated by the Netex Configuration Manager?
    • The order in which paths are generated is related to the order in which ADAPTER statements are specified in the NCT. Paths are generated in the following order: For each Local Host ADAPTER (proceeding from last to first), paths are generated to each Remote Host ADAPTER (proceeding from first to last). For example: 
          HOSTA   HOST     TYPE=Linux   MODEL=Fedora
                  ADAPTER  MODEL=N130    NETADDR=02 TO=eth0  
                  ADAPTER  MODEL=N130    NETADDR=03 T0=eth0
          HOSTB   HOST    TYPE=Linux    MODEL=Fedora
                  ADAPTER  MODEL=N130    NETADDR=12 T0=eth0
                  ADAPTER  MODEL=N130    NETADDR=13 T0=eth0

       
        Paths will be generated in the following order:
              Path 1: 03->12
              Path 2: 03->13
              Path 3: 02->12
              Path 4: 02->13