Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2779
Views
15
Helpful
6
Replies

Modifying a vNIC Template adding a new VLAN (400)

Go to solution
mg.figueroa
Level 1
Level 1

‎09-10-2015 09:16 AM - edited ‎03-01-2019 12:21 PM

Hi:

  I have a Cisco UCS B200 M2, UCSM 2.2(3e).  I just created a new vlan 400 (BKP_192.168.6.0). When I proceed to modify the vNIC Templates to add the newly created vlan 400, I receive the following warning message:

 

Modify Vlans

Your change:

Create: Network Vlan_BKP_192.168.6.0 (org-root/lan-conn-templ-DOL-prodA/if-Vlan_BKP_192.168.6.0)

Will require User Acknowledgement before the Reboot of:

Service Profile ESX-03 (org-root/ls-ESX-03) [Server:sys/chassis-1/blade-3]

Service Profile ESX-04 (org-root/ls-ESX-04) [Server:sys/chassis-2/blade-1]

Service Profile ESX-05 (org-root/ls-ESX-05) [Server:sys/chassis-2/blade-2]

Service Profile ESX-01 (org-root/ls-ESX-01) [Server:sys/chassis-1/blade-1]

Are you sure you want to apply the changes?

Pres Yes to disregard the warning and submit changes, No to quit the wizard

or Cancel to make changes to the current configuration

 

I found in a forum after a google search that when I modify a vNIC Template adding a vlan is a task that do not requires a hosts/blades reboot.

 

In this case, how do I proceed to successfull add the new vlan in the vNIC Templates? I have a total of 40 production VMware virtual servers distributed in these 4 hosts/blades.

 

Please refere to the attached document for more info

 

Thanks

 

Miguel Figueroa

1 person had this problem
Preview file
381 KB
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Justin Welch
Level 1
Level 1
In response to mg.figueroa

‎09-10-2015 11:52 AM

Hello,

 

INFO][0xab9e8b90][Sep 10 12:58:50.728][ls:analyzeConfig]       bindingChange 0, hostEthIfChange 0,hostEthIfProfileChange 0, hostEthIfQosChange 0,hostEthIfQosHostControlChange 0, hostEthIfNwCtrlChange 0, hostEthIfProfileRedeployRequired 0,hostFcIfChange 0, hostFcIfProfileRedeployRequired 0,hostFcIfPersChange 0, hostFcIfProfileChange 0, hostFcIfQosChange 0, hostFcoeIfChange 0, hostIfPCIeChange 0, vifChange 0, vlanChange 1, vsanChange 0, ipChange 0,bootOrderChange 0, biosProfileChange 0, bladeIdentityChange 0,agentPolicyChange 0, biosFwChange 0,storageControllerFwChange 0, adaptorHostFwChange 0,adaptorNwFwChange 0, mgmtControllerFwChange 0,localDiskPolicyChange 0, pinChange 0, solChange 0,flexFlashConfigChange 1, cimcVmediaConfigChange 0,epAuthChange 1,bootVnicChange 0, bootPXEChange 0, boardCtrlFwChange 0, errInsufficientResources 0,LocalDiskFwChange 1,pnuosConfig 1, rebootRequired 1,ConfigRename 0,FcZoneChange 0,failed 0,

 

Notice the items with a 1 next to them. The servers want to reboot to for:

flexFlashConfigChange 1

LocalDiskFwChange 1

 

You can also see your VLAN change pending:

vlanChange 1

 

 

Hope this helps.

 

Justin

View solution in original post

6 Replies 6

Go to solution
Justin Welch
Level 1
Level 1

‎09-10-2015 09:51 AM

Hello,

 

Usually there is another task such as a firmware update this is waiting to run in the background. If you want to see what is causing this start an SSH session to one of your fabric interconnects. Be sure you are logging the session and run the following commands:

connect local-mgmt

tail-mgmt-log svc_sam_dme

 

now try to apply the vlan to the template again. You should see a bunch of logging output in the SSH session. If you can put that in your next post we can probably determine what else is pending that is making the server want to reboot.

 

 

