Things To Remember While Doing Upgrades on Mission Critical Sun Equipment….

1a: Sending Stop-A with non-Sun keyboards or over a telnet connection

With a terminal server, the terminal is hardcoded to a “cli” interface which, in turn, telnets to the console port on the destination host. The point is to get the *telnet* to generate a break, which can be done by:

Press ctrl-] (or whatever is the telnet escape sequence)
At the telnet prompt, enter “send break”

Note that the terminal server port hosting the console must be configured NOT to pay attention to breaks and instead pass it on to the server.

1b: Sending Stop-A with non-Sun direct connect keyboards (such as those connected to a KVM)
Rumor has it that “break” or “ctrl-break” or even “~#” are equivalent to Stop-A.

2: Veritas Volume Manager can/will break. You may be able to set environment variables to make the command line tools work, but it wont fix the GUI.

If you see an error like this

vxdg init data-sauron u01=c2t46d2 vxdg: fatal: relocation error: file /etc/vx/slib/ symbol _libc_register_forkhandler: referenced symbol not found

then you’ll have to do a jig like this


And get use to the vxdg and vxassist command like this

vxdg init grpname grpname01=c1t1d0
vxdg -g grpname adddisk grpname02=c#t#d#
vxassist -g grpname make newvol 50m
vxassist -g grpname make volname 200m layout=mirror disk01 disk02

3: ufsdump does its job, but it’s far too slow when the source file for the restore is on an NFS share. Put the source file on a local disk and restore from there.

One thought on “Things To Remember While Doing Upgrades on Mission Critical Sun Equipment….

  1. just want to say thank so much for this page. Fantastic … got me out of a quandry

Comments are closed.