-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
None
In my setup I have a physical interface taken over by VPP. I assign IP to that interface and in show ip fib in shows up fine. However, when I do ip_fib_dump, I see the is_drop flag is on, and that's why in hc2vpp, they show the next hop to be `blackhole`.
Here are the details:
Output of sh int:
vpp# show int
Name Idx State Counter Count
GigabitEthernet0/9/0 1 up
GigabitEthernet0/a/0 2 up
local0 0 down
Output of sh int addr:
GigabitEthernet0/9/0 (up): 10.10.10.100/24 GigabitEthernet0/a/0 (up): 10.0.0.100/24 local0 (dn):
In sh ip fib, we see these routes related to 10.0.0.X:
10.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:10 buckets:1 uRPF:9 to:[0:0]] [0] [@0]: dpo-drop ip4 10.0.0.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:9 buckets:1 uRPF:14 to:[0:0]] [0] [@4]: ipv4-glean: GigabitEthernet0/a/0 10.0.0.100/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:12 buckets:1 uRPF:13 to:[0:0]] [0] [@2]: dpo-receive: 10.0.0.100 on GigabitEthernet0/a/0 10.0.0.255/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:11 buckets:1 uRPF:11 to:[0:0]] [0] [@0]: dpo-drop ip4
In vat however, the ip_fib_dump is:
table-id 0, prefix 10.0.0.0/32 weight 1, sw_if_index -1, is_local 0, is_drop 0, is_unreach 0, is_prohitbit 0, afi 1, next_hop 0.0.0.0 table-id 0, prefix 10.0.0.100/24 weight 1, sw_if_index 2, is_local 0, is_drop 1, is_unreach 0, is_prohitbit 0, afi 1, next_hop 0.0.0.0 table-id 0, prefix 10.0.0.100/32 weight 1, sw_if_index 2, is_local 0, is_drop 1, is_unreach 0, is_prohitbit 0, afi 1, next_hop 10.0.0.100 table-id 0, prefix 10.0.0.255/32 weight 1, sw_if_index -1, is_local 0, is_drop 0, is_unreach 0, is_prohitbit 0, afi 1, next_hop 0.0.0.0
Is the dump correct? Due to is_drop flag is on the next hop in operational routes in HC2VPP is appears to be 'blackhole'.
Note:
If I do a tap connect and assign it a /24 ip, the ip_fib_dump for the corresponding routes will not have is_drop on.
- blocks
-
HC2VPP-196 Operational route data is unrepresentative of fib table
- Done