Thanks

Justin

Go to solution
mg.figueroa
Level 1
Level 1
In response to Justin Welch

‎09-10-2015 11:41 AM

Hi Justin:

 I used putty for the ssh session. This what appears as soon as the modify vlan user ack message appears (the last screen shot inside the word doc I sent in the first post).

 

]
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:checkPinning]        ConfigIssues::checkPinning (org-root/ls-ESX-01/ether-eth0)(0)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:allocateEthIfVif]    Dealing with DcxVif with Id[805], switchId[1]
[INFO][0xab9e8b90][Sep 10 12:58:50.725][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-eth-1
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:setVlanChange]       ConfigChange: setVlanChange (FcManager::configFcIfVsans adaptor vlan NameChange or SwitchIdChange or LcChange Evaluation)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:setVlanChange]       ConfigChange: setVlanChange (FcManager::configFcIfVsans switch vlan NameChange or SwitchIdChange or LcChange Evaluation)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][app_sam_dme:config]     HostEthIfProfile::config: org-root/ls-ESX-01/ether-eth0, hostEthIf: sys/chassis-1/blade-1/adaptor-1/host-eth-1
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:checkPinning]        ConfigIssues::checkPinning (org-root/ls-ESX-01/ether-eth0)(0)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:allocateEthIfVif]    Dealing with DcxVif with Id[806], switchId[2]
[INFO][0xab9e8b90][Sep 10 12:58:50.725][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-eth-1
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:setVlanChange]       ConfigChange: setVlanChange (FcManager::configFcIfVsans adaptor vlan NameChange or SwitchIdChange or LcChange Evaluation)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:setVlanChange]       ConfigChange: setVlanChange (FcManager::configFcIfVsans switch vlan NameChange or SwitchIdChange or LcChange Evaluation)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][app_sam_dme:config]     HostEthIfProfile::config: org-root/ls-ESX-01/ether-eth0, hostEthIf: sys/chassis-1/blade-1/adaptor-1/host-eth-1
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:config]              oper vcon: 1
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:configureEthVnics]   STATIC/DYNAMIC going thru org-root/ls-ESX-01/ether-eth1 (orig assigned:1)
[INFO][0xab9e8b90][Sep 10 12:58:50.725][ls:configureEthVnics]   host if (id:2)(dn:sys/chassis-1/blade-1/adaptor-1/host-eth-2)
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:config]              Setting OperOrder on VicDn[org-root/ls-ESX-01/ether-eth1], OperOrder[2]
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:checkPinning]        ConfigIssues::checkPinning (org-root/ls-ESX-01/ether-eth1)(0)
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:allocateEthIfVif]    Dealing with DcxVif with Id[807], switchId[2]
[INFO][0xab9e8b90][Sep 10 12:58:50.726][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-eth-2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][app_sam_dme:config]     HostEthIfProfile::config: org-root/ls-ESX-01/ether-eth1, hostEthIf: sys/chassis-1/blade-1/adaptor-1/host-eth-2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:checkPinning]        ConfigIssues::checkPinning (org-root/ls-ESX-01/ether-eth1)(0)
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:allocateEthIfVif]    Dealing with DcxVif with Id[808], switchId[1]
[INFO][0xab9e8b90][Sep 10 12:58:50.726][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-eth-2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][app_sam_dme:config]     HostEthIfProfile::config: org-root/ls-ESX-01/ether-eth1, hostEthIf: sys/chassis-1/blade-1/adaptor-1/host-eth-2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:config]              oper vcon: 1
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:init]                adding 2 to mezz-id 1
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:init]                adding 1 to mezz-id 1
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:init]                lExisting 2, lRequired 2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    mezz 1 size 2 ifs size 2
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    mezz 2 size 0 ifs size 0
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    mezz 3 size 0 ifs size 0
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    mezz 4 size 0 ifs size 0
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:cleanupFcVnics]      going thru org-root/ls-ESX-01/fc-fc0
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:cleanupFcVnics]      org-root/ls-ESX-01/fc-fc0 is orig assigned
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:cleanupFcVnics]      going thru org-root/ls-ESX-01/fc-fc1
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:cleanupFcVnics]      org-root/ls-ESX-01/fc-fc1 is orig assigned
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    going thru org-root/ls-ESX-01/fc-fc0
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    org-root/ls-ESX-01/fc-fc0 is orig assigned
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    vnic id : 3
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:configureFcVnics]    host if: 1
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:config]              Setting OperOrder on VicDn[org-root/ls-ESX-01/fc-fc0], OperOrder[3]
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:checkPinning]        Check pinning (vnic=org-root/ls-ESX-01/fc-fc0)(swId=1)
[INFO][0xab9e8b90][Sep 10 12:58:50.726][ls:pinInterface]        FCManager::pinInterface called for org-root/ls-ESX-01/fc-fc0
[INFO][0xab9e8b90][Sep 10 12:58:50.727][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-fc-1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:config]              oper vcon: 1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configureFcVnics]    going thru org-root/ls-ESX-01/fc-fc1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configureFcVnics]    org-root/ls-ESX-01/fc-fc1 is orig assigned
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configureFcVnics]    vnic id : 4
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configureFcVnics]    host if: 2
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:config]              Setting OperOrder on VicDn[org-root/ls-ESX-01/fc-fc1], OperOrder[4]
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:checkPinning]        Check pinning (vnic=org-root/ls-ESX-01/fc-fc1)(swId=2)
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:pinInterface]        FCManager::pinInterface called for org-root/ls-ESX-01/fc-fc1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][app_sam_dme:config]     [DefinitionBI::config] no QoS policy for Host Intf: sys/chassis-1/blade-1/adaptor-1/host-fc-2
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:config]              oper vcon: 1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][vnic:validateIScsiOver] validateIScsiOverlayVnic (org-root/ls-ESX-01)(issues=0x0)
[INFO][0xab9e8b90][Sep 10 12:58:50.727][vnic:prevalidateVnicIS] prevalidateVnicIScsiIf: (org-root/ls-ESX-01)(issues=0x0)
[INFO][0xab9e8b90][Sep 10 12:58:50.727][vnic:configCompute]     Entered IScsiBI::configCompute isEval 1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][vnic:configCompute]     Exiting IScsiBI::configCompute isEval 1
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:setEpAuthChange]     ConfigChange: setEpAuthChange (EpAuthProfileBI::config)
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configLsZones]       IniGroupBi::configLsZones() started for sp org-root/ls-ESX-01.
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configBootZones]     BootConfig is Existing
[INFO][0xab9e8b90][Sep 10 12:58:50.727][ls:configLsZones]       IniGroupBi::configLsZones() finished for sp org-root/ls-ESX-01.
[INFO][0xab9e8b90][Sep 10 12:58:50.727][app_sam_dme:prevalidat] PCV *AnalyzeImpact* Server[sys/chassis-1/blade-1] Deleted VlanPorts Sw[A]-[0], Sw[B]-[0]
[INFO][0xab9e8b90][Sep 10 12:58:50.728][ls:analyzeConfig]       AnalyzeConfig: ack-phys[sys/chassis-1/blade-1] ls-phys[sys/chassis-1/blade-1]
[INFO][0xab9e8b90][Sep 10 12:58:50.728][ls:analyzeConfig]       bindingChange 0, hostEthIfChange 0,hostEthIfProfileChange 0, hostEthIfQosChange 0,hostEthIfQosHostControlChange 0, hostEthIfNwCtrlChange 0, hostEthIfProfileRedeployRequired 0,hostFcIfChange 0, hostFcIfProfileRedeployRequired 0,hostFcIfPersChange 0, hostFcIfProfileChange 0, hostFcIfQosChange 0, hostFcoeIfChange 0, hostIfPCIeChange 0, vifChange 0, vlanChange 1, vsanChange 0, ipChange 0,bootOrderChange 0, biosProfileChange 0, bladeIdentityChange 0,agentPolicyChange 0, biosFwChange 0,storageControllerFwChange 0, adaptorHostFwChange 0,adaptorNwFwChange 0, mgmtControllerFwChange 0,localDiskPolicyChange 0, pinChange 0, solChange 0,flexFlashConfigChange 1, cimcVmediaConfigChange 0,epAuthChange 1,bootVnicChange 0, bootPXEChange 0, boardCtrlFwChange 0, errInsufficientResources 0,LocalDiskFwChange 1,pnuosConfig 1, rebootRequired 1,ConfigRename 0,FcZoneChange 0,failed 0, serverIssues 0x0, networkIssues 0x0, storageIssues 0x0, vnicIssues 0x0, iscsiIssues 0x0 FLAGS APPLIED: 0x0, willExecute 0
[INFO][0xab9e8b90][Sep 10 12:58:50.728][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS required
[INFO][0xab9e8b90][Sep 10 12:58:50.728][app_sam_dme:fsmLsServe] Starting (stage=sam:dme:LsServerConfigure:WaitForMaintPermission)(dn=org-root/ls-ESX-01)
[INFO][0xab9e8b90][Sep 10 12:58:50.730][app_sam_dme:fsmCompute] SP-Rename: AssociateFSM Begin Qual [sys/chassis-2/blade-3]
[INFO][0xab9e8b90][Sep 10 12:58:50.730][app_sam_dme:fsmCompute] SP-Rename: Starting (stage=sam:dme:ComputePhysicalAssociate:begin)(dn=sys/chassis-2/blade-3)
[INFO][0xab9e8b90][Sep 10 12:58:50.730][app_sam_dme:muComputeP] muComputePhysicalComputeChangeCb invoked
[INFO][0xab9e8b90][Sep 10 12:58:50.730][app_sam_dme:muComputeP] Looking at adapter sys/chassis-2/blade-3/adaptor-1
[INFO][0xab9e8b90][Sep 10 12:58:50.732][app_sam_dme:fsmCompute] Starting (stage=sam:dme:ComputePhysicalAssociate:downloadImages)(dn=sys/chassis-2/blade-3)
[INFO][0xab9e8b90][Sep 10 12:58:50.733][app_sam_dme:fsmCompute] Starting (stage=sam:dme:ComputePhysicalAssociate:copyRemote)(dn=sys/chassis-2/blade-3)
[INFO][0xab9e8b90][Sep 10 12:58:50.736][app_sam_dme:fsmCompute] Re-setting Non-Fatal Warnings on Service Profile[org-root/ls-ESX-06] Server[sys/chassis-2/blade-3]
[INFO][0xab9e8b90][Sep 10 12:58:50.743][app_sam_dme:fsmCompute] SP-Rename: AssociateFSM Begin Qual [sys/chassis-1/blade-2]
[INFO][0xab9e8b90][Sep 10 12:58:50.743][app_sam_dme:fsmCompute] SP-Rename: Starting (stage=sam:dme:ComputePhysicalAssociate:begin)(dn=sys/chassis-1/blade-2)
[INFO][0xab9e8b90][Sep 10 12:58:50.743][app_sam_dme:muComputeP] muComputePhysicalComputeChangeCb invoked
[INFO][0xab9e8b90][Sep 10 12:58:50.743][app_sam_dme:muComputeP] Looking at adapter sys/chassis-1/blade-2/adaptor-1
[INFO][0xab9e8b90][Sep 10 12:58:50.745][app_sam_dme:fsmCompute] Starting (stage=sam:dme:ComputePhysicalAssociate:downloadImages)(dn=sys/chassis-1/blade-2)
[INFO][0xab9e8b90][Sep 10 12:58:50.745][app_sam_dme:fsmCompute] Starting (stage=sam:dme:ComputePhysicalAssociate:copyRemote)(dn=sys/chassis-1/blade-2)
[INFO][0xab9e8b90][Sep 10 12:58:50.749][app_sam_dme:fsmCompute] Re-setting Non-Fatal Warnings on Service Profile[org-root/ls-ESX-02] Server[sys/chassis-1/blade-2]
[INFO][0xab9e8b90][Sep 10 12:58:50.758][sam_dme:formatSuccessR] In formatSuccessRspConfigEstimateImpactCb
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS required
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS NOT required
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS required
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS required
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS required
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isDeploymentDeferre] Maint policy: org-root/maint-MaintenPolicy, deployment IS NOT deferred
[INFO][0xab9e8b90][Sep 10 12:58:50.758][ls:isUserAckRequired]   Maint policy: org-root/maint-MaintenPolicy, user ack IS NOT required
[INFO][0xab9e8b90][Sep 10 12:58:52.041][fsm:trigger]            global limit 48 processed 2 queue 0 pending 0

 

