RX2600 help please

[Richard J Maher]

Hi,

I've just taken delivery of one of those lovely rx2600 boxes as seen on Ebay. In the US everything was working as advertised but the Management card/module appears to have been a little rattled on its way to Oz :-(

The Good news: -

- It boots automatically with VMS 8.3
- If I connect a serial cable I get the Login prompt and can loggin as SYSTEM and everything looks tickety-boo.
- The network doesn't start automatically (and I'll fix that later) but I can start TCP/IP and then Telnet to the box at 192.168.1.159

The Bad news: -
- I can't Telnet to the Management card at 192.168.1.51 (This was all working prior to departure)
- *The far right "System" LED is blinking amber at 1sec intervals*
- I've got no idea how to find out what it's blinking about
- I don't have one of those funny 25-pin "printer" console plug things
- There are two green LEDs next to the Mgmnt card port (I guess xmit/recv?) but about 1cm to the right of them is a green blinking(1sec) LED also
- I don't appear to be able to get a console

Anything other than "your stuffed" greatly appreciated :-)

Cheers Richard Maher

PS. How do you tell theses things not to power up until I actually hit the Power button? And then how do you get them to stay down when you turn 'em off?

[Richard J Maher]

Sorry, just the wrong IP address.

It was there all the time.

Cheers Richard Maher

[Phil.Howell]

Anything other than "your stuffed" greatly appreciated :-)

Surely that should be "you're stuffed" :)

[Hoff]

Please read the manuals.

There's the manual for the base box, and there's the MP iLO manual.

Failure to read the manuals with this box will lead only to frustration; there are three different user interfaces within the typical base rx2600 series box (EFI, BMC, and (assuming one is installed) MP iLO card), plus a UI for any RAID controller, plus the UIs for the management tools, plus the OpenVMS UIs. And they're all different.

As for this case, even if the IP addresses and the MP passwords and any and all other access into the box is unavailable, you can easily re-set the system sufficiently to start a configuration.

As a side note, I'd discourage the use of 192.168.0.0/16, as that tends to mess up VPN routing if/when you get around to using that. Use of a subnet somewhere in 10.0.0.0/8 or in 172.16.0.0/12 is a much better choice for a private LAN.

As for the discussion that led up to the answer here, that's out in the comp.os.vms cross-posting of the original question.