I am pleased to announce that TC7.3.3 has been released.
This version contains mainly bug fixes but has also re-named the web-snapshot feature to "Remote Monitoring". To activate this feature in TC7.3.3 an option key is now required. Please read the release notes for more details.
Note: There are currently some issues publishing the release notes at the time of this post, please stay tuned as it will be available in an hour or two. We are sorry for any issues this may cause. I have attached a copy of the release note to this post just in case.
The release notes has been refurbished and will no longer list specific bugs but rather provide a pre-defined bug search in the Cisco bug tool. This gives a better and dynamic overview of open and resolved caveats.
Solved! Go to Solution.
Dave, you beat me too it. I was typing and noticed an email came in that this thread got a new reply.
To clarify to Dave's tip, hardware serial and specific system type description are located in the "General Settings" category.
Within system overview, there are two columns: endpoints on the left, and system parameters (aka settings) on the right. General settings is in the right column.
I forgot to mention that the example CSV file is commented out in the bottom of the script.
But I guess you have already figured that out :)
Whilst I appreciate you comments, I personally have not seen much public evidence of the reason why the option key was introduced, i.e. "due to a massive pressure from users who did not want their systems subjected to monitoring". The general feeling I have extracted from this fiasco and on-going debate over the past months is that most users have been annoyed, confused, angered and dismayed by the decision.
Compared to some users on this forum, we have a limited number of C and SX devices, perhaps only 60 or 70 units. However, we feel that Cisco has not only lost its way on this particular point, but in general has gone completely doolally. It appears that Cisco are increasingly becoming self absorbed in their own pomposity, and this will lead to alienation of its customer base. This is simply one of an continuing line of inexplicable change decisions, but I can see additional issues proliferate through other arms within Cisco, including core business such as Networking.
Lets face it, what could Cisco have done to appease the "massive pressure from users" in implementing this change to enable de-selection of monitoring? Well, I am going to make an assumption here that this "massive pressure" must have come from a large user/s, and so I will also assume that such large user will have centralised management abilities of these devices, and more than likely will have changed the default passwords on all management interfaces (such as Web/SSH and even local GUI). So, these devices are already protected from general users making changes, and we have the option of adding non-administrative users to the interface. Why an earth then, could Cisco simply not have created a boolean option (such as a tick box) that could only be set by authorised administrators? Would this have been so detrimental to functionality?
I can't fathom it at all, but I think our decision will be in the long term to completely move away from Cisco in this area. I hope that such corporate decisions do not continue and that senior management in Cisco should be directed toward and peruse their own customer feedback on these forums. Perhaps they will then get a sense of perspective and start making better decisions for their customers.