Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Using Policy Manager logs to verify policy upgrade

When upgrading the fabric using policy upgrade,Policy Manager logs on the APIC's can be checked to see the status of the upgrade. One thing to note is that the upgrade logs for different nodes can be spread across the APIC's in a random order. Policy Manager on all APIC's may have to be checked to account for all the nodes in the fabric. The policy upgrade logs are saved in svc_ifc_policymgr.bin.log. The latest logs are saved in the log file that does not have a number.
Below are some logs to check during the upgrade, only relevant output is shown.

admin@apic1:~> cd /var/log/dme/log
admin@apic1:log> pwd
/var/log/dme/log


The below logs show the messages exchanged between Policy Manager on APIC and Policy Element for node 202 and also indicates the firmware upgrade is in progress for a policy name ''switch even'

admin@apic1:log> more svc_ifc_policymgr.bin.log
32506||14-07-14 21:18:13.103+00:00||polRegisterForPolici||DBG4||fr=ifc_policymgr:2:1:6:0:31:1,to=ifc_policyelem:1:202:5:0:6:1,

co=repl:31:1:0xf8000000000012f8:6,si=0xca05061d42aabc8:0x3||(envelope 0x10000000008bb: SEND:RESPONSE[polRegisterForPolicies/]) CONTENT :||../common/src/framework/./core/proc/Stimulus.cc||848
303||14-07-14 21:18:13.103+00:00||ifm||DBG3||to=ifc_policyelem:1:202:5:0,co=ifm||message with msgid 0x4fa46108aa8 sent to peer (envelope 0x10000000008bb)||../common/src/ifm/./Protocol.cc||881
303||14-07-14 21:18:13.105+00:00||ifm||DBG3||to=ifc_policyelem:1:202:5:0,co=ifm||peer acknowledged the reception of msgid 0x4fa46108aa8 (envelope 0x10000000008bb)||../common/src/ifm/./Protocol.cc||706
32506||14-07-14 21:18:15.279+00:00||actionUpdate/||DBG4||fr=ifc_policyelem:1:202:5:0:255:127,to=ifc_policymgr:2:1:6:0:17:2,

co=doer:17:2:0x8800000000001641:1,si=0xca05fffd44c8d3c:0x0||(envelope 0x10000000008cf: RECEIVE-BULK:REQUEST[actionUpdate/]) CONTENT :
<actionUpdate dn="topology/pod-1/node-202/sys/fwstatuscont/upgjob/node-202" action="222" run="5963" stage="77" timestamp="1405372693545">
<maintNodeInMaintTask childAction="deleteNonPresent" data="" descr="" dn="action/policyelemsubj-[topology/pod-1/node-202/sys/fwstatuscont/upgjob/node-202]/maintNodeInMaintTask-CanIUpgrade" endTs="never" fail="0" id="CanIUpgrade" invErrCode="none" invErrDescr="" invRslt="" lcOwn="local" modTs="2014-07-14T21:18:13.545+00:00" oDn="topology/pod-1/node-202/sys/fwstatuscont/upgjob/node-202" operSt="processing" originMinority="no" runId="5963" startTs="2014-07-14T21:18:13.545+00:00" status="created" try="0" ts="2014-07-14T21:18:13.545+00:00"/>
<maintNodeInMaint childAction="deleteNonPresent" dn="topology/pod-1/node-202/sys/fwstatuscont/upgjob/node-202" fwName="n9000-11.0(0.819)" lcOwn="local" modTs="2014-07-14T21:18:13.545+00:00" monPolDn="uni/fabric/monfab-default" nodeId="202" nodeIp="0.0.0.0" peerNodeIp="0.0.0.0" polName="switcheven" rn="" status="created" upgradeStatus="completeok" windowStartTime="2014-07-14T21:06:55.067+00:00" windowTimeCap="00:00:00:00.000"/>
32506||14-07-14 21:18:15.279+00:00||maint||DBG4||co=doer:17:2:0x8800000000001641:1,

