HP Service Insertion Guide K/KA/WB.15.15

Tunnel operational status
Troubleshooting helpPossible causeIssueID
Run the following CLI command to check for
tunnel endpoint IP resolution status.
Network connectivity issue
• The tunnel endpoint is on a
directly connected subnet but
down (not responding to ARP
requests).
• The tunnel endpoint is not on a
directly connected subnet and
there is no IP route on the
switch to reach the tunnel
endpoint IP address.
• The tunnel endpoint is not on a
directly connected subnet, there
is an IP route on the switch to
reach the endpoint IP address
but the corresponding nexthop
is down (not responding to ARP
requests).
• The uplink interface on the
switch via which the endpoint
or gateway is reachable is
down.
Tunnel’s operstatus is reported
as DOWN in the CLI or Event
logs or via OpenFlow.
1
HP-3800-SW# show interface tunnel
type intercept
Status
Interface State : Down
Down Reason : No route to
destination
Destination Address Route :
Next Hop IP :
Next Hop Interface :
Next Hop IP Link Status :
Source Address :
Egress port :
Look for the ‘State’ field being ‘Down’ and
also the ‘Down Reason’ and ‘Next Hop’
related fields below this field.
If there is no route to the destination, the
Nexthop fields would be empty.
Check the IP route table, gateway availability
and uplink interface status to troubleshoot
further.
Look for the following message in the event
logs:
ASIC component failure
Loopback port going down can
result in tunnels momentarily going
Tunnel’s operstatus is reported
as DOWN in the CLI or Event
logs or OpenFlow.
2
Service Tunnel decapsulation
interface flap – Packets may have
been dropped.
down (software picks a new
loopback port as soon as the
current loopback port goes down).
When the last line card goes down, the tunnel
will be reported as down until a new line card
comes up again.
Note that a loopback port goes
down only when a line card that
Run the following CLI command to know if
the tunnel is down due to resource
unavailability.
houses the loopback port goes
down. There is one loopback port
on every linecard and so if one
linecard goes down, another
HP-3800-SW# show interface tunnel
type intercept
linecard’s loopback port will start
handling tunnel packets.
Status
During the transition, tunneled
packets can be dropped.
Interface State : Down
Down Reason : Out of resources
Look for the “Down Reason” field in the output
that indicates there are no ASIC resources.
On stackable platforms, each port
group represents the equivalent of
one linecard and has one
loopback port. If a port group is
down, a loopback port from
another port group will handle
tunneled packets.
Encapsulation path - traffic steering to tunnel (via OpenFlow)
Troubleshooting helpPossible causeIssueID
Run the following CLI command and
check if the ifindex in the OpenFlow
Flow Mod rule is valid.
Invalid tunnel ifindex
The tunnel ifindex in an OF FlowMod
must match a configured tunnel
interface’s ifIndex.
FlowMod failure when trying to
program an OpenFlow rule that is
diverting packets to a tunnel
interface.
1
HP-3800-SW$ show interface
tunnel type intercept
Otherwise, the FlowMod will fail.
Interface Index :
1000000001
20 Service Insertion