Troubleshooting Tips

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Line 44: Line 44:
|Emergency   
|Emergency   
|The Framework has stopped running for at least two minutes.  
|The Framework has stopped running for at least two minutes.  
-
|}
+
|}<br>
-
Related Links: <br>[[Frequently Asked Questions|Frequently Asked FAQs]]
+
Related Links: <br>[http://docwiki.cisco.com/wiki/Frequently_Asked_Questions_%28FAQs%29"Frequently Asked Questions|Frequently Asked FAQs"]

Revision as of 10:55, 2 July 2010

This article helps you to identify and remedy common problems that may arise as you run the Mediator and the Mediator Manager applications.

Q) What are the tools recommended for tethereal network capture?
A) You can use Wireshark. This is a network protocol analyzer for Unix and Windows.


Q) What are the auxillary tools required to troubleshoot Mediator?
A) You need to use the following tools:

  • WinSCP
  • Putty
  • HyperTerminal


Q) What does the LED status of the Mediator indicate?
A) The running status of the Mediator is described in the table below:

LED Code Status Description
None Power off
Initalizing
Rebooting
The Mediator is not powered up.
The Mediator is initializing.
The Mediator is rebooting
One long flash followed by a pause Idle The Mediator is booted up and running, but the Framework is not running.
Two short flashes followed by a pause Installing The Framework is starting for the first time and is installing itself.
Three long flashes followed by a pause Running The Framework is running normally.
Four short flashes followed by a pause Error The Framework is running, but errors are present. Check the Message Log for details.

Three short flashes, followed by three long flashes, followed by three short flashes, followed by a pause

Emergency The Framework has stopped running for at least two minutes.

Related Links:
"Frequently Asked Questions|Frequently Asked FAQs"

Rating: 0.0/5 (0 votes cast)

Personal tools