Total power loss

My sig should be attached to the bottom to give you all the useful info should anyone need it but..
Here goes..i upgraded from a GF4 4600Ti to this beautiful FX 5950 Ultra and put simply i cant run the games in any higher rez's or with FSAA or AF than i used to coz i get total power loss..complete shutdown, BANG!..off it goes and i have to let the f*ker cool down for 20 minutes before it will let me turn it back on (ooerr)
Anyone any ideas
P.S its attached to a Dell 21" P1110 Monitor

Well thnx guys but I took matters into my own hands
Ive ordered this http://www.thermaltake.com/purepower/W0023.htm
and this (actually 2 of them..1 for my mate)
http://www.thermaltake.com/coolers/aquarius/a1681.htm
both from http://www.cpucitystore.co.uk/catalog/ ..so far the sales is brilliant and I got free Saturday delivery and a little discount..nice bit of bargaining..I strongly sudgest paying the site a visit..very good prices and cheaper delivery than a lot of onliners..speak to Aaron
tell me your thoughts

Similar Messages

WRT160N V3 - Power loss issue

Hi friends.
I have a problem with my WRT160N - V3.
Everytime I have a full power loss at my home, the router only starts again if i unplug and plug the power cable.
Is there some resolution for this?
Thanks anyway.
PS: Sorry for my bad English....

Hi Matt. If I get it right, what I have to do now to always power on automated is:
unplug the power adapter from power source
unplug the power adapter from router
plug the power adapter to power source
plug the power adapter to router
If I have a total power loss, will the router start automatic?
Thanks!

Broadband does not auto reconnect after power loss

I have a D-Link DSL-302G ADSL modem and Netgear AC1900 on an Eaton Powerware 5110 UPS. When there is power loss or brown out in our neighbourhood , our internet goes off and does not reconnect automatically. I then have to physically turn off the Netgear Router and turn back on to get the Green LED Internet light back on. The modem seems unaffected, but it is bridged so my router controls the connection process. Now this is what has me puzzled - my devices never lose power because of the UPS, and the router connection mode is set to "always on" , and Internet IP address is set to "Get Dynamically from ISP" Is it the local Telstra exchange dropping all connections when swithcing to battery backup, and then disrupting the normal connection process for the Router upon power resume ? Can you confirm what happens, or are there some tests I can do? This is very inconvenient as I run a terminal server, and not in the office all the time to reboot the router.

Hi Melior,
Normally, if there was a loss of power at your premises but not at the exchange then once the power was restored your modem should automatically reconnect (In this instance, a UPS should keep the modem powered up and connected). If there was a loss of power at the exchange your modem should connect automatically once the exchange is powered back up.
So given the information that you have provided, I would suggest that you check your equipment.
- Ben

MSI Z68A-GD65 G3 Power On after Ac Power loss how to turn it off?

Hi,
I want my computer to stay off when the power go down. But it is automatically powering on after Ac power loss even though I set in BIOS to stay off. Any ideas? Happened twice already.
SPECS:
i5 2500k
MSI Z68 ZD65 BIOS v23.6
Antec 400W Seasonic S12-II based PSU
Power On After Ac Power Loss Option in bios is "OFF"
Thanks.

Quote
Restore after AC Power Loss
This item specifies whether your system will reboot after a power failure or interrupt
occurs. Settings are:
[Power Off] Always leaves the computer in the power off state.
[Power On] Always leaves the computer in the power on state.
[Last State] Restore the system to the status before power failure or interrupt
occurred.
If you have this properly configured as you indicate in your post, try a full cmos clear and set it back and to re-test.
If that is of no help, what bios version do you have installed?

RVL200 won't auto-reconnect to Internet after power loss (PPPoE)

My RVL200 firmware 1.1.7 is configured for PPPoE. The connection to the Internet is via an ATT (SBC) DSL line using a Siemens Slipstream 4100 modem. The 4100 is configured to allow the PPPoE connection to be managed by the router. The RVL200's PPPoE fails to automatically reconnect to the Internet after a power loss (or if I click Disconnect on the RVL200's web page). This is true for both the Connect on Demand and Keep Alive PPPoE alternatives. In either case, I have to go to the router's web screen and manually click "Connect" to force a reconnection. The LAN is populated by Win XP SP2 systems.
Is there some special configuration needed on the LAN, in the RVL200's routing table, or in the modem to allow automatic reconnection to occur? Obviously it is undersirable to have to give out the RVL200 password to everyone who might need to force a reconnect after a power loss.
Neither the RVL200 Admin Guide not the Users Guide has any useful information on this issue.

I have to manually reconnect it. This issue came up when testing what would happen with an RVL200 in a power failure - whether it would automatically reconnect. I don't expect a lot of power failures, but I do want the network to reconnect automatically rather than have to count on someone knowing how to do it and having the apssword.
Am I correct that it is supposed to automatically re-establish the PPPoE connection?
What triggers the reconnection?

Have to reset WRT54G after a power loss

Hi,
I have a WRT54G ver 2 running firmware version 4.21.1. "Keep Alive" is enabled for the PPoE connection to my provider.
My two problems:
1) Anytime I encounter a power loss I have to reset the router and then of course reconfigure it. In the past, I never had to do this whenever there was a loss of power.
2) In a related problem, I cannot use the wireless print server. As soon as I get it configured and working other PCs on my network lose internet connectivity. That forces me to reset the the router, which forces me to reconfigure the wireless print server, and the sysle begins again!
Is it possible the ver of firmware I'm running is the issue or do I have a faulty router?

Routers seem to be sensitive to electrical surges and noise. This can cause them to loose their settings. You should keep your router plugged into a high quality surge suppressor with EMI/RFI filtering, such as the Belkin SurgeMaster Gold Series. EMI/RFI filtering is required. A surge suppressor alone is not enough because surge suppression does not start until the voltage exceeds 330 volts. Alternatively, most UPS devices have both surge suppression and EMI/RFI filtering.
If this does not prevent your router from "forgetting" its settings, then the router is malfunctioning, and it should be replaced. A router that forgets its settings is not secure.
Message Edited by toomanydonuts on 01-08-2008 10:54 PM

Imac G5 power loss

Hello, i don't know how many of you still have an iMac G5 out there, but i was wondering if anyone has ever had any problems relating to sudden power loss. Sometimes I will be working on something and it just shuts down. i would like to know if anyone out there might know if some setting could be responsible for this. thanks in advance.

You could try the following forum, plenty of iMac G% users there I'm sure.
Forum : Using your iMac G5
Steve

Computer hangs on AC Power loss on Docking station (Z61p)

I have a problem that the computer hangs if IU disconnect the power to my docking station similar to:
http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69370
Is this a known problem for the Z-series? Any solution?

Quote
Restore after AC Power Loss
This item specifies whether your system will reboot after a power failure or interrupt
occurs. Settings are:
[Power Off] Always leaves the computer in the power off state.
[Power On] Always leaves the computer in the power on state.
[Last State] Restore the system to the status before power failure or interrupt
occurred.
If you have this properly configured as you indicate in your post, try a full cmos clear and set it back and to re-test.
If that is of no help, what bios version do you have installed?

Domain.sites" could not be opened. After power loss

Oh sht have i got a prob.
I'm getting this message after a power loss, iweb will just not open anything............
The document "Domain.sites" could not be opened.
IWEB
Can’t open file “~/Library/Application Support/iWeb/Domain.sites.”
I have main site posted, so need to get that back into iweb of course. But I've also been working on new part to the site. It looks like I've lost everything and of course it's on the one drive I don't back up!!!
Can anyone help with what this could be?!?!
Thanks
Rob

Sorted

Strrange problem with Acrobat Reader 9 and power loss

