posted by hal 20090608

---

If resolv.conf exists on your NIS server - ypserv will always use DNS forwarding on Solaris.

posted by hal 20030606 | permalink | path | initial version: 200300605.

This is a slightly edited reply of a recent posting on news about setting up your NIS master server. If /etc/resolv.conf exists ypserv will always start with the "-d" option - it does not matter what you do in /var/yp/Makefile (from the man page for ypserv on the "-d" option: go to the DNS (Domain Name Service) for more host information).

To make sure DNS forwarding is turned off

• use "B=" in /var/yp/Makefile
• edit /usr/lib/netsvc/ypstart so ypserv does not start with the "-d" option
• stop/start the nis-server using /usr/lib/netsvc/{ypstop|ypstart}
• use ps or pgrep to check that ypserv is not running with the "-d" option and also check that rpc.nisd_resolv isn't running

A snip from the news posting

ypserv is running with the '-d' option, which according to Answer Book means that it is running without DNS forwarding.

And my reply:

are you dead sure? have you checked ypserv actually does run without "-d" using ps? setting "B=" in /var/yp/Makefile does not prevent ypserv from starting with "-d" as long as /etc/resolv.conf exists (and nsswitch.conf does not matter either - see below). There are perfectly valid reasons for wanting the NIS master to be a "pure" DNS client (without using forwarding for your NIS clients) - ie you want to run nslookup. When setting up NIS servers I normally change the offending lines in /usr/lib/netsvc/ypstart from

if [ -f /etc/resolv.conf ]; then
$YPDIR/ypserv -d && echo ' ypserv\c'
else
$YPDIR/ypserv && echo ' ypserv\c'
fi

to simply

$YPDIR/ypserv && echo ' ypserv\c'

It's still there in Solaris 9 and Sun code maintainers should take note - if we change the "B=" in /var/yp/Makefile we want it to have effect :-|

---

Ubergeek' switch to Linux animation is funny and spot on.

posted by hal 20030530 | permalink | path | initial version: 20030530.

Compiling a kernel on Linux brings me back to the days (in the last millenium ...) of SunOS 4.1.x and Unicos. Fun and satisfying the first few times (on the same level as compiling public domain software); but it's a procedure which any modern operating system really should manage without (Sun and Microsoft admittedly are living in a simpler universes). Ubergeek has created a superb animated cartoon pinpointing the way of Linux. And while you are at ubergeek's place check out the Mac and Toaster cartoons as well.

---

Storage Automated Diagnostic Environment replaces StorTools - a step forward in testing of SAN/Fibre attached Sun hardware.

posted by hal 20030529 | permalink | path | initial version: 20030529

After struggling with StorTools last year I recently had the need to test an a5000. It seems like the old StorTools package has been decommisioned and instead we've got the Storage Automated Diagnostic Environment (version 2.2 released last week and now downloadable (registration required) from the sun download/sysadmin area).

The package installs in /opt/SUNWstade and just like SyMon and SunVTS is a bit bloated. Recent devices like fibre channel tape drives, V880 disks and backplane are supported. Sun seems to think that we want to manage all things at all times from anywhere (not a bad idea) - so by default there is a web server listening on port 7654 (login: ras/agent), you can set up your storage to be diagnosed/monitored in a NIS like master/slave/client style. Installation is straightforward (but the web interface is unusable until you have put in the site information). Your /etc/inet/services, /etc/inet/inetd.conf and /var/spool/cron/crontabs/root will be modified by the (master) install.

The web interface gives you great control over the test options (ie you can select individual disks in the A5000-Disk test) and is just as usable as the command line alternative. Use the verbose option when accessing the individual tests from the command line (as some tests takes a long time and to give you an idea of what is going on behind the scenes). Here's some sample output testing an A5200:

freya# pwd
/opt/SUNWstade/Diags/bin
freya#
freya# ./a5ksestest -v -o dev=/dev/es/ses0
"a5ksestest:  called with options: dev=/dev/es/ses0"
"a5ksestest: Started."
"Started test on /dev/es/ses0"
"Box Name = freysen00"
"SES physical path: /devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ses@w5080020000026901,0:0"
"Power Supplies (0,2 in front, 1 in rear)"
"Power Supply 0 is OK"
"Power Supply 1 is OK"
"Power Supply 2 is OK"
"Fans (0 in front, 1 in rear)"
"Fan 0 detected to be OK"
"Fan 1 detected to be OK"
"ESI Interface board(IB) (A top, B bottom)"
"Interface Board A: OK()"
"GBIC module (1 on left, 0 on right in IB)"
"Interface Board A: GBIC Module: 0 OK(mod.-05)"
"Interface Board A: GBIC Module: 1 NOT INSTALLED"
"Interface Board B: OK()"
"GBIC module (1 on left, 0 on right in IB)"
"Interface Board B: GBIC Module: 0 NOT INSTALLED"
"Interface Board B: GBIC Module: 1 OK(mod.-05)"
"Disk backplane (0 in front, 1 in rear)"
"Front backplane"
"Front backplane is OK"
"Temperature sensors (on front backplane)"
"Temperature sensor 0, on the front backplane is OK: 40C "
"Temperature sensor 1, on the front backplane is OK: 37C "
"Temperature sensor 2, on the front backplane is OK: 37C "
"Temperature sensor 3, on the front backplane is OK: 36C "
"Temperature sensor 4, on the front backplane is OK: 39C "
"Temperature sensor 5, on the front backplane is OK: 40C "
"Temperature sensor 6, on the front backplane is OK: 39C "
"All temperature sensors on front backplane are OK "
"Back backplane"
"Back backplane is OK"
"Temperature sensors (on rear backplane)"
"Temperature sensor 0, on the rear backplane is OK: 34C "
"Temperature sensor 1, on the rear backplane is OK: 39C "
"Temperature sensor 2, on the rear backplane is OK: 37C "
"Temperature sensor 3, on the rear backplane is OK: 37C "
"Temperature sensor 4, on the rear backplane is OK: 36C "
"Temperature sensor 5, on the rear backplane is OK: 36C "
"Temperature sensor 6, on the rear backplane is OK: 37C "
"All temperature sensors on rear backplane are OK "
"(freysen00) Interconnect assembly"
"(freysen00) Interconnect Assembly OK"
"(freysen00) Loop  configuration"
"(freysen00) Loop A is configured as a single loop"
"(freysen00) Loop B is configured as a single loop"
"Drive 0, on the front is Installed"
"Drive 0, on the front is OK"
"Node WWN for Drive 0, on the front is 20000020370c45e0 "
"Drive 0, on the back is Installed"
"Drive 0, on the back is OK"
"Node WWN for Drive 0, on the back is 20000020370c3e10 "
...
...
"Node WWN for Drive 5, on the back is 20000020370c450b "
"Drive 6, on the front is Installed"
"Drive 6, on the front is OK"
"Node WWN for Drive 6, on the front is 20000020370c4df8 "
"Drive 6, on the back is Installed"
"Drive 6, on the back is OK"
"Node WWN for Drive 6, on the back is 20000020370c3e1c "
"a5ksestest: Stopped successfully."
freya# 

freya# ./a5ktest -v -o "dev=/dev/rdsk/c0t22d0s2|fstest=disable"
"Options: dev=/dev/rdsk/c0t22d0s2|fstest=disable"
grep: can't open ../../../../var/opt/SUNWstade/DATA/WWN_MAP
"a5ktest: Started."
grep: can't open ../..//DATA/WWN_MAP
"Write/Read Device Buffer Loopback: Pattern: 0x7e7e7e7e"
"Write/Read Device Buffer Started: pattern: 0x7e7e7e7e"
"Write/Read Device Buffer Completed: 1000 passes"
"Write/Read Device Buffer Loopback: Pattern: 0x1e1e1e1e"
"Write/Read Device Buffer Started: pattern: 0x1e1e1e1e"
"Write/Read Device Buffer Completed: 1000 passes"
...
...
"Write/Read Device Buffer Loopback: Pattern: 0xfdfdfdfd"
"Write/Read Device Buffer Started: pattern: 0xfdfdfdfd"
"Write/Read Device Buffer Completed: 1000 passes"
"number of blocks 17682084"
"Testing 176820 blocks on disk"
"blk_base(),base=1,nblk=17682084"
"Start AsyncIO test from block 1 to 176821. "
"Start SyncIO test. "
"Test passed."
"End of Rawtest: /dev/rdsk/c0t22d0s2"
"Checking RDLS counts"
"RDLS counts are the same"
"a5ktest: Stopped successfully."
freya# 

Use luxadm -v display your_a5000 to find the device paths of your socal devices and then add the string ":devctl" to the path when running the socal test:/

freya# ./socaltest -v -o "dev=/devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0:devctl" 
"called with options: dev=/devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0:devctl"
"socaltest: Started."
"Begin socaltest on /devices/sbus@2,0/SUNW,socal@d,10000:0: board 1, slot d, port 0"
"socaltest on /devices/sbus@2,0/SUNW,socal@d,10000:0 done"
"socaltest: Stopped successfully."
freya#

---

Sun Certified Security Administrator exam passed. CV for Halvard "Hal" Halvorsen updated.

posted by hal 20030507 | permalink | path | initial version: 20030506

Just got the news through email that I did pass the Sun Certified Security Administrator for Solaris 9 exam so the cv has been updated.

If the beta test is anything to go by this exam will require quite a bit of work to pass. This is reflected in the pass score which is set at a lower than normal 60% (SCNA pass level is 70%). I scored 66% on the beta test - the beta had roughly 150 questions so I am happy with that.

About the only hint I can provide without giving the game away is that this is a Sun certification so make sure you are prepared for the Solaris specifics like the Basic Security Module (BSM), Role-Based Access Control (RBAC - overly complex? reminds me of setting up serial ports and modems) and ACL's.

If anyone can think of a good abbreviation for Sun Certified Security Administrator - let me know.

---