IP address allocation for service profile
Hi everyone,
I know the reason why we would need an ip address for a blade from mgmt ip pool, however, is there any particular reason why we would need that for a service profile ?
Mark said it is required just when a third party stuff comes into play, and actually what is that ????
Thanks so much.
JF
Comments
If the IP is with the service profile, it travels with the service profile if it gets re-associated to a different blade in the same or a different chassis. If the IP belongs to the blade, it’s the same address regardless which service profile is associated. I would say it makes more sense to do it the first way than to assign it to the blade, because if you want to KVM in you want to know the IP address of the “service”, e.g. the ESXi instance or Windows install, not the blade.
Brian McGahan, CCIE #8593 (R&S/SP/Security), CCDE #2013::13
[email protected]
Internetwork Expert, Inc.
http://www.INE.com
From: [email protected] [mailto:[email protected]] On Behalf Of powerfongfong
Sent: Wednesday, June 05, 2013 6:58 PM
To: Brian McGahan
Subject: [CCIE DC] IP address allocation for service profile
Hi everyone,
I know the reason why we would need an ip address for a blade from mgmt ip pool, however, is there any particular reason why we would need that for a service profile ?
Mark said it is required just when a third party stuff comes into play, and actually what is that ????
Thanks so much.
JF
INE - The Industry Leader in CCIE Preparation
http://www.INE.com
Subscription information may be found at:
http://www.ieoc.com/forums/ForumSubscriptions.aspx
Right, you would almost always want to IPMI/KVM to the SP IP address, not the blade. Unless you wanted to watch the assoc/disassoc process occur, then you'd only be able to KVM to the blade to watch that process.
Cool, so is there any difference between KVM to the service profile and KVM to the blade that the specific service profile is associated to ?
Thanks
JF
Not while the SP is associated to the blade, no.
Got it, cheers!