Always and with all PI installations I know I get an Error #2032 with "Message (RSL Error 2 of 7)" in Deploy => Monitoring Deployment, if I try to assign a monitoring template to a device or port group. Is there a workarround or bugfix out?
Workaround:Place the 'framework_22.214.171.12446.swz','mx_126.96.36.19946.swz' and 'spark_188.8.131.5246.swz' at VM Folder: /applications/common/flex/treetable (eg: /opt/CSCOlumos/apache-tomcat-7.0.40/webapps/webacs/applications/common/flex/treetable)
Last Modified:Oct 24,2013
At PI2.0 the folder looks like this according affected files:
I have experience the same problem under different tools in PI. I did notice it first under “Deploy>Monitoring deployment>Interface Health template>deploy and I get the 2032 error.
I have learn that this occurs when you use a client with no internet connection and you try to start above deployment tools.
What happens is that when you try to open such page in PI web interface, the flash player starts and try to get some files on the PI but the URL it get from the PI application points to a library that do not contains the file (Bug in PI?). The files the flash player looks for is called something like framework_184.108.40.20628.swz and spark_220.127.116.1128.swz and so on. The url from PI looks like https://PI_Server/webacs/applications/SAMDeployTemplate/js/framework_18.104.22.16828.swz but the file is missing.
The flash player have a backup way to get the xxxxxx.swz files it needs. If it can’t find the files in the application, it try to get it from Adobe http://fpdownload.adobe.com . But in my case my client can’t access internet so I get the error 2032.
I have another installation at another site that allows internet access everything works fine. The flash player can load the files it needs and store them locally on the client PC. Then I can take that PC back to the another site with no internet access where I did get the 2032 error and now It works fine because the flash player have the files it needs to handle the PI application.
I have a case open but it has not been solved yet.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...