XUA: NonStop IP address not showing up in monitor dumps / wrong UAGROUP is selected when attempting MFA logon from an SSH session

XUA: NonStop IP address not showing up in monitor dumps / wrong UAGROUP is selected when attempting MFA logon from an SSH session

This is NOT an XUA issue.  This is an issue with older versions of SSH (pre-ACS), which does not provide the ip address.  Specifically, because the ip address is not being recorded in the Safeguard audit, there is no ip address to provide to XUA.  The only solution is to upgrade SSH on the affected NonStop to a T0801L02_ACS or later version of SSH.  This will correct the issue of the ip address not being recorded in the Safeguard audit.

If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.

    • Related Articles

    • XUA: How to do an XUA monitor

      1. Uncomment the MONITOR keyword in the UACONF file by editing the file and removing the ?!? from the first position in the line. The modified line should look as follows: MONITOR $S.#XUA.MONITOR Note: If your spooler does not have a collector called ...

    • XUA: How to enable UAGROUP SAFEGUARD-PRIVLOGON

      As of Netbatch SPR T9190AER NetBatch now supports SAFEGUARD Security-Group privileges. Safeguard PRIV-LOGON functionality available beginning with Safeguard releases H06.11 and G06.32. The from_user must be $EVERYONE or $EVERYONE-NET as the NETBATCH ...

    • XYPRO GUIs can't connect to the NonStop host after the host ip address is changed

      If the user cannot connect to the NonStop host after the host ip address has been changed, then both XYGATETR (XTR) on the NonStop host and the GUI must be modified to reflect the new ip address 1. If XYGATE/TR (XTR) is configured on multiple NonStop ...

    • XUA: How does IPLOOKUP find the ip address for a session?

      IPLOOKUP can use different search criteria to look up IP addresses, such as the terminal name, the transport process, and the port number. Depending on which search criteria is supplied and which stack process the connection came through, IPLOOKUP ...

    • XUA: System response is delayed when logging onto a TACL via an SSH session

      1. Ask the customer to check the ELP_OBJECT value for the affected STN process in STNCOM. a. STNCOM $<proc name> (Where $<proc name> is the name of the desired STN process, e.g. $ZPTY) If the STN process name isn't known, do a "STATUS *, PROG ...