|
Installation Issues
|
|
|
|
Failed or
unsuccessful installation on a bare-metal server.
|
Attempted
installation of the controller is being made without meeting the system
requirements for the release.
|
Access the
latest
Cisco APIC-EM
release notes and review the system requirements. Be sure to review the
appropriate specific system requirements for a bare-metal installation.
|
|
Failed or
unsuccessful installation on a virtual machine.
|
Attempted
installation of the controller is being made without meeting the system
requirements for the release.
|
Access the
latest
Cisco APIC-EM
release notes and review the system requirements. Be sure to review the
appropriate specific system requirements for a virtual machine installation,
including the VMware resource pool requirements.
| Note
|
For additional assistance with deploying the controller in a
virtual machine, refer to the appendix in the
Cisco Application Policy Infrastructure Controller
Enterprise Module Installation Guide that discusses virtual machine
preparation.
|
|
|
Failed or
unsuccessful installation on either a bare-metal server or virtual machine.
|
Core
services failing to start up on the
Cisco APIC-EM.
|
Perform the
following actions:
-
If
possible, log into the controller's GUI.
-
Review
the state of the controller services in the
Systems Health tab.
-
Create
an rca file and send to support for additional assistance.
References:
|
|
Unable to
log into the controller GUI after an apparently successful installation.
|
Network
connectivity to the controller is failing.
|
Review and
test your network connections to the controller.
Reference:
|
|
Update Issues
|
|
|
|
Unable to
update
Cisco APIC-EM
using the recommended standard methods.
|
|
Run the
apply_update script.
Reference:
|
|
Configuration Issues
|
|
|
|
Controller
in a
single
host configuration appears to be in an unstable state. For example,
applications are not running, are inaccessible, and/or not appearing in the
GUI.
|
Controller
in unstable state, possibly due to error(s) in entering configuration values
with the Cisco APIC-EM configuration wizard.
|
Log into
the host, check the configuration values, and reenter any configuration values
that are incorrect.
References:
|
|
Controller
in a
multi-host
configuration appears to be in an unstable state. For
example, applications are not running, are inaccessible, and/or not appearing
in the GUI.
|
Controller
in unstable state, possibly due to error(s) in entering configuration values
with the Cisco APIC-EM configuration wizard.
|
Log into
the host, check the configuration values, and reenter any configuration values
that are incorrect.
References:
|
|
Controller was working fine for a period of time after its initial deployment,
but then lapses into an unstable state. For example, applications are not
running, are inaccessible, and/or not appearing in the GUI.
|
Possible
user or other error in configuration values that occurs after the initial
deployment.
|
Revert
back to the first configuration or the factory default configuration.
References:
|
|
Controller
was working fine for a multi-host configuration, but after a period of time one
of the hosts becomes erratic and unstable.
|
Possible
failed service or services in the multi-host cluster.
|
Remove and
then reattach unstable host from the multi-host cluster.
References:
|
|
Controller
was working fine for a multi-host configuration, but after a period of time one
of the hosts
fails.
|
Possible
failed service or services in the multi-host cluster.
|
Remove
and then reattach failed and inoperable host from the multi-host cluster.
References:
|
|
Hardware Issues
|
|
|
|
Single
host (on an physical appliance or server) reboots, but the controller is not
returning to former status.
|
Services
are failing as a result of the reboot and not restarting
|
If
possible, log into the controller's GUI, determine the failed service, restart
the service.
| Note
|
You can
review the status of controller services using the controller's GUI.
|
References:
|
|
Service Issues
|
|
|
|
Service
failure on a host that leads to one or more applications on the controller
failing. For example, getting a "503 Service Unavailable" message when trying
to access the Controller UI.
|
|
If
possible, log into the controller's GUI, determine the failed service, restart
the service.
| Note
|
You can
review the status of controller services using the controller's GUI.
|
References:
|
|
Password Issues
|
|
|
|
Lost
password for controller access.
|
A user
(administrator, installer or observer) has lost their password, and there
exists at least one controller administrator (ROLE_ADMIN) user account.
|
Perform
the appropriate password recovery for this scenario.
References:
|
|
Lost
password for controller access.
|
A user
(administrator, installer or observer) has lost their password and there exists
only one controller administrator (ROLE_ADMIN) user account and that account
cannot be successfully logged into.
|
Perform
the appropriate password recovery for this scenario.
References:
|
|
Lost
password for system access.
|
The Linux
grapevine user password has been lost.
|
Perform
the appropriate password recovery for this scenario.
References:
|
Feedback