I'm installing ESXi on M620 blades, with 2 physical NIC's being partitioned to 4 virtual NIC's each for a total of 8 NIC's.  ESXi is binding the first 2 NIC's to management.  When trying to ping the management interface only 5-10% of the packets reply.  After unbinding the first NIC, and leaving only the 2nd NIC for management, there were no problems with packet loss.  I then tried binding random NIC's from 2-8 and no issues with any of them.  The only problem is when using the first NIC, either by itself, or with another set of ports; running persistent pings will drop many packets.  This issue has been reproducible on multiple M620 blades.  Is there anything special about the first NIC port when you using partitioning?

Does anyone know how i can completely turn off the servers 2008 in CMD?

Hi

I’m using RACADM to remotely power on dell server. Unfortunately, the RACADM commands are not accepted by the DRAC anymore, as the default Dell certificate is expired.

Have few question,

1. how can we regenerate the certificate and upload it?
2. how can we move Https to http?

Thank You

Manoj

Hi all,

I want to buy a poweredge r320 to virtualize multiple windows 7 machines over ESXi 5.5. My question is about the resolution because i didn't see any information about video or graphics card for this server. Will my guest OS look ok or do i have to buy a video card apart form the server itself? If so which card is recommended?

My best regards

I am a Noob so not sure if this question is stupid or the concept is ahead of its time. Bee experimenting with with servers and i was wondering if its possible to virtulize multiple physical servers as one. As in a have need for multiple servers in my work space, but when one goes down we have to hurry up and make a new server for our business applications to work. We have been looking into virtulization and are currently testing running VM,s on our test server, but this will not help if my virtual server itself goes down. Is there a way i can combine multiple physical machines into one via virtualization and then make Virtual servers within that, so that if one machine goes down others can compensate. Basically a Raid 5 Configuration but for machines rather than hard disk.

Hi,

I'm facing the problem that my 9G bladecenter sees 1200W PSU's when there are 2100W versions installed.

How does this come ?

I have installed Open Manage Essentials and cannot see anything on the chassis, only the DRAC is seen.

I hope this can be solved.

Cheers,

Matt

Hey all,

I just received our poweredge vrtx system with two m520 blade's that are going to be utilized as virtual servers, everything is setup and good to go as far as the blade's and storage goes, however i am trying to get the networking side configured properly,  and from what they say you cannot have your OOB on the same subnet as your servers will be on,  problem is we are a flat network running the /24 subnet, i would hate having to go through the headache of resubnetting just to get my virtual system up.

My questions is can we totally bypass the OOB not even plug it in and setup a LAG for the 8 port 1gbe switch to our distribution switch,  we are a one location shop so if i could just bring up the CMC on the server and manage the configuration from there,  would that be a viable solution than trying to resubnet my network. 

Unlike Laptop DVD Drives the T710s have DVD Drives that only work while the Server is floor mounted.  Rack mounting turns the DVD Drive by 90 degrees on its side.  If one is dumb enough to try and put a DVD in the drive, the DVD just falls out. I am trying to find a DVD Drive for these servers that will work in any orientation.  Any help will be most appreciated. Thanks.

After installing the second processor intel xeon my dell start to work not proporly although the machine is not over heat the vents start working at full capacity. This problem happens often.

bios version 2.7

We try to find out the temp the machine is workin but it seems the machine dosent count with this type os sensor.

I have DELL PE 2800 server its graphics card is faulty i want to install external graphics card what i should do for it. 

Additionally i have one SCSI empty drive fixed with server and no OS is loaded what is possible solution in this specific condition.

I have try to fix external card but not able to access bios to install OS. Waiting for reply thank you.

Hi Guys,

I've been hitting my head of the wall from the past few weeks dealing with dell support, so I figured I'd through it out to the community to see if there's some wise person out there, that can help.

Basically I have 5 servers on customer sites, carbon copies of each other. (Specs Below)

T620

32GB RAM

E5-2620v2 - Hex with HT

Raid 5 H710 512 Cache

4x 300GB SAS 15K

iDRAC7 Express

Server 2012 R2 Pre-installed by dell.

Each server runs two VM's DC/DB IIS.

No A/V on host, iscsi target for backup connected in the VM.

Basically the problem is that the server starts to crawl at a horrible speed, pinging between the VMs goes to 100+ms. Even with the VM's turned off the server(host) still crawls. Opening Hyper-v manager 30+ seconds.

Here's the "funny part" rebooting the server doesn't resolve the issue but turn the server (host) off for 30 seconds and boom its all good again.

Could be fine for a week or a month after the reboot, I'm thinking it might be something to do with a cache on the RAID card with queues filling up or something like that.

Any Ideas?

Hello,

My Dell Poweredge 1850 hangs during POST.  It displays a message saying: Memory/battery problems were detected. The adapter has recovered, but cached data was lost. Press any key to continue.

I press a key and the Server 2003 screen appears and starts to load but then the screen goes dark.  It does not continue to boot.

I have read about replacing a battery and also trying CTRL M but I am not sure what to do.  Could it be a battery and if so, is it the CMOS battery or is there another?

Any assistance is appreciated.

Greg

Greetings,

Tried to install Debian OS in my first R220. Boot failed in acpi. The BIOS version of my R220 is 1.1.4.

If I hack my boot media to add "acpi=off" in the kernel boot option then it boots successfully.

If I boot the blade with CentOS it boots successfully too. So problem is only with Debian and perhaps its version of acpid.

Questions:

• Is there a BIOS setting which will allow me to boot Debian without adding "acpi=off" to kernel boot option?
• Will updating BIOS from 1.1.4 to 1.2.1 fix this problem?

Thanks for help.

Hi there,

We've neglected to upgrade our PowerEdge R910's BIOS since we bought them 3-4 years ago, so we are currently running on 1.1.7 - for the past 2-3 days, I have trying to upgrade the BIOS to 2.10 (and below) but failing miserably.

