From 58e0c076d8b51819a30ed903523d7b9ea28bcd36 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Jul 31 2025 09:03:54 +0000 Subject: Update hostname of hop-box for hypervisors Fixes: https://pagure.io/fedora-infrastructure/issue/12685 --- diff --git a/modules/sysadmin_guide/pages/hardware_troubleshooting_power.adoc b/modules/sysadmin_guide/pages/hardware_troubleshooting_power.adoc index 2b2d522..aa0a91f 100644 --- a/modules/sysadmin_guide/pages/hardware_troubleshooting_power.adoc +++ b/modules/sysadmin_guide/pages/hardware_troubleshooting_power.adoc @@ -6,7 +6,7 @@ This SOP shows some of the steps required to troubleshoot and diagnose a power i Symptoms: - This server is not responding at all, and will not power on. -- To get to mgmt of RDU2-CC devices it’s a bit trickier than RDU3. We have a private management vlan there, but it’s only reachable via cloud-noc-os01.rdu-cc.fedoraproject.org. I usually use the ‘sshuttle’ package/command/app to transparently forward my traffic to devices on that network. That looks something like: `sshuttle 172.23.1.0/24 -r cloud-noc-os01.rdu-cc.fedoraproject.org` +- To get to mgmt of RDU2-CC devices it’s a bit trickier than RDU3. We have a private management vlan there, but it’s only reachable via noc-cc01.rdu-cc.fedoraproject.org. I usually use the ‘sshuttle’ package/command/app to transparently forward my traffic to devices on that network. That looks something like: `sshuttle 172.23.1.0/24 -r noc-cc01.rdu-cc.fedoraproject.org` - The devices are all in the 172.23.1 network. There’s a list of them in `ansible-private/docs/rdu-networks.txt` but this host is: `172.23.1.105`. - In the Bitwarden Vault, the management password can be obtained. - Logs show issues with voltages not being in the correct range. @@ -33,7 +33,7 @@ Purpose:: === Troubleshooting Steps .Connect to the management VLAN for the RDU2-CC network: -This is only required because this server is not in RDU3 datacenter. Use sshuttle to make a connection to the 172.23.1.0/24 (from your laptop directly, not from the batcave01 to the management network). `sshuttle 172.23.1.0/24 -r cloud-noc-os01.rdu-cc.fedoraproject.org` +This is only required because this server is not in RDU3 datacenter. Use sshuttle to make a connection to the 172.23.1.0/24 (from your laptop directly, not from the batcave01 to the management network). `sshuttle 172.23.1.0/24 -r noc-cc01.rdu-cc.fedoraproject.org` .SSH to the batcave01 and retrieve the ip address for this machine Ssh to the batcave01, access the ansible-private repo and read the IP address for this machine from the `docs/rdu-networks.txt`