Hello,
I have a Lenovo T61P (6457-A26) with Windows XP, and I have found a very strange behaviour with Adobe Acrobat Reader 9.
Sometimes I open a PDF, and I read one or two pages, and then my laptop has a problem like a power loss (remove of the batter).
I can read those PDF on other PC/MAC/Linux, ... no problem at all.
So I'm thinking about an incompatibility with my laptop and Acrobat Reader...
So for now, I've installed another PDF viewer (FoxIt), and I can open my PDF without fearing this lost of power...
Did somebody experienced something like that? If yes, are there some solutions?
Alessandro

1. It happens with any file i want to open in browser.
2. The Problem is specific to browser. When I open a document in the Reader application everithing works fine.
kind regards
Marcel

8.02 POA crashes w/ntdll.dll fault after power loss

Hi,
Running GW 8.0.2 on Windows 2003 server (POA, MTA and GWIA). After power loss on Friday, POA will not stay up for long - crashes with:
"Faulting application gwpoa.exe, version 8.0.2.10840, faulting module ntdll.dll version 5.2.3790.4455" error.
MTA and GWIA are not crashing.
I thought maybe it could be a corrupt message but the only messages in the queues are dated today and not Friday (\PO\wpcsout\ofs\4 - wpcsin queues are empty). I am currently running gwcheck.exe against the message databases but that is going to take a couple hours. Any thoughts? Thanks.

Originally Posted by DJMUGI
Hi, I'm reaching out to DJHess (and other forum members) - we are having nearly exactly the same issue (same version of GW, gwpoa.exe and ntdll.dll), POA does not stay up long (crashes after just a few hours) - but we did not have a power loss (that I am aware of). Was a solution ever determined for this issue? Did gwcheck.exe help (it does not for us)?
I am having the exact same problem. Below are the specs of my GroupWise servers:
GroupWise 8.0.2 (POA and MTA)
Server OS: 2008 R2 x64
The POA will randomly shut down with an ntdll.dll error fault. I have migrated this server to new hardware and a new OS (user to be on a 2003 R2 SP2 server and half the RAM). Same issue. Anyone have a fix for this?

FPGA Reset during power loss? NI 9802 Module

We have recently started using the NI 9802 on a cRIO system. We are getting the error -65550 discussed here: http://digital.ni.com/public.nsf/allkb/BD118434E87B9732862575C8006FD7FB
The article says that the error can be caused by the FPGA resetting while the drive was mounted. "To prevent this error from happening in the future, do not reset the
FPGA while you have an SD card mounted, reset before you mount the card
or after the card is unmounted." Does a power loss reset the FPGA and require you to reformat the card??? We plan to use this as a remote system and power failure is possible. We would not be able to travel hundreds of miles back to the device to reformat an SD card in the event of a power loss. This can't be right. How could they sell a module that worked like that?
Also, does the card need to be formatted with FAT32 or FAT16?
[will work for kudos]
Solved!
Go to Solution.

I would like to submit a suggestion for the next version of this module. It would be awesome if in the rare but possible case of the crio losing power that the card did not become corrupt and you would then not need to travel all the way to the device and pull the SD cards out and reformat them with a pc before your system could be come operational. Like the ability to reformat at run-time would be a decent fail safe function. Even though you would lose all the data you had recorded onto the SD Card, wasting time and money, at least the entire system would not be fatally crippled by a simple loss of power and unexpected device reboot.
As it stands, even with a quality power backup battery as you have suggested, the simple possibility that you could lose power and need to manually perform a format on the SD card makes this module inferior to simply plugging in a big USB drive, both in terms of reliability and storage space. The appeal to this module, even though it could only hold two 2 gig SD cards, was its apparent ruggedness and reliability over using a usb drive.
Respectfully waiting for a new version of this module,
Rex
[will work for kudos]

Problems with connecting to internet after power loss w WRT54G v3

