But if you scroll down in the text file to the output of show interfaces all and check the counters of this ports, you will see that Unicast Rx is showing 0. No mac-addresses were learned on ports 1 to 10. Maybe you can also provide the output of show running-config, so we can check if something in the configuration may affect the mac-learning. Maybe the cable was attached to another port by mistake. So please make sure that the attached end device is active and sending traffic through the switch.Ĭheck with the command show interface 1 is the interface is UP or DOWN.Ĭheck with show mac-address (without specifying port) if the mac address appeares on another port. The entry will age out and be removed if no packet was received in the last 5 minutes. You can use the command show lldp info remote on the switch to check which devices sent LLDP information.īut of course the mac-address should be visible in the mac-address table if the device sent at least one packet trough the switch in the last 5 minutes. A layer2 switch configured for authentication can use the feature ip client-tracker but this switch doesnt support it.Įnd device that support LLDP can also provide information to the switch via LLDP TLVs. Only a 元 switch or router should have the IPs in the arp table and only for this clients which need their traffic to be routed. It uses MAC addresses for forwarding dicisions and doesnt need IP to mac mappings (arp entries). HPE Blog, Austria, Germany & SwitzerlandĪ layer 2 switch will by default not display arp information about directly connected devices.
0 kommentar(er)
