I am getting the folowing message when trying to launch a KVM session from the KVM Launch Manager page "The IP address to reach the server is not set.", ok so of course we check and the IP address is set and on the same subnet as the IC's. I can also get a successful KVM console from within the UCS manager (2.0(s)). Any ideas?
Sounds like you don't have enough IPs in your Management IP Pool - can you verify? By setting your Service Profile to "Pooled" you need to have enough IPs for each blade PLUS every Service Profiles using "pooled" management IP.
Ex.
Let's say you have 8 blades and you set the Service Profile Management IP to "pooled". You would need 8 IPs for the blades, and ANOTHER 8 for the service profile. This means you need at least 16 available IPs in the Management Pool. The blade CIMC IPs remain static, but the Service Profile IP will be mobile. This gives you two IPs per blade+service profile.
Yes I can ping both FI's from the client and the IP KVM pool has the correct information. I did change the IP's in the policy for the KVM pool and ever since it has not worked via the web.....
Are you assigning a Management IP to your Service Profiles (which follow the service profile from blade to blade) or are you just using the built-in default Management IP pool (which is static and remains assigned to the blade)?
Can you also paste the output of the follow command from the UCSM CLI:
Sounds like you don't have enough IPs in your Management IP Pool - can you verify? By setting your Service Profile to "Pooled" you need to have enough IPs for each blade PLUS every Service Profiles using "pooled" management IP.
Ex.
Let's say you have 8 blades and you set the Service Profile Management IP to "pooled". You would need 8 IPs for the blades, and ANOTHER 8 for the service profile. This means you need at least 16 available IPs in the Management Pool. The blade CIMC IPs remain static, but the Service Profile IP will be mobile. This gives you two IPs per blade+service profile.
