Avaya Pod Fx, Troubleshooting Manual, Page: 28 / 66

Access the vCenter command line interface and use the following commands to fix this issue.
esxcli network nic down -n vmnic<X>
esxcli network nic up -n vmnic<X>
Where
<X>
is the number of the vmnic to be fixed.
Related links
Troubleshooting general issues on page 24
Quick Fixes
Application Problem Description Solution or Workaround
Pod Visualization Manager The application does not open
when launched or produces a “SA
not accessible” warning. 1. The jboss application server
may be down. Check for
status and restart jboss using
the following commands as
root
user:
• On the PVM VM check the
jboss status using the
command
service jboss
status
.
• Restart jboss using the
command
service jboss
restart
.
•
2. The Serviceability Agent may
be down. Check for status
and restart spirit agent using
the following commands as
root
user:
• On the PVM VM check the
spirit agent status using the
command
service
spiritAgent status
.
• Restart spirit agent using
the following commands:
service spiritAgent
stop
service snmpd restart
service spiritAgent
start
Table continues…
Troubleshooting general issues
October 2017 Troubleshooting the Avaya Pod Fx
™
28
Comments on this document? infodev@avaya.com