This configuration technically works, however, it is not recommended for (at least) two reasons.
ACS is security central for your network. It stores all of your usernames and credentials at a very minimum. If this box has to be rebooted for an LMS issue, that could lock people out of your network. If there is a security compromise due to LMS, then all of your credentials are compomised as well. Likewise, LMS is your central configuration repository. If there is an ACS security problem, and an attacker gains control of the server, they would have access to device configurations.
The other reason has to do with the number of TCP ports used by each application. With both running on the same box, you may run out of free TCP ports. If this happens, then neither application would function.
We generally recommend your ACS server is a secured, isolated machine with minimal physical access. And while we have tested applications like HPOV NNM on the same server as LMS, we recommend you give it as much server resources as possible so that it can perform all of its tasks in the best way possible.
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...