ECS: OBS: xDoctor: RAP073: Rilevato errore di connessione dello switch

Riepilogo: Questa Knowledge Base spiega come gestire l'avviso Errore di connessione dello switch rilevato.

Questo articolo si applica a Questo articolo non si applica a Questo articolo non è legato a un prodotto specifico. Non tutte le versioni del prodotto sono identificate in questo articolo.

Sintomi

xDoctor riporta il seguente codice sintomo 2041:
Timestamp = 2019-03-18_084014
Category = Environment
Source = Switch
Severity = ERROR
Message = Switch Connection Failure detected 
Extra = {'turtle.rack': {'Traceback (most recent call last):\n File "
RAP = /usr/local/xdoctor/pacemaker/switch.py"
Solution = PASSWORD'
Pacemaker switch.py segnala:
# sudo /usr/local/xdoctor/pacemaker/switch.py
<node data="True" name="169.254.1.1">
<switch name="turtle.rack">
    <error msg="Traceback (most recent call last):  File &quot;/usr/local/xdoctor/pacemaker/switch.py&quot;, line 265, in collect    
swt = xSwitch.switch(ip, user, password=base64.b64decode(self.env[&apos;PASSWORD&apos;]), sshKey=None, sshOption=sshOption, verbose=self.debug, 
askPass=True, timeout=60, debug=self.debug)  File &quot;/usr/local/xdoctor/lib/xdoctor/switch.py&quot;, line 103, in __init__    
self.open()  File &quot;/usr/local/xdoctor/lib/xdoctor/switch.py&quot;, line 151, in open    raise Exception(&quot;invalid password max 
retries&quot;)Exception: invalid password max retries;"/>
  </switch>

Causa

È probabile che la password impostata per xDoctor non corrisponda alla password dello switch interessato.

Risoluzione

Errore di connessione: Automazione NUOVO!

 

IMPORTANTE. È stata rilasciata una nuova funzionalità in xDoctor 4-8.104.0 e versioni successive. Questa knowledge base (KB) è ora automatizzata con Service Console per tentare rapidamente di controllare le connessioni degli switch. Lo script rileva la password, gli switch dei clienti, i problemi di configurazione in xDoctor e risolve i problemi noti delle chiavi ssh dovuti alla sostituzione degli switch, fornisce un riepilogo dettagliato dei risultati e indica se ha risolto eventuali problemi con le chiavi ssh. Questa soluzione funziona su switch di seconda e terza generazione per il rilevamento e la risoluzione delle chiavi SSH.

Per ulteriori informazioni sulla configurazione delle automazioni, procedi: ECS: ObjectScale: Come eseguire gli script di automazione della KB (pilota automatico)  

 

Per trovare il nodo master del rack:

Comando: 

ssh master.rack

 

Per trovare l'IP NAN, è possibile utilizzare l'IP identificato nell'avviso o da getrackinfo:

Comando:

admin@ecsnode1:~> getrackinfo
Node private      Node              Public                                BMC
Ip Address        Id       Status   Mac                 Ip Address        Mac                 Ip Address        Private.4(NAN)    Node Name
===============   ======   ======   =================   ===============   =================   ===============   ===============   =========
192.168.219.1     1        MA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.101   169.254.1.1       provo-red
192.168.219.2     2        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.102   169.254.1.2       sandy-red
192.168.219.3     3        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.103   169.254.1.3       orem-red
192.168.219.4     4        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.104   169.254.1.4       ogden-red
192.168.219.5     5        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.105   169.254.1.5       layton-red
192.168.219.6     6        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.106   169.254.1.6       logan-red
192.168.219.7     7        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.107   169.254.1.7       lehi-red
192.168.219.8     8        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.108   169.254.1.8       murray-red

 

  1. Eseguire il comando di automazione dal nodo master con xDoctor 4-8.104.0 e versioni successive.
Comando: 
Nota: --target-rack è supportato per questa azione. 
# sudo xdoctor autopilot --kb 39838 --target-rack <rack_colour>
Esempio:
admin@ecsnode1:~>  sudo xdoctor autopilot --kb 39838 --target-rack red
Checking for existing screen sessions...
Starting screen session 'autopilot_kb_39838_20250626_112318'...
Screen session 'autopilot_kb_39838_20250626_112318' started successfully.
Attaching to screen session 'autopilot_kb_39838_20250626_112318'...

Using /etc/ansible/ansible.cfg as config file
VERSION: 3.0
Playbook tasks: 47
Role tasks: 97
Total tasks: 144 across 1 host(s)

PLAY [red] ******************************************************************************************************************************************************************
Detected 8 hosts for this play.

TASK [target_check : set_fact] **********************************************************************************************************************************************
ok: [169.254.1.1 -> localhost] => {"ansible_facts": {"allowed_targets": "Please use: --target-rack", "target_node_check": false, "target_rack_check": true, "target_vdc_check": false}, "changed": false}

TASK [target_check : context] ***********************************************************************************************************************************************
skipping: [169.254.1.1] => {"changed": false, "false_condition": "node_script == false and target_node_check == true or rack_script == false and target_rack_check == true or vdc_script == false and target_vdc_check == true", "skip_reason": "Conditional result was False"}

...truncated
 
  1. Riepilogo della revisione:

Esempio: 

TASK [Print all summaries] **************************************************************************************************************************************************
ok: [169.254.1.1] => {
    "msg": [
        "*******************************************************************************",
        "Switch xDoctor 'RAP073' password and SSH summary:",
        "*******************************************************************************",
        "Validated Frontend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838.",
        "Validated Backend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838.",
        "Validated Backend management connections: PASS: Management connections are up and connected to the frontend switches.",
        "*******************************************************************************",
        "Validated ssh keys to switch(es): PASS: All ssh keys are valid and nothing was corrected.",
        "Validated xDoctor alert: PASS: Alert RAP073 was not present in xDoctor.",
        "*******************************************************************************"
    ]
}

TASK [Set fact for context] *************************************************************************************************************************************************
ok: [169.254.1.1 -> localhost] => {"ansible_facts": {"context": " Validated Frontend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838., Validated Backend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838."}, "changed": false}

TASK [Fail if validation fails] *********************************************************************************************************************************************
fatal: [169.254.1.1]: FAILED! => {"changed": false, "msg": "Review the summary above for recommendations."}

NO MORE HOSTS LEFT **********************************************************************************************************************************************************

PLAY RECAP ******************************************************************************************************************************************************************
169.254.1.1                : ok=65   changed=13   unreachable=0    failed=1    skipped=73   rescued=0    ignored=1
169.254.1.2                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.3                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.4                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.5                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.6                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.7                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
169.254.1.8                : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

=============================================================================================================================================================================
Status: FAIL
Time Elapsed: 0h 1m 25s
Debug log: /tmp/autopilot/log/autopilot_39838_20250626_113201.log
Message:  Validated Frontend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838., Validated Backend switch(es): FAIL: The passwords for the Dell managed switch(es) are incorrect and need to be configured in the xDoctor settings according to KB 39838.
=============================================================================================================================================================================

 

  1. Aggiornare la password xDoctor: 
admin@ecsnode7:~> sudo xdoctor -c --expert

xDoctor Configuration Menu
--------------------------
[Expert Mode Active]

(1)  Overview
(2)  Scheduling
(3)  Archiving
(5)  Repository



(9)  Miscellaneous

(0)  Exit

Please make a choice: 9

xDoctor Miscellaneous
---------------------


(3)  Switches
(4)  Remove Hardware Alerting Timestamp

(0)  Main menu

Please make a choice: 3

xDoctor Switch Settings
---------------------
Enable Switch Analysis?  [Yes]:
Switches [hare,rabbit,fox,hound]:
Username [admin]:
Password [*****]:

[New Switch Settings]
Enabled = Yes
Switches = hare,rabbit,fox,hound
Username = admin
Password = *****

> Issue new settings?  [No]: yes
2024-11-20 16:03:53,702: xDoctor_4.8-100.0 - INFO    : Settings saved and distributed ...

xDoctor Miscellaneous
---------------------


(3)  Switches
(4)  Remove Hardware Alerting Timestamp

(0)  Main menu

 

Automazione della KB di base: 
ECS: xDoctor: RAP073: Rilevato errore di connessione dello switch

Un ulteriore consolidamento della KB in questa automazione:
ECS: xDoctor segnala un errore di connessione dello switch a causa di una chiave RSA in known_hosts

Prodotti interessati

Elastic Cloud Storage

Prodotti

Elastic Cloud Storage
Proprietà dell'articolo
Numero articolo: 000039838
Tipo di articolo: Solution
Ultima modifica: 02 apr 2026
Versione:  10
Trova risposta alle tue domande dagli altri utenti Dell
Support Services
Verifica che il dispositivo sia coperto dai Servizi di supporto.