Problems Of Expether Io Expansion Unit (40G); Problems On Expether Manager Software - NEC ExpEther-2S User Manual

9.2 Problems of ExpEther IO Expansion Unit (40G)


The PCI Express card mounted on the ExpEther IO Expansion Unit (40G) cannot be
recognized.
→
Check if the PCVI Express card is properly inserted into the PCI Express slot of the ExpEther
IO Expansion Unit (40G).
→
Check if the power of the ExpEther IO Expansion Unit (40G) is turned on.
→
Check if the extension power cable is properly connected for the PCI Express card that
needs to be connected to the extension power cable.

The power turned off during the operation and wouldn't turn on.
→
The ExpEther IO Expansion Unit (40G) may have detected a temperature anomaly or the
power has turned off. Remove the power cord from the ExpEther IO Expansion Unit (40G)
and check if there is any problem in the operating environment. Check if there is any problem
of the operation of the cooling fan of the ExpEther IO Expansion Unit (40G) after turning on
the power.
→
Check if the power cord has been pulled out or if the main power switch has been turned off.

The performance of the mounted device is low.
→
Products other than those whose operation has been checked mounted on the ExpEther IO
Expansion Unit (40G) may not be cooled. Contact your sales representative for the product
whose operation has been checked.
→
Check that four connection ports of the ExpEther IO Expansion Unit (40G) are all connected.

ID LED does not light up by pressing the UID switch.
→
Check if the ExpEther board and the ExpEther IO Expansion Unit (40G) are connected.
→
To light up ID LED by pressing the UID switch, you need to install ExpEther Manager on the
control unit that is on the same network.
→
Check if you can identify the target ExpEther IO Expansion Unit (40G) from ExpEther
Manager.

9.3 Problems on ExpEther Manager Software


ExpEther Manager does not start.
→
Check again if the configured environment variables are correct.
→
Check again if eem.conf is correctly configured.
→
If you have changed environment variables and eem.conf, restart EEM.

The CLI (command line) times out.
→
Check if the control unit is correctly connected on the ExpEther network by the network cable
and the status of the external L2 switch.
→
Check again if eem.conf is correctly configured.
→
If you specify a long data length to the option parameter "-length" of the CLI subcommand
"dumpreg" and "dumprom", specify a shorter data length and adjust it.

The host information of the ExpEther board (40G) is set by using the ExpEtherConfig tool.
However, the information is not reflected on the management software.
→
After setting the host information, execute the CLI subcommand "audit"

Collecting the information in case of a problem
→
Collect the information from the following directories in case of a problem.
<EEM path>/logs/
<EEM path>/conf/
<EEM path>/tomcat/logs/
71