If the NICDEF in the directory specifies a vswitch or LAN for automatic connection at logon, then a DEFINE for that device will also automaically connect it.
You have multiple ways to get where you want to go, but a good start will be to update the directory first with what you want the final configuration to look like. This way you won't get automatic couples associated with your "old" configuration. Brian Nielsen On Thu, 13 Sep 2007 07:55:00 -0500, Berry van Sleeuwen <[EMAIL PROTECTED]> wrote: >Hello list, > >When I define a NIC for the linuxmachine I use something like: > >DEFINE NIC F00 TYPE QDIO >COUPLE F00 SYSTEM OSNLINUX > >In the directory the NIC is specified as special. > >In one machine we have defined three NIC's. F00 coupled to AOSN, F10 >coupled to AOSNBU and F20 coupled to OSNLINUX. The F20 was created to move >the linuxmachine to vswitch. F00 was the old connection to guest LAN. >Today we had to disconnect F00 from the guest LAN and then redefine F00 to >connect to the Vswitch. Then the F00 would replace the F20 device and th e >machine would be moved to the vswitch. > >I have found something I can't explain. The NIC F00 was coupled to AOSN >just after the DEFINE command, no couple was needed. But we wanted the NIC >to be coupled to OSNLINUX so the couple to AOSN was not correct. I did not >expect the define to automatically connect to the guest LAN. What could be >the logic? Did I have to UNCOUPLE first? > >Thanks, Berry. >======================== ========================= =======================
