Re: Suse 10 problems - SSH

I want to thank everyone for their willingness to offer help. You
guys rock!

Our problem seems to have been resolved. Apparently there were two
issues. The first was a hardware issue with a switch module on the
blade center chassis upon which the server resides. This was only
detected when someone finally noticed some transient packet loss with
some of the blades and started tracing it back to the chassis. The
second was that our xord.com on suse had apparently gotten messed up/
corrupted. I do not know how the xord corruption came about. They
were able to restore it eventually.

Once those items were resolved, all our functionalities (as far as I
know anyway, I'm still reviewing/testing but so far so good) returned
after a reboot.

Anyway, thanks again.
.

Relevant Pages

  • Re: Blade standarts - which is the best for me?
    ... chassis, e.g. so that you don't need a new chassis every time they ... revolution is better that just keeping an old standard... ... I'm simply saying that you need to be sure your blade chassis is ... Yes, this is true, but we wanted to start without SAN. ...
    (microsoft.public.windows.server.general)
  • RE: question.. not sure where to post..!!
    ... The blade servers a separate server. ... The shared chassis has a built in KVM and Gig switch. ... normal SCSI drives, the model we looked at used IDE laptop drives. ...
    (RedHat)
  • Re: Blade standarts - which is the best for me?
    ... Look for a vendor who commits to supporting their blade chassis for some ... revolution is better that just keeping an old standard... ... Yes, this is true, but we wanted to start without SAN. ...
    (microsoft.public.windows.server.general)
  • Re: DHCP, boot server race?
    ... are networked via paths that are integral to the chassis backplane. ... XPe blade server -> a general purpose blade computer on which we will ... We are using PXE and we do have DHCP as supported by the "switch/DHCP ...
    (microsoft.public.windowsxp.embedded)