HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Control number (device file), Ignite restore and ...
Operating System - HP-UX
1833788
Members
2770
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2003 10:31 AM
06-19-2003 10:31 AM
Control number (device file), Ignite restore and MC ServiceGuard
Hello Folks,
I have a question related to the device file (control number)and the MC ServiceGuard configuration.
Normally the device file number changes after the Ignite restore. Since the c? is the hardware-bus id.
In a non-cluster environment I can the device file number by using the following commands.
#ioscan -f | grep -e INTERFACE | grep -v target | awk '{print $3, $1, $2 }' > infile
#sbin/ioinit -f /infile -r
----reboot----
#insf -e
Someone told me that the above commands/procedure is not recommended in the cluster environment. Is there any other better procedure for this to do?
I really appreciate your response.
Thanks,
Nikee
I have a question related to the device file (control number)and the MC ServiceGuard configuration.
Normally the device file number changes after the Ignite restore. Since the c? is the hardware-bus id.
In a non-cluster environment I can the device file number by using the following commands.
#ioscan -f | grep -e INTERFACE | grep -v target | awk '{print $3, $1, $2 }' > infile
#sbin/ioinit -f /infile -r
----reboot----
#insf -e
Someone told me that the above commands/procedure is not recommended in the cluster environment. Is there any other better procedure for this to do?
I really appreciate your response.
Thanks,
Nikee
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2003 11:58 AM
06-19-2003 11:58 AM
Re: Control number (device file), Ignite restore and MC ServiceGuard
Your friend must be refering to :
1) Matching the same devices on both nodes, and,
2) Re-making the cluster.ascii file to accomodate the changes.
The cluster binaries control all the resources with MC/SG so they would have to be remade.
There is one more possibility, your procedure is incomplete.
A) #ioscan -f | grep -e INTERFACE -e DEVICE | grep -v target | awk '{print $3, $1, $2 }' > /infile
(* Note: infile resides in / *)
B) # vi /infile and modify
# shutdown -r y
# ISL> hpus -is (* single user mode *)
# /sbin/ioinit -f /infile -r
# auto reboot takes place
###########################################
# TWO
###########################################
1) A) above
2) B) above
3) mv /stand/ioconfig /stand/ioconfig.sav
mv /etc/ioconfig /etc/ioconfig.sav
shutdown -r now
4) Do to missing 'ioconfig' file the server will stop at: (IOINTRC:>
5) (IOINTRC:> # /sbin/ioint -c
6) (IOINTRC:> # /sbin/ioinit -f /infile -r
7) auto reboot takes place
Make sure you have two make_tape_recovery tapes verified before doing this.
1) Matching the same devices on both nodes, and,
2) Re-making the cluster.ascii file to accomodate the changes.
The cluster binaries control all the resources with MC/SG so they would have to be remade.
There is one more possibility, your procedure is incomplete.
A) #ioscan -f | grep -e INTERFACE -e DEVICE | grep -v target | awk '{print $3, $1, $2 }' > /infile
(* Note: infile resides in / *)
B) # vi /infile and modify
# shutdown -r y
# ISL> hpus -is (* single user mode *)
# /sbin/ioinit -f /infile -r
# auto reboot takes place
###########################################
# TWO
###########################################
1) A) above
2) B) above
3) mv /stand/ioconfig /stand/ioconfig.sav
mv /etc/ioconfig /etc/ioconfig.sav
shutdown -r now
4) Do to missing 'ioconfig' file the server will stop at: (IOINTRC:>
5) (IOINTRC:> # /sbin/ioint -c
6) (IOINTRC:> # /sbin/ioinit -f /infile -r
7) auto reboot takes place
Make sure you have two make_tape_recovery tapes verified before doing this.
Support Fatherhood - Stop Family Law
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP