From e92cf99540dc93571f75461526f7ba0973f1d735 Mon Sep 17 00:00:00 2001 From: Yuri Slobodyanyuk Date: Wed, 16 Nov 2022 15:49:42 +0000 Subject: [PATCH] ETX mac-table addition --- ...ebug-and-information-commands-cheat-sheet.adoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/cheat-sheets/RAD-ETX-203-205-220-debug-and-information-commands-cheat-sheet.adoc b/cheat-sheets/RAD-ETX-203-205-220-debug-and-information-commands-cheat-sheet.adoc index cb6a6de..45936a9 100644 --- a/cheat-sheets/RAD-ETX-203-205-220-debug-and-information-commands-cheat-sheet.adoc +++ b/cheat-sheets/RAD-ETX-203-205-220-debug-and-information-commands-cheat-sheet.adoc @@ -66,6 +66,21 @@ service-ping local-ip 13.13.13.1/30 dst-ip 13.13.13.2 next-hop 13.13.13.2 egress |*show configure flows summary details* |List all flows configured on this ETX with details +|*config flow _name_* + +*mac-learning* + +*show mac-table* + +*no mac-learning* +|Enable MAC address learning inside a flow. The _flow_ should be the one where +those MAC addresses are supposed to be learned, and in the appropriate +direction. E.g. if the equipment of the end client is connected to ETX port +`ethernet 0/10`, then you should run this command under the flow that has +`ingress port 0/10`, to see if the ETX can see client's equipment. WARNING: +after showing the results, make sure to disable the MAC learning, as it may +interfere with the client's traffic. + |*show config system system-date* | Show system time of the appliance, important for logs/alarms correlation.