<html><body><p><font size="2">What you can do is create network alias to the old IP. Run mmchnode to change hostname/IP for non-quorum nodes first. Make one (or more) of the nodes you just change a quorum node. Change all of the quorum nodes that still on old IPs to non-quorum. Then change IPs on them.</font><br><br><font size="2">Thanks,</font><br><font size="2">Tru.</font><br><br><img width="16" height="16" src="cid:1__=0ABB0B25DFCBC9F58f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for gpfsug-discuss-request---10/11/2017 04:53:49 AM---Send gpfsug-discuss mailing list submissions to gp"><font size="2" color="#424282">gpfsug-discuss-request---10/11/2017 04:53:49 AM---Send gpfsug-discuss mailing list submissions to gpfsug-discuss@spectrumscale.org</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">gpfsug-discuss-request@spectrumscale.org</font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug-discuss@spectrumscale.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">10/11/2017 04:53 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">gpfsug-discuss Digest, Vol 69, Issue 26</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">Send gpfsug-discuss mailing list submissions to<br> gpfsug-discuss@spectrumscale.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </font></tt><tt><font size="2"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=</a></font></tt><tt><font size="2"><br>or, via email, send a message with subject or body 'help' to<br> gpfsug-discuss-request@spectrumscale.org<br><br>You can reach the person managing the list at<br> gpfsug-discuss-owner@spectrumscale.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of gpfsug-discuss digest..."<br><br><br>Today's Topics:<br><br> 1. Changing ip on spectrum scale cluster with every node down<br> and not connected to network. (Andi Rhod Christiansen)<br> 2. Re: Changing ip on spectrum scale cluster with every node<br> down and not connected to network. (Jonathan Buzzard)<br> 3. Re: Changing ip on spectrum scale cluster with every node<br> down and not connected to network. (Andi Rhod Christiansen)<br> 4. Re: Changing ip on spectrum scale cluster with every node<br> down and not connected to network.<br> (Simon Thompson (IT Research Support))<br> 5. Checking a file-system for errors<br> (Simon Thompson (IT Research Support))<br> 6. Re: Changing ip on spectrum scale cluster with every node<br> down and not connected to network. (Jonathan Buzzard)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 11 Oct 2017 07:46:03 +0000<br>From: Andi Rhod Christiansen <arc@b4restore.com><br>To: "gpfsug-discuss@spectrumscale.org"<br> <gpfsug-discuss@spectrumscale.org><br>Subject: [gpfsug-discuss] Changing ip on spectrum scale cluster with<br> every node down and not connected to network.<br>Message-ID:<br> <3e6e1727224143ac9b8488d16f40fcb3@B4RWEX01.internal.b4restore.com><br>Content-Type: text/plain; charset="us-ascii"<br><br>Hi,<br><br>Does anyone know how to change the ips on all the nodes within a cluster when gpfs and interfaces are down?<br>Right now the cluster has been shutdown and all ports disconnected(ports has been shut down on new switch)<br><br>The problem is that when I try to execute any mmchnode command(as the ibm documentation states) the command fails, and that makes sense as the ip on the interface has been changed without the deamon knowing.. But is there a way to do it manually within the configuration files so that the gpfs daemon updates the ips of all nodes within the cluster or does anyone know of a hack around to do it without having network access.<br><br>It is not possible to turn on the switch ports as the cluster has the same ips right now as another cluster on the new switch.<br><br>Hope you understand, relatively new to gpfs/spectrum scale<br><br>Venlig hilsen / Best Regards<br><br>Andi R. Christiansen<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</font></tt><tt><font size="2"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_pipermail_gpfsug-2Ddiscuss_attachments_20171011_820adb01_attachment-2D0001.html&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=NrezaW_ayd5u-bE6ppJ6p3FBluuDTtv6KHqb4TwaGsY&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_pipermail_gpfsug-2Ddiscuss_attachments_20171011_820adb01_attachment-2D0001.html&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=NrezaW_ayd5u-bE6ppJ6p3FBluuDTtv6KHqb4TwaGsY&e=</a></font></tt><tt><font size="2">><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 11 Oct 2017 09:01:47 +0100<br>From: Jonathan Buzzard <jonathan.buzzard@strath.ac.uk><br>To: gpfsug-discuss@spectrumscale.org<br>Subject: Re: [gpfsug-discuss] Changing ip on spectrum scale cluster<br> with every node down and not connected to network.<br>Message-ID: <8b9180bf-0bef-4e42-020b-28a9610012a1@strath.ac.uk><br>Content-Type: text/plain; charset=windows-1252; format=flowed<br><br>On 11/10/17 08:46, Andi Rhod Christiansen wrote:<br><br>[SNIP]<br><br>> It is not possible to turn on the switch ports as the cluster has the <br>> same ips right now as another cluster on the new switch.<br>> <br><br>Er, yes it is. Spin up a new temporary VLAN, drop all the ports for the <br>cluster in the new temporary VLAN and then bring them up. Basically any <br>switch on which you can remotely down the ports is going to support <br>VLAN's. Even the crappy 16 port GbE switch I have at home supports them.<br><br>JAB.<br><br>-- <br>Jonathan A. Buzzard Tel: +44141-5483420<br>HPC System Administrator, ARCHIE-WeSt.<br>University of Strathclyde, John Anderson Building, Glasgow. G4 0NG<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 11 Oct 2017 08:18:01 +0000<br>From: Andi Rhod Christiansen <arc@b4restore.com><br>To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>Subject: Re: [gpfsug-discuss] Changing ip on spectrum scale cluster<br> with every node down and not connected to network.<br>Message-ID:<br> <9fcbdf3fa2df4df5bd25f4e93d2a3e79@B4RWEX01.internal.b4restore.com><br>Content-Type: text/plain; charset="us-ascii"<br><br>Hi Jonathan,<br><br>Yes I thought about that but the system is located at a customer site and they are not willing to do that, unfortunately.<br><br>That's why I was hoping there was a way around it<br><br>Andi R. Christiansen<br><br> <br>-----Original Message-----<br>From: gpfsug-discuss-bounces@spectrumscale.org [</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a></font></tt><tt><font size="2">] On Behalf Of Jonathan Buzzard<br>Sent: 11. oktober 2017 10:02<br>To: gpfsug-discuss@spectrumscale.org<br>Subject: Re: [gpfsug-discuss] Changing ip on spectrum scale cluster with every node down and not connected to network.<br><br>On 11/10/17 08:46, Andi Rhod Christiansen wrote:<br><br>[SNIP]<br><br>> It is not possible to turn on the switch ports as the cluster has the <br>> same ips right now as another cluster on the new switch.<br>> <br><br>Er, yes it is. Spin up a new temporary VLAN, drop all the ports for the cluster in the new temporary VLAN and then bring them up. Basically any switch on which you can remotely down the ports is going to support VLAN's. Even the crappy 16 port GbE switch I have at home supports them.<br><br>JAB.<br><br>-- <br>Jonathan A. Buzzard Tel: +44141-5483420<br>HPC System Administrator, ARCHIE-WeSt.<br>University of Strathclyde, John Anderson Building, Glasgow. G4 0NG _______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=</a></font></tt><tt><font size="2"><br><br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 11 Oct 2017 08:32:37 +0000<br>From: "Simon Thompson (IT Research Support)" <S.J.Thompson@bham.ac.uk><br>To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>Subject: Re: [gpfsug-discuss] Changing ip on spectrum scale cluster<br> with every node down and not connected to network.<br>Message-ID: <D60392F9.62536%s.j.thompson@bham.ac.uk><br>Content-Type: text/plain; charset="us-ascii"<br><br>I think you really want a PMR for this. There are some files you could potentially edit and copy around, but given its cluster configuration, I wouldn't be doing this on a cluster I cared about with explicit instruction from IBM support.<br><br>So I suggest log a ticket with IBM.<br><br>Simon<br><br>From: <gpfsug-discuss-bounces@spectrumscale.org<</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a></font></tt><tt><font size="2">>> on behalf of "arc@b4restore.com<</font></tt><tt><font size="2"><a href="mailto:arc@b4restore.com">mailto:arc@b4restore.com</a></font></tt><tt><font size="2">>" <arc@b4restore.com<</font></tt><tt><font size="2"><a href="mailto:arc@b4restore.com">mailto:arc@b4restore.com</a></font></tt><tt><font size="2">>><br>Reply-To: "gpfsug-discuss@spectrumscale.org<</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a></font></tt><tt><font size="2">>" <gpfsug-discuss@spectrumscale.org<</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a></font></tt><tt><font size="2">>><br>Date: Wednesday, 11 October 2017 at 08:46<br>To: "gpfsug-discuss@spectrumscale.org<</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a></font></tt><tt><font size="2">>" <gpfsug-discuss@spectrumscale.org<</font></tt><tt><font size="2"><a href="mailto:gpfsug-discuss@spectrumscale.org">mailto:gpfsug-discuss@spectrumscale.org</a></font></tt><tt><font size="2">>><br>Subject: [gpfsug-discuss] Changing ip on spectrum scale cluster with every node down and not connected to network.<br><br>Hi,<br><br>Does anyone know how to change the ips on all the nodes within a cluster when gpfs and interfaces are down?<br>Right now the cluster has been shutdown and all ports disconnected(ports has been shut down on new switch)<br><br>The problem is that when I try to execute any mmchnode command(as the ibm documentation states) the command fails, and that makes sense as the ip on the interface has been changed without the deamon knowing.. But is there a way to do it manually within the configuration files so that the gpfs daemon updates the ips of all nodes within the cluster or does anyone know of a hack around to do it without having network access.<br><br>It is not possible to turn on the switch ports as the cluster has the same ips right now as another cluster on the new switch.<br><br>Hope you understand, relatively new to gpfs/spectrum scale<br><br>Venlig hilsen / Best Regards<br><br>Andi R. Christiansen<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</font></tt><tt><font size="2"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_pipermail_gpfsug-2Ddiscuss_attachments_20171011_cd962e6b_attachment-2D0001.html&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=Iy6NQR-GJD1Hkc0A0C96Jkesrs6h-6HpOnnw3MOQmi4&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_pipermail_gpfsug-2Ddiscuss_attachments_20171011_cd962e6b_attachment-2D0001.html&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=Iy6NQR-GJD1Hkc0A0C96Jkesrs6h-6HpOnnw3MOQmi4&e=</a></font></tt><tt><font size="2">><br><br>------------------------------<br><br>Message: 5<br>Date: Wed, 11 Oct 2017 08:46:46 +0000<br>From: "Simon Thompson (IT Research Support)" <S.J.Thompson@bham.ac.uk><br>To: "gpfsug-discuss@spectrumscale.org"<br> <gpfsug-discuss@spectrumscale.org><br>Subject: [gpfsug-discuss] Checking a file-system for errors<br>Message-ID: <D6039904.6256F%s.j.thompson@bham.ac.uk><br>Content-Type: text/plain; charset="us-ascii"<br><br>I'm just wondering if anyone could share any views on checking a<br>file-system for errors.<br><br>For example, we could use mmfsck in online and offline mode. Does online<br>mode detect errors (but not fix) things that would be found in offline<br>mode?<br><br>And then were does mmrestripefs -c fit into this?<br><br>"-c<br> Scans the file system and compares replicas of<br> metadata and data for conflicts. When conflicts<br> are found, the -c option attempts to fix<br> the replicas.<br>"<br><br>Which sorta sounds like fix things in the file-system, so how does that<br>intersect (if at all) with mmfsck?<br><br>Thanks<br><br>Simon<br><br><br><br>------------------------------<br><br>Message: 6<br>Date: Wed, 11 Oct 2017 09:53:34 +0100<br>From: Jonathan Buzzard <jonathan.buzzard@strath.ac.uk><br>To: gpfsug-discuss@spectrumscale.org<br>Subject: Re: [gpfsug-discuss] Changing ip on spectrum scale cluster<br> with every node down and not connected to network.<br>Message-ID: <1507712014.9906.5.camel@strath.ac.uk><br>Content-Type: text/plain; charset="UTF-8"<br><br>On Wed, 2017-10-11 at 08:18 +0000, Andi Rhod Christiansen wrote:<br>> Hi Jonathan,<br>> <br>> Yes I thought about that but the system is located at a customer site<br>> and they are not willing to do that, unfortunately.<br>> <br>> That's why I was hoping there was a way around it<br>> <br><br>I would go back to them saying it's either a temporary VLAN, we have to<br>down the other cluster to make the change, or re-cable it to a new<br>unconnected switch. If the customer continues to be completely<br>unreasonable then it's their lookout.<br><br>JAB.<br><br>-- <br>Jonathan A. Buzzard Tel: +44141-5483420<br>HPC System Administrator, ARCHIE-WeSt.<br>University of Strathclyde, John Anderson Building, Glasgow. G4 0NG<br><br><br><br>------------------------------<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HQmkdQWQHoc1Nu6Mg_g8NVugim3OiUUy5n0QgLQcbkM&m=3xds8LVU2TdfiaqkM91LA06caiYHJleBqSwOZ6ff81M&s=21OH1KjxVbfDBz9Kdr0USitreLsyXEbP9rHC7Vxmhw0&e=</a></font></tt><tt><font size="2"><br><br><br>End of gpfsug-discuss Digest, Vol 69, Issue 26<br>**********************************************<br><br></font></tt><br><br><BR>
</body></html>