07-03-2013 10:38 AM
We've been running the following command on all of our HP-UX 11.23 PA-RISC servers for years.
/opt/ignite/bin/make_net_recovery -v -n 3 -u -s mkeadm02 -x inc_entire=vg00 -x exclude=/net -x exclude=/cdrom -P s >> /var/adm/log/ignite.log
We do this on a monthly basis. It runs out of cron.
As I said, we've been doing it this way for years.
Today however, one of our HP-UX 11.23 PA-RISC servers generated the following message and the make_net_recovery was unsuccessful.
ERROR: group_name:DESCRIBE_GROUP: "group_name" attribute not found.
save_config: Error - get_system_info failed to get VxVM disk group information from smapi listener.
======= 07/03/13 12:08:12 CDT make_net_recovery completed unsuccessfully
We've tried to re-run it on this server but it keeps generating the same message.
The make_net_recovery ran fine last month on this server.
No recent changes were done to this server as far as patching.
It was last patched in March of this year.
Anyone know what this "group_name attribute not found" refers too?
Any help would be greatly appreciated.
BTW, this same make_net_recovery command runs fine on all the other HP-UX 11.23 PA-RISC servers in our environment. Only this one server is having the problem.
Thanks in advanced for any assistance.
07-03-2013 11:24 AM
Are you using VxVM as a volume manager? Are there any issues with it?
The reason I ask is:
>>ERROR: group_name:DESCRIBE_GROUP: "group_name" attribute not found.
>>save_config: Error - get_system_info failed to get VxVM disk group information from smapi listener.
Perhaps the two messages are related?
I have found a reference to DESCRIBE_GROUP in a DRD manual where DRD was failing because a disk group name was longer than 16 characters. I don't know if the same applies to Ignite or not.
The manual I found is at:
If it is not this, it may be something else related to VxVM.
Search for "DESCRIBE_GROUP"
07-03-2013 01:38 PM
To answer your question, we aren't using VXVM for volume management.
Thanks for the DRD document link but it doesn't appear to be related to the Ignite errors we're encountering.
I suspect we'll have to follow up with HP support on this one.
Thanks for replying.