Blogs Classifieds Downloads FlashChat Gallery Googlemap Invite Friends Links Projects Reviews Wiki
 


Welcome to the pSeries Tech Forums, our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software.

You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments.

Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community.

Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Our Sponsors
Want to advertise?  


Reply
 
LinkBack Thread Tools
  #1  
Old December 2nd, 2007
mshulman1980's Avatar
mshulman1980 Offline
Member
 
Join Date: October 2006
Posts: 38
VLAN security on virtual ethernet

I need to deploy a number of outward facing micropartitions on a p570 that my organization wants to be isolated from one another on the network, so in the event that a single lpar is compromised, it's only possible to even communicate with a small subset of servers out there.
My concern is, if all of the LPARs are micropartitions and are using the same VIO pair (many of the lpars will actually be on the same subnet and vlan), is it possible for them to be isolated from one another since interlpar traffic doesn't exit the frame, but rather travels down the backplane, hits the virtual ethernet switch and then gets routed appropriately? Our firewall rules happen at the physical switch level, and as far as I know those rules won't propogate down to the virtual switch.
If the lpars are exposed to one another, it increases our risk factor.
The VIO networking that we use tends to be mostly out of the box SEA failover stuff. However, I'm open to changing that configuration if it will fix this problem.

Thanks in advance for your advice on this.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #2  
Old December 4th, 2007
cdelgadop's Avatar
cdelgadop Offline
Senior Member
 
Join Date: November 2006
Posts: 310
Send a message via MSN to cdelgadop
Re: VLAN security on virtual ethernet

Hi

Your firewall rules protect your internal servers from bogus comming from outside. Then some filters at physical LAN switches levels may be applied.

Inside your pSeries servers there's a sort of LAN Switch that uses real memory addresses to simulate an ARP table to send data to each virtual ethernet interface, that's why communications are so fast. Now let's say you have a physical Switch in your organization. You can protect communications by creating domains called VLANs, you can also configure so communications between servers in different VLANS is not allowed, by applying some rules to packets travelling those VLANS (as well as your Switch has some TCPIP Layer 3 capabilities).

You can do the same when configuring your Virtual LAN adapter at HMC level in the profile of the client LPAR. You can tell any given Virtual LAN adapter to accpet packets tagged with given VLAN ID. This way you can secure your communications at LAN level. You can also create firewall rules at AIX level and apply best recommendations so you internal OS would be hardenned in case of intrussion.

Hope this helps
__________________
cd3lgad0p
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #3  
Old January 29th, 2008
kbr's Avatar
kbr Offline
Junior Member
 
Join Date: November 2007
Posts: 20
Re: VLAN security on virtual ethernet

you can also maybe think about using lpar without vio... assign 1 (or more) physical card to each partition will simplify your isolation problem...
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #4  
Old January 31st, 2008
vasco's Avatar
vasco Offline
Junior Member
 
Join Date: April 2007
Location: Lisbon, Portugal
Posts: 28
Re: VLAN security on virtual ethernet

If the compromised partition is the VIO, then all is wide open.

It's safer to use physical ethernets assigned by the HMC (wich wont have internet access, we hope), it will be slower and more expensive.

The AIX firewall should be used in every lpar to enforce rules about what can came in (this can be done with virtual or physical interfaces).
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #5  
Old January 31st, 2008
Administrator's Avatar
Administrator Offline
Administrator
 
Join Date: May 2006
Posts: 111
Blog Entries: 3
Re: VLAN security on virtual ethernet

Consider cd3lgad0p'sanswer the correct one and ignore the other two. Your network administrator should be able to secure your servers with the information cd3lgad0p provided.
__________________
$ PATH=pretending!/usr/ucb/which sense
no sense in pretending!
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #6  
Old January 31st, 2008
vasco's Avatar
vasco Offline
Junior Member
 
Join Date: April 2007
Location: Lisbon, Portugal
Posts: 28
Re: VLAN security on virtual ethernet

