Rob Morrow's Weblog

Creating idprom images (last part of building a 12k/15/20k/25k SC from "scratch")
I ran into this quite by accident. A couple of 20K's got so royally hosed that they needed to have their SC's built from scratch. So, I rebuilt the OS from a known-good flash archive, downloaded SMS 1.5, and ran smsinstall. After that I needed to build the IDprom images for the domains. Here's how I did it: Given: Mac address and Serial Number (easy...they're both on the front bottom of the cabinet) sms-svc> sysid -d a -e 0:0:be:a8:4:7c -s 143A2008BD This translates to: become sms-svc user, and do "sysid -d -e -s " Keep in mind that the only thing that'll change in the above equation as you move through all of the domains (yes...an IDprom has to get created for each domain possible) is to increase the mac address by one number for each new domain. Example: Domain A ....above example... Domain B sysid -d b -e 0:0:be:a8:4:7d -s 143A2008BD Domain C sysid -d c -e 0:0:be:a8:4:7e -s 143A2008BD Seeing a pattern? Of course it's much easier if you have done an smsbackup prior to rebuilding the SC's. That way you can skip this nonsense and go straight to smsrestore. If using the second method, it's best to restore to the non-active SC, then do a "setfailover on" from the active SC, then do a "setfailover force" from the active SC. You can verify that it worked easily enough. The "SF15K-gen-ethers.sh" (bundled with the SC) will only work with valid IDproms. Otherwise, you can inspect the output of that command in /tmp/ethers and it should be obvious if it worked [or not].

@ 09:12 PM EST [ Comments [0] ]

Opening Statement
Firstly, these flockers :) make the tools that made it easy to get the blog moving forward:

flock

So, here's the deal. I needed a place-holder for problems/solutions that I encounter. I promise to update this area with both as I come across them. Not trying to reinvent the wheel here, but we still see interesting problems with Solaris/Storage/HES.

History: I am a Systems Support Engineer at Sun Microsystems. Basically this makes me Sun's customer-facing engineer for large installations and complex break/fix. Sun supports my endeavors with tools, standards, etc. I encounter such a wide range of systems/storage issues that it becomes difficult to track solutions generally because the volume gets so darn high.
I specialize in high-end server (SunFire 6900, E12K-E25K, etc.) and storage (6320/9990, etc.) I am also interested in tracking unusual workaday Solaris problems as well.
So, my thinking is that I can place  problem::solution descriptions here for later retrieval. I will openly place submitted comments in the blog (nothing too racy, please). If someone submits a SysAdmin/Engineering problem that is right for anything near my pay-grade (not rock-star...more like lounge-lyricist), I will post it and do what I can to help out. There should be a lot of system/storage output in here...descriptions, command output, how-do-I, sort of things.

So, to kick things off (and because I don't have a problem to solve today other than the sheer work involved in rebuilding a couple of E20K System Controllers from scratch--Solaris 8 shipped on the SC's---PITA), here's a site I have liked for several years: cuddletech. They do a particularly good job of creating cheat-sheets for VxVm, and there's a really good technical history of the San Foundation Suite FC driver stack (go to the main site, then append "fc"...I won't link it because there is a....ummm....questionable image at the top.)