Thanks

 

Miguel

0 Helpful

Go to solution
Justin Welch
Level 1
Level 1
In response to mg.figueroa

‎09-10-2015 11:52 AM

Hello,

 

INFO][0xab9e8b90][Sep 10 12:58:50.728][ls:analyzeConfig]       bindingChange 0, hostEthIfChange 0,hostEthIfProfileChange 0, hostEthIfQosChange 0,hostEthIfQosHostControlChange 0, hostEthIfNwCtrlChange 0, hostEthIfProfileRedeployRequired 0,hostFcIfChange 0, hostFcIfProfileRedeployRequired 0,hostFcIfPersChange 0, hostFcIfProfileChange 0, hostFcIfQosChange 0, hostFcoeIfChange 0, hostIfPCIeChange 0, vifChange 0, vlanChange 1, vsanChange 0, ipChange 0,bootOrderChange 0, biosProfileChange 0, bladeIdentityChange 0,agentPolicyChange 0, biosFwChange 0,storageControllerFwChange 0, adaptorHostFwChange 0,adaptorNwFwChange 0, mgmtControllerFwChange 0,localDiskPolicyChange 0, pinChange 0, solChange 0,flexFlashConfigChange 1, cimcVmediaConfigChange 0,epAuthChange 1,bootVnicChange 0, bootPXEChange 0, boardCtrlFwChange 0, errInsufficientResources 0,LocalDiskFwChange 1,pnuosConfig 1, rebootRequired 1,ConfigRename 0,FcZoneChange 0,failed 0,

 

