Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problem installing signaling server in dl320 g4 1

Status
Not open for further replies.

jmpprd

Technical User
Nov 16, 2007
39
DO
e are trying to install the signaling server 5.0 on a dl320 g4 faced with the following problem.

this is the log file:

ProLiant System BIOS - D20 (03/10/2007)Copyright 1982, 2007 Hewlett-Packard Development Company, L.P.

2048 MB AvailableProcessor 1 initialized at 3.60 GHz/800 MHz(2MB L2)

Advanced Memory Protection Mode: Advanced ECC SupportRedundant ROM Detected -

This system contains a valid backup system ROM.<F9 = Setup>Integrated Lights-Out 2 Standard press [F8] to configure iLO 2 v1.29 Feb 28 2007 <IP unknown>SATA Option ROM ver 2.00.A10Copyright 1982, 2007. Hewlett-Packard Development Group, L.P. Port0: (Hard Disk) FB080C4080 Drive Write Cache Disabled HP Ethernet Boot Agent v8.3.9Copyright (C) 2000,2005 Hewlett-Packard Development Company, L.P.All rights reserved.Press Ctrl-S to Enter Configuration Menu ... Press "F9" key for ROM-Based Setup Utility Press "F10" key for System Maintenance Menu Press "F12" key for PXE boot For access via BIOS Serial Console Press "ESC+9" for ROM-Based Setup Utility Press "ESC+0" for System Maintenance Menu Press "ESC+@" for PXE bootAttempting Boot FromCD-ROMV1.6a++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Tier1 Server ID =

3, ProLiant DL320 G4

Initializing bsp drive for server type 3

Loading driver sysAtaInit

Loading driver sysSataInit

sysSataInit(0, 39, 7)

sysSataInit: creating (0, 0) = /dev/sda

Loading driver sysSatlInit

Loading driver sysMC146818Init

Loading driver sysHpDL320G4WatchdogInit























VxWorks System Boot





Copyright 1984-2004 Wind River Systems, Inc.











CPU: PC PENTIUM

Version: VxWorks5.5.1

BSP version: 1.2/3

Creation date: May 23 2007, 21:39:15



/dev/sda1 /boot msdos ro,autosync

/dev/sda2 /p vfat ro,autosync

/dev/sda3 /u vfat rw,autosync

/dev/sda4 /e vfat rw,autosync

/dev/hda1 /cd0 iso9660 user,ro,noauto,changeno

warn

Mounting /cd0

Mounting /boot

Could not mount /boot

Selecting nvram file from 0 sources



Reading boot parameters from (null)

Could not read nvram file, using default boot string





Press ^B to stop auto-boot...

7 6 5 4 3 2 1 0

auto-booting...





boot device : sata=0,0

unit number : 0

processor number : 0

file name : /p/mainos.sys

flags (f) : 0x0



Attaching to disk device...

mounting /p

mount failed.



Error loading file: errno = 0xd0001.

Can't load boot file!!



can you help me ?

 
Is this a Nortel supplied server or yours? There is some additional hardening and BIOS changes in the Nortel supplied box and one of the shelf will not work. You used to be able to get away with it with the ISP1100s and a Dell PowerEdge350, but that also was problematic at times.

911Guru
 
this is a nortel suplied server, i have 2 with the some problem.

what is the process to solve this case ????


thanks
 
Wait a second, I think I see your problem. The COTS servers run Linux, and it looks like you are loading VxWorks. Do you maybe have a SS Disk for an ISP1100? What release are you trying to install?

911Guru
 
i trying to install signaling server SSISP1100_50031

note :in the nortel website you only have to option


signaling server isp1100 and CP-PM



 
i found a document from nortel :
Product BriefCommunication Server 1000M
The foundation of your unified communications experience

in this domument i read that the signaling server on hp dl320 g4 you can install a linux o vxworks .


and remember the linux is for NRS .

 
I am getting the exact same thing when trying to start the install tool from the Signaling Server CD. Was this ever resolved?
 
You install Linux only if you are installing enterprise manager. The Linux OS does NOT support TPS for sets or trunks. The only application that can be loaded is NRS and Enterprise Manager.

You install VxWorks if you need TPS. You can also install the NRS on this OS.

The problem looks like you are using the video monitor to attempt the install you need to be plugged into the com port on the back of the machine with your laptop just like the ISP1100 servers.
 
I am trying to install VxWorks on the HP COTS signaling server (purchased from Nortel).

I have installed many ISP1100's, and never had a problem booting them from the CD.

I have followed the procedures in the NTP's, which state that the signaling server CD is bootable, and should automatically start the install tool.

I am connected to the server through the serial port.

I have also downloaded the signaling server .iso image from Nortel, and burned it to disc, and get the same symptoms as the original post.

I have also made a bootable floppy and attempted to use that to boot the server, with no success.

Has anyone had experience loading SS 5.00.31 on the HP DL320 G4?
 

Are you "seeing" the boot up through the com port connection? ( you mentioned LOG file in the original post)

Nortel had a note that they setup these servers once they ship them to the customer but in case the settings are reset on the server, they say to Boot to the Bios (F9) and in the RBSU menu screen go to "serial console and EMS -Bios serial console port" and confirm that baud is 9600 and it is set to COM1 instead of AUTO, and legacy USB Support is Disabled.

 
The server was not set up by Nortel. The hard drive is blank.

I followed the procedures for setting the options in the BIOS. I see the same messages from the original post on my serial terminal.

It looks like there is a mistake in the bootup config files on the CD, and the server is not able to start the install tool.
 
Does this apply to you?

Lifting of Stop Ship - NTDU97AAE5 - HP Signaling Servers
2007-12-05

Nortel is communicating that the stop ship on HP Signaling Servers has been lifted. Orders for the NTHU97AAE5 HP Server will resume shipping on November 20th, 2007. The original stop ship affected orders that included both the NTHU65AA Signaling Server software and the NTHU97AAE5 HP Server. The orginal problem prevented CS1000 signaling server software from loading on some Hewlett Packard HP DL320G4 rack mount servers. Some servers shipped from Nortel have a DVD drive that is incompatible with the current 5.00.31 software load. The symptom is that on initial installation, the software installer cannot find a specific file and the loader stops. HP servers shipped prior to September 24th 2007 will not be affected by this issue. Only servers shipped after this date within a specific range of serial number will have this issue. All other Signaling Server platforms were not affected by this alert including: ISP1100, CPPM-SS, IBM x306m. This alert also did not affect the Linux based software that can be installed on the HP Server. These include the following: NTHU67AA / NTE90670 - Enterprise common Manager S/W CD NTHU66AA / NTE90660 - NRS Application Server S/W CD NTE90665 - Linux Operating System CD If you already have the software installed or have not encountered this installation issue, then the server is OK and no action is required.
 
From the bulletin:

Analysis:
HP servers have been shipping since the GA of Release 5.0 in July 2007. In the September timeframe, HP changed the
DVD drive in the unit to a newer model. This new DVD drive is not currently compatible to the VxWorks Operating
System included in our Signaling Server software load. The symptom is that on initial installation, the software installer
cannot find a specific file and the loader stops. Nortel is planning on updating the Signaling Server software load to
include the drivers for the new DVD drive. The update should be available before the end of 2007. Once this is
complete, the affected HP servers will be able to load the signaling server software. A subsequent bulletin will be published with the appropriate details.
Nortel has worked with HP to determine when the DVD drives were replaced and are able to determine, via the serial
number, if the server will load the current 5.00.31 signaling server software. The serial numbers are visable both on the
carton and on the server. Servers that fall in the serial number range USE707xxxx to USE734xxxx are OK and will load
the 5.00.31 signaling server software as expected. Servers that fall in the serial number range USE738xxx and higher will
not load the current signaling server software. Nortel has segregated the inventory and we are now able to resume
shipments of the HP signaling servers.
 
allenmac, if the bulitin from curtismo does not apply to you try to see if you can partition the drive with FDISK and format it with MSDOS (don't bother making the partition huge)

Someone I know was playing around with a sig server and found that the software was looking for a partion on the HDD drive....

BSP version: 1.2/3
Creation date: May 23 2007, 21:39:15

/dev/sda1 /boot msdos ro,autosync
/dev/sda2 /p vfat ro,autosync
/dev/sda3 /u vfat rw,autosync
/dev/sda4 /e vfat rw,autosync
/dev/hdc1 /cd0 iso9660 user,ro,noauto,changenowarn
/dev/fd0 /f0 msdos user,rw,noauto,changenowarn
Mounting /cd0
Mounting /boot
0x1efe8eb0 (tBoot): dosFsLib.c : Malformed boot sector. Offset 32, value 0.
0x1efe8eb0 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the next block as boot block.
0x1efe8eb0 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 5.
0x1efe8eb0 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions are properly handled.
Selecting nvram file from 0 sources

Reading boot parameters from (null)
Could not read nvram file, using default boot string
 
also when you interupt the boot up ^B and change the boot params (C) and try to set the BOOT DEVICE to CD0
 
Thanks for the info on the bulletin. My server is one of the newer ones with the updated DVD, and my Sig Server CD NTE90655 is dated June 2007.

I am going to see if there is a newer version on the Nortel site, if not, I am going to try to add a partition to the HDD.

I have already gone through and changed the boot parameters manually to cd0 with no success.

I will post my results.
 
The Nortel channel partner for our vendor is checking on the new signaling server software release to support the HP signaling servers affected by the bulletin (was supposed to be available sometime in December).

I created a partition on the HDD named boot, and copied the nvram.sys file from the root of the signaling server cd to the HDD.

The server now partially boots and selects the nvram.sys file from the hard drive, but still cannot load /cd0/mainos.sys file.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top