erikgantar

updated

17 years ago

0

2254

November 16th, 2009 01:00

Event 2003 has occurred on storage system

I receive this message in my email every 2 min. Hosts are vsphere esxi and esx 4.0

Event 2003 has occurred on storage system FCXXXXXXXXXXXXXX for device N/A at 11/16/09 09:24:10 The event description is: The storage system received too many events in this poll cycle to display here. This event does not necessarily indicate a problem.

  • kelleg

    6 Operator

    •

    4537 Posts

    411

    0

    Posted November 17th, 2009 08:00

    You probaby should contact VMware to see if they can help.

    glen

  • kelleg

    6 Operator

    •

    4537 Posts

    411

    0

    Posted November 16th, 2009 10:00

    I'll guess that the array is very busy and at each poll cycle it can not capture all events in the required time. Check on the array to see if there are any faults listed in the Event Log - right click on SPA and select View Events. If you do not see any faults, then this just means the array is very busy.

    glen

  • 411

    0

    Posted November 16th, 2009 22:00

    The Event Log is empty. I think that is something wrong with vsphere. We even move from esx to esxi and from boot from SAN to boot localy from USB and from local storage but we still have the same problems. The problem is when this messegas start the VM become very, very slow.
  • 411

    0

    Posted November 18th, 2009 06:00

    Actualy we have AX4-5F an only NAVISPHERE express
  • MikeCypcar

    16 Posts

    411

    0

    Posted November 18th, 2009 06:00

    Did you check the connectivity settings.  How did you register them on the CX?  EMC99467 states:

    For VMware native failover, failovermode settings are as follows:

    •

    CX and CX3 series arrays: failovermode MUST be set to 1

    •

    CX4 arrays operating with FLARE revisions prior to 04.28.000.5.704: failovermode MUST

    be set to 1

    •

    CX4 arrays operating with FLARE 04.28.000.5.704 or later:

    - ESX 2.x or 3.x: Failovermode MUST be set to 1

    - ESX 4.0 or above:

     

    Failovermode is recommended to be set to 4 for ALUA behavior with

    ESX Fixed failover policy, or

     

    Failovermode may be set to 1 for active/passive behavior with ESX MRU

    failover policy