I have updated the iDrac firmware to 1.98 (Build 08) and Lifecycle Controller Firmware to 1.6.0.73, when I go into LC Platform Update, select FTP, I get the available list and the only component which needs to be updated is the BIOS, everything else has successfully updated fine.  When I select BIOS update, it starts to download the file and then apply it but an error mismatch notification is displayed and server reboots back into LC.

I have gone to downloads.dell.com site and downloaded previous BIOS updates ie R910010202C.exe, R910-020500C.exe and the latest R910-021000.exe, copied one of them onto a USB stick and tried to update the BIOS within LC Platform Update via USB - it reads the USB and then comes up with a Dell Non-Authorised message (which is what I was getting via the FTP update before updating iDrac & LC to a newer version).

We are running ESXi 5.5U2 on the units and I'm at loss now on how I can bring the BIOS update to date.

Any help/suggestions is much appreciated.

hi,

sorry if i am posting it in wrong place, if so please redirect me to appropriate place to ask this question.

and sorry if my question sounds unprofessional :)

so, i have big experience in assembling and troubleshooting desktop computers, but i have never worked with server type hardware.

lately i purchased motherboard N051F and thought that as with desktop motherboards i would simply connect two power button pins and it would power on. but as i discovered it has completely different system of such pins. i have only motherboard, cpu and ram. do i need some other parts/cables to power it on and receive some output on display. also i would like to know if it has integrated gpu or do i have to insert one?

Hi All,

we have two servers both used for backup .

one of them is poweredge 2900 and I want to find out the following :

1.Can I get a software which can help me check and configure the raid on windows rather than bios ?

I think our raid version is 5.1 .

2. I am trying to update the firmware and bios but looking at dell website there are tons and tons of firmware so I am not sure which ones is applicable to our server even though I am looking at poweredge 2900 with our service tag number.

for instance there is firmware upgrade for tape tl2000 which is confusing me as that needs to be under the tape drive support so why am I seeing it under the power edge ? how can the server update the firmware of the library ? 

I used the suu luncher but that made me even more confuse as there is a list iof things to update most of which do not exist on our server such as sas controller etc ?

I appreciate your help on advising how I can go about installing these firmware

My servers windows 2008r2 Taskbar got disable. When i click on taskbar and properties it said Restrictions, This operation has been cancelled due to restrictions in effect on this computer. please contact your system administrator, even though i am the administrator.

Can someone help me to turn it back on?

One of my clients has a Dell PowerEdge 840 that worked yesterday but does not today. When it is plugged in, the fan starts up on high and it starts to boot even without pressing the power button. It has the normal blue light on the front but also has the no memory modules detected diagnostic code on the front. I have adjusted the memory, rearranged the DIMMS, and taken some of them out but still nothing. Also, I have taken all the components off of the motherboard except for the processor, but it still does the same thing. Further, I set the jumper to clear the NVRAM but still nothing. Any more ideas?

we have a warning light with one blade server and we exported the logs (cmc and cel) as follow :

cmc log :