dn='"DXVABAAHKAAAAygAAAA=="'||Processing firmware upgrade request from node: 202 currentState: 4 polName: switcheven windowStart: 1405372015067 windowCap: 0||../svc/policymgr/src/gen/ifc/app/./imp/maint/TaskMaintNodeInMaintCanIUpgradeUpdateImp.cc||87
32506||14-07-14 21:18:15.279+00:00||maint||DBG4||co=doer:17:2:0x8800000000001641:1

||Found node in scheduler queue. Deleting it since upgrade is complete.202||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||379
32506||14-07-14 21:18:15.279+00:00||maint||INFO||co=doer:17:2:0x8800000000001641:1,

dn='"DUVABAMoAAAALAHN3aXRjaGV2ZW4A"'||A node has completed upgrade successfully, node:202||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||410
32506||14-07-14

 

 


The below logs, show that the user has paused the upgrade for policy name 'switchodd 'and the APIC is waiting for the user to resume the upgrade


admin@apic1:log> more svc_ifc_policymgr.bin.log
32691||14-07-14 20:58:47.946+00:00||maint||DBG4||co=doer:17:1:0x88000000000013dc:1,

dn='"DXVABAAHJAAAAyQAAAA=="'||Processing firmware upgrade request||../svc/policymgr/src/gen/ifc/app/./imp/maint/TaskMaintNodeInMaintCanIUpgradeUpdateImp.cc||76
32691||14-07-14 20:58:47.946+00:00||maint||DBG4||co=doer:17:1:0x88000000000013dc:1,

dn='"DXVABAAHJAAAAyQAAAA=="'||Processing firmware upgrade request from node: 201 currentState: 1 polName: switchodd windowStart: 1405371187000 windowCap: 0||../svc/policymgr/src/gen/ifc/app/./imp/maint/TaskMaintNodeInMaintCanIUpgradeUpdateImp.cc||87
32691||14-07-14 20:58:47.946+00:00||maint||DBG4||co=doer:17:1:0x88000000000013dc:1,

dn='"DUFABAAoAc3dpdGNob2RkAA=="'||Found an existing upgstatus polName=switchodd||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||230
32691||14-07-14 20:58:47.946+00:00||maint||INFO||co=doer:17:1:0x88000000000013dc:1,

dn='"DUVABAMkAAAAKAHN3aXRjaG9kZAA="'||Rejecting upgrade request from node: 201. Scheduler is paused, waiting for admin to unpause.||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||241


Note that the logs for node 101,102 and 201 are seen on apic2 while node 202 is seen on apic1.

admin@apic2:log> more svc_ifc_policymgr.bin.log | grep node:101
32696||14-07-14 21:36:17.929+00:00||maint||INFO||co=doer:17:1:0x88000000000017e7:1,

dn='"DUVABAGUAAAAKAHN3aXRjaG9kZAA="'||A node has completed upgrade successfully, node:101||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||410

admin@apic2:log> more svc_ifc_policymgr.bin.log | grep node:102
32693||14-07-14 21:22:03.842+00:00||maint||INFO||co=doer:17:1:0x88000000000016bb:1,

dn='"DUVABAGYAAAALAHN3aXRjaGV2ZW4A"'||A node has completed upgrade successfully, node:102||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||410

admin@apic2:log> more svc_ifc_policymgr.bin.log | grep node:201
32695||14-07-14 21:39:01.413+00:00||maint||INFO||co=doer:17:1:0x880000000000183f:1,

dn='"DUVABAMkAAAAKAHN3aXRjaG9kZAA="'||A node has completed upgrade successfully, node:201||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||410

 

admin@apic1:log> more svc_ifc_policymgr.bin.log | grep node:202

21:18:15.279+00:00||maint||INFO||co=doer:17:2:0x8800000000001641:1,

dn='"DUVABAMoAAAALAHN3aXRjaGV2ZW4A"'||A node has completed upgrade successfully, node:202||../svc/policymgr/src/gen/ifc/app/./imp/maint/MaintConcCtl.cc||410
32506||14-07-14

129
Views
0
Helpful
0
Comments