config loading on hp c7000

[Johan Huysmans]

The "SET EBIPA" section of my config file is loaded very slowly. All the other sections are on a more normal speed.

Is this normal or can this be tuned?

thx!

[Johan Huysmans]

It takes 20 seconds to perform following command:

SET EBIPA SERVER 192.168.251.70 1


During the run it also outputs following lines:
Successfully set device (iLO) bay # 1 to IP address 192.168.251.70
A possible duplicate IP address was found on the network: 192.168.251.70.
A possible duplicate IP address was found on the network: 192.168.251.71.
A possible duplicate IP address was found on the network: 192.168.251.72.
A possible duplicate IP address was found on the network: 192.168.251.73.
A possible duplicate IP address was found on the network: 192.168.251.74.
A possible duplicate IP address was found on the network: 192.168.251.75.
A possible duplicate IP address was found on the network: 192.168.251.76.
A possible duplicate IP address was found on the network: 192.168.251.78.
A possible duplicate IP address was found on the network: 192.168.251.79.
A possible duplicate IP address was found on the network: 192.168.251.80.
A possible duplicate IP address was found on the network: 192.168.251.81.
A possible duplicate IP address was found on the network: 192.168.251.82.
A possible duplicate IP address was found on the network: 192.168.251.83.
A possible duplicate IP address was found on the network: 192.168.251.84.

For the IP addresses to be assigned EBIPA must be enabled.


Is this normal?

[The Brit]

Hi Johan,

Yes, I believe this is normal.

When you modify or apply an IP address in EBIPA, and click the APPLY button, the OA performs an update on all of the device bays, even though they may not have changed.

The sad part is that it doesn't seem to have enough smarts to recognize that the "duplicate" is the actual bay it is currently trying to update. i.e it tries to set IP = X on the device bay which already has IP = X, and announces that it is a duplicate. It will give this response for every bay where the IP is not changing.

Go figure.

Dave.

[Johan Huysmans]

thx for the info!

Is there any chance it will be solved in a future firmware version?

[Cederberg]

Yes it seems to be fixed in OA FW version 3.00

The method used to determine duplicate EBIPA IP addresses within OA 2.60 and earlier has been found to be unreliable and at times indicates duplicate IP addresses that were in fact not duplicate, thus duplicate IP address checking has been removed from the OA 3.00.