EMC Clarion CX-400 /Event Number 4953/

[Valex@]

Добрый вечер всем!

С недавних пор subj стал писать в лог сообщение каждые 10 минут:

Time Stamp 10/02/06 14:00:18 Event Number 4953
Severity Warning Host emc1
Storage Array N/A SP N/A Device N/A
Description Unable to download file from originator and master, download aborted.

Нет ли у кого рашифровки этого сообщения Event Number 4953 ? Можно на e-mail - valexсобакаmccinetточкаru

Предполагаю, что эту инфу можно получить с www.emc.com, но там требуется регистрация. А subj достался "в наследство", поэтому предоставить требуемую для регистрации инфу я не могу

Заранее спасибо.

[a_shats]

А управлялка штатная от массива есть ? Что она говорит, что в ея логах ?

[Valex@]

Это как раз сообщение из лога программы управления массивом. Navisphere называется.

[CrazyFrog]

Question:   Resolving Navisphere "unable to download file from originator and master" error message
Environment: EMC SW: Navisphere Manager 6.x
Environment: Product: CLARiiON CX-Series
Environment: Product: CLARiiON FC-Series
Problem: Error message is filling up event logs and may be causing a Navisphere performance problem
Problem: (4953) Unable to download file from originator and master, download aborted
Root Cause: Often, this happens when the IP address of the master (or of the system that the domain change was saved to -- the originator) changed while still in the domain.
Fix: Check the IP address of the master. If that is not the issue, try the following steps:

  1. Verify that all the arrays are in the domain.  You can do this by bringing up the Navisphere GUI and verify that all systems are online via the domain status dialog.
  2. Remove the affected array (the one getting the messages) from the domain using the GUI.
  3. Add the array back into the domain.

If the system/domain is in a state where this cannot be performed, go to the setup page of the affected system and remove the node from the domain from there.  Then, add it back in via the GUI.  

Note: When you first go into the GUI, after removing the node using the setup page, the system will still appear in the domain configuration.  You must remove it first and then add it back in.

Fix:
If nothing else works, the only fix is to reset the domain and security. However, this is disruptive and will erase all of the security settings as well as domain settings. Make note of the domain and security setting prior to resetting the domain and security.

[Valex@]

Root Cause: Often, this happens when the IP address of the master (or of the system that the domain change was saved to -- the originator) changed while still in the domain.

Вот именно из-за этого.

CrazyFrog, огромный Вам респект!