Bill Mackler <
underh20.s...@gmail.com> wrote:
> I did issue -> show /SP/network
> all network configs are still there.
Well, simple then.
If you are 100% sure the network config for the ILOM is there, then you
have a hardware problem and the ethernet port on it is blown.
You never really explained this in any detail:
"There was a network outage at our data center. It lasted for about 8 hours."
I find it kind of odd a network outage at a data center took 8 hours to fix,
unless it was extensive damage, from a lightning strike maybe? Of course a
backhoe down the road tearing out a fiber cable could be to blame also.
We took a hit in 2008 from a near by lightning strike and ethernet was the
only casualty. Most of our Cisco switches were showing green when something
was plugged into a port, but the transceivers must of been blown inside
because there was no traffic, no matter what you tried. Same with one of the
old Sun 280r's and some of those old Cobalt Raq4 things.
Look, all you have to do is configure the ILOM from the serial side to use
an internal 192.168.1.x address, set up a laptop the same way, plug one into
the other using a regular eth (or xover) cable and see if they talk.
If you still can't ping it with a direct connection, your eth port on it is
shot. End of story.
It's not likely to be firmware or software at this point.
Get an explanation of the 8 hour outage and what caused it, if the word
"lightning" is used as any part of it, assume the worst.
-bruce
b...@ripco.com