Unable to access Host IMM - PureData System for Analytics

Resolving The Problem

At the top of /etc/hosts file, the IMM ip address for both HA/HA2 should be listed

Ex.

192.168.1.100 netezza-h1-imm.netezza.com netezza-h1-imm # h1 imm
192.168.1.101 netezza-h2-imm.netezza.com netezza-h2-imm # h2 imm

/etc/hosts is just a text file. It should be accurate, but the information is not validated

To verify the actual IMM network configuration,use :

/opt/nz-hwsupport/install_tools/nz-rmgt.pl

This will give you menu option to view and configure IMM.
Select an Option:
1: Enter IP information
2: Set email alerts
3: View existing information
4: Exit

Use option 3 to view the information.

Example output:
Network Enabled = Enabled
DHCP Client = Disabled
Hostname = netezza-h2-imm
IP Address = 192.168.1.101
Subnet = 255.255.255.0
Gateway = 192.168.1.1

If the information does not match, verify with the network/DNS team to identify what SHOULD be the correct information.

If /etc/hosts must be updated, you can use any text editor to correct it.
If the IMM configuration itself must be updated, use option 1 of nz-rmgmt.pl
Use option 3 again to verify the changes went through

If the IMM config seems correct, but the GUI is still not reachable via browser, next check for open ports.

The full list of ports required to be open are available online, but the key ports are:
80 (browser)
443 (browser, SSL enabled)
3900 (remote control)

You should test connectivity over these ports from the desired endpoint.

This is most likely the admin's laptop and NOT the PDA system itself.

Example:

C:\Users\IBM_ADMIN>ping 192.168.1.101
C:\Users\IBM_ADMIN>telnet 192.168.1.101 80
C:\Users\IBM_ADMIN>telnet 192.168.1.101 443
C:\Users\IBM_ADMIN>telnet 192.168.1.101 3900


If you are unable to ping the IMM (and ICMP has not been blocked in the infrastructure), you should examine the cabling onsite.

If the cables are plugged in, configure a laptop to be on the same subnet, and plug a new cable directly into the IMM.

If the IMM pings locally, it is either the cable, or the network. Consult the network team to narrow down further.

If the IMM fails to ping locally, reboot the IMM.
/opt/nz-hwsupport/install_tools/asu64 rebootimm

If the IMM still fails to ping locally, check the UEFI changelogs for any relevant FW known issues.
If on latest FW, or no known issues, escalate the issue.

If ping works, but any of the telnet commands result in port-refused or failure, consult the network team to open ports.

If the telnet command results in a login prompt, but a browser is still not able to connect, it is a laptop browser configuration issue and is outside the scope of this document. The IMM is working properly.