You observe issues with VM traffic after configuring a
session with Ethernet destinations.
|
—
|
Ensure that the Ethernet destination is not connected to
the same uplink switch. The SPAN packets might cause problems with the IP
tables, the MAC tables, or both on the uplink switch, which can cause problems
with the regular traffic.
|
A session state is up and the packets are not received at
the destination ports.
|
—
|
Verify that the correct VLANs are allowed on the trunk
destination ports.
|
The session displays an error.
|
—
|
- Make sure that
VSM-VEM connectivity is working correctly.
- Force
reprogramming of the session on the VEM.
-
shut
-
no shut
|
The ERSPAN session is up, but does not see packets at the
destination.
|
The ERSPAN ID is not configured.
|
Make sure that the ERSPAN ID is configured at the
destination.
|
An ERSPAN-enabled VMKernel NIC is not configured on the
host or VEM.
|
Make sure that you create a VMKernel NIC on the host using
a port profile configured for ERSPAN.
|
The ERSPAN-enabled VMKernel NIC is not configured with a
proper IP, gateway, or both.
|
Ping the ERSPAN IP destination from the host VMKernel NIC.
vmkping
dest-id
Use the
vempkt command to capture packets
on the VMKernel NIC LTL and ensure ERSPAN packets are being sent. Use the
vemlog debug sfspan d command so
that the ERSPAN packets appear in the vempkt capture log.
|