2200M2 ELOM serial port

So last night after I got the box running; a friend and I used WireShark
to examine the session between the laptop and the 2200M2.

So we immediately saw that the Java-based Remote Console uses port 8890
as well as 443. Googling THAT gets me references to other folks with the
same issues; one reports 9000-9003 are needed as well.

I just want to gripe that nowhere in the Sun docs did I see any mention
of needed ports for ILOM or ELOM.

If that had, it would have same me a lot of wasted time; and I can't
be alone...

--
A host is a host from coast to
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433

In comp.sys.sun.admin David Lesher <> wrote:
>
>
> So last night after I got the box running; a friend and I used WireShark
> to examine the session between the laptop and the 2200M2.
>
> So we immediately saw that the Java-based Remote Console uses port 8890
> as well as 443. Googling THAT gets me references to other folks with the
> same issues; one reports 9000-9003 are needed as well.
>
> I just want to gripe that nowhere in the Sun docs did I see any mention
> of needed ports for ILOM or ELOM.
>
> If that had, it would have same me a lot of wasted time; and I can't
> be alone...
>

I'm glad you have the machione running again.

I thought that your difficulty was with communicating via the serial port,
not through the network interface. Your gripe is valid, though. I
remember taking some time to track down that information myself.


--
Dr Tristram J. Scott
Energy Consultant

(Tristram Scott) writes:


>I'm glad you have the machione running again.

>I thought that your difficulty was with communicating via the serial port,
>not through the network interface. Your gripe is valid, though. I
>remember taking some time to track down that information myself.

You REALLY did not want to ask:

Saga:

A) Build box with ELOM over CAT5.

B) Deploy in colo

.....


C) Have issue, can't get ELOM Remote Console to work

D) WTF?!?! It did at A)

E) Waste weeks looking for answers, building SSH tunnels, trying to get
an adjacent box &/or one of the 2200's own VM to run the Java so we can
sniff. As I recall, OpenSol lacks the Java needed. [Someone else tried
this; don't recall actual failure..]

F) Give up, pull box. [Takes coordination; it's not really a colo; it's
donated space in $BigCompany's room with theirs.]

G) Friend/Wireshark guru and I try and set up same to test.

H) Discover not even 64Bit Apple Java 6 will run ELOM; also fails - %&*%

I) Try and set ELOM to have temporary outside access so that a Sun
worshipper 60 miles away can look at it from there.

J) Wireshark guru/Friend botches address change [we were tired...this was
an after-dinner attempt] and lose access...

K) Try monitor, see F2 prompt but ZERO mention of the secret "hit a key
while BIOS scrolls by" clue.

L) Give up; bring back, waste many more hours on serial per Fine Manuals.

M) Stumble across K) backdoor. Eureka!! Fix ELOM IP's.

N) Flash via ELOM

O) Brick box when it fails.

P) Ask help.

Q) Get battery+CD image suggestion

R) Pull batt, burn CD's, rescue box.

S) Carry back to G's and run Wireshark with a Linux and XP VM's;

T) Futz with their Java until it works...

U) Run Wireshark; see ports. Took 5 min max.

V) [Yet to do: ask colo to open new ACL holes. Want to be SURE we
know all the ports needed..]

W) [Reinstall box.]

Y) Try and grok ORIGINAL problem; Xen keeps dying. (Meanwhile, XVM Server
has been abandoned.)



ALL the C through W because Sun did not say: "You need these ports" and
"You need this JAVA version..."

For the record; from what I've read: ILOM uses different ports, and has
different JAVA requirements.

--
A host is a host from coast to
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433