I'm having problems connecting to the internet after a power loss with my WRT54G v3 wireless router. I'm at the latest firmware version (4.21.1).
I found similar problems with the V2 version of this router.
After a power failure, I can access the http interface to the router,all of my settings are there (not set to factory settings),the unit is connected to my ISP provider,I can ping from the router, but none of my wired or wireless PCs can ping.
To "fix" this condition, I have to reset to factory settings, then re-load my saved configuration.This usually works, but sometimes I have to hard reset the unit.
Anyone having this problem? Anyone have a fix?

Sudden loss of power for extended periods of time will 9x out of 10 will corrupt the saved configurations and can only be fixed in the way you already described.
A solution for this is getting an UPS incase of a power failure your equipment will be on battery back up until either the battery runs out or power is restored (depending on the model changed the battery time)
With Knowledge… Impossible means nothing.
Credentials
Computer experience: 11 years
Cisco networks experience: 8 years
Network administrator: 6 years
N.E.T. networks experience: 6 years
Linksys networks experience: 6 years
Recent additions: A+ | Networks+ | Linux+ | Security+

Yosemite does not start after power loss

I just want to report a bug related to the new OSX Yosemite.
Here at work I have to manage around 30 iMacs, plus some MacBook Pro.
After some initial tests, where I did not discover any particular incompatibility with our applications, I decided to upgrade my machines to Yosemite, but I had to stop the upgrade process when I realized the new OSX has this big and strange problem... now I have my machines half upgraded.
It happened to have some power losses due to the bad weather conditions, and after each one the machines with Yosemite didn't start... you have the black screen with the apple logo and the bar freezed at almost 50%.
You can only power OFF and ON till the computer finally starts... usually it takes 5-6 tries.
The problem is not related with the iMac models, I have some different kind of iMac and on overyone I have the very same problem, the only thing these machines have in common is the new OSX 10.10 (10.10.1 didn't fix this problem), the others with Mavericks does no suffer this matter after the same power loss.
Hope this report could reach some Apple developer, in any case if I have to produce some log to debug it let me know, I will be happy to help.
Massimo

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
Feedback
Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.
Feedback via Apple Developer

WLC 4402 - APs last reboot reason power loss

st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Hi,
we have a Wireless LAN Controller WLC 4402, Software Version 4.1.192.22M (Mesh).
At the moment there are 6 Access Points in one house, one of them is the root AP. The others are only connected via electrical socket.
AP’s are: AIR-LAP1131AG-E-K9 / Boot Version 12.3.8.0 / IOS Version 12.4(3g)JMC1
I think the configuration worked fine over a period of 2 years.
Now the problem is that the number of access points connected to the controller is changing nearly every minute. At times there is only one AP connected to the controller. So it is impossible for the clients to build up a steady connection. They have to log in via the guest user web interface at short intervals or they can’t see the wireless lan.
First we thought it would be a problem of one or two “defect” access points. But we replaced 4 of the 6 access points and the problem is still there.
An example, yesterday:
13:17 o’clock – 2 AP’s
13:19 o’clock – 4 AP’s
13:21 o’clock – 5 AP’s
13:23 o’clock – 4 AP’s
13:25 o’clock – 5 AP’s
13:25 o’clock – 4 AP’s
13:26 o’clock – 5 AP’s
13:26 o’clock – 6 AP’s
13:28 o’clock – 4 AP’s
13:28 o’clock – 2 AP’s
Eye-catching is the following message of the log, which appears often: “52       Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
Also eye-catching is the AP up time. The Root AP is up for over 80 days. But all the other access points show an up time of a few minutes until some hours…but not more.
Does anybody know what the problem could be?? I read some similar threads but no solution.
In the following an abstract of the log:
21        Mon May 16 13:25:43 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
22        Mon May 16 13:25:30 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
23        Mon May 16 13:25:30 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
24        Mon May 16 13:25:30 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
25        Mon May 16 13:25:05 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
26        Mon May 16 13:24:10 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
27        Mon May 16 13:24:10 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
28        Mon May 16 13:24:10 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
29        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
30        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
31        Mon May 16 13:23:59 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
32        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
33        Mon May 16 13:23:58 2011        AP 'AP001d.45d8.4ea6', MAC: 00:1d:71:e1:b2:20 disassociated previously due to AP Reset. Last reboot reason: power loss
34        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
35        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
36        Mon May 16 13:23:31 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
37        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
38        Mon May 16 13:23:30 2011        AP 'AP001d.e557.6f0c', MAC: 00:1d:70:01:b5:a0 disassociated previously due to AP Reset. Last reboot reason: power loss
39        Mon May 16 13:23:13 2011        Client Association: Client MAC:00:1d:71:e1:b2:2f Base Radio MAC :00:1d:70:01:bc:20 Slot: 1 User Name:c1130-001D45D84EA6
40        Mon May 16 13:23:13 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
41        Mon May 16 13:23:04 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:23:5e:49:9d:e0' from mesh node '00:1f:ca:cc:b7:40'.
42        Mon May 16 13:22:57 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
43        Mon May 16 13:22:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
44        Mon May 16 13:22:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
45        Mon May 16 13:22:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
46        Mon May 16 13:22:39 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
47        Mon May 16 13:22:17 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
48        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
49        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
50        Mon May 16 13:21:57 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
51        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
52        Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
53        Mon May 16 13:21:39 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
54        Mon May 16 13:21:32 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
55        Mon May 16 13:21:12 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:b5:a0'.
56        Mon May 16 13:21:05 2011        Client Association: Client MAC:00:1d:70:01:bc:2f Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-001DE5576FD8
57        Mon May 16 13:20:32 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
58        Mon May 16 13:20:11 2011        Mesh child node '00:1d:70:01:bc:2f' is no longer associated with mesh node '00:1f:ca:cc:b7:40'.
59        Mon May 16 13:20:06 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
60        Mon May 16 13:19:57 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
61        Mon May 16 13:19:57 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
62        Mon May 16 13:19:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
63        Mon May 16 13:19:49 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:bc:20
64        Mon May 16 13:19:49 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
65        Mon May 16 13:19:49 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
66        Mon May 16 13:19:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
67        Mon May 16 13:19:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
68        Mon May 16 13:19:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
69        Mon May 16 13:19:36 2011        AP Disassociated. Base Radio MAC:00:1d:71:e1:b2:20
70        Mon May 16 13:19:36 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
71        Mon May 16 13:19:36 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
Greetings Lydia

st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Hey,
last week I tried to upgrade the controller step-by-step.
Under the software 4.1.192.35M the problem was still there… access points were often disassociated from the controller.
There were problems with Software 4.2.207.54M too. The access points couldn’t reach the download-status. The log of the access point said that it could not open the tar-file.
So I went back to 4.1.192.35M. Of course the controller lost some of its configuration. I configured it new with the same settings as before.
After it the wireless connection seemed to be a little bit more robust. I asked the users to test the connection at the weekend and this is the answer:
“so we tested the WLAN during the weekend. The situation definitely improved with respect to before. Authetication is much faster and the connection (when active) is sensibly faster.
However the connection is still very unstable and it is necessary every five-ten minutes to reconnect (especially for intense network traffic like when watching a streaming content or using VOIP applications. Actually switching off and on again the WLAN card (Airport) often a new authentication is not required. However, without doing so the connection would not resume alone to a working state.
So what to say? Better than before (thanks) but far from being fixed. From last September to January we did not experience any problem, so it must be something that chronologically happened at the beginning of the year, it is not a systemic problem.
But there were no changes or anything else at the beginning of the year.
Do you mean it makes sense to resume upgrading? I’m a little bit afraid of more problems like under 4.2.207.54M
Greetings Lydia

Total power loss

Similar Messages

Maybe you are looking for