We have ANM 3.2 installed at a customer and they wish to have an account logged in and have the dashboard up and on a monitor in the NOC at all times. Just want to check in if it is possible to change the default idle timeout (30 minutes) to 0 and if this would then allow that session to remain up/open always as desired. I imagine it would.
Also is this only availbe to change via advanced config with anm-tool? I think so.
Thank you for the response. I noted that version 4.1 has the following option: /opt/CSCOanm/bin/anm-tool --advanced-options=1 configure which appears to allow you to change this. We have verson 3.2, which does not have this --advanced-options=1 option. Also it creates the file /opt/SCOanm/etc/cs-config.properties for both versions.
Firstly, would this be the same file you are refering to? Second, if so, I would then make the addition to this file, right? Or would creating the system.properties file work as well on version 3.2?
Just want to confirm these points. Otherwise will also take your suggestion on the script under advisemant as well (a good one - Thanks).
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...