11-17-2011 08:08 AM
Let's put it to rest!
This is effectively a re-hash of the issues outlined here:
https://supportforums.cisco.com/message/3478938#3478938
I'm opening a new thread to spur discussion, plus I'd like to test out this "open an SR from a discussion" capability that I just read about.
Personally, we have a client with a 4 node VSVM "video wall" and a dedicated VSOM operator workstation. All are running VSM 6.3.1.
Also, all workstations pass the client profiler tool with flying colours.
I intend to engage the client, possibly after lunch, and utilize:
- DebugView
- WireShark
- VSM Support Reports
... to attempt to get to the bottom of the issue. I'm hoping to get tangible explanations for how / why this is occuring.
-RSO
11-17-2011 04:53 PM
Any luck getting it to replicate?
11-18-2011 06:46 AM
Well, I've certainly managed to replicate some bizare behaviour that is definitely not intended. I've gathered video clip highlighting the behaviour I experienced and attached it to the TAC case.
I've left the VSM server and VSVM endpoint in this state, and I'm confident I could reproduce this behaviour again. I'm awaiting addtional instruction from TAC regarding what additional data they actually require.
VSM is at 6.3.2
VSVM client is at 6.3.409.0
VSVM node is Windows XP, SP3
VSOM workstation is Windows 7 x64, IE8.
11-24-2011 06:11 AM
To anyone else that is curious, this is still an issue in VSM 6.3.2 and is apparently covered under BugIDs:
CSCzi32616
&
CSCtk08688
Unfortunately, I am unable to get more information than that.
Here are the workarounds:
- use VSOM operations manager in full screen mode
- shut down the VSVM client and push the view then open it again.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide