IPO 12.0 Upgrade fails on Dell 630 servers

[NYSTECH]

Attempted to upgrade a Dell 630 from 11.1.3.2 to 12.0. Getting following error.
12.0 Upgrade of IP Office server failed. Sever did not upgrade after 3 attempts. Getting Error: An error occurred during reading of kickstart fileDisk "mapper/rootvg-rootvol" given in ignordisk command does not exit. The installer will now terminate.
Using 256G USB/ Rufus. Verified the ISO with Cheksum. Tried different USBs . I Did find one SOL on support site the resolution for that one which is exact same issue was that that server wasn't supported. I am looking through docs to see if this one is but, that doesn't seem like a great resolution to tell the customer.

Anyone else seen this or have resolution besides replacing the Server.

 

[IamaSherpa]

Have you verified the Dell 630 compatibility with Rocky Linux R9.3 (RHEL 9.x) ?

For what I can see these are the only supported OS, I've been told by Avaya that has to be strictly observed:

• BIOS
• Citrix XenServer 6.5
• Citrix XenServer 7.0
• Novell SuSE Linux Enterprise Server 11
• Red Hat® Enterprise Linux 6
• Red Hat® Enterprise Linux 7
• Red Hat® Enterprise Linux 8
• SUSE Linux ES 12
• SuSE Linux ES 15
• VMware ESXi 5.1
• VMware ESXi 5.5
• VMware ESXi 6.0
• VMware ESXi 6.5
• VMware ESXi 6.7
• VMware ESXi 7.0
• Windows Server 2008 R2
• Windows Server 2012
• Windows Server 2012 R2
• Windows Server 2016
• Windows Server 2019 LTSC

IPO R12 on HP Proliant Avaya Server Issues - Avaya: IP Office

Has anyone upgraded their HP Proliant (Avaya-provided) server from R11.1.3.1 to R12 yet? The log is showing a bunch of errors with some of files and then it just ends in "Pane is dead" at the bottom, which does nothing. It's like it can't read or pull some of the files. I used Rufus 4.6...

www.tek-tips.com

 

[JoConnex]

Had the same issue on a R640, after upgrading the Bios, I was able to upgrade. I found the BIOS download on the PLDS.

 

[NYSTECH]

Jo Connex yes was thinking of upgrading BIOS. The latest version I see on PLDS is BIOS_KM6P8_LN2.1.19.0.BIN

Is that the one you used?

 

[lleeNC]

I don't think the R630 is supported, per Avaya. It does not have RHEL 9.

Let me know if you do get it to work but we already spoke with Avaya and that's what they said. Only the R240 and R640 are supported or any other servers that has RHEL 9

 

[NYSTECH]

Some Docs say it is supported other don't mention it. Avaya has told us it is

 

[lleeNC]

I hate Avaya.

We are planning on moving it to VMware, where RHEL 9 is supported along with R12.

 

[NYSTECH]

I am trying to find file kickstart fileDisk "mapper/rootvg-rootvol" given in ignordisk command does not exit. but can't locate it.

Anyone know what folder/file it is supposed to be in?

 

[NYSTECH]

Just wanted to follow up with Avaya's response. The Dell 630 is not supported.
With the new Rocky Linux, we had to install additional modules to ensure compatibility with these two servers. Furthermore, for IPO 12.1 the installation process was changed from BIOS mode to UEFI mode. The primary reason we cannot support the older hardware is the lack of necessary Linux kernel modules.

IP Office Platform Guidelines Capacity manual shouldn’t be taken in account for upgrade purpose. It serves as a reference for planning, scaling, and optimizing IP Office deployments.”

The following tables list the specifications of the current Avaya supplied servers used for IP Office solutions.

Server option	Large Server	Small Server
ASP130 P3	ASP110 P3	–
SAP	700514098	700514262	700515009
Chassis	Dell R640	Dell R640	Dell R240
Rack size	1U	1U	1U
Processor	2 x 4210, 2.2GHz	2 x 4210 2.2GHz	1 x E2124, 3.3GHz
Cores per CPU	10	10
L3 Cache		13.75MB
Memory (RAM)	48GB	48GB	16GB
Hard disk drive	4 x 600GB	4 x 600GB	1 x 1TB, 7.2K
RAID Options	6	6	6
RAID Controller	H730	H730	Bios
Power Supplies	2 x 750W	2 x 750W	1
NICS	6 x 1GB full duplex	6 x 1GB full duplex	2
Optical Drive	1 x DVD ROM	1 x DVD ROM	None
Rail Kit	Yes	Yes

Server Combinations and Usage​

• The Server Edition Primary and Server Edition Secondary must be on equivalent platforms. This constraint applies equally to virtual servers. It is possible to mix native and virtual central servers, but the resources allocated to the virtual environment should match the native server.
• You cannot re-provision a Server Edition server without a complete reinstall. For example, to convert a primary server to a secondary or expansion system.
• You cannot set up a Server Edition Expansion System (L) in the Standard IP Office mode of operation in the IP Office Server Edition Solution. You cannot convert a Server Edition Expansion System (V2) to a Server Edition Primary or Server Edition Secondary server.
• The use of any external Voicemail Pro server is not supported.