network access not working even though I can ping

[Anonymous user]

I'm working with a an AP9618 card which was just installed in a 2200 XL UPS.

I can get in through the console and I configured the IP address. Now I can ping to the device and I can ping from it.

However, I can't access it via telnet, ssh, http, https. This is all within the same telnet so there's no firewall between me and the card. From my workstation, I can access other AP96xx cards on the network, no problem.

If I scan the device with nmap, it reports that all TCP ports are filtered. A UDP scan with nmap shows ports 161 and 33281 in an indeterminate state ("open|filtered").

Any ideas how I can get this thing functioning?

[Anonymous user]

I'm working with a an AP9618 card which was just installed in a 2200 XL UPS.

I can get in through the console and I configured the IP address. Now I can ping to the device and I can ping from it.

However, I can't access it via telnet, ssh, http, https. This is all within the same telnet so there's no firewall between me and the card. From my workstation, I can access other AP96xx cards on the network, no problem.

If I scan the device with nmap, it reports that all TCP ports are filtered. A UDP scan with nmap shows ports 161 and 33281 in an indeterminate state ("open|filtered").

Any ideas how I can get this thing functioning?

[BillP · Accepted solution]

Have you triple checked your subnet mask and default gateway settings between the computer you're at and the AP9618? I see this as a common problem when you can ping but not access. I also am thinking to verify the IP address is correct or that there is no IP conflict anywhere. If you pull the network cable, does the ping stop?

Another thing I thought of was if you had a proxy set up on your system somewhere that was forgetton.

Are the other cards on the same VLAN, LAN, etc as this AP9618?

If you're really sure you've ruled that out, you can also verify these services are actually enabled on the card or if they have been disabled or modified. To check web for example, log in via local console and go to Network-> Web/SSL/TLS and verify what is there to make sure someone didn't change it. You could paste it too here as well.

Another option is just to reset the card to defaults and try one more time. This option is under System->Tools I think and you could reset the card to defaults then make sure to press Esc until you get back to the main menu and press log out or else it won't work until your session times out if you don't actually "log out."

Hope that helps get you started!

[Anonymous user]

In addition to Angela N's most excellent recommendations/advice, you should/could also check to make sure your card's firmware is at the latest revision, which is AOS 3.7.3 / SUMX 3.7.2 given that this is for a Smart-UPS. If its really old / outdated that could cause issues! ...Good luck!

[Anonymous user]

Thanks for responding. Yes, I checked all that. I can observe ping traffic using Wireshark, and then the other (failing) traffic, and verify that the MAC address matches that of the device. The other cards are on the same VLAN.

Just tried a reset to defaults, didn't help.

I just had a chat with a support person who told me that I should remove the card and do something called a "Brain Dead Test", then reinsert the card. This will entail shutting down the UPS so it's going to have to wait until scheduled downtime.

[Anonymous user]

Thanks, Battman. I just stepped away from where I was doing the serial console connection, but the Quality & Assurance slip taped to the outside of the anti-static bag in which the card was packed does say that the FW revision is AOS 3.7.3 / SUMX 3.7.2.

[Anonymous user]

Not sure I've ever heard that brain-deading a UPS made any difference to the network card, but worth a try. Another thing you can do is re-flash the card, as I've seen corruption rear its ugly head once in awhile. You can get the .exe file for the aos/sumx combo from APC and either ftp the files in one at a time, (starting with the AOS) or use the upgrade wizard.

[Anonymous user]

Ah, that sounds promising. Is that what I need: "Network Management Card v3.7.2 Firmware for Smart-UPS with AP9617/8/9"? (Even though it only says 3.7.2 and doesn't mention 3.7.3?)

I tried downloading the utility and running it. But it looks like it only works over IP! When I ran it, it said

Checking network connection ... OK

Testing login ... Login failed

And the result.txt file has:

Using AOS file

: AOS = apc_hw02_aos_373.bin

Using Application file: APP = apc_hw02_sumx_372.bin

Checking network connection ...  ERROR!!! Login unsuccessful.

Not all Network Management Cards were upgraded successfully:

    10.0.4.69: Could not log into the Management Card's FTP server.

Encountered 1 failures during upgrade.

I guess I can go back to the serial connection and see if I can try to enable the FTP server.

[Anonymous user]

Well, FTP server was already enabled. While connected to the serial connection, I did verify the firmware numbers and they are the latest.

I tried turning on https and ssh, instead of http and telnet, but I still can't access the card over the network.

It was interesting, when I turned on https, I got a couple screens to accept, ending with "Type yes to accept or enter to cancel." I hit enter by mistake, but the next screen still showed Accepted.

[Anonymous user · Accepted solution]

If FTP doesn't work, your last resort is to send the files Xmodem slow boat way from your hyperterminal connection into the card's console. ...it will take about 12 to 15 minutes per download even at the highest speed option (38,400). Good luck!

[Anonymous user]

Ah, the two .bin files?

I might try  that. First I'll have to get my hands on HyperTerminal or something else that supports Xmodem for Win7 (doesn't seem to be available in PuTTy).

How do I send both files? I played with the Xmodem option in the card and it looked like it only takes a single download then reboots.

There's another card on my desk, a 9630, which was believed to be defective prior to when I came on board. I wonder if it had the same symptoms; that might point to the UPS after all, and maybe a "brain dead test" will be the answer.

[BillP]

A braindead only resets the UPS communications and I also agree with Battman that this is a useless step in troubleshooting network connectivity with the Network Management Card. I would skip that and lets move on.

Can you try a direct connection from a computer to this card via a crossover cable?

I don't think firmware is the issue if you're able to log in via serial.

[Anonymous user · Accepted solution]

Yeah, I was thinking of trying a direct ethernet connection, so this morning I connected the card and a laptop to a microswitch. Seemed to work fine.

Then I connected both of them to the same network switch, and it stopped working again. I even tried mirroring the port on which the card is connected so I could monitor it with Wireshark. I can see the traffic being sent to the card, but the card doesn't respond to anything except ping.

[Anonymous user]

I thought maybe it was an issue with the connection to the network switch (maybe the automatic port config or something) so I tried branching off the network switch to the microswitch and then connected the card from there. Didn't work.

So I connected the laptop to the microswitch to at least see if things would keep working within the microswitch. Didn't work.

So then I broke the connection between the microswitch and the network switch. I.e., restoring the test configuration from my previous post. And it still didn't work.

So now I think I may have just gotten lucky that time.

Since you all think that a braindead won't help, any idea what I need to do to reach a tech who will help me without requiring me to jump through pointless hoops?

[BillP]

Hi Elliot,

If you have some time today, I can work with you..I am on eastern time.

I'll send you an email.

[Anonymous user]

Hey, thanks to Angela N. for finding some time to go over this with me on the phone.

It turns out that it was a network config issue after all! I'd set the card to use netmask 255.255.255.252 when it should have been 255.255.252.0.

The inconsistent results in later tests were undoubtedly because I wasn't always using the same IP address on the laptop that I was using to test--sometimes it was in the same /30 subnet as the card, sometimes it wasn't.

[Anonymous user · Accepted solution]

Many years later, this thread is still helpful! I was having the exact same issue, where i could ping the UPS but no other services would work. Turns out someone forgot to put in the Default Gateway in the IP configuration. Once that was in, everything worked again.