12-06-2019 07:41 AM - edited 12-06-2019 07:43 AM
When I setup SPAN, I loose connectivity to the destination. I can’t remote into the destination computer to run Wireshark. These are 2 switches acting in a stack.
switch(config)#do show monitor session 1
Session 1
-------------
Type : Local Session
Source Ports :
Both : gi4/0/45
Destination Ports : Gi1/0/26
Encapsulation : Native
Ingress : Disabled
Solved! Go to Solution.
12-06-2019 07:58 AM
if the port where the device connected - you enable span monitor this will be monitor port so you will loose access.
best is PC have 2 nic cards for you to remote in and monitor other connect for the span port (wireshark).
12-06-2019 07:56 AM
That is normal behavior of a SPAN destination port.
The state of the destination port is up/down by design. The interface shows the port in this state in order to make it evident that the port is currently not usable as a production port.
see link for further info:
HTH
12-06-2019 07:58 AM
if the port where the device connected - you enable span monitor this will be monitor port so you will loose access.
best is PC have 2 nic cards for you to remote in and monitor other connect for the span port (wireshark).
12-06-2019 08:08 AM
Does this mean if Wireshark were already running on the destionation, Wireshark would still capture the packets even though I can not access the destination?
12-06-2019 08:16 AM
That is correct. Wireshark will capture the packets.
HTH
12-06-2019 08:45 AM
Thanks!
12-06-2019 08:41 AM
yes if your already running Wireshark on that port, and you have all the information capture on the destination device.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide