We have done a major upgrade with a management appliction that uses the cimserver on the Cisco switches. I have 4 x 9216A running 3.2(2c) and at exactly the same time, the cimxmlserver crashed on all of them. I put it down to something that the upgrade of our app has done. Our other switches (including 9509's) are running 3.3(something) and they are not causing any problems.
I do know that the SMI-S agent (cimserver) on 3.3 and above uses 1.2 or something where 3.2 uses 1.1.
I could not poll 3.3 due to this SMI-S problem but now it has been fixed and I believe it has introduced the problem I am seeing.
Any comments? Whats the bet, I need an upgrade? So much for SMI-S for being the be all end all management solution. SNMP is so much easier.
I am unable to start the cimserver at all. I do a no cimserver start then a cimserver start and it crashed immediately.
<msgDesc>cimxmlserver crashed with crash type:crash without
I will raise a call through our vendor and expect to wait for an extraordinary time to get an answer on this.... I liked being about to raise a call direct with the CCO. I don't like this storage switch support model one little bit.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...