CMC-2D7L45J Oct 30 13:25:40 Login success from 172.18.37.188 (username=root, type=GUI, sid=15121)
CMC-2D7L45J Oct 30 13:25:27 GUI login failed (username=CML, ip=172.18.37.188, reason=User does not exist)
CMC-2D7L45J Oct 27 08:43:46 Chassis health is Non-critical
CMC-2D7L45J Aug 28 11:43:09 session close succeeds: sid=35562
CMC-2D7L45J Aug 28 11:27:24 Login success from 172.18.85.57 (username=root, type=GUI, sid=35562)
CMC-2D7L45J Aug 25 18:08:32 session close succeeds: sid=41269
CMC-2D7L45J Aug 25 18:08:09 root from 172.18.37.48: session timeout sid 8011
CMC-2D7L45J Aug 25 17:37:58 Login success from 172.18.37.48 (username=root, type=GUI, sid=8011)
CMC-2D7L45J Aug 13 14:04:38 Chassis health is Healthy
CMC-2D7L45J Aug 13 14:04:37 System health recovery
CMC-2D7L45J Aug 13 14:02:57 System health failover request RC=80010000
CMC-2D7L45J Aug 13 14:02:57 lost network link failover condition detected
CMC-2D7L45J Aug 13 14:02:44 Chassis health is Critical
CMC-2D7L45J Jul 15 16:30:34 Chassis health is Healthy
CMC-2D7L45J Jul 15 16:30:31 CMC2: firmware versions are same 4.50 A00
CMC-2D7L45J Jun 2 14:27:29 session close succeeds: sid=32391
CMC-2D7L45J Jun 2 14:19:55 Login success from 172.18.37.12 (username=root, type=GUI, sid=32391)
CMC-2D7L45J May 23 00:53:27 Chassis health is Critical
CMC-2D7L45J May 23 00:47:53 Chassis health is Healthy
CMC-2D7L45J May 23 00:47:14 Chassis configuration detected at 221.0 VAC.
CMC-2D7L45J May 23 00:47:06 CMC2: active
CMC-2D7L45J May 23 00:47:06 CMC2: input power up
CMC-2D7L45J May 23 00:47:06 [0:46:32]CMC2: standby CMC2 takes active
CMC-2D7L45J May 23 00:47:06 [0:46:31]CMC2: reset active CMC1
CMC-2D7L45J May 23 00:47:06 [0:46:31]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J May 23 00:46:27 CMC1: firmware versions are same 4.50 A00
CMC-2D7L45J May 23 00:46:26 CMC1: shutdown initiated
CMC-2D7L45J May 23 00:46:26 CMC1: wait for to be reset
CMC-2D7L45J May 23 00:46:15 CMC1: failover was initiated by mond
CMC-2D7L45J May 23 00:46:15 System health failover request RC=80010000
CMC-2D7L45J May 23 00:41:53 lost network link failover condition detected
CMC-2D7L45J May 23 00:41:17 Chassis health is Healthy
CMC-2D7L45J May 23 00:41:13 Chassis configuration detected at 238.0 VAC.
CMC-2D7L45J May 23 00:41:07 CMC1: active
CMC-2D7L45J May 23 00:41:07 CMC1: input power up
CMC-2D7L45J May 13 09:54:07 root from 172.18.37.12: session timeout sid 22509
CMC-2D7L45J May 13 09:53:13 session close succeeds: sid=41269
CMC-2D7L45J May 13 09:52:42 root from 172.18.37.12: session timeout sid 27843
CMC-2D7L45J May 13 09:23:29 Login success from 172.18.37.12 (username=root, type=GUI, sid=22509)
CMC-2D7L45J May 13 09:06:51 Login success from 172.18.37.12 (username=root, type=GUI, sid=27843)
CMC-2D7L45J May 12 15:03:51 Chassis health is Critical
CMC-2D7L45J May 12 14:58:16 Chassis health is Healthy
CMC-2D7L45J May 12 14:57:38 Chassis configuration detected at 230.0 VAC.
CMC-2D7L45J May 12 14:57:30 CMC2: active
CMC-2D7L45J May 12 14:57:30 CMC2: input power up
CMC-2D7L45J May 12 14:57:30 [14:56:54]CMC2: standby CMC2 takes active
CMC-2D7L45J May 12 14:57:30 [14:56:53]CMC2: reset active CMC1
CMC-2D7L45J May 12 14:57:30 [14:56:53]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J May 12 14:56:50 CMC1: firmware versions are same 4.50 A00
CMC-2D7L45J May 12 14:56:49 CMC1: shutdown initiated
CMC-2D7L45J May 12 14:56:49 CMC1: wait for to be reset
CMC-2D7L45J May 12 14:56:38 CMC1: failover was initiated by mond
CMC-2D7L45J May 12 14:51:19 Chassis configuration detected at 232.0 VAC.
CMC-2D7L45J May 12 14:51:11 CMC1: active
CMC-2D7L45J May 12 14:51:11 CMC1: reset by peer
CMC-2D7L45J May 12 14:51:11 [14:50:37]CMC1: standby CMC1 takes active
CMC-2D7L45J May 12 14:51:11 [14:50:36]CMC1: reset active CMC2
CMC-2D7L45J May 12 14:51:11 [14:50:36]CMC1: active CMC is removed
CMC-2D7L45J May 12 14:43:19 System health failover request RC=80010000
CMC-2D7L45J May 11 18:15:10 Chassis health is Critical
CMC-2D7L45J May 11 18:09:35 Chassis health is Healthy
CMC-2D7L45J May 11 18:08:57 Chassis configuration detected at 229.5 VAC.
CMC-2D7L45J May 11 18:08:49 CMC2: active
CMC-2D7L45J May 11 18:08:49 CMC2: reset by peer
CMC-2D7L45J May 11 18:08:49 [18:8:15]CMC2: standby CMC2 takes active
CMC-2D7L45J May 11 18:08:49 [18:8:14]CMC2: reset active CMC1
CMC-2D7L45J May 11 18:08:49 [18:8:14]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J May 11 18:08:49 [18:7:56]CMC2: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J May 11 18:08:49 [16:19:25]CMC2: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J May 11 18:08:10 CMC1: shutdown initiated
CMC-2D7L45J May 11 18:08:10 CMC1: wait for to be reset
CMC-2D7L45J May 11 18:07:58 CMC1: failover was initiated by mond
CMC-2D7L45J May 11 18:06:58 System health failover request RC=80010000
CMC-2D7L45J May 11 18:06:58 lost network link failover condition detected
CMC-2D7L45J May 11 18:06:44 Chassis health is Critical
CMC-2D7L45J May 8 16:19:28 Chassis health is Healthy
CMC-2D7L45J May 8 16:19:26 CMC1: firmware versions are same 4.50 A00
CMC-2D7L45J May 6 14:08:14 Chassis health is Critical
CMC-2D7L45J May 6 14:02:39 Chassis health is Healthy
CMC-2D7L45J May 6 14:02:02 Chassis configuration detected at 230.0 VAC.
CMC-2D7L45J May 6 14:01:54 CMC1: active
CMC-2D7L45J May 6 14:01:54 CMC1: reset by peer
CMC-2D7L45J May 6 14:01:54 [14:1:18]CMC1: standby CMC1 takes active
CMC-2D7L45J May 6 14:01:54 [14:1:17]CMC1: reset active CMC2
CMC-2D7L45J May 6 14:01:54 [14:1:17]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J May 6 14:01:16 CMC2: firmware versions are same 4.50 A00
CMC-2D7L45J May 6 14:01:13 CMC2: shutdown initiated
CMC-2D7L45J May 6 14:01:13 CMC2: wait for to be reset
CMC-2D7L45J May 6 14:01:02 CMC2: failover was initiated by mond
CMC-2D7L45J May 6 14:01:02 System health failover request RC=80010000
CMC-2D7L45J May 6 13:56:25 Chassis health is Healthy
CMC-2D7L45J May 6 13:55:44 Chassis configuration detected at 229.5 VAC.
CMC-2D7L45J May 6 13:55:37 CMC2: active
CMC-2D7L45J May 6 13:55:37 CMC2: reset by peer
CMC-2D7L45J May 6 13:55:37 [13:55:4]CMC2: standby CMC2 takes active
CMC-2D7L45J May 6 13:55:37 [13:55:3]CMC2: reset active CMC1
CMC-2D7L45J May 6 13:55:37 [13:55:3]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J May 6 13:55:37 [13:53:50]CMC2: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J May 6 13:55:01 CMC1: firmware versions are same 4.50 A00
CMC-2D7L45J May 6 13:54:59 CMC1: shutdown initiated
CMC-2D7L45J May 6 13:54:59 CMC1: wait for to be reset
CMC-2D7L45J May 6 13:54:48 CMC1: failover was initiated by mond
CMC-2D7L45J May 6 13:54:48 System health failover request RC=80010000
CMC-2D7L45J May 6 13:53:53 Chassis health is Healthy
CMC-2D7L45J May 1 16:07:33 session close succeeds: sid=15600
CMC-2D7L45J May 1 16:02:10 iDRAC-7 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-4 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-6 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-5 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-2 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-8 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-1 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 16:02:10 iDRAC-3 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:59:09 iDRAC-8 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-7 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-6 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-5 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-4 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-3 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-2 firmware update initiated
CMC-2D7L45J May 1 15:59:09 iDRAC-1 firmware update initiated
CMC-2D7L45J May 1 15:53:44 Login success from 172.18.37.236 (username=root, type=GUI, sid=15600)
CMC-2D7L45J May 1 15:53:03 session close succeeds: sid=55921
CMC-2D7L45J May 1 15:45:05 iKVM firmware update completed successfully.
CMC-2D7L45J May 1 15:42:45 iKVM firmware update started.
CMC-2D7L45J May 1 15:41:57 iDRAC-6 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:41:56 iDRAC-4 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:41:56 iDRAC-7 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:41:56 iDRAC-8 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:41:56 iDRAC-5 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:38:40 iDRAC-8 firmware update initiated
CMC-2D7L45J May 1 15:38:40 iDRAC-7 firmware update initiated
CMC-2D7L45J May 1 15:38:40 iDRAC-6 firmware update initiated
CMC-2D7L45J May 1 15:38:40 iDRAC-5 firmware update initiated
CMC-2D7L45J May 1 15:38:40 iDRAC-4 firmware update initiated
CMC-2D7L45J May 1 15:35:26 iDRAC-2 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:35:26 iDRAC-3 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:35:26 iDRAC-1 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:33:44 iDRAC-3 firmware update initiated
CMC-2D7L45J May 1 15:33:44 iDRAC-2 firmware update initiated
CMC-2D7L45J May 1 15:33:44 iDRAC-1 firmware update initiated
CMC-2D7L45J May 1 15:12:05 iDRAC-7 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-6 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-4 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-2 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-3 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-5 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:05 iDRAC-8 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:12:04 iDRAC-1 firmware update aborted: Corrupt Image
CMC-2D7L45J May 1 15:07:08 iDRAC-8 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-7 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-6 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-5 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-4 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-3 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-2 firmware update initiated
CMC-2D7L45J May 1 15:07:08 iDRAC-1 firmware update initiated
CMC-2D7L45J May 1 15:03:25 Chassis health is Critical
CMC-2D7L45J May 1 15:02:49 iKVM firmware update failed. Checksum error.
CMC-2D7L45J May 1 15:02:33 iKVM firmware update started.
CMC-2D7L45J May 1 15:01:57 Login success from 172.18.37.236 (username=root, type=GUI, sid=55921)
CMC-2D7L45J May 1 15:01:21 GUI login failed (username=root, ip=172.18.37.236, reason=Illegal password length)
CMC-2D7L45J May 1 14:59:16 lost network link failover condition detected
CMC-2D7L45J May 1 14:57:48 Chassis health is Healthy
CMC-2D7L45J May 1 14:57:15 Chassis configuration detected at 230.0 VAC.
CMC-2D7L45J May 1 14:57:08 CMC1: active
CMC-2D7L45J May 1 14:57:08 CMC1: reset by board reset
CMC-2D7L45J May 1 14:57:08 [14:56:29]CMC1: standby CMC1 takes active
CMC-2D7L45J May 1 14:57:08 [14:56:28]CMC1: reset active CMC2
CMC-2D7L45J May 1 14:57:08 [14:56:28]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J May 1 14:56:23 CMC2: shutdown initiated
CMC-2D7L45J May 1 14:56:23 CMC2: wait for to be reset
CMC-2D7L45J May 1 14:56:12 CMC2: failover was initiated by mond
CMC-2D7L45J May 1 14:56:11 System health failover request RC=80010000
CMC-2D7L45J May 1 14:53:52 Chassis health is Healthy
CMC-2D7L45J May 1 14:53:52 CMC1: FWupdate successful to version 4.50 A00
CMC-2D7L45J May 1 14:53:51 CMC2: firmware versions are same 4.50 A00
CMC-2D7L45J May 1 14:53:50 Chassis health is Non-critical
CMC-2D7L45J May 1 14:50:59 Chassis configuration detected at 230.0 VAC.
CMC-2D7L45J May 1 14:50:53 CMC2: active
CMC-2D7L45J May 1 14:50:53 CMC2: reset by board reset
CMC-2D7L45J May 1 14:50:53 [14:50:10]CMC2: standby CMC2 takes active
CMC-2D7L45J May 1 14:50:53 [14:50:9]CMC2: reset active CMC1
CMC-2D7L45J May 1 14:50:53 [14:50:9]CMC2: no heartbeat
CMC-2D7L45J May 1 14:49:59 CMC1: shutdown initiated
CMC-2D7L45J May 1 14:49:54 session close succeeds: sid=17728
CMC-2D7L45J May 1 14:47:28 Chassis health is Non-critical
CMC-2D7L45J May 1 14:47:26 CMC2: FWupdate successful to version 4.50 A00
CMC-2D7L45J May 1 14:47:26 Chassis health is Healthy
CMC-2D7L45J May 1 14:47:25 CMC1: firmware versions are different [4.30 A00:4.50 A00]
CMC-2D7L45J May 1 14:38:04 Failed to update local CMC firmware: Checksum failed.
CMC-2D7L45J May 1 14:36:06 iKVM firmware update failed. Checksum error.
CMC-2D7L45J May 1 14:35:50 iKVM firmware update started.
CMC-2D7L45J May 1 14:24:56 Failed to update local CMC firmware: Checksum failed.
CMC-2D7L45J May 1 14:23:27 Login success from 172.18.37.236 (username=root, type=GUI, sid=17728)
CMC-2D7L45J Apr 28 17:47:21 root from 172.18.37.57: session timeout sid 56297
CMC-2D7L45J Apr 28 16:46:37 Login success from 172.18.37.57 (username=root, type=GUI, sid=56297)
CMC-2D7L45J Apr 27 18:05:29 root from 172.18.37.57: session timeout sid 37876
CMC-2D7L45J Apr 27 17:26:15 Login success from 172.18.37.57 (username=root, type=GUI, sid=37876)
CMC-2D7L45J Apr 24 19:41:13 root from 172.18.37.60: session timeout sid 50893
CMC-2D7L45J Apr 24 19:11:05 Login success from 172.18.37.60 (username=root, type=GUI, sid=50893)
CMC-2D7L45J Apr 24 18:50:22 System health recovery
CMC-2D7L45J Apr 24 18:50:16 System health failover request RC=80010000
CMC-2D7L45J Apr 24 17:52:27 root from 172.18.37.12: session timeout sid 4525
CMC-2D7L45J Apr 24 17:22:06 Login success from 172.18.37.12 (username=root, type=GUI, sid=4525)
CMC-2D7L45J Apr 24 17:17:09 root from 172.18.37.60: session timeout sid 18510
CMC-2D7L45J Apr 24 16:25:06 Login success from 172.18.37.60 (username=root, type=GUI, sid=18510)
CMC-2D7L45J Apr 24 16:14:38 root from 172.18.37.60: session timeout sid 27467
CMC-2D7L45J Apr 24 15:42:38 Login success from 172.18.37.60 (username=root, type=GUI, sid=27467)
CMC-2D7L45J Apr 24 15:42:25 GUI login failed (username=, ip=172.18.37.60, reason=Illegal user name length)
CMC-2D7L45J Apr 24 15:42:22 GUI login failed (username=root, ip=172.18.37.60, reason=Illegal password length)
CMC-2D7L45J Apr 24 15:12:07 root from 172.18.37.60: session timeout sid 44237
CMC-2D7L45J Apr 24 14:35:33 root from 172.18.37.57: session timeout sid 39074
CMC-2D7L45J Apr 24 14:28:55 Login success from 172.18.37.60 (username=root, type=GUI, sid=44237)
CMC-2D7L45J Apr 24 14:05:22 Login success from 172.18.37.57 (username=root, type=GUI, sid=39074)
CMC-2D7L45J Apr 24 14:02:12 session close succeeds: sid=27637
CMC-2D7L45J Apr 24 14:01:48 Login success from 172.18.37.57 (username=root, type=GUI, sid=27637)
CMC-2D7L45J Mar 16 15:24:12 Chassis health is Critical
CMC-2D7L45J Mar 16 15:23:48 Chassis health is Healthy
CMC-2D7L45J Mar 16 15:23:46 CMC1: firmware versions are same 4.30 A00
CMC-2D7L45J Mar 12 15:06:55 Chassis health is Critical
CMC-2D7L45J Feb 3 15:41:34 session close succeeds: sid=64246
CMC-2D7L45J Feb 3 15:40:07 Login success from 172.18.37.12 (username=root, type=GUI, sid=64246)
CMC-2D7L45J Feb 3 15:39:56 GUI login failed (username=ROOT, ip=172.18.37.12, reason=User does not exist)
CMC-2D7L45J Feb 3 15:39:43 GUI login failed (username=root, ip=172.18.37.12, reason=Invalid password )
CMC-2D7L45J Feb 3 14:19:55 root from 10.1.157.200: session timeout sid 62886
CMC-2D7L45J Feb 3 13:57:59 session close succeeds: sid=59550
CMC-2D7L45J Feb 3 13:57:07 Login success from 172.18.37.12 (username=root, type=GUI, sid=59550)
CMC-2D7L45J Feb 3 13:56:56 GUI login failed (username=root, ip=172.18.37.12, reason=Invalid password )
CMC-2D7L45J Feb 3 13:02:31 Login success from 10.1.157.200 (username=root, type=GUI, sid=62886)
CMC-2D7L45J Feb 3 12:52:04 session close succeeds: sid=10518
CMC-2D7L45J Feb 3 12:49:08 Login success from 172.16.161.200 (username=root, type=GUI, sid=10518)
CMC-2D7L45J Feb 3 12:45:16 Chassis health is Healthy
CMC-2D7L45J Feb 3 12:44:28 CMC1: active
CMC-2D7L45J Feb 3 12:44:28 CMC1: reset by peer
CMC-2D7L45J Feb 3 12:44:28 [12:43:56]CMC1: standby CMC1 takes active
CMC-2D7L45J Feb 3 12:44:28 [12:43:55]CMC1: reset active CMC2
CMC-2D7L45J Feb 3 12:44:28 [12:43:55]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J Feb 3 12:44:28 [12:43:14]CMC1: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J Feb 3 12:44:28 [10:30:41]CMC1: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J Feb 3 12:44:28 [10:25:24]CMC1: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J Feb 3 12:43:51 CMC2: shutdown initiated
CMC-2D7L45J Feb 3 12:43:51 CMC2: wait for to be reset
CMC-2D7L45J Feb 3 12:43:40 CMC2: failover was initiated by mond
CMC-2D7L45J Feb 3 12:43:40 System health failover request RC=80010000
CMC-2D7L45J Feb 3 12:43:16 Chassis health is Healthy
CMC-2D7L45J Feb 3 11:20:38 root from 172.18.37.12: session timeout sid 32256
CMC-2D7L45J Feb 3 10:49:59 Login success from 172.18.37.12 (username=root, type=GUI, sid=32256)
CMC-2D7L45J Feb 3 10:32:00 Chassis health is Critical
CMC-2D7L45J Feb 3 10:30:44 Chassis health is Healthy
CMC-2D7L45J Feb 3 10:26:30 Chassis health is Critical
CMC-2D7L45J Feb 3 10:25:28 Chassis health is Healthy
CMC-2D7L45J Feb 3 10:25:26 CMC2: firmware versions are same 4.30 A00
CMC-2D7L45J Feb 3 10:24:56 Chassis health is Critical
CMC-2D7L45J Feb 3 08:13:40 session close succeeds: sid=56009
CMC-2D7L45J Feb 3 08:11:46 Login success from 172.16.130.230 (username=root, type=GUI, sid=56009)
CMC-2D7L45J Feb 2 14:17:31 session close succeeds: sid=34504
CMC-2D7L45J Feb 2 14:17:12 Login success from 172.16.130.230 (username=root, type=GUI, sid=34504)
CMC-2D7L45J Jan 30 11:45:15 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:44:29 CMC2: active
CMC-2D7L45J Jan 30 11:44:29 CMC2: reset by peer
CMC-2D7L45J Jan 30 11:44:29 [11:43:56]CMC2: standby CMC2 takes active
CMC-2D7L45J Jan 30 11:44:29 [11:43:55]CMC2: reset active CMC1
CMC-2D7L45J Jan 30 11:44:29 [11:43:55]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J Jan 30 11:43:52 CMC1: shutdown initiated
CMC-2D7L45J Jan 30 11:43:52 CMC1: wait for to be reset
CMC-2D7L45J Jan 30 11:43:41 CMC1: failover was initiated by mond
CMC-2D7L45J Jan 30 11:43:40 System health failover request RC=80010000
CMC-2D7L45J Jan 30 11:39:11 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:38:25 CMC1: active
CMC-2D7L45J Jan 30 11:38:25 CMC1: reset by peer
CMC-2D7L45J Jan 30 11:38:25 [11:37:53]CMC1: standby CMC1 takes active
CMC-2D7L45J Jan 30 11:38:25 [11:37:52]CMC1: reset active CMC2
CMC-2D7L45J Jan 30 11:38:25 [11:37:52]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J Jan 30 11:37:49 CMC2: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 30 11:37:49 CMC2: shutdown initiated
CMC-2D7L45J Jan 30 11:37:48 CMC2: wait for to be reset
CMC-2D7L45J Jan 30 11:37:37 CMC2: failover was initiated by mond
CMC-2D7L45J Jan 30 11:37:37 System health failover request RC=80010000
CMC-2D7L45J Jan 30 11:33:12 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:32:26 CMC2: active
CMC-2D7L45J Jan 30 11:32:26 CMC2: reset by peer
CMC-2D7L45J Jan 30 11:32:26 [11:31:54]CMC2: standby CMC2 takes active
CMC-2D7L45J Jan 30 11:32:26 [11:31:53]CMC2: reset active CMC1
CMC-2D7L45J Jan 30 11:32:26 [11:31:53]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J Jan 30 11:31:50 CMC1: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 30 11:31:49 CMC1: shutdown initiated
CMC-2D7L45J Jan 30 11:31:49 CMC1: wait for to be reset
CMC-2D7L45J Jan 30 11:31:38 CMC1: failover was initiated by mond
CMC-2D7L45J Jan 30 11:31:37 System health failover request RC=80010000
CMC-2D7L45J Jan 30 11:27:13 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:26:26 CMC1: active
CMC-2D7L45J Jan 30 11:26:26 CMC1: reset by board reset
CMC-2D7L45J Jan 30 11:26:26 [17:25:55]CMC1: standby CMC1 takes active
CMC-2D7L45J Jan 30 11:26:26 [17:25:54]CMC1: reset active CMC2
CMC-2D7L45J Jan 30 11:26:26 [17:25:54]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J Jan 30 11:25:51 CMC2: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 30 11:25:50 CMC2: shutdown initiated
CMC-2D7L45J Jan 30 11:25:50 CMC2: wait for to be reset
CMC-2D7L45J Jan 30 11:25:38 CMC2: failover was initiated by mond
CMC-2D7L45J Jan 30 11:25:38 System health failover request RC=80010000
CMC-2D7L45J Jan 30 11:21:11 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:20:24 CMC2: active
CMC-2D7L45J Jan 30 11:20:24 CMC2: reset by peer
CMC-2D7L45J Jan 30 11:20:24 [11:19:53]CMC2: standby CMC2 takes active
CMC-2D7L45J Jan 30 11:20:24 [11:19:52]CMC2: reset active CMC1
CMC-2D7L45J Jan 30 11:20:24 [11:19:52]CMC2: no heartbeat
CMC-2D7L45J Jan 30 11:17:08 CMC2: shutdown initiated
CMC-2D7L45J Jan 30 11:17:08 CMC2: wait for to be reset
CMC-2D7L45J Jan 30 11:16:57 CMC2: failover was initiated by mond
CMC-2D7L45J Jan 30 11:16:57 System health failover request RC=80010000
CMC-2D7L45J Jan 30 11:16:09 Chassis health is Healthy
CMC-2D7L45J Jan 30 11:16:08 CMC2: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 30 11:15:46 Chassis health is Critical
CMC-2D7L45J Jan 29 16:04:27 root from 10.1.157.200: session timeout sid 34608
CMC-2D7L45J Jan 29 15:36:35 lost network link failover condition detected
CMC-2D7L45J Jan 29 15:33:07 Login success from 10.1.157.200 (username=root, type=GUI, sid=34608)
CMC-2D7L45J Jan 29 15:32:53 Chassis health is Healthy
CMC-2D7L45J Jan 29 15:32:05 CMC2: active
CMC-2D7L45J Jan 29 15:32:05 CMC2: reset by peer
CMC-2D7L45J Jan 29 15:32:05 [15:31:33]CMC2: standby CMC2 takes active
CMC-2D7L45J Jan 29 15:32:05 [15:31:32]CMC2: reset active CMC1
CMC-2D7L45J Jan 29 15:32:05 [15:31:32]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J Jan 29 15:31:30 CMC1: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 29 15:31:30 CMC1: shutdown initiated
CMC-2D7L45J Jan 29 15:31:29 CMC1: wait for to be reset
CMC-2D7L45J Jan 29 15:31:18 CMC1: failover was initiated by mond
CMC-2D7L45J Jan 29 15:31:17 System health failover request RC=80010000
CMC-2D7L45J Jan 29 15:18:08 Chassis health is Healthy
CMC-2D7L45J Jan 29 15:17:21 CMC1: active
CMC-2D7L45J Jan 29 15:17:21 CMC1: reset by peer
CMC-2D7L45J Jan 29 15:17:21 [15:16:49]CMC1: standby CMC1 takes active
CMC-2D7L45J Jan 29 15:17:21 [15:16:48]CMC1: reset active CMC2
CMC-2D7L45J Jan 29 15:17:21 [15:16:48]CMC1: active CMC2 requests standby to go active
CMC-2D7L45J Jan 29 15:16:46 CMC2: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 29 15:16:44 CMC2: shutdown initiated
CMC-2D7L45J Jan 29 15:16:44 CMC2: wait for to be reset
CMC-2D7L45J Jan 29 15:16:39 System health recovery
CMC-2D7L45J Jan 29 15:16:33 CMC2: failover was initiated by mond
CMC-2D7L45J Jan 29 15:16:33 System health failover request RC=80010000
CMC-2D7L45J Jan 29 15:05:02 Chassis health is Healthy
CMC-2D7L45J Jan 29 15:04:15 CMC2: active
CMC-2D7L45J Jan 29 15:04:15 CMC2: reset by peer
CMC-2D7L45J Jan 29 15:04:15 [15:3:43]CMC2: standby CMC2 takes active
CMC-2D7L45J Jan 29 15:04:15 [15:3:42]CMC2: reset active CMC1
CMC-2D7L45J Jan 29 15:04:15 [15:3:42]CMC2: active CMC1 requests standby to go active
CMC-2D7L45J Jan 29 15:04:15 [15:3:24]CMC2: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J Jan 29 15:04:15 [17:20:59]CMC2: recovery from mond 0x0e 0x00, error=0x00000000.
CMC-2D7L45J Jan 29 15:03:39 CMC1: shutdown initiated
CMC-2D7L45J Jan 29 15:03:39 CMC1: wait for to be reset
CMC-2D7L45J Jan 29 15:03:27 CMC1: failover was initiated by mond
CMC-2D7L45J Jan 29 15:03:25 CMC1: firmware versions are same 4.30 A00
CMC-2D7L45J Jan 17 19:20:05 System health failover request RC=80010000
CMC-2D7L45J Jan 17 19:19:54 Chassis health is Critical
CMC-2D7L45J Jan 17 17:21:00 Chassis health is Non-critical

