Can you help update in iMC ......?

[MohammadH]

Hi

I can't find the file imccfgupdm in <imc>/server/conf/log ?

[LindsayHill]

Sorry, typo there, look for imcupgdm* 

[MohammadH]

HI

I have the file in the attachment can you check ?

thank you

[LindsayHill]

Looking at it, it seems to go through these steps:
1/ Delete the old firmware - works OK
2/ Transfer the Boot Manager - all works OK
3/ Transfer the new firmware - transfer seems to be working, but then at the end it's saying that it can't find the file on the switch. Here's the relevant output:
013-07-29 10:05:42.820 [INFO (0)] [THREAD(8904)] dev id: 47, dev ip: 172.20.0.25. File operator end, result code: 100
2013-07-29 10:05:42.820 [INFO (0)] [THREAD(8904)] dev id: 47, dev ip: 172.20.0.25. CTransferProtocol::transfer end ......
2013-07-29 10:05:42.820 [INFO (0)] [THREAD(8904)] [CPolicyUpload::exec()] dev id: 47, ip: 172.20.0.25. Transfer file to device, end .......
2013-07-29 10:05:42.820 [INFO (0)] [THREAD(8904)] [CPolicyUpload::exec()] iDetailErrorCode = 5500
2013-07-29 10:05:42.853 [INFO (0)] [THREAD(8904)] dev id: 47 dev ip: 172.20.0.25. image: A5500EI-CMW520-R2220P07.bin, location: flash:/, not found in sysImageTable.
2013-07-29 10:05:42.853 [INFO (0)] [THREAD(8904)] [CPolicyUpload::exec()] dev id: 47, ip: 172.20.0.25. Get image index of A5500EI-CMW520-R2220P07.bin from device failed, result code: -100
2013-07-29 10:05:42.867 [INFO (0)] [THREAD(8904)] [CExecuter::exec()] Step failed, break !


If you look at the flash on that switch, can you see the new image there?

If it was my network, I'd probably be using Wireshark, and looking at the traffic between IMC and that switch, to better understand where it's failing. You may prefer to log a case - it's up to you.

[MohammadH]

hi

yes i can see the file there in the switch ?!

[LindsayHill]

And the file size on the switch looks correct? If it is, the transfer is completing successfully,

Do you have working SNMP read-write configured for this device?

[MohammadH]

Hi

the file size is 13991278 kb so it correct and so the  SNMP read-write it work fine.

[LindsayHill]

Just saw a couple of other things that look a bit odd:

2013-07-29 09:22:06.650 [ERROR (0)] [THREAD(6052)] [CQvDBConnADP::CQvDBConnADP]Database has not connect!
2013-07-29 09:22:06.650 [ERROR (0)] [THREAD(6052)] [CQvDBConnADP::status] Isconnected failed, errorMsg:Cannot open database "icc_db" requested by the login. The login failed.
2013-07-29 09:22:06.743 [ERROR (106)] [THREAD(6052)] CQvDBConnMgrInst::instance: Mgr cant correctly init, exit. DBInfo Class Name:class CUpgradeDBInfo
2013-07-29 09:22:06.743 [INFO (0)] [THREAD(6052)] exitAppError: serious error, exit...
2013-07-29 09:22:24.870 [INFO (0)] [THREAD(9412)] [CQvApplication::start] call globalInit().

I'm not sure what's causing that - it might be nothing to worry about, as it's not really causing your problem here.

And it looks like SNMP Read-write isn't working:
2013-07-29 10:01:51.968 [INFO (10)] [THREAD(8904)] [CSnmpOper::iCommitOper] send snmp set packge fail.->[172.20.0.25]
2013-07-29 10:01:51.968 [INFO (0)] [THREAD(8904)] Commit snmp operation failed.

Use Wireshark, look at what's going on between IMC and the switch.

[MohammadH]

Hi

i use the Wireshark one before but i don't now how to use it I'm new to Wireshark very new. can you tell me how to do it.

[Peter_Debruyne]

Hi,

Try the "check access settings" in IMC first, it should test snmp read and write communities and report on the status.

Resource - Batch operation - Check Access settings - Add device, select snmp only (no need for telnet/ssh) and verify the result (with details option).

Other option is wireshark, install wireshark on the IMC server (x86/x64), start the capture and use this display filter:

(snmp.data == 2 or snmp.data == 3) and ip.addr == 1.1.1.1

Update IP to your switch IP. This filter will only show the snmp SET and RESPONSE packets.

When you see a SET packet to the switch, it should reply with a RESPONSE and inside the snmp section of the packet there should be a NOERROR status.

If you do not see an snmp response, there might be:

* acl restricting SNMP access

* wrong community string

Both of these should be checked in the switch config,

Best regards,Peter