|
||||||||||||
|
|
|
|
 |
||||||||
 |
renaming board name (NIC) |
 |
|
 |
10-28-2008, 06:08 PM
|
#1 |
|
Guest
Status:
Posts: n/a
|
renaming board name (NIC)
think this will mess up the BM filters. Is there a safe way to do this or will I have to wipe the filters and start over with the defaults? TIA |
|
 |
 |
 |
|
Re: renaming board name (NIC) |
|
|
|
|
10-28-2008, 09:54 PM
|
#2 |
|
Guest
Status:
Posts: n/a
|
Re: renaming board name (NIC)
In article <490738E0.51D5.00D6.0@nospam.com>, John wrote:
> I'm setting up a BM3.9 sp1 server. I would like to rename the NIC's but I > think this will mess up the BM filters. > Is there a safe way to do this or will I have to wipe the filters and start > over with the defaults? You will indeed have to redo the filters. If you know what you are doing, it's pretty easy, but you have to stick in a filtsrv migrate operation when done editing files. The whole procedure is giving in my BMgr filtering book (see URL below). You will first (absolutely!) want to backup the .cfg files in the ETC directory. You will need to unload filtsrv.nlm before editing the filters.cfg file, or before copying an edited version to ETC. (Or it will be overwritten with NDS-stored version). Edit the tcpip.cfg, netinfo.cfg and filters.cfg file to rename the interfaces involved. Delete any netinfo.chk file or change its contents to 0. Wipe the filters out in NDS (in the NBMrulecontainer), copy edited files to ETC and do a filtsrv migrate procedure. Then reinitialize system to put all new values in place. (May be best to unload LAN drivers first, but usually doesn't matter). I do this a lot. Craig Johnson Novell Support Connection SysOp *** For a current patch list, tips, handy files and books on BorderManager, go to http://www.craigjconsulting.com *** |
|
|
|
|
|
|
Re: renaming board name (NIC) |
|
|
|
|
11-03-2008, 03:41 PM
|
#3 |
|
Guest
Status:
Posts: n/a
|
Re: renaming board name (NIC)
I did what you outlined here but when I reinitialize the server, the old
board names return in the TCPIP.CFG file and show up with the old names under INETCFG. The filters seemed to be holding the new names though but if I select to add a new filter, the old names are my choices. I did delete the netinfo.chk file before starting this process. I also unloaded filtsrv, ipflt and had all the BM services stopped and inetcfg unloaded. Am I missing a step? >>> On 10/28/2008 at 7:54 PM, Craig Johnson<craigsj@ix.netcom.com> wrote: > In article <490738E0.51D5.00D6.0@nospam.com>, John wrote: >> I'm setting up a BM3.9 sp1 server. I would like to rename the NIC's but > I >> think this will mess up the BM filters. >> Is there a safe way to do this or will I have to wipe the filters and > start >> over with the defaults? > > You will indeed have to redo the filters. If you know what you are > doing, > it's pretty easy, but you have to stick in a filtsrv migrate operation > when > done editing files. The whole procedure is giving in my BMgr filtering > book > (see URL below). > > You will first (absolutely!) want to backup the .cfg files in the ETC > directory. > > You will need to unload filtsrv.nlm before editing the filters.cfg file, > or > before copying an edited version to ETC. (Or it will be overwritten > with > NDS-stored version). > > Edit the tcpip.cfg, netinfo.cfg and filters.cfg file to rename the > interfaces > involved. Delete any netinfo.chk file or change its contents to 0. > > Wipe the filters out in NDS (in the NBMrulecontainer), copy edited files > to > ETC and do a filtsrv migrate procedure. Then reinitialize system to put > all > new values in place. (May be best to unload LAN drivers first, but > usually > doesn't matter). I do this a lot. > > Craig Johnson > Novell Support Connection SysOp > *** For a current patch list, tips, handy files and books on > BorderManager, go to http://www.craigjconsulting.com *** |
|
|
|
|
|
|
Re: renaming board name (NIC) |
|
|
|
|
11-10-2008, 08:26 PM
|
#4 |
|
Guest
Status:
Posts: n/a
|
Re: renaming board name (NIC)
In article <490EFF8C.51D5.00D6.0@nospam.com>, John wrote:
> Am I missing a step? > Somehow, yes, unless since you did this you tried a reboot and things came up ok. The board names are created in netinfo.cfg, and inetcfg will show the names that are in that file. Inetcfg, of course, will write them into that file. If you don't want to edit netinfo.cfg, then you can delete the boards in Inetcfg and re-enter them. If you do that, you lose the nat settings and IP addresses so you have to redo those as well (in Inetcfg). Tcpip.cfg holds the nat definitions and some routing settings. The board names created in netinfo.cfg are referenced in tcpip.cfg, so the names here have to match netinfo.cfg. Filters.cfg (until BM 3.7) held the filters and exceptions (and custom definitions). It now holds (usually) a copy of those, while the source has been moved into NDS. You can use a valid copy of filters.cfg to migrate data into NDS as I described earlier, using a filtsrv migrate procedure. If you modify all the files correctly, you should be able to either unload the lan drivers and reinitialize system, or just reinitialize system. Netinfo.cfg is where you can get yourself into trouble as the syntax is strict. Also, those # symbols there are NOT comment characters. Craig Johnson Novell Support Connection SysOp *** For a current patch list, tips, handy files and books on BorderManager, go to http://www.craigjconsulting.com *** |
|
|
|
|
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
|
|
|||
|
|
Powered by: vBulletin Version 3.0.7
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
© 2003-2004 All Rights Reserved GroupBrowser LLC.
