Dave's right. This may be related to an issue relating to a requirement for a direct connection to Cisco.com. A sniffer trace filtering on packets going to www.cisco.com when trying to run the report would be helpful. Clearly, if anything is seen we have a problem similar to the bug Dave mentioned.
In addition to the sniffer trace, the invreports.log would also be helpful.
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 customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...