cel log :

Noncritical Mon Oct 27 2014 08:43:45 Server 5 health changed to a warning state from a normal state.
OK Wed Aug 13 2014 14:04:38 The chassis management controller (CMC) is redundant.
OK Wed Aug 13 2014 14:04:37 The CMC 2 LAN heartbeat is detected.
OK Wed Aug 13 2014 14:04:37 The CMC 1 LAN heartbeat is detected.
Critical Wed Aug 13 2014 14:02:44 Chassis management controller (CMC) redundancy is lost.
Critical Wed Aug 13 2014 14:02:32 The CMC 1 LAN heartbeat is lost.
Critical Wed Aug 13 2014 14:02:32 The CMC 2 LAN heartbeat is lost.
OK Tue Jul 15 2014 16:30:33 The chassis management controller (CMC) is redundant.
OK Tue Jul 15 2014 16:30:30 The CMC 1 LAN heartbeat is detected.
Critical Fri May 23 2014 00:53:27 Chassis management controller (CMC) redundancy is lost.
Critical Fri May 23 2014 00:47:58 The CMC 1 LAN heartbeat is lost.
OK Fri May 23 2014 00:47:52 The chassis management controller (CMC) is redundant.
Critical Fri May 23 2014 00:46:56 Chassis management controller (CMC) redundancy is lost.
OK Fri May 23 2014 00:43:34 IO module A1 is online.
OK Fri May 23 2014 00:43:28 IO module A2 is online.
OK Fri May 23 2014 00:43:25 IO module B2 is online.
OK Fri May 23 2014 00:43:23 IO module B1 is online.
OK Fri May 23 2014 00:43:07 IO module C1 is online.
OK Fri May 23 2014 00:43:03 IO module C2 is online.
Critical Fri May 23 2014 00:41:27 The CMC 1 LAN heartbeat is lost.
OK Fri May 23 2014 00:41:17 The CMC 2 LAN heartbeat is detected.
Critical Fri May 23 2014 00:41:15 The CMC 2 LAN heartbeat is lost.
OK Fri May 23 2014 00:40:57 The chassis management controller (CMC) is redundant.
Critical Mon May 12 2014 15:03:50 Chassis management controller (CMC) redundancy is lost.
Critical Mon May 12 2014 14:58:20 The CMC 1 LAN heartbeat is lost.
OK Mon May 12 2014 14:58:15 The chassis management controller (CMC) is redundant.
Critical Mon May 12 2014 14:57:21 Chassis management controller (CMC) redundancy is lost.
OK Mon May 12 2014 14:52:12 The CMC 2 LAN heartbeat is detected.
Critical Mon May 12 2014 14:52:11 The CMC 2 LAN heartbeat is lost.
OK Mon May 12 2014 14:52:02 The chassis management controller (CMC) is redundant.
Critical Mon May 12 2014 14:51:03 Chassis management controller (CMC) redundancy is lost.
Critical Mon May 12 2014 14:42:54 The CMC 2 LAN heartbeat is lost.
Critical Sun May 11 2014 18:15:09 Chassis management controller (CMC) redundancy is lost.
Critical Sun May 11 2014 18:09:41 The CMC 1 LAN heartbeat is lost.
OK Sun May 11 2014 18:09:34 The chassis management controller (CMC) is redundant.
Critical Sun May 11 2014 18:08:39 Chassis management controller (CMC) redundancy is lost.
OK Sun May 11 2014 18:07:57 The chassis management controller (CMC) is redundant.
OK Sun May 11 2014 18:07:56 The CMC 2 LAN heartbeat is detected.
Critical Sun May 11 2014 18:06:44 Chassis management controller (CMC) redundancy is lost.
Critical Sun May 11 2014 18:06:33 The CMC 1 LAN heartbeat is lost.
Critical Sun May 11 2014 18:06:32 The CMC 2 LAN heartbeat is lost.
OK Thu May 08 2014 16:19:28 The chassis management controller (CMC) is redundant.
OK Thu May 08 2014 16:19:25 The CMC 2 LAN heartbeat is detected.
Critical Tue May 06 2014 14:08:14 Chassis management controller (CMC) redundancy is lost.
Critical Tue May 06 2014 14:02:44 The CMC 2 LAN heartbeat is lost.
OK Tue May 06 2014 14:02:39 The chassis management controller (CMC) is redundant.
Critical Tue May 06 2014 14:01:44 Chassis management controller (CMC) redundancy is lost.
Critical Tue May 06 2014 13:56:38 The CMC 2 LAN heartbeat is lost.
OK Tue May 06 2014 13:56:33 The CMC 1 LAN heartbeat is detected.
Critical Tue May 06 2014 13:56:31 The CMC 1 LAN heartbeat is lost.
OK Tue May 06 2014 13:56:24 The chassis management controller (CMC) is redundant.
Critical Tue May 06 2014 13:55:27 Chassis management controller (CMC) redundancy is lost.
Critical Tue May 06 2014 13:54:22 The CMC 1 LAN heartbeat is lost.
OK Tue May 06 2014 13:53:52 The chassis management controller (CMC) is redundant.
OK Tue May 06 2014 13:53:49 The CMC 2 LAN heartbeat is detected.
Critical Thu May 01 2014 15:59:09 Server 3 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:59:08 Server 3 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:33:42 Server 3 health changed to a non-recoverable state.
OK Thu May 01 2014 15:10:55 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 15:10:52 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 15:10:51 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 15:10:34 The CMC 1 LAN heartbeat is lost.
Critical Thu May 01 2014 15:07:00 Server 4 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:06:59 Server 4 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:06:58 Server 3 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:06:58 Server 2 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:06:55 Server 1 health changed to a non-recoverable state.
Critical Thu May 01 2014 15:03:24 Chassis management controller (CMC) redundancy is lost.
OK Thu May 01 2014 14:59:47 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:59:46 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 14:59:37 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:58:51 The CMC 1 LAN heartbeat is lost.
Critical Thu May 01 2014 14:57:56 The CMC 2 LAN heartbeat is lost.
OK Thu May 01 2014 14:57:47 The chassis management controller (CMC) is redundant.
Critical Thu May 01 2014 14:56:56 Chassis management controller (CMC) redundancy is lost.
OK Thu May 01 2014 14:55:44 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:55:43 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 14:54:43 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:54:40 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 14:54:35 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:54:33 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 14:53:58 The CMC 1 LAN heartbeat is detected.
Critical Thu May 01 2014 14:53:54 The CMC 1 LAN heartbeat is lost.
OK Thu May 01 2014 14:53:52 The chassis management controller (CMC) is redundant.
OK Thu May 01 2014 14:53:51 A firmware or software incompatibility was corrected between CMC 1 and CMC 2.
OK Thu May 01 2014 14:53:49 The chassis management controller (CMC) is not redundant.
Critical Thu May 01 2014 14:50:38 Chassis management controller (CMC) redundancy is lost.
Critical Thu May 01 2014 14:47:30 The CMC 2 LAN heartbeat is lost.
OK Thu May 01 2014 14:47:28 The chassis management controller (CMC) is not redundant.
Noncritical Thu May 01 2014 14:47:25 A firmware or software incompatibility detected between CMC 1 and CMC 2.
OK Thu May 01 2014 14:47:25 The chassis management controller (CMC) is redundant.
OK Thu Apr 24 2014 18:50:31 The CMC 1 LAN heartbeat is detected.
Critical Thu Apr 24 2014 18:50:29 The CMC 1 LAN heartbeat is lost.
OK Thu Apr 24 2014 18:50:21 The CMC 1 LAN heartbeat is detected.
Critical Thu Apr 24 2014 18:49:51 The CMC 1 LAN heartbeat is lost.
Critical Sun Mar 16 2014 15:24:11 Chassis management controller (CMC) redundancy is lost.
Critical Sun Mar 16 2014 15:24:00 The CMC 2 LAN heartbeat is lost.
OK Sun Mar 16 2014 15:23:49 The CMC 2 LAN heartbeat is detected.
OK Sun Mar 16 2014 15:23:48 The chassis management controller (CMC) is redundant.
Critical Sun Mar 16 2014 15:23:46 The CMC 2 LAN heartbeat is lost.
OK Sun Mar 16 2014 15:23:45 The CMC 2 LAN heartbeat is detected.
Critical Wed Mar 12 2014 15:06:54 Chassis management controller (CMC) redundancy is lost.
Critical Wed Mar 12 2014 15:06:41 The CMC 2 LAN heartbeat is lost.
OK Mon Feb 03 2014 15:41:16 Log cleared.

so what should we do right now to solve this warning ??

Hello,

I've been trying to figure out what these errors mean and how to correct them on my C2100 server. I boot the server, it runs through bios, and the last thing right before it goes to the OS is a bunch of beeps and then it outputs...

DQS Test Minor Delays Error

RD DQ DQS Error

Memtest Dimm Disable Error

CLTT Minor Circuit Tst Failed Error

Not sure what is wrong/broken/or whatever, but any help is appreciated!

Thanks