Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[andrew.keating]

We previously had a DFL-800, worked OK for a few years, recently died.

We bought 2 DFL-860E's (one as a cold spare) and configured them as per the previous one.

After about 5 days of use (internet access, VPN clients, IPSEC tunnels) - it froze - lights still flashing, but unable to access the unit, and no longer working.  We restarted it, it froze again within 6 hours.  We switched to the 2nd unit (same config) - it froze within a few hours too.

The units are in a colocation datacentre (so environmental conditions should not be an issue).

Has anyone experience 'freezing' up like this?

At this point we are probably going to return them and move to another vendor - just thought I would check for any solutions.

Thanks
Andy

[danilovav]

In generally, it's very strange situation - i have DFL (also 860E) which works by couple of months without problems
What F/W do you have?
Can you check the reason by
- setup syslog and get logs, what happens right before?
- check by console - does DFL hanged or just dropped network interfaces?

[lingnau]

Did you try connecting via serial cable to see if anything get's printed on the console?

[xavierbt]

Did you try with another power supply ?
I have 2 dfl-800 and original power supplies died in both.

[zammtronic]

Hello andrew and danilovav

I am working to configure two DFL-860E units at remote sites in preparation to migrate from our current DFL-800 and DFL-210. Occasionally the local 860 will hang on activate, and the remote unit is currently frozen (this has been happening at least once a day as del test new configurations).

They are both at FW version 2.27.03.25-14781.

I will try to setup sys logs on the local unit and attempt to grab errors.

Will the DFL become responsive again after a hang, since there has been no opportunity to log in and verity the committed changes?

Any feedback will be appreciated. The current configuration changes being committed were new address names on a Lan-Lan VPN tunnel.

[danilovav]

Log messages are very important

Also, at the freeze moment, try
- ping internal IP
- connect via serial cable and check is it working or now

[PBilodeau]

I recently purchased a DFL-860E to put in the Data-center.  It froze on me 2 times in the last two days while I was configuring it.  Both times it froze while clicking in a menu to get somewhere, not while activating or saving anything.

I didn't check the log yet, as it's in a data-center about 45 minutes from here.   It's really a pain!

Can someone tell me if this has been fixed?

Thanks.

[PBilodeau]

OK.  Just had to go to the data center and restart it.  Before doing so, I checked a few things:

1- All servers directly connected to the internal side of the DFL-860E could communicate with each other.
2- The management interface (HTTPS) was dead.  No reply at all.
3- The management console on SSH was dead as well.
4- All access to specific WAN adresses normally passing thru to the internal network no longer worked.

Unfortunately I couldn't check the log.  Next time?  I hope there won't be a next time!

If the DFL was completely frozen, that would explain point 2 to 4, but why the internal network could still communicate?  Only the rules that got mixed up internally?

I no longer have the packaging, so I can't return it, but if it dies again on me, arghhhhhh!  I can't afford to have such a central piece of equipement in a data center be as unreliable as that.  The guys administering the data-center warned me to only use Cisco.....

Please someone...  Help me solve this and stick with D-Link  ;-)

[danilovav]

Which version of firmware do you use?

Checking from inside is very important... In most often cases, DFL has problems with interface downs, physical freezes i saw only in case bad electricity power. Intreface down can be solved by switch between DFL and ISP equipment

Do you have other ways to check DFL? Something, additional IP on server directly for management...
Plz, setup logs and if happened next time, check by console and from LAN

[PBilodeau]

I was using firmware 2.27.02.  I recently registered my DFL-860E on the support site, and checked the firmware upgrades.  This issue I'm getting has apparently been fixed in 2.30.01.  I donwloaded it and upgraded about 15 minutes ago.   We'll see.

Regarding you other questions, I already gave some of the answers.  See point 1 to 4 in my previous post.

Anyhow, I hope the firmware upgrade will be the solution.  I'll get back here if it's not resolved.

Thanks!