Skip to content

Commit 36cf87d

Browse files
cumulusAniacumulusAnia
committed
fix command output format
1 parent 859695d commit 36cf87d

2 files changed

Lines changed: 82 additions & 79 deletions

File tree

‎content/cumulus-linux-516/Layer-3/Routing/Routing-Tables.md‎

Lines changed: 41 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -80,49 +80,50 @@ The following example looks up the route in the routing table for the destinatio
8080
```
8181
cumulus@switch:~$ nv action lookup vrf default router fib ipv4 10.10.10.3
8282
Action executing ...
83-
84-
dst: 10.10.10.4
85-
nhid: 106
86-
protocol: bgp
87-
metric: 20
88-
flags: []
89-
90-
id: 106
91-
group: 62,102
92-
protocol: zebra
93-
flags: []
94-
95-
id: 62
96-
gateway: fe80::4ab0:2dff:feff:6ac0
97-
dev: swp52
98-
scope: link
99-
protocol: zebra
100-
flags: []
101-
102-
id: 102
103-
gateway: fe80::4ab0:2dff:fe8b:d6bf
104-
dev: swp51
105-
scope: link
106-
protocol: zebra
107-
flags: []
108-
109-
Action succeeded
83+
{
84+
"dst": "10.10.10.3/32",
85+
"nhid": 106,
86+
"protocol": "bgp",
87+
"metric": 20,
88+
"flags": [],
89+
"nexthop": {
90+
"id": 106,
91+
"group": {
92+
"62": {
93+
"gateway": "fe80::4ab0:2dff:feff:6ac0",
94+
"dev": "swp52",
95+
"scope": "link",
96+
"protocol": "zebra",
97+
"flags": []
98+
},
99+
"102": {
100+
"gateway": "fe80::4ab0:2dff:fe8b:d6bf",
101+
"dev": "swp51",
102+
"scope": "link",
103+
"protocol": "zebra",
104+
"flags": []
105+
}
106+
},
107+
"protocol": "zebra",
108+
"flags": []
109+
}
110+
}
111+
Action succeeded
110112
```
111113

112114
The following example shows the route in the routing table for the destination with the IPv6 address 228:35::5
113115

114116
```
115117
cumulus@switch:~$ nv action lookup vrf default router fib ipv6 fe80::4ab0:2dff:fe8b:d6bf
116-
Action executing ...
117-
118-
dst: fe80::/64
119-
dev: br_default
120-
protocol: kernel
121-
metric: 256
122-
flags: []
123-
pref: medium
124-
125-
Action succeeded
118+
{
119+
"dst": "fe80::/64",
120+
"dev": "br_default",
121+
"protocol": "kernel",
122+
"metric": 256,
123+
"flags": [],
124+
"pref": "medium"
125+
}
126+
Action succeeded
126127
```
127128

128129
## Show FIB Table Entries
@@ -180,9 +181,9 @@ To show IPv4 FIB table entries for a specific prefix in a VRF, run the `nv show
180181
```
181182
cumulus@leaf01:~$ nv show vrf default router fib ipv4 route 10.10.10.1/32
182183
183-
Prefix Next-hop Proto Scope Summary
184-
------------------ ---------------------- ------ ------ -----------------------
185-
10.10.10.1/32 nhid 68 bgp global Metric: 20
184+
Prefix Next-hop Protocol Scope Summary
185+
------------- -------- -------- ------ ----------
186+
10.10.10.1/32 nhid 68 bgp global Metric: 20
186187
```
187188

188189
To show IPv6 FIB table entries for a specific prefix in a VRF, run the `nv show vrf <vrf-id> router fib ipv6 route <prefix>` command.

‎content/cumulus-linux-517/Layer-3/Routing/Routing-Tables.md‎

Lines changed: 41 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -80,49 +80,51 @@ The following example looks up the route in the routing table for the destinatio
8080
```
8181
cumulus@switch:~$ nv action lookup vrf default router fib ipv4 10.10.10.3
8282
Action executing ...
83-
84-
dst: 10.10.10.4
85-
nhid: 106
86-
protocol: bgp
87-
metric: 20
88-
flags: []
89-
90-
id: 106
91-
group: 62,102
92-
protocol: zebra
93-
flags: []
94-
95-
id: 62
96-
gateway: fe80::4ab0:2dff:feff:6ac0
97-
dev: swp52
98-
scope: link
99-
protocol: zebra
100-
flags: []
101-
102-
id: 102
103-
gateway: fe80::4ab0:2dff:fe8b:d6bf
104-
dev: swp51
105-
scope: link
106-
protocol: zebra
107-
flags: []
108-
109-
Action succeeded
83+
{
84+
"dst": "10.10.10.3/32",
85+
"nhid": 106,
86+
"protocol": "bgp",
87+
"metric": 20,
88+
"flags": [],
89+
"nexthop": {
90+
"id": 106,
91+
"group": {
92+
"62": {
93+
"gateway": "fe80::4ab0:2dff:feff:6ac0",
94+
"dev": "swp52",
95+
"scope": "link",
96+
"protocol": "zebra",
97+
"flags": []
98+
},
99+
"102": {
100+
"gateway": "fe80::4ab0:2dff:fe8b:d6bf",
101+
"dev": "swp51",
102+
"scope": "link",
103+
"protocol": "zebra",
104+
"flags": []
105+
}
106+
},
107+
"protocol": "zebra",
108+
"flags": []
109+
}
110+
}
111+
Action succeeded
110112
```
111113

112114
The following example shows the route in the routing table for the destination with the IPv6 address 228:35::5
113115

114116
```
115117
cumulus@switch:~$ nv action lookup vrf default router fib ipv6 fe80::4ab0:2dff:fe8b:d6bf
116118
Action executing ...
117-
118-
dst: fe80::/64
119-
dev: br_default
120-
protocol: kernel
121-
metric: 256
122-
flags: []
123-
pref: medium
124-
125-
Action succeeded
119+
{
120+
"dst": "fe80::/64",
121+
"dev": "br_default",
122+
"protocol": "kernel",
123+
"metric": 256,
124+
"flags": [],
125+
"pref": "medium"
126+
}
127+
Action succeeded
126128
```
127129

128130
## Show FIB Table Entries
@@ -180,9 +182,9 @@ To show IPv4 FIB table entries for a specific prefix in a VRF, run the `nv show
180182
```
181183
cumulus@leaf01:~$ nv show vrf default router fib ipv4 route 10.10.10.1/32
182184
183-
Prefix Next-hop Proto Scope Summary
184-
------------------ ---------------------- ------ ------ -----------------------
185-
10.10.10.1/32 nhid 68 bgp global Metric: 20
185+
Prefix Next-hop Protocol Scope Summary
186+
------------- -------- -------- ------ ----------
187+
10.10.10.1/32 nhid 68 bgp global Metric: 20
186188
```
187189

188190
To show IPv6 FIB table entries for a specific prefix in a VRF, run the `nv show vrf <vrf-id> router fib ipv6 route <prefix>` command.

0 commit comments

Comments
 (0)