When is the In-Band KVM pool required as part of IMC Access Policy?

[SIMMN]

With the good old UCSM days, I have always used Out-of-Band KVM or blade management pools which is the same subnet as the UCS FI MGMT.

With the Intersight or IMM, I heard there are specific use cases that the In-Band management or In-band KVM pools would be mandetory...But I have difficulty finding any information on when the In-Band management would be required...Anyone could help?

[Brian Morrissey · Accepted solution]

For servers it used to be for SNMP, vMedia, and Syslog policies it required an inband IP but that has since changed.

The only remaining item that I am aware of for servers that requires inband is using Intersight's built-in OS install wizards/workflows ( https://www.intersight.com/help/saas/resources/OSinstallguide#os_install_steps )

"Before initiating OS installation on your server, ensure to configure In-Band in the IMC Access Policy. You cannot proceed with OS installation without IMC Access policy (In-Band) configuration"

The other part that requires inband management is if you are going to query the chassis IFM/IOMs via SNMP  (https://www.cisco.com/c/en/us/td/docs/unified_computing/Intersight/b_Intersight_Managed_Mode_Configuration_Guide/b_intersight_managed_mode_guide_chapter_01100.html).  Only In-Band configuration is supported for Chassis IMC Access Policy.

[SIMMN]

Thanks!

I somehow feel the "Only In-Band configuration is supported for Chassis IMC Access Policy." is outdated as well...

[Brian Morrissey]

It'll successfully deploy the profile on the chassis but it'll ignore any OOB config in the IMC access policy: