Problem Description:
• customer is planning to upgrade the infra to version 20.9.x
• as recommended by the BCS team ( Cisco Business critical service team ) , customer requested to execute "Aura Script”.
• Aura script identified the "CPU Clock configured is 2.6 instead of 2.8"
• CloudOps upgraded the infra for customer from 16 CPU's to 32 CPU's , but clock remain the same.
• customer want to confirm if they can move forward with CPU clock 2.6 or otherwise CloudOps required to upgrade the infra to VM type with clock 2.8.
DSV hosted on azure
that makes sense usually we can find out type of hypervisor its hosted in kernl logs
In Kern.log while bootup it will show Microsoft
or get a linux command to identify if Azure infrastructure. (Get source command)
Problem Description:
• customer is planning to upgrade the infra to version 20.9.x
• as recommended by the BCS team ( Cisco Business critical service team ) , customer requested to execute "Aura Script”.
• Aura script identified the "CPU Clock configured is 2.6 instead of 2.8"
• CloudOps upgraded the infra for customer from 16 CPU's to 32 CPU's , but clock remain the same.
• customer want to confirm if they can move forward with CPU clock 2.6 or otherwise CloudOps required to upgrade the infra to VM type with clock 2.8.
DSV hosted on azure
that makes sense usually we can find out type of hypervisor its hosted in kernl logs
In Kern.log while bootup it will show Microsoft
or get a linux command to identify if Azure infrastructure. (Get source command)