The switch adds it to its MAC address table associated with the port number. What action will occur if a switch receives a frame and does have the source MAC address in the MAC table The switch refreshes the timer on that entry. The host forwards the frame to all other hosts.
Cisco mac address table saved after power loss update#
PD device, Power source: PSE, Power Priority: High, Wattage: 6.5 The host sends the frame to the switch to update the MAC address table. Network Policy(Voice): VLAN 835, tagged, Layer-2 priority: 5, DSCP: 46 (PS) Power Source Entity, (PD) Power Device (NP) Network Policy, (LI) Location Identification Media Attachment Unit type - not advertised LLDP neighbor info showing voice vlan 835ĬLBdg640Test-AS2960-0#sh lldp neighbors fa0/1 detail Operational Trunking Encapsulation: nativeĪdministrative Native VLAN tagging: enabledĪdministrative private-vlan host-association: noneĪdministrative private-vlan mapping: noneĪdministrative private-vlan trunk native VLAN: noneĪdministrative private-vlan trunk Native VLAN tagging: enabledĪdministrative private-vlan trunk encapsulation: dot1qĪdministrative private-vlan trunk normal VLANs: noneĪdministrative private-vlan trunk associations: noneĪdministrative private-vlan trunk mappings: none Resulting Switchport config - voice vlan is 835ĬLBdg640Test-AS2960-0#show int fa0/1 switchportĪdministrative Trunking Encapsulation: dot1q Can anyone suggest why this is happening? There is no static mac address table blocking configured on the switch. I can see the MAC address of the phone is learned in the right VLANs, but the mac address is showing as "Drop", which normally means the address is statically configured to be blocked. However, I then see no traffic from the phone on the switch. On connecting the phone, I get the port authenticated and assigned to the correct VLAN, with LLDP-MED advertising the correct voice vlan. I am configuring a Cat 2960 port for connecting a VOIP phone, authenticated by MAB.
0 kommentar(er)
