ST#53793 for the primary motivation for this.

  1. Edit /etc/hosts - on this box it was nearly empty, guess it never got updated. The host's idea of its own IP and hostname are near the top.
  2. Edit /etc/sys_id - it's plaintext, just has the non-FQ hostname.
  3. Edit /etc/config/netif.options - for cthulu 129.97.75.x -> cthulhu 129.97.7.x there wasn't anything to change.

That takes care of the base OS's idea of name and IP. xhier still needs to be edumacated though, and that might be a bit tricky. In some ways, it might be easier to uninstall xhier packages first, then reinstall - same thing we do for an OS upgrade. Robyn sez to have a look at the renumber command. It knows about the OS stuff too.

Create a renumber_mappings file:
cthulu cthulhu

And try running it:

1>(root)@cthulu[147]% renumber -m renumber_mappings 
renumber FYI: /etc/config/cesag needs to be changed
Index: /etc/config/cesag
Binary files /etc/config/cesag and /tmp/ren_1153643/ren_tmp differ
renumber FYI: /fsys1/.software/local/os-extras/data/gateway needs to be changed
Index: /fsys1/.software/local/os-extras/data/gateway

It seems to have worked with respect to the operating system, except one file was missed, /etc/config/static-route.options.

It drove xhier bonkers though:

1>(root)@cthulhu[106]% xh-install xhier
xh-set-access-rights: The access-rights file for this host
xh-set-access-rights:   ("cthulhu.cs") is likely incorrect
xh-set-access-rights:   as it doesn't (completely) describe
xh-set-access-rights:   how the "xhier" package arrived here.
xh-set-access-rights: Please modify it on the administration
xh-set-access-rights:   master host for the "xhier" package
xh-set-access-rights:   so that it describes both outgoing
xh-set-access-rights:   AND incoming distribution paths.
xh-set-access-rights: See "man xhier-config" and
xh-set-access-rights:     "man access-rights" for details.

And cthulhu won't let me send it files from cscf.cs, from where it draws admin stuff. Edit access-rights on cthulhu by hand though, and xh-install xhier works just ducky.

Netscreen bugs can cause protocol failure in circuit setup messages - Jason knows what to do, it's the same thing that breaks NFS every now and again.

-- MikePatterson - 06 Jul 2006

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2012-09-06 - BillInce
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback