CAN FI BE IN A DIFFIRENT SUBNET THEN SERVER MANAGEMENT IP

[Jean Paul Enerst]

Hi All,

Quick question here:  OUR FI is in a subnet, let's say(10.1.1.0/24) and of course at the moment the blades IP address are whintin that subnet(DHCP via address pool in SP). Both inband and out of band

Can the inband IP address( IP for vSphere not IPMI-kvm or even both) be in a different subnet. For instance 192.168.16.0/24?

I am running 2.1(3b)A .  I have read that in newer release the inband IP can be different than the OOB. But can't seem to find something for the FI and the BLADES!

I am in the midle of a project where i need to move one of the blade to a total diffrent subnet which is different from the FI. When i changed the IP of that testing blade to a subnet different the FI, i lost network connection and the event showing waiting for the flogi(show npv flogi-tab show the blade is present )... and N5 show incomplete in the arp table!

Thanks,

[Walter Dey]

https://supportforums.cisco.com/t5/unified-computing-system/management-of-blades-outband-and-inband-ip/td-p/2460408

Starting firmware 2.2, you can now access the KVM of the M3 blade server via inband network.  In other words, before  with out of band you can only access the kvm via the same network as your fabric interconnect management network. With inband you can now use the same network that the blades use for data traffic.

Caveats:
Only Cisco UCS B-M3 and C-M3 later server platforms support inband CIMC access. Inband CIMC access for Cisco UCS B-M1, B-M2, and Cisco UCSC-M1, and C-M2 server platforms is not supported.

One OOB IP addresses is taken out of the mgt IP pool, for every blade inserted in a chassis slot.

One Inband IP address per service profile is needed, indep. if the profile is associated or not.