2 questions: ISX Manager and AP9617 NMC

[Anonymous user]

We've got an ISX Manager server that I'm trying to set up as the trap receiver for all our APC UPS's. So far, I've only been able to get one of them to properly work. Whenever I do a discovery for the IP addresses of the others, I receive one of several errors: Ping failure (despite me being able to do so myself), SNMP failure (despite it being configured on the UPS itself), or SNMP timeout. Any suggestions?

Also, I've deployed a few of the AP9617 NMCs and configured them, but now I am no longer able to access them via Telnet or Web interface. They are on the network as I can ping them, but the interfaces are inaccessible. I've tried resetting the card multiple times but it is basically locked itself from any external access method. What gives or how can I reset to factory defaults?

[TheNotoriousKMP_apc]

Hello,

Regarding the cards with the ISX Manager, are they on the public side of your network, or on the APC private side? Are the Usernames and Passwords the same as the one that IS working and found by ISX Manager? Are they all the same version of Firmware on the card?

With the AP9617's, can you start an FTP session with them? If so, and can get in using the Username and Password, you can try to do a firmware upgrade on those, hoping that it is just an AOS error that is not allowing for the interface to load. However, you may have to do a physical reset on it by following the K-base.

[Anonymous user]

I tried a physical reset of one of the units and that finally got the interfaces to come up. I thought I had done that once before, but apparently not. After doing so, I was finally then able to get the ISX Manager to recognize it.

As for the firmware/AOS, they are all the same (3.5.5) except for the 2 Symmetra PX systems we have, I believe they are 3.3.1 except they are the ones now that I'm not able to access. I'm thinking they will have to be put in some kind of maintenance bypass mode to get the cards to reset similar to the process with the Smart-UPS I just did.

EDIT: By the way, all the units are on the public domain except for the Symmetra system that is physically connected to the ISX Manager (that's another issue I'm working on). And they are all also still running on the default username/password.

Message was edited by: gdavidson79

[TheNotoriousKMP_apc]

Hello,

Good to hear, are you still experiencing any problems with the integration of these with ISX Manager?

[Anonymous user]

KMP,

Yes, I was finally able to get the Symmetra (v3.3.1) loaded into ISX Manager with some help from APC support. Turns out it doesn't like misspelled community names...ha ha. I swear I looked at those settings until my eyes bled but it is now up and running. Thanks again for your advice.

[TheNotoriousKMP_apc]

Greg,

Excellent. Next time if there's a problem, if you haven't already ventured into it, I would start an FTP session with the card that is working, and do a "get config.ini" and take a look at that configuration in the community names section, then match that to a config (by doing the same thing), of another one that isn't working. You can re-up an edited config file after you make changes to it, so that essentially, you can just take the config that works, change the IP address, and re-load it to another card.

[Anonymous user]

I had an NMC that wasn't on the ISX. I upgraded the firmware to 3.5.8. It lives on a 1000RM2U.

Before the upgrade, I was able to http to the NMC. Even after the upgrade, I could access the GUI. But then I added it to the ISX and now I can't talk to it anymore.

What gives? Doesn't the reset button actually factory default the NMC??? I must be doing something wrong because even after hitting the reset button, it responds (ping) on the same IP. I can't log in using apc/apc or any other username and password that I've used.

How do I actually do a factory reset on that NMC?

Any help from the pros would be appreciated. Thanks in advance.

[Anonymous user]

Hi Sonnyali,
Sounds like something might have happened during the firmware upgrade. Since it responds to ping, it should still have the same ip. I would try to reflash the firmware first, if that doesn't work, it might be best to connect to it through the ups' serial interface. This way we can check a few things and determine if the firmware upgrade has taken out the ftp/web server interfaces.

You will need the black 940-0024 serial cable that came with the unit and a computer with a serial port or usb to serial converter. The port settings you will need to use are as follows 2400,8,n,1. Once connected, hit the enter key a few times to pull up a login prompt. Once you've logged in, verify that the status of the card is P+N+A+. If it is anything else, you will need to reflash the firmware, possibly through the serial interface. You can find the instructions here:

http://nam-en.apc.com/cgi-bin/nam_en.cfg/php/enduser/std_adp.php?p_faqid=768

All the reset button on the card does is reboot the network interface and temporarily reset the username. To reset it to defaults, you can only do that through the web, telnet, or serial interfaces. Hope this helps, let us know if you need any further assistance.

[Anonymous user · Accepted solution]

We've got an ISX Manager server that I'm trying to set up as the trap receiver for all our APC UPS's. So far, I've only been able to get one of them to properly work. Whenever I do a discovery for the IP addresses of the others, I receive one of several errors: Ping failure (despite me being able to do so myself), SNMP failure (despite it being configured on the UPS itself), or SNMP timeout. Any suggestions?

Also, I've deployed a few of the AP9617 NMCs and configured them, but now I am no longer able to access them via Telnet or Web interface. They are on the network as I can ping them, but the interfaces are inaccessible. I've tried resetting the card multiple times but it is basically locked itself from any external access method. What gives or how can I reset to factory defaults?