From: Tru64 User (tru64user@yahoo.com)
Date: Tue Jul 09 2002 - 16:57:46 EDT
Thanks go to Selden for hie re-assuring, educating
email. Response below.
--- Selden E Ball Jr <SEB@LNS62.LNS.CORNELL.EDU>
wrote:
>
> Richard,
>
> You wrote
>
> > OK, thinking out loud.
>
> OK, I'll think out loud back to you ;-)
>
> We have several systems that have had fddi removed
> and some that have had second e'net interfaces added
> but I don't think we've actually replaced fddi by
> e'net.
>
> > I have to replace our FDDI cards with Ethernet
> Cards,
> > on a tru64 v4.0g 4100 system.
> > It currently have one "tu0: DEC TULIP (10/100)
> > Ethernet Interface" and one FDDI. tu0 will remain,
> and
> > an add a second, tu1, taking off fd0.
>
> > Questions:
> > 1. What are the minimal steps i can take (minimal
> > downtime), assuming i get a similar NIC card to
> one
> > already existing? (My assumption: Since system
> already
> > knows about type, wont need to load all drivers
> again)
>
> doconfig causes the correct drivers to be loaded as
> a result of
> the changes it makes to the system configuration
> file.
> doconfig also creates any necessary device files and
> rebuilds the kernel.
>
> > 2. What do i do with the old FDDI card
> configuration,
> > or simply remove the hardware?
>
> Simply remove the hardware is one option.
>
> However...netsetup puts network software settings in
> /etc/rc.config
>
> You may want to remove the settings for fd0 from
> rc.config
> by using rcmgr
> fd0's settings are probably in rc.config as NETDEV_1
> tu0 is probably NETDEV_0
> (man rcmgr for more details)
>
> > I have read the previous post (included below)from
> a
> > summary, and deduced the following plan::
>
> You left out one step (5a)
>
> > 1. shutdown system
> > 2. Pull old hardware out
> > 3. Install new hardware
> > 4. Boot with genvmunix
> > 5. doconfig
> ==>5A. Move new kernel in place
> > 6. Reboot
>
> I assume you have steps 7/8/9 because you have your
> own local
> proprietary changes to the configuration file. If
> you don't have
> any changes of your own then you can avoid 7/8/9/10
> entirely.
> Alternatively, you could merge your local changes
> into the
> configuration file after step 5 and avoid steps 5a
> and 6:
> strictly speaking, a second reboot is not necessary,
> although
> if you do reboot, you can take that time to check to
> make sure
> the new hardware is working before you make more
> changes of your own.
>
> In other words, move step 11 to before step 7 and
> test.
>
>
> > 7. Manual merge kernel configs
> > 8. doconfig -c
> > 9. Move new kernel in place
> > 10.Reboot
> > 11.netconfig
>
> > Any shortcuts or corrections?
> > Once I start this procedure,I have to do it at the
> > quickest pace possible, getting it right the first
> > time.
>
> I'd want to reboot after running netconfig to make
> sure
> the appropriate services are being started at boot
> time
> on the new interface.
>
> > PS. Request recommendation for NICs/vendor
>
> DEC/Compaq DE600-AA.
>
> We've continued to use DE500-AA or -BA cards bought
> on the used market.
> While they do have the problem that they aren't
> reliable in
> 100Mbit full duplex, there are no concerns about
> support by
> particular O/S releases.
>
> Generic 3rd party interfaces don't work.
> Only a very few licensed 3rd party interfaces are
> compatible
> with Tru64 -- ITI used to make some, but not since
> they got bought out.
>
> I hope this helps a little.
>
> Selden
> ======
> Selden E. Ball, Jr.
>
> Cornell University Voice:
> +1-607-255-0688
> Laboratory for Elementary-Particle Physics FAX:
> +1-607-255-8062
> LT105 R. R. Wilson Laboratory
> http://www.lns.cornell.edu/~seb/
> Dryden Road Internet:
> SEB@LNS.CORNELL.EDU
> Ithaca, NY, USA 14853-8001 HEPnet/SPAN:
> LNS62::SEB = 44284::SEB
>
>
>
> > _Thanks
>
> > Richard
=====
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:46 EDT