Cisco Bug: CSCuw49171 - Indicate that changing APIC hostname requires a controller reboot
Feb 20, 2018
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: Hostname may be reported incorrectly for certain logging features ex syslogging to an apic will still show the old hostname, not the new one. Checking /etc/hosts will show multiple entries for the apic hostname. admin@apic1:~> cat /etc/hosts 10.0.208.64 10.0.88.92 Leaf1 10.0.88.95 Leaf2 10.0.88.128 Leaf3 10.0.88.93 Spine1 10.0.88.94 Spine2 127.0.0.1 apic1 10.0.0.1 apic1 apic1 <<< Desired Name 10.0.0.1 apic1 apic1-test10 <<< Old name Conditions: Hostname is changed on the apic directly.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases