Epicenter Server Issues - Extreme Networks EPICenter Guide Manual

2 Go to the EPICenter install directory:
cd /opt/extreme/epc5_0
3 Make sure the
directory:
setenv LD_LIBRARY_PATH /opt/extreme/epc5_0/database
4 Execute the following command:
database/dbeng9.exe -f basecamp.db
5 Watch the output from this command. If the database program indicates it cannot recover the database,
delete the database log:
rm basecamp.log
and try executing the previous command again:
database/dbeng9.exe -f basecamp.db
6 If the database is successfully recovered, restart the server.
If the database cannot be recovered, you will need to restore the database from a backup. See
Appendix C in the EPICenter Reference Guide for instructions on restoring the database from a backup.

EPICenter Server Issues

Problem: Cannot talk to a specific switch.
Verify that the switch is running ExtremeWare software version 2.0 or later.
Ping the switch's IP address to verify availability of a route. Use the
Solaris command shell.
If the switch is using SNMPv1, verify that the read and write community strings used in EPICenter match
those configured on the switch. If the switch is using SNMPv3, verify that the SNMPv3 parameters
configured in EPICenter match those on the switch.
Problem: ExtremeWare CLI or ExtremeWare Vista changes are not reflected in EPICenter.
Verify that the switch is running ExtremeWare software version 2.0 or later.
From the Inventory Manager, click Sync to update the information from the switch. This refreshes the
switch specific data, validates the SmartTrap rules, and ensures that the EPICenter server is added as a
trap receiver (Extreme switches only).
If the problem persists, verify that the EPICenter workstation has been added in the list of trap
destinations on the given switch:
1 Telnet to the switch.
2 Log in to the switch.
3 Type
show management
show snmpv3 target-addr <ipaddress>
An Extreme switch can support a maximum of 6 trap destinations in ExtremeWare 2.0, and up to 16 trap
destinations with ExtremeWare 5.0 or greater. If EPICenter is not specified as a trap destination, then no
EPICenter Concepts and Solutions Guide
environment variable is set to the EPICenter directory installation
LD_LIBRARY_PATH
to verify that the system running the EPICenter is a trap receiver, or
ping
if the device is running SNMPv3.
EPICenter Server Issues
command from a MS DOS or
169