[weblacky]

Ok,
I've tried to look this up but I get a generic description of using an L2 controller with an Origin system...I don't own a clustering SGI system.  I expect to use this with Fuel and Tezro stations via their L1 USB ports.

Can someone give me a "quick start" guide to getting into a L2 controller and which connections to use and how you navigate to each connected L1 USB-linked system?

I don't know how "navigation" in general works on the L2 controller without the whole "rack" and "slot" notion. Also does the CRTL D & T work inside to go from a connected system system's L1 to that system's PROM console?

I'm looking into buying a cheap L2 on eBay soon, but for right now I'm trying to study before hand.

Thanks!

[Raion]

The L2 controller is not strictly necessary for operations but does help. The main goal of an L2 is configuration of bricks attached, if you are dealing with a correctly serialized set of bricks it's not necessary.

[weblacky]

The L2 controller is not strictly necessary for operations but does help. The main goal of an L2 is configuration of bricks attached, if you are dealing with a correctly serialized set of bricks it's not necessary.

Hi Raion,
I've been told by a few longtime members here that the L2 controller has one superpower that I should probably have.

That is that the L2 controller apparently seems to have the super power to forcibly redirect the system Console without having to figure out what serial port it might be lurking on or at least that's the impression given to me by certain members.

I just snagged one on eBay for about ultra-cheap. And I'm creating the digikey list for the DB50 connector, 48VDC (AC to DC adapter), and the internal lithium battery it requires. I'd like to hold off and open it up and check those capacitors and put those on my list as well before I finish my order. But after that I should have everything I need to get one running. 

I do enough work with Fuel and Tezro by saving myself from needing two or three simultaneous null modem cables hooked to every port imaginable to find the darn PROM text output, it would be a blessing if a single USB cable means 1 cord, L1 and Console PROM access in ONE connection...all the time.

I realize it doesn't serve much else of the purpose but I'm tired of having to figure out which port the PROM is outputting on and if someone's changed the darn baud rates on me. If one cable gets me every single text output the system will do, everytime, then that's exactly what I want.

I'm buying it specifically for this purpose and no other that I can think of.

[Raion]

Then you'll have little trouble using it for that purpose. As far I remember the L2 owners guide is basically what you want.

[jwhat]

Hi Weblacky,

here are steps to get L2 going:

0. Wire up your 48V DC PS (see my blog page - or do search here for details from Jan-Jaap)
1. Connect to the L2 Console port (serial 38400) (there are two ports - console & modem)
2. Connect L2 to ethernet network
3. Power up L2, you should see the boot diags coming via serial console port
4. (Wrong - as this config will be lost on reboot) On L2 go into "shell" , this will take you into the L2 underlying "BusyBox" unix shell (via serial)
5. (Wrong - as this config will be lost on reboot) From shell set IP address using "standard" UNIX "ifconfig" utility (via serial)
6. (Wrong) From shell confirm you can ping another machine on your network (via serial)
7. (Wrong) Exit shell (via serial)
4. (Right) use L2 ip command to set ip/netmask/broadcast
5. Set your date/time zone
6. Unplug power and confirm ip address & date/time zone have been keep over power cycle.
8. Reboot L2 (l2_reboot or reboot_l2 ... read the manual ;-) ) (via serial)
9. Now on reboot you should be able to telnet into the L2 and no need for serial connection anymore.. (via any box on network with telnet)
10. Does not work !!!!

if you get to 10, then I will recheck with an actual L2 to validate what I have put in from my poor memory ;-)

EDIT: I had to replace L2 on my O350, yesterday so re-validated this, lots of "Wrongs" so memory not so good...

Cheers from Oz,

jwhat/John

[kubatyszko]

Once you get the L2 working, you hook up the individual systems via USB cable.
Pay attention to the serial of each system - it must be unique.
When I manage my Fuel over L2 - it's exactly the same as using the serial port inside
When I manage my dual O300 with numa link, I can use the "*" to issue commands to BOTH nodes at the same time (like "* power up") or prefix with the individual machine's ID to only talk to the one.
The benefit for me is not having to use the internal L1 serial port in my Fuel.

[weblacky]

Once you get the L2 working, you hook up the individual systems via USB cable.
Pay attention to the serial of each system - it must be unique.
When I manage my Fuel over L2 - it's exactly the same as using the serial port inside
When I manage my dual O300 with numa link, I can use the "*" to issue commands to BOTH nodes at the same time (like "* power up") or prefix with the individual machine's ID to only talk to the one.
The benefit for me is not having to use the internal L1 serial port in my Fuel.

Yes, I finally convinced myself to just get one. It's just that the instructions talk about a numerator system is based on rack & slot number and such and I was curious if anyone knew how in the heck to navigate if you hook up more than one workstation system to it.

However it's highly likely that what I'll be doing is using it entirely in telnet mode on a single system at a time. But you never know.

[jwhat]

Hi Weblacky,

you don't need to worry about the RACK/SLOT configuration with Fuel.

Nor do you you have to worry about Fuel taking on the Serial Number from the L2 (it won't let this happen).

Finally in the instructions I forget to put in a critical step....

11. Plug in the USB cable into Fuel and L2 ;-)

EDIT: Also you can update the L2 firmware via Fuel USB connection with "flashsc -p l2.bin all", just be sure not to use 6.5.30 firmware, use PATCH SG0007149

Cheers from Oz,

jwhat/John.

[weblacky]

Yo,
I have finally purchased an L2 controller of eBay (super cheap), I made a 48V DC PSU for it and everything basically runs (got a new internal battery too at Jan-Japp's recommendation, beforehand). Current firmware is 1.40, I set the time, time zone,and cleared the old network settings. I am worried though that I cleared the static settings and it claims the DHCP client is starting...but never gets an IP?!? Same ethernet cable with a laptop gets IP just fine. Tried two different network locations...no worky.

Network switch confirms MAC address of L2 controller when ethernet cable is attached...so media level is working. Is the DHCP client known to be trash? I'll see about setting a static later...I just don't want to, long term.

[weblacky]

Found out DHCP client program is just JUNK on an L2 controller running v1.40, static IP works FINE. DHCP client cannot get an IP to to save its life. Static worked just fine so I guess that explains why the old owner had it on static as well...