Extreme Networks EPICenter 6.0, Справочное руководство

Страница: 464 / 580

EAPS Protocol Monitoring and Verification
EPICenter Reference Guide
464
If errors are reported, you should log into the affected device(s) to correct the problems. (You can do
this using the EPICenter Interactive Telnet feature, assuming you have the proper Administrator
privileges.) Once you have corrected any reported errors, you should run the verification again to
ensure that the configuration is correct.
●
Click the Refresh button to re-run the verification process.
●
Click Save... to save the verification results to a file.
The recommended workflow for identifying and correcting EAPS configuration problems is as follows:
1 Run the Verify EAPS command.
2 If there are errors, you can click the domain or device link in the source column, and this will put
you into Focus mode for the domain or device where the errors occurred.
3 From a highlighted device node on the EAPS map, you can run the EAPS Log report, which may
contain much information useful in debugging these issue. (Just move the cursor over the node and
the resulting pop-up contains a link to generate the EAPS Log Report—
Figure 234 on page 459
shows this pop-up.)
4 From the highlighted device node on the EAPS map, right-click to bring up the pop-up menu, then
select
Device > Telnet . This opens an interactive Telnet session on the device, without exiting the
EAPS Monitor application. This means you can execute CLI commands on the device while still
viewing the EAPS Verification Report and the EAPS map showing the highlighted device or domain.
5 When you have fixed the problems via ExtremeWare or ExtremeXOS commands, you can close the
Telnet applet, and then Refresh the EAPS Verification Report to see the results of your corrections.
NOTE
It may take multiple iterations of correcting errors and running the verification process to produce a correct EAPS
configuration, as correcting one set of configuration errors may reveal other errors. You should continue to re-run the
verification process until no errors are reported.
The following table lists the error types that may be reported by the EAPS verification process:
Source The element that was the source of the error. By clicking this link you can
highlight the domain, device, or link on the EAPS map.
Description An more detailed description of the error.
Table 46: EAPS Verification Error Types
• No Master Node • Inconsistent EAPS Node Naming • No Physical Link
• Multiple Master Nodes • Control VLAN not in QP3 • Domain List Mismatch
• Disabled EAPS Node • Unprotected Shared Link • Link ID Not Configured
• Missing Control VLAN • Duplicate Link ID • Control VLAN Misconfigured
• Missing Primary Domain Port • Missing Link ID • Protected VLAN Misconfigured
• Missing Secondary Domain
Port
• Mismatched Link ID • Shared Port Misconfigured
• Mismatched Domain Ports • Misconfigured Shared Port Mode • Controller Misconfigured
• Incomplete VLAN Protection • Shared Port Not Created
Table 45: EAPS Verification Results Report
Column