10-24-2013 09:08 AM
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?
thx for hints in advance,
10-24-2013 09:13 AM
these are the BUG's :
CSCuj39571 PI 2.0 - Monitor template deploy generates RSL #2032 error
CSCuj41410 PI 2.0 FCS shows RSL error #2032 in multiple pages
I don't see any workaround for them , you can check with TAC.
[Do rate the useful post]
10-25-2013 12:39 AM
Thx for your answer. Snip from Bugtool:
Workaround:Place the 'framework_126.96.36.19946.swz','mx_188.8.131.5246.swz' and 'spark_184.108.40.20646.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,2013Status:Fixed
At PI2.0 the folder looks like this according affected files:
ade # ls mx_4.* framework_4.* spark_4.*
framework_220.127.116.1189.swf mx_18.104.22.16889.swf spark_22.214.171.12489.swf
framework_126.96.36.19967.swf mx_188.8.131.5267.swf spark_184.108.40.20667.swf
framework_220.127.116.1167.swz mx_18.104.22.16867.swz spark_22.214.171.12467.swz
framework_126.96.36.19928.swf mx_188.8.131.5228.swf spark_184.108.40.20628.swf
framework_220.127.116.1128.swz mx_18.104.22.16828.swz spark_22.214.171.12428.swzframework_126.96.36.19901.swz mx_188.8.131.5201.swz spark_184.108.40.20601.swz ade
The mentioned version of this files are noot there: Where do we get this files? Is there a bundled downloadable bugfix out?
10-25-2013 01:45 AM
I also did not find these files. you can get in touch with TAC so that they can conatct the development team. They may have some patch for this..
10-25-2013 04:50 AM
How can I use the Open TAC request tool for Prime Infrastructure with this large Serial-Nrs of PI that doesnt fit into the SN# field of TAC service request tool even I delete all '-'?
10-31-2013 04:04 AM
Please post if someone got a solution for this. I dont understand how to implement the workaround provided for this Bug.
11-05-2013 05:39 AM
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_220.127.116.1128.swz and spark_18.104.22.16828.swz and so on. The url from PI looks like https://PI_Server/webacs/applications/SAMDeployTemplate/js/framework_22.214.171.12428.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.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: