Los Angeles1
asked on
AIX, stand alone LPAR
I have a single VIOS and single LPAR running with SEA, and everything is working great
What I need now is a stand alone LPAR (without a VIOS)
I need this somewhat quickly and temporarily
Is there a way to turn off the VIOS and convert the existing LPAR from SEA to one that will have a dedicated ethernet adapter (with no VIOS involved)
That way I could use the existing OS and software once the conversion is done
Is this possible, and how would I go about this ?
Thanks
What I need now is a stand alone LPAR (without a VIOS)
I need this somewhat quickly and temporarily
Is there a way to turn off the VIOS and convert the existing LPAR from SEA to one that will have a dedicated ethernet adapter (with no VIOS involved)
That way I could use the existing OS and software once the conversion is done
Is this possible, and how would I go about this ?
Thanks
ASKER
Out of curiosity, why cant I do th efollowing
1> Disable the SEA Virtual adapter named "Ethernet"
2> Go to the IO tab of the managed profile and create or enable one of the ethernet adapters there to be directly wired to my LPAR ?
Thanks
1> Disable the SEA Virtual adapter named "Ethernet"
2> Go to the IO tab of the managed profile and create or enable one of the ethernet adapters there to be directly wired to my LPAR ?
Thanks
I thought you wanted an LPAR with directly attached network and disks!
If it's just for the network, OK, that's easier.
You can't (or at least shouldn't) "disable the SEA".
The SEA is a bridge between the real adapter(s) of the VIOS and the internal network to which the LPARs are connected, an entity persistent to the VIOS and not to a single client LPAR.
What you can do is remove the virtual Ethernet client adapter from the LPAR configuration and attach a real adapter slot, if there is one left.
Please be aware the the LPAR's network remains configured over the (now obsolete) virtual adapter, so you won't be able to access the LPAR via network after rebooting it.
You must open a virtual terminal and reconfigure the network over the new, real adapter which will show up as ent1/en1. The virtual ent0/en0 will still appear with "lsdev", but now as "Defined" instead of "Available".
If it's just for the network, OK, that's easier.
You can't (or at least shouldn't) "disable the SEA".
The SEA is a bridge between the real adapter(s) of the VIOS and the internal network to which the LPARs are connected, an entity persistent to the VIOS and not to a single client LPAR.
What you can do is remove the virtual Ethernet client adapter from the LPAR configuration and attach a real adapter slot, if there is one left.
Please be aware the the LPAR's network remains configured over the (now obsolete) virtual adapter, so you won't be able to access the LPAR via network after rebooting it.
You must open a virtual terminal and reconfigure the network over the new, real adapter which will show up as ent1/en1. The virtual ent0/en0 will still appear with "lsdev", but now as "Defined" instead of "Available".
ASKER
Sorry I did not describe my requirements properly.
I am going to attempt the following:
1> Remove the virtual ethenet client adapter
2> Attach a real adapter slot
In the VIrtual Adapters tab, I have the following
In the IO tab, I have the following
I assume I should perform the following:
1> In the Virtual Adapters tab, delete the "Ethernet" row
2> Go to the IO tab, and mark the fourth entry as "Required"
3> While keeping the VIOS shutdown, start the LPAR independently of the VIOS
Is this correct ?
Thanks
I am going to attempt the following:
1> Remove the virtual ethenet client adapter
2> Attach a real adapter slot
In the VIrtual Adapters tab, I have the following
Ethernet 2 N/A N/A Yes
Client SCSI 3 VIOS1(201) 3 Yes
Server Serial 0 Any Partition Any Partition Slot Yes
Server Serial 1 Any Partition Any Partition Slot Yes
In the IO tab, I have the following
U78AF.001.WZS00UC-P1-T1 PCI-to-PCI bridge Required 512
U78AF.001.WZS00UC-P1-C34-L1 Ethernet controller 513
U78AF.001.WZS00UC-P1-C35-L1 Fibre Channel Serial Bus 515
U78AF.001.WZS00UC-P1-C34-L2 Ethernet controller 528
U78AF.001.WZS00UC-P1-T2 PCI-E SAS Controller 544
U78AF.001.WZS00UC-P1-C36-L1 Ethernet controller 545
U78AF.001.WZS00UC-P1-C37-L1 Fibre Channel Serial Bus 547
U78AF.001.WZS00UC-P1-C36-L2 Ethernet controller 560
I assume I should perform the following:
1> In the Virtual Adapters tab, delete the "Ethernet" row
2> Go to the IO tab, and mark the fourth entry as "Required"
3> While keeping the VIOS shutdown, start the LPAR independently of the VIOS
Is this correct ?
Thanks
1) ok
2) ok
3) if you bring down the VIOS, where should the LPAR get its disk from?
You still have vscsi to be served, or didn't I understand your setup?
2) ok
3) if you bring down the VIOS, where should the LPAR get its disk from?
You still have vscsi to be served, or didn't I understand your setup?
ASKER
Actually, you did understand my set up
I did not take the disk into consideration until right after I sent the note
Anything else I need to complete this task other than bring up both the VIOS and LPAR ??
Thanks
I did not take the disk into consideration until right after I sent the note
Anything else I need to complete this task other than bring up both the VIOS and LPAR ??
Thanks
... and reconfigure the network over the new entx device, using a virtual terminal, because network access will not be possible.
ASKER
I mkarked the fourth entry in the IO tab as required,
and deleted the "Ethernet" entry in the
VIrtual Adapters tab
I started the VIOS and the LPAR
On the LPAR, I see
#
Did I do something wrong. I do not see what adapter to define using mktcpip
From smitty mktcpip, I see:
The ent
Which one of these should I configure? It does not look like en1 is available
U78AF.001.WZS00UC-P1-C34-L2 Ethernet controller 528
and deleted the "Ethernet" entry in the
VIrtual Adapters tab
I started the VIOS and the LPAR
On the LPAR, I see
# lsdev | grep en
en0 Defined Standard Ethernet Network Interface
en1 Defined 02-00 Standard Ethernet Network Interface
en2 Defined 02-01 Standard Ethernet Network Interface
ent0 Defined Virtual I/O Ethernet Adapter (l-lan)
ent1 Available 02-00 PCIe2 4-port 10GbE Mezz Adapter (a2191007df1033e7)
ent2 Available 02-01 PCIe2 4-port 10GbE Mezz Adapter (a2191007df1033e7)
inet0 Available Internet Network Extension
rcm0 Defined Rendering Context Manager Subsystem
vscsi0 Available Virtual SCSI Client Adapter
#
Did I do something wrong. I do not see what adapter to define using mktcpip
From smitty mktcpip, I see:
Available Network Interfaces
Move cursor to desired item and press Enter.
en0 Standard Ethernet Network Interface
en1 02-00 Standard Ethernet Network Interface
en2 02-01 Standard Ethernet Network Interface
et0 IEEE 802.3 Ethernet Network Interface
et1 02-00 IEEE 802.3 Ethernet Network Interface
et2 02-01 IEEE 802.3 Ethernet Network Interface
F1=Help F2=Refresh F3=Cancel
F8=Image F10=Exit Enter=Do
/=Find n=Find Next
The ent
Which one of these should I configure? It does not look like en1 is available
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
- using IVM create a new LPAR with the desired characteristics and
- assign the required adapter slots to it
- cable the adapters for SAN and Ethernet access
- customize your SAN zoning so that the new LPAR can see a sufficient number of disks to accomodate the OS.
- using your installation DVDs install all "devices.*" filesets into the old LPAR
- pull an mksysb of the old LPAR to DVD, tape or NIM
- shut down the old LPAR
- boot the new LPAR from the mksysb medium and restore the old image
- done
You could also make the disks of the old LPAR available to the new one, shut down the old LPAR and boot the new one.
Using new disks has the advantage that nothing of the old environment can be destroyed by accident, because this environment remains untouched.
If you don't have the required adapters you must create a full system LPAR, which would involve deleting the old LPAR (install all devices.* stuff and pull an mksysb first!) and the IVM, then boot the managed system itself from the mksysb media to build the full system LPAR from it.