Skip to main content
Cisco Meraki

Last Seen Switch Port of Client Keeps Changing

In an MS network, the Client details page reports the client's last known switch and port number:

Figure I.

 

This Dashboard information is based on the most recent MS switch to see the source MAC address of the client ingress one of its ports.

 

A client device's last known port could change frequently, showing up on different MS uplink ports, if a device is not directly connected to an MS switch.

 

Lets suppose you have a network comprising of MS switches and non-Meraki switches in which frames sent from devices connected to your non-Meraki switch must ingress an MS switch to reach their destination, as per the diagram below.

 

Figure II.

7ea8f2da-9a28-4e74-aca8-26c895f76a8f

In the example shown in Figure II. device A sends a frame to device B. This frame will ingress MS-1 port 1 and this will be reported as last seen. Immediately following communication with device B, device A sends a frame to device C. The frame will ingress MS-2 port 2 and this will change the last seen location to this switch and port combination.

 

When a wireless device is roaming between APs connected to different MS switchports. The mobile client will always appear as Last seen on the most recent switchport to receive frames from the mobile client.

 

Figure III.

1da8809f-25bb-402a-b7a1-8b767736bfbb

In the example shown in Figure III. a mobile client moves from AP1 to AP2 to AP3 respectively. If the client is sending data continuously they will first be reported as seen on MS-1 port 1, then last seen on MS-1 port 2 and finally last seen on MS-2 port 1.