PowerConnect 6248

SJ Stanaitis sstanaitis at dpsource.com
Wed Jun 17 09:51:26 CDT 2009


My old Dell 3048's would randomly brick themselves.  After replacing
them 4 times in 1 month I upgraded... our 6248's are behaving so far
though...

--S

-----Original Message-----
From: linux-poweredge-bounces at lists.us.dell.com
[mailto:linux-poweredge-bounces at lists.us.dell.com] On Behalf Of Adrian
Schmitz
Sent: Wednesday, June 17, 2009 10:29 AM
To: 'Brian McNally'
Cc: linux-poweredge at lists.us.dell.com
Subject: RE: PowerConnect 6248

I feel your pain.. we've had similar issues with our 3448P switches. 

-----Original Message-----
From: linux-poweredge-bounces at lists.us.dell.com
[mailto:linux-poweredge-bounces at lists.us.dell.com] On Behalf Of Brian
McNally
Sent: Tuesday, June 16, 2009 8:32 PM
To: linux-poweredge at lists.us.dell.com
Subject: Re: PowerConnect 6248

We have a couple 6248s and they've had similar problems. I found that it

was possible to crash the SSH daemon just by sending enough traffic to 
it. I've subsequently turned off SSH on the switch and only manage it 
via the serial console or web interface. The SSH bug may have been fixed

in a later firmware upgrade, but I'm not really sure as I haven't had a 
chance to apply the latest firmware yet. I've reported at least 7 bugs 
to Dell about these switches in the last year, some serious (like this 
one), with little evidence that the bugs are being taken seriously.

--
Brian McNally

Matthias Saou wrote:
> dellpoweredge at semantico.com wrote :
> 
>> The switch is working fine. The firmware is 2.1.0.13. It's just the
ssh 
>> daemon that's died. Health status doesn't say there's any problem
though 
>> on the admin. Anyone else had a similar problem?
> 
> I had similar, yet worse, problems on some 6224 which had their ssh
> daemon wide open to the Internet (bad idea in the first place,
> yeah...). Even with the latest firmware at the time, it kept happening
> regularly and the only solution was to manual powercycle the devices.
> 
> Once they were changed to be on a private subnet only, no more
> problems. My guess is that some external scans must have been able to
> crash the ssh daemon and the admin part of the switch, since the
access
> through the serial console port stopped working too. The rest (packet
> forwarding and routing) was still working...
> 
> Matthias
> 

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq



More information about the Linux-PowerEdge mailing list