Device Center issue with short hostname in links and certificate with FQDN
Master - Server setup on windows; Master has CS, CM; Slave_1 has CS, RME; Slave_2 has CS, DFM;
full computer name is hostname.dns-suffix.
RME is registerd with FQDN of Slave_1 on Master through CS > Home Page Admin > Application Registration
the same was done with DFM of Slave_2
when logging in to the Master, going to Device Center, selecting a device, all reports which links to 'Slave_1' or 'Slave_2' will be called with their short name which triggers a security alert that the name in the certificate does not match the hostname.
Is there a possibility to change the links in Device Center (I think it must vbe done in one of the registration files...- but where).
This problem does only occure in Device Center and in no other application.
PX_HOST = hostname
PX_FQDN = hostname.dns-suffix
on Master and Slave_X; the certificates were created with FQDN
Re: Device Center issue with short hostname in links and certifi
Unfortunately, this is not easily done. Device Center relies on data from the PIDM subsystem which is stored in the Common Services database. The hostname is determined by asking the OS for its local hostname. That will almost always be the value of COMPUTERNAME on Windows. It would be easier to regenerate the certs with the short hostnames.
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...