HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

rp7410 looses SCSI ID's

 
Timo J
Frequent Advisor

rp7410 looses SCSI ID's

Configuration:

- two rp7410 hosts
- two PCI Ultra 160 SCSI Adapter on each host
- DS2300 connected to both hosts

Because of the configuration, I had to set SCSI ID's on first host to 6 instead of default 7.

I'll boot the machine, stop at BCH and change the ID's. After that everything is OK. But If I shut down the host and let it be without electricity e.g. half an hour and boot it up again, the SCSI ID's defaults to 7.

We've changed all the batteries we can find from the system (One at each cell board and one at MP-card) but still the ID's are lost if host is disconnected from power supply for some time.
N/A
7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: rp7410 looses SCSI ID's

Shalom,

The scsi card is sitting in i/o slot 7, and that is where the system thinks everything hung on it lies.

Perhaps something else can be set to 6 other than things hung off that card.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Timo J
Frequent Advisor

Re: rp7410 looses SCSI ID's


Nope, cards are sitting on I/O-slots 5 & 6. I've done that ID change many times on rp5470 models, and never had a problem with that.
N/A
Torsten.
Acclaimed Contributor

Re: rp7410 looses SCSI ID's

Depending on the HBA model you probably need to use the mptconfig tool.
see man mptconfig

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Timo J
Frequent Advisor

Re: rp7410 looses SCSI ID's

HBA Type is PCI Ultra160. Looks like mptconfig is for mpt-driven PCI-X Ultra320 HBA.
N/A
tkc
Esteemed Contributor

Re: rp7410 looses SCSI ID's

ok, let's try to isolate if the problem is due to hp-ux. when you boot up again, at the bch level, did you notice the scsi id already changed back to default, 7 ?
if so, we do not have to investigate into any issue due to hpux patches or scsi driver. i would suspect the firmware of the rp7410 has overwritten the bch scsi id.

refer to :
http://www.docs.hp.com/en/A6829-96002/ch02s06.html

2 methods of setting the scsi id are the firmware and bch.
Phil uk
Honored Contributor

Re: rp7410 looses SCSI ID's

Mikko,

On this server, say for instance you power off for 30mins and indeed your ID changes from 6 back to 7 as stated, what happens to the system clock...does it also loose 30mins?
As a brief experiment, the "good" system which you have ID7 set....why dont you change, from BCH, the ID to something like 4 and power it off for 30mins (BUT DONT TRY TO BOOT HPUX), and see if it also actually defaults back to ID7.
It would be intersting to see if the machine is also "going to defaults", albeit you wouldn't necessarily notice as you already have a default value of 7. If it maintains ID4 then change it back to 7 for normal operation before you boot it again.
(Does the clock loose 30mins - or however long it was powered off for?)
Finally, what is the product number for the U160's?
Can you let us know the result of the "experiment"
Phil
Timo J
Frequent Advisor

Re: rp7410 looses SCSI ID's

At last, problem solved. The reason for that strange behaviour were bad battery connectors on cell boards (Or at least after changing the connectors, the problem did not exist ;) ). The connectors were so close to contact that sometimes they contacted the battery and sometimes not. And because we moved the rack sometimes a little, the contact was randomly on and off.

When this problem occured first time, we measured all the batteries (one on each cell board and one on MP-card) on that system and the voltage levels were ok. But after visual inspection we noticed that problem with the connectors.

N/A