Bridge GUI Guide: Monitoring
189
listed in ascending order of cost, with the lowest cost path
listed first.)
Routes
- possible routes to the destination MP in
descending order of preference
5.8.7
FastPath Mesh Loops
FP Mesh prevents bridging loops from forming on Core
interfaces, which connect MPs to one another. A network loop
can form, however, when MPs can also detect one another on
their FP Mesh Access interfaces. If such a loop exists on the
network, it is displayed in the
Mesh Status
screen’s
Loops
frame.
Figure 5.26.
Mesh Status
screen,
Loops
frame, all platforms
Review the network topology to make sure that the
connections causing the loops are intentional (for purposes of
redundancy) rather than accidental.
MAC Address
- the MAC address of the Mesh Point
detected by the current MP on an FP Mesh Access
interface
Interface
- the FP Mesh Access interface on which the
network MP is detected
State
- whether that interface is
blocking
,
forwarding
or
disabled
Reason
- why the interface is the current
State
(above)
5.9 System Log Monitoring
The Bridge logs significant system activity and status
information.
Access the log by clicking
Monitor
->
System Log
.
If you log on to a
Log Viewer-
level account, the Bridge GUI
opens on the
System Log
screen.
Administrator
- and
Maintenance
-level administrators can view the entire log, while
Log Viewer
-level administrators can view only non-
configuration events.
Each activity item is date-and-time stamped, its severity is
indicated and a brief text description is given. Among other
information, the log records:
FIPS self-test runs and results
when Secure Clients contact and negotiate keys with the
Bridge
system configuration changes
