DCE SW 7.2.6 stay in conflict with client sw version 6.1.1

[DCIM_Support]

Good evening,

I have a problem with the sw 6.1.1 on client systems and the DCE expert version7.2.6.

Problem Description:

Last week we installed new UPS systems type Smart-UPS RC 3000 RM XL.
The systems have the sw version 6.1.1 on the network card type AP9631.
The AOS as well the Application modul have the same version 6.1.1.
We detected a security issue with the recommandation to upgrade the systems to version 6.2.1

We started the upgrade on the DCE system over the known utility.

The upgrade was sucessfull for all Smart UPS with SW version 5.x.
For all system with sw version 6.1.1 the update was not sucessfull.

What was the problem?
On the smart ups we defined several user types.
The superuser apc with a non standard password. This usertype is new in Version 6.x
The user is defined per default and cannot be deleted.

We also defined a user with admin rights as we know from the version 5.x and earlier.
After the sw upgrade was not sucessfull, we take a look at the system per ssh connection.
Whether the AOS nor the Application modul were updated. We found the old version.
After rebooting the network card the system was recognized by the DCE without alerts.

The log file of the UPS showed no information which give us a clear hint regarding the problem.

The file transfer started at 22:38:14. There is no message why the file transfer was not sucessfull.
Now we try a manual update with a user with admin rights. Log in per scp was sucessfull.
After we starting the update the system asked us for a username and password.
We canceled the update and starting a new scp connection over the a login with the superuser.
The manual update was sucessfull.

After we check the device transfer settings on the DCE systems. The setting are wrong and we changed to the username and password of the superuser.

With full of hope we started again the sw upate but it fails.

In the meantime we realize the update manually so that the systems running with the new sw version 6.2.1.

Question:

1) Which failure we have made?

2) In case of we made nothing wrong, what are the consequences?
    SCP/FTP updates is only possible with the superuser.
    a) Does it afects only the version 7.2.6 (DCE) and the client version 6.1.1 (Smart UPS)
    b) Does it afects all version 6.x on the client side?
    c) Does it afect only the version 7.2.6 on the DCE side?

For your support I would like to say in advanced
"Thank you very much"

Kindly regards Frank

(CID:97486219)

[DCIM_Support · Accepted solution]

Hi Frank,

I looked at this for some time. I first downgraded a Smart-ups NMC2 to firmware 6.1.1. This unit had default credentials.  Everything looked OK. I then logged into my DCE 7.2.6 server and added that UPS. I tried upgrading it to the most current and I too seemed to fail (see screenshot below). The apparent difference is my AP9631 appeared to lock up and needed to be rebooted. I checked and everything seemed to be default except that Telnet was turned off. I did not think this should matter so just in case, I re-ran the test. Again the upgrade failed and the NMC needed to be rebooted. I've since let the support folks for the NMC know.

I then went to another DCE server which I had updated to 7.2.7. This server is on the same network segment as both the original DCE server and the NMC. I added the device to the 7.2.7 DCE server. I ran the same upgrade from 7.2.7 and went without issue. I logged in to the NMC and it is now reporting:

Name: sumx
Version: v6.2.1

I looked at the release notes for 7.2.7 but did not see anything related to this. It does appear however that at least in my test, upgrading DCE to 7.2.7 resolved this issue.

Steve

P.S., last screenshot is from the 7.2.7 box and successful upgrade.

(CID:97486300)

[DCIM_Support]

Hello Steven,

thank you very much for the fast response.

Excellente service.

Sld. Frank

(CID:97486503)

[DCIM_Support]

Hi Frank,

I just wanted to add, the other differences between the 2 DCE servers were (and I just thought of this) the unit was showing up with DNS name and the 2nd server only had a single entry for credentials. It is possible that the fact that the initial server did not have these settings could have influenced the issue as well.

As for the update, you'll need to contact tech support to obtain 7.2.7. This issue may be best dealt with at that level as well.

Steve

(CID:97486388)

[DCIM_Support]

Hello Steven,

just in the moment I´m looking for the version 7.2.7.

The latest version I found was 7.2.6.

It is possible to support us getting the version 7.2.7?

Muchas gracias Frank

(CID:97486504)

[DCIM_Support]

Hi Steven,

thank you very much for your service.

Regards Frank

(CID:97486505)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.