BMYUP2109
Failed to change the password of ISFUSER on the switch.
Severity
Warning
User response
Do the following steps to diagnose and report the problem:
- Run the following command to get the switch IP
address.
Example output:oc get switch mgmt1-rackag5 -o yaml | grep switchIpadress
switchIpadress: fd8c:215d:178e:c0de:e69d:73ff:fe69:b400
- Check connectivity to the switch from one of the compute node using the following steps:
- Run the following command to get the node details.
Example output:oc get node
NAME STATUS ROLES AGE VERSION compute-1-ru27.rackag5.mydomain.com Ready worker 5d14h v1.25.14+bcb9a60 compute-1-ru6.rackag5.mydomain.com Ready,SchedulingDisabled worker 9d v1.25.14+bcb9a60 compute-1-ru7.rackag5.mydomain.com Ready,SchedulingDisabled worker 9d v1.25.14+bcb9a60 control-1-ru2.rackag5.mydomain.com Ready control-plane,master 9d v1.25.14+bcb9a60 control-1-ru3.rackag5.mydomain.com Ready control-plane,master 9d v1.25.14+bcb9a60 control-1-ru4.rackag5.mydomain.com Ready control-plane,master 9d v1.25.14+bcb9a60
- Run the following command to log in to
node.
Example output:oc debug node/compute-1-ru27.rackag5.mydomain.com
Temporary namespace openshift-debug-svmds is created for debugging node... Starting pod/compute-1-ru27rackag5mydomaincom-debug ... To use host binaries, run `chroot /host` Pod IP: 172.88.55.32 If you don't see a command prompt, try pressing enter. sh-4.4# ping fd8c:215d:178e:c0de:e69d:73ff:fe69:b400 PING fd8c:215d:178e:c0de:e69d:73ff:fe69:b400(fd8c:215d:178e:c0de:e69d:73ff:fe69:b400) 56 data bytes 64 bytes from fd8c:215d:178e:c0de:e69d:73ff:fe69:b400: icmp_seq=1 ttl=64 time=5.48 ms 64 bytes from fd8c:215d:178e:c0de:e69d:73ff:fe69:b400: icmp_seq=2 ttl=64 time=0.464 ms ^C --- fd8c:215d:178e:c0de:e69d:73ff:fe69:b400 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 0.464/2.971/5.478/2.507 ms sh-4.4#
- Run the following command to get the node details.
- If ping to switch IP is not working, then collect Network logs and contact IBM support.
- If ping to switch IP works, then run the following commands to get the default username and
password.
oc get secret mgmt1-rackag5-secret -o yaml | grep defaultUserName oc get secret mgmt1-rackag5-secret -o yaml | grep defaultUserPasswrd
- Decode the username and password obtained from the previous
step.
echo <username/password> | base64 --decode
- Try to SSH from one of the compute node using the default
credentials.
Example output:ssh cumulus@fd8c:215d:178e:c0de:e69d:73ff:fe69:b400
The authenticity of host 'fd8c:215d:178e:c0de:e69d:73ff:fe69:b400 (fd8c:215d:178e:c0de:e69d:73ff:fe69:b400)' can't be established. ECDSA key fingerprint is SHA256:n9XPEXgyP8A5fgKBCFB4NVwnwwtBYfNnoS5mIu27L7c. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'fd8c:215d:178e:c0de:e69d:73ff:fe69:b400' (ECDSA) to the list of known hosts. cumulus@fd8c:215d:178e:c0de:e69d:73ff:fe69:b400's password: Linux mgmt1-rackag5 4.19.0-cl-1-iproc #1 SMP PREEMPT Cumulus 4.19.149-1+cl4.3u1 (2021-01-28) armv7l Welcome to NVIDIA Cumulus (R) Linux (R) For support and online technical documentation, visit http://www.cumulusnetworks.com/support The registered trademark Linux (R) is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis. Last login: Mon Jan 29 04:11:14 2024 from fd8c:215d:178e:c0de:d8a0:53d6:6eb6:6a55 ***************************************************************** Please send these support file(s) to support@cumulusnetworks.com: /var/support/cl_support_mgmt1-rackag5_20230721_092859.txz /var/support/cl_support_mgmt1-rackag5_20230821_041846.txz /var/support/cl_support_mgmt1-rackag5_20230822_151434.txz /var/support/cl_support_mgmt1-rackag5_20230910_040832.txz /var/support/cl_support_mgmt1-rackag5_20230911_061727.txz /var/support/cl_support_mgmt1-rackag5_20231026_072515.txz ***************************************************************** cumulus@mgmt1-rackag5:mgmt:~$
- If the credentials are not working, then collect Network logs and contact IBM support.