Subscribe

Cannot Access Fas2050 using Netapp System Manager

Hello,

I'm trying to manage our filers (fas2050) using the Netapp System Manager.  When I add the discovered devices and try and login I get the following error -

API invoke failed.  The remote server returned an error: (502) Bad Gateway

I'm on the same subnet as the filer

Any ideas?

Thanks

Re: Cannot Access Fas2050 using Netapp System Manager

Looking into your problem.

Can you provide the following information:

1. you filer ONTAP version. your System Manager version.

2.output of the command "route -sn" on your filer.

3. output of command "ifconfig -a" on filer cli.

4. Output of the command "ipconfig /all" from from Windows server where System manager is installed.

Try pinging the filer from you Windows system ( which has system manager install)  using the full hostname and IP.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Cannot Access Fas2050 using Netapp System Manager

Looking into your problem.

Can you provide the following information:

1. you filer ONTAP version. your System Manager version - 7.3.3.

2.output of the command "route -sn" on your filer. -

Routing tables

Internet:
Destination      Gateway            Flags     Refs     Use  Interface
default          10.254.253.1       UGS         4     2733  vif1
10.254.253/24    link#5             UC          0        0  vif1
10.254.253.1     0:0:c:7:ac:0       UHL         1        0  vif1
10.254.253.10    0:10:db:ff:20:50   UHL         0        0  vif1
10.254.253.84    0:c:29:b7:c9:78    UHL         0      285  vif1
10.254.253.90    link#5             UHL         1     3713  vif1
10.254.253.100   0:17:8:50:b4:b0    UHL         1      443  vif1
10.254.253.101   0:50:56:b8:5f:45   UHL         0       26  vif1
10.254.253.112   0:c:29:1a:24:7     UHL         0      124  vif1
10.254.253.135   2:a0:98:24:85:68   UHL         0      483  lo
10.254.253.255   ff:ff:ff:ff:ff:ff  UHL         0     2435  vif1
127              127.0.0.1          UGS         0      290  lo
127.0.0.1        127.0.0.1          UH          2       52  lo

3. output of command "ifconfig -a" on filer cli.

e0a: flags=0xad48867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:24:85:68 (auto-1000t-fd-up) flowcontrol full
        trunked vif1
e0b: flags=0xad48867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        ether 02:a0:98:24:85:68 (auto-1000t-fd-up) flowcontrol full
        trunked vif1
lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1
        ether 00:00:00:00:00:00 (VIA Provider)
vif1: flags=0x22d48863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
        inet 10.254.253.135 netmask-or-prefix 0xffffff00 broadcast 10.254.253.25
5
        partner vif1 (not in use)
        ether 02:a0:98:24:85:68 (Enabled virtual interface)

4. Output of the command "ipconfig /all" from from Windows server where System manager is installed.

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.254.253.84
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.254.253.1
DHCP Server . . . . . . . . . . . : 10.254.253.100
DNS Servers . . . . . . . . . . . : 10.254.253.100
                                    10.0.0.10

Try pinging the filer from you Windows system ( which has system manager install)  using the full hostname and IP.

Yes, both work.

One thing the fqdn of the filers in the NSM is 'hostname.hostname' rather than 'hostname.domainname'  not sure if that is the reason??