Notice the items with a 1 next to them. The servers want to reboot to for:

flexFlashConfigChange 1

LocalDiskFwChange 1

 

You can also see your VLAN change pending:

vlanChange 1

 

 

Hope this helps.

 

Justin

Go to solution
mg.figueroa
Level 1
Level 1
In response to Justin Welch

‎09-10-2015 12:17 PM

Hi Justin:

 

    Yesterday I just finished restarting all the 6 blades that compose the 2 chasis in our UCS infrastructure. Learning from your last post, I have to make something else to clear the change pendings out of the UCS. I don't have clear if, Selecting the Yes option in the User Ack warning message, UCS will immediately will reboot the hosts/blades or it will give a break to shutdown the VMs first and then reboot the hosts/blades.

Thanks a lot for your support, I just making my first steps in the Cisco UCS World.

 

Miguel Figueroa

0 Helpful

Go to solution
Justin Welch
Level 1
Level 1
In response to mg.figueroa

‎09-10-2015 12:22 PM

Hello,

 

As long as your maintenance policy on these servers is set to user_ack you will just have pending activities for a reboot. Until then the blades will not reboot.

https://supportforums.cisco.com/document/122691/understanding-and-configuring-cisco-ucs-maintenance-policy

 

 

Thanks,

Justin

0 Helpful

Go to solution
mg.figueroa
Level 1
Level 1
In response to Justin Welch

‎09-11-2015 10:01 AM

Hi Justin:

 

  Thanks for your help. I want to share this youtube link. Its clearly explains all about UCS Maintenance Policy settings.

 

https://www.youtube.com/watch?v=QQTlm98NgTI

 

Thanks a lot for your help!!!

 

Miguel Figueroa

Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card