Quote:
Originally Posted by Administrator
Consider cd3lgad0p'sanswer the correct one and ignore the other two. Your network administrator should be able to secure your servers with the information cd3lgad0p provided.
You are joking... right ???
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #7  
Old January 31st, 2008
kbr's Avatar
kbr Offline
Junior Member
 
Join Date: November 2007
Posts: 20
Re: VLAN security on virtual ethernet

lol :-) consider vasco and mine right and not admin...
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #8  
Old January 31st, 2008
mshulman1980's Avatar
mshulman1980 Offline
Member
 
Join Date: October 2006
Posts: 38
Re: VLAN security on virtual ethernet

Yes, assigning physical NICs to every lpar would be the easiest and probably most secure choice, it isn't really an option since we're due to the fact that our planning group is targetting somewhere from 40-50 lpars on each 570, so there's the issue of how many slots we would need, between at least 2 NICs for each network on each LPAR, getting all of the fibre adapters set up within the VIO, etc etc.

There is a command called viosecure which I am still researching which addresses this problem.

Installing ipsec (or some varient thereof) on each LPAR would probably be a good idea... however I'm not sure that I have the time or expertise to put it out there in some maintainable fashion.

Thanks all for your responses.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #9  
Old January 31st, 2008
kbr's Avatar
kbr Offline
Junior Member
 
Join Date: November 2007
Posts: 20
Re: VLAN security on virtual ethernet

For me the best way to secure a lan still using physical interfaces... I understand that your planning make it difficult, but sometimes virtualizing everything is not the best choice...

It's my opinion but I think if you talk with security experts they will say you the same...

if you multiply entry points you multiply risks...

That's a reason why I don't think using csm machine with trusted root account on each nodes is not always a good choice...

But it's my humble opinion... ;-)

Last edited by kbr; January 31st, 2008 at 11:04.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #10  
Old January 31st, 2008
vasco's Avatar
vasco Offline
Junior Member
 
Join Date: April 2007
Location: Lisbon, Portugal
Posts: 28
Re: VLAN security on virtual ethernet

Quote:
Originally Posted by mshulman1980
There is a command called viosecure which I am still researching which addresses this problem.
I don't know what that command does, maybe it will help.

Quote:
Originally Posted by mshulman1980
Installing ipsec (or some varient thereof) on each LPAR would probably be a good idea... however I'm not sure that I have the time or expertise to put it out there in some maintainable fashion.
IBM calls IPsec to IP filters, and that's what you need to configure. (# smitty ipsec).
But, as kbr refered there is the spoofing problem (at MAC or TCP/IP level), so maybe the only _good_ answer is really IPSEC (secure encrypted tunnels between the lpars). But you'll have some communications overhead and have to spend aditional RAM and CPU resources.

And managing the PKI infrastruture with tunnels between 40 or 50 lpars wont be a piece of cake.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

These are the 100 most searched terms
Search Cloud
0042-001 0042-001 nim 0513-001 the system resource controller daemon is not active 0513-001 the system resource controller daemon is not active. 0514-061 0514-061 cannot find a child device 0514-061 cannot find a child device. 0516-787 0516-787 extendlv 0516-787 extendlv: maximum allocation for logical volume 110000ac aa00e1f3 aio aix aix aio aix freeware aixif_arp_dup_addr b150f22a b181fb53 ba010004 c1001020 d133c002 dacnone dcb47997 dlpar fcp_array_err6 fget_config gnu tar aix gsclvmd gtar aix hi yall hmc root password hmc vmware hscl05db ibm p6 ibm p6 520 libpopt aix libpopt.a libpopt.a(libpopt.so.0) is needed by rsync-2.6.2-1 migratelv mksysb navisphere agent nim server pseries pseriestech rsync aix sc_disk_err4 scan_error_chrp vio server websm xhost file ... powered by Simple Search Cloud


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by vbWiki Pro 1.3 RC5. Copyright ©2006-2007, NuHit, LLC

vBulletin Skin developed by: vBStyles.com


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48