to a destination and it selects the wrong route based on metric. Alot of this issue may be based on the seed metric that was put into the redistribution
The best way to look at this is in lab form
LAB
------
so we have fully meshed frame-relay
and we have 2 as rip and ospf
We have 2 redistribution points
r1 will redistribute rip into opsf
r3 will redistribute ospf into rip
so ideally what we want is fully connectivity between the two routing domains
R1
---
r1(config)#router ospf 1
r1(config-router)#redistribute rip subnets
r1(config-router)#
so we have redistributed rip into ospf
s3
---
switch3#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
O E2 1.1.1.1 [110/20] via 192.168.2.1, 00:01:19, Port-channel1
2.0.0.0/32 is subnetted, 1 subnets
O E2 2.2.2.2 [110/20] via 192.168.2.1, 00:01:19, Port-channel1
33.0.0.0/24 is subnetted, 1 subnets
C 33.33.33.0 is directly connected, Loopback0
3.0.0.0/32 is subnetted, 1 subnets
O E2 3.3.3.3 [110/20] via 192.168.2.1, 00:01:19, Port-channel1
22.0.0.0/32 is subnetted, 1 subnets
O E2 22.22.22.22 [110/20] via 192.168.2.1, 00:01:19, Port-channel1
O 192.168.5.0/24 [110/2] via 192.168.2.1, 00:01:19, Port-channel1
10.0.0.0/24 is subnetted, 2 subnets
O E2 10.228.254.0 [110/20] via 192.168.2.1, 00:01:19, Port-channel1
O E2 10.229.254.0 [110/20] via 192.168.2.1, 00:01:20, Port-channel1
11.0.0.0/32 is subnetted, 1 subnets
O 11.11.11.11 [110/2] via 192.168.2.1, 00:01:20, Port-channel1
O 192.168.1.0/24 [110/2] via 192.168.2.1, 00:01:20, Port-channel1
C 192.168.2.0/24 is directly connected, Port-channel1
44.0.0.0/32 is subnetted, 1 subnets
O 44.44.44.44 [110/3] via 192.168.2.1, 00:01:20, Port-channel1
O 192.168.3.0/24 [110/2] via 192.168.2.1, 00:01:20, Port-channel1
switch3#ping 22.22.22.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Although the ospf domain knows how to get to the rip domain it has routes for example 22.22.22.22 which is s2 loopback in the rip domain the ping is failing.
s2
---
switch2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
R 1.1.1.1 [120/2] via 10.228.254.2, 00:00:25, FastEthernet0/2
2.0.0.0/32 is subnetted, 1 subnets
R 2.2.2.2 [120/1] via 10.228.254.2, 00:00:25, FastEthernet0/2
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/2] via 10.228.254.2, 00:00:25, FastEthernet0/2
22.0.0.0/32 is subnetted, 1 subnets
C 22.22.22.22 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 2 subnets
C 10.228.254.0 is directly connected, FastEthernet0/2
R 10.229.254.0 [120/1] via 10.228.254.2, 00:00:25, FastEthernet0/2
switch2#
switch 2 has only routes to the rip domain it has no way of knowing how to get back to return the ping traffic to the rip domain
if i put debug icmp on s2 and ping 22.22.22.22
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
01:31:05: ICMP: echo reply sent, src 22.22.22.22, dst 192.168.2.3
we are recieving the icmp ping but we do not have a route to 192.168.2.3
so lets redistribute ospf routes into rip
r3
---
r3(config)#router rip
r3(config-router)#redistribute ospf 1 metric 1
r3(config-router)#
so we are redistributing ospf with a seed metric of 1 hop
On s3 the ping is still failing
switch3#ping 22.22.22.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
switch3#
s2
---
switch2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
R 1.1.1.1 [120/2] via 10.228.254.2, 00:00:12, FastEthernet0/2
2.0.0.0/32 is subnetted, 1 subnets
R 2.2.2.2 [120/1] via 10.228.254.2, 00:00:12, FastEthernet0/2
33.0.0.0/32 is subnetted, 1 subnets
R 33.33.33.33 [120/2] via 10.228.254.2, 00:00:12, FastEthernet0/2
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/2] via 10.228.254.2, 00:00:12, FastEthernet0/2
22.0.0.0/32 is subnetted, 1 subnets
C 22.22.22.22 is directly connected, Loopback0
R 192.168.5.0/24 [120/2] via 10.228.254.2, 00:00:13, FastEthernet0/2
10.0.0.0/24 is subnetted, 2 subnets
C 10.228.254.0 is directly connected, FastEthernet0/2
R 10.229.254.0 [120/1] via 10.228.254.2, 00:00:14, FastEthernet0/2
11.0.0.0/32 is subnetted, 1 subnets
R 11.11.11.11 [120/2] via 10.228.254.2, 00:00:14, FastEthernet0/2
R 192.168.1.0/24 [120/2] via 10.228.254.2, 00:00:14, FastEthernet0/2
R 192.168.2.0/24 [120/2] via 10.228.254.2, 00:00:14, FastEthernet0/2
44.0.0.0/32 is subnetted, 1 subnets
R 44.44.44.44 [120/2] via 10.228.254.2, 00:00:14, FastEthernet0/2
R 192.168.3.0/24 [120/2] via 10.228.254.2, 00:00:14, FastEthernet0/2
switch2#ping 192.168.2.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 58/65/68 ms
switch2#
we have a route to 192.168.2.3 and ping successfully
s3
---
Ok lets on s3 do a trace route 22.22.22.22
switch3#traceroute 22.22.22.22
Type escape sequence to abort.
Tracing the route to 22.22.22.22
1 192.168.2.1 0 msec 0 msec 0 msec
2 192.168.3.1 0 msec 0 msec 0 msec
3 10.229.254.3 9 msec 8 msec 17 msec
4 192.168.1.1 8 msec 17 msec 8 msec
5 192.168.3.1 17 msec 33 msec 17 msec
6 10.229.254.3 17 msec 17 msec 25 msec
7 192.168.1.1 25 msec 17 msec 25 msec
8 192.168.3.1 25 msec 25 msec 25 msec
9 10.229.254.3 34 msec 42 msec 42 msec
10 192.168.1.1 42 msec 33 msec 34 msec
11 192.168.3.1 34 msec 42 msec 42 msec
12 10.229.254.3 42 msec 50 msec 50 msec
OK we have an issue
s3 is sending the packet to s1 which is sending the packet then to r1. R1 is then sending the packet to r3??? (realistically we would want it to go to r2
Then r3 is sending the packet to s1 which is sending to r1 which is sending in to r3 so we have a loop
Lets take a look why r1 is selecting r3 over r1
r1#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
R 2.2.2.2 [120/1] via 10.229.254.3, 00:00:25, Serial0/0
[120/1] via 10.229.254.2, 00:00:26, Serial0/0
33.0.0.0/32 is subnetted, 1 subnets
O 33.33.33.33 [110/3] via 192.168.3.11, 00:42:00, FastEthernet0/0
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/1] via 10.229.254.3, 00:00:25, Serial0/0
22.0.0.0/32 is subnetted, 1 subnets
R 22.22.22.22 [120/1] via 10.229.254.3, 00:00:26, Serial0/0
O 192.168.5.0/24 [110/2] via 192.168.3.11, 00:42:01, FastEthernet0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.228.254.0 [120/1] via 10.229.254.3, 00:00:05, Serial0/0
[120/1] via 10.229.254.2, 00:00:04, Serial0/0
C 10.229.254.0 is directly connected, Serial0/0
11.0.0.0/32 is subnetted, 1 subnets
O 11.11.11.11 [110/2] via 192.168.3.11, 00:42:06, FastEthernet0/0
O 192.168.1.0/24 [110/2] via 192.168.3.11, 00:42:06, FastEthernet0/0
O 192.168.2.0/24 [110/2] via 192.168.3.11, 00:42:06, FastEthernet0/0
44.0.0.0/32 is subnetted, 1 subnets
O 44.44.44.44 [110/3] via 192.168.3.11, 00:42:06, FastEthernet0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
so r1 is learning 22.22.22.22 natively in rip via r2 with hop of 2 which we redistributed into ospf. R3 was recieving the network 22.22.22.22 from ospf
(admin distance of 110) and rip from r2 (Admin distance of 120) so it selected the ospf route. We then redistributed ospf into rip with metric of 1
r3#sh ip route 22.22.22.22
Routing entry for 22.22.22.22/32
Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric 2
Redistributing via rip
Advertised by rip metric 1
Last update from 192.168.1.1 on FastEthernet0/0, 00:01:54 ago
Routing Descriptor Blocks:
* 192.168.1.1, from 1.1.1.1, 00:01:54 ago, via FastEthernet0/0
Route metric is 20, traffic share count is 1
*Mar 1 02:27:53.999: RIP: received v2 update from 10.229.254.2 on Serial0/0
*Mar 1 02:27:54.003: 1.1.1.1/32 via 10.229.254.3 in 2 hops
*Mar 1 02:27:54.003: 2.2.2.2/32 via 0.0.0.0 in 1 hops
*Mar 1 02:27:54.003: 3.3.3.3/32 via 10.229.254.3 in 2 hops
*Mar 1 02:27:54.003: 10.228.254.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:27:54.003: 10.229.254.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:27:54.003: 11.11.11.11/32 via 10.229.254.3 in 2 hops
*Mar 1 02:27:54.007: 22.22.22.22/32 via 10.229.254.3 in 2 hops
notice from 10.229.254.2 (r2) the 22.22.22.22 network is 2 hops away
while
*Mar 1 02:28:00.535: RIP: received v2 update from 10.229.254.3 on Serial0/0
*Mar 1 02:28:00.539: 1.1.1.1/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.539: 2.2.2.2/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.539: 3.3.3.3/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.539: 10.228.254.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.539: 10.229.254.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.539: 11.11.11.11/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 22.22.22.22/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 33.33.33.33/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 44.44.44.44/32 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 192.168.1.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 192.168.2.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 192.168.3.0/24 via 0.0.0.0 in 1 hops
*Mar 1 02:28:00.543: 192.168.5.0/24 via 0.0.0.0 in 1 hopsu all
while from r3 the 22.22.22.22 network is 1 hop away
so r1 was now recieiving a route from r3 the redistributed ospf route of 22.22.22.22 with metric of 1 vs the 22.22.22.22 from native rip metric of 2
so it selected the route via r3 as a metric this then has cause a loop based on metric
There is a few ways to repair this we could do a distribute list to filter the route on r1 recieved from r3
lets take a look at this
so on r1
we will do
r1
===
r1#sh run | begin access-list 112
access-list 112 deny ip host 10.229.254.3 host 22.22.22.22
access-list 112 permit ip any any
so i define my access list say deny from source of 10.229.254.3 (r3 source for routing updates) and i want to block the update for 22.22.22.22
then i allow ip any any as match everything else other wise it would deny everything from source 22.22.22.22
r1#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
R 2.2.2.2 [120/1] via 10.229.254.3, 00:00:21, Serial0/0
[120/1] via 10.229.254.2, 00:00:10, Serial0/0
33.0.0.0/32 is subnetted, 1 subnets
O 33.33.33.33 [110/3] via 192.168.3.11, 00:12:20, FastEthernet0/0
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/1] via 10.229.254.3, 00:00:21, Serial0/0
22.0.0.0/32 is subnetted, 1 subnets
R 22.22.22.22 [120/2] via 10.229.254.2, 00:02:36, Serial0/0
O 192.168.5.0/24 [110/2] via 192.168.3.11, 00:12:22, FastEthernet0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.228.254.0 [120/1] via 10.229.254.3, 00:00:23, Serial0/0
[120/1] via 10.229.254.2, 00:00:12, Serial0/0
C 10.229.254.0 is directly connected, Serial0/0
11.0.0.0/32 is subnetted, 1 subnets
O 11.11.11.11 [110/2] via 192.168.3.11, 00:12:22, FastEthernet0/0
O 192.168.1.0/24 [110/2] via 192.168.3.11, 00:12:22, FastEthernet0/0
O 192.168.2.0/24 [110/2] via 192.168.3.11, 00:12:22, FastEthernet0/0
44.0.0.0/32 is subnetted, 1 subnets
O 44.44.44.44 [110/3] via 192.168.3.11, 00:12:22, FastEthernet0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
r1#
r1#sh ip route 22.22.22.22
Routing entry for 22.22.22.22/32
Known via "rip", distance 120, metric 2
Redistributing via ospf 1, rip
Advertised by ospf 1 subnets
Last update from 10.229.254.2 on Serial0/0, 00:03:03 ago
Routing Descriptor Blocks:
* 10.229.254.2, from 10.229.254.2, 00:03:03 ago, via Serial0/0
Route metric is 2, traffic share count is 1
r1#
we are now recieving 22.22.22.22 via r2 as a hop count of 2 so we have filtered from r3 but notice we are still recieving all other routes from r3
Now on s3 we can ping
s3
---
switch3#ping 22.22.22.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 59/65/67 ms
switch3#
so we have resolved the issue but this is a bit of short sighted solution there is bound to be other networks downstream which could have similar issues
The problem really originates from redistributing rip routes into ospf and then ospf redistributing these rip routes back into rip. A solution could be
higher metric at redistribution this could get hard to manange with some downstream routes still having problems. The best solution is to stop the rip routes
that where redistributed into ospf from getting back into the rip domain but still allowing the ospf routes in.
We can use a solution as route-tagging
i will change r1 back to having the previous issue with 22.22.22.22
r1
--
r1(config)#router rip
r1(config-router)#no distribute-list 112 serial0/0
r1(config-router)#no distribute-list 112 in s0/0
s3
---
switch3#traceroute 22.22.22.22
Type escape sequence to abort.
Tracing the route to 22.22.22.22
1 192.168.2.1 0 msec 0 msec 0 msec
2 192.168.3.1 0 msec 0 msec 0 msec
3 10.229.254.3 8 msec 8 msec 17 msec
4 192.168.1.1 8 msec 9 msec 16 msec
5 192.168.3.1 9 msec 8 msec 17 msec
6 10.229.254.3 25 msec 50 msec 17 msec
7 192.168.1.1 25 msec 17 msec 25 msec
8 192.168.3.1 26 msec 17 msec 25 msec
switch 3 is back looping when trying to get 2.2.2.2
On r1 lets look at how to repair
r1
---
r1(config)#route-map TAG permit 10
r1(config-route-map)#set tag 10
r1(config-route-map)#exit
r1(config)#router ospf 1
r1(config-router)#no redistribute subnets
Unknown routing protocol - "no redistribute subnets"
r1(config-router)#no redistribute rip subnets
r1(config-router)#no redistribute rip
r1(config-router)#redistribute rip subnets route-map TAG
r1(config-router)#
so basically we create a route-map name TAG anything that goes through the route-map will be set with a TAG 10.
We then applied this route-map to the redistribution into rip
If we look on switch 3 at route redistributed from rip 22.22.22.22
s3
---
switch3#sh ip route 22.22.22.22
Routing entry for 22.22.22.22/32
Known via "ospf 1", distance 110, metric 20
Tag 10, type extern 2, forward metric 2
Redistributing via rip
Last update from 192.168.2.1 on Port-channel1, 00:02:51 ago
Routing Descriptor Blocks:
* 192.168.2.1, from 1.1.1.1, 00:02:51 ago, via Port-channel1
Route metric is 20, traffic share count is 1
Route tag 10
switch3#
r3
---
r3#config t
Enter configuration commands, one per line. End with CNTL/Z.
r3(config)#route-map MATCHTAG deny 10
r3(config-route-map)#match tag 10
r3(config-route-map)#route-map MATCHTAG permit 20
r3(config-route-map)#exit
r3(config)#
now on r3 we will create a route-map to deny anything with a tag of 10 and then permit everything else.
Now we will apply this to the routing process during redistribution
r3(config)#router rip
r3(config-router)#no redistribute ospf 1 metric 1
r3(config-router)#redistribute ospf 1 metric 1 route-map MATCHTAG
r3(config-router)#
r1
--
r1#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
R 2.2.2.2 [120/1] via 10.229.254.2, 00:00:00, Serial0/0
33.0.0.0/32 is subnetted, 1 subnets
O 33.33.33.33 [110/3] via 192.168.3.11, 00:07:40, FastEthernet0/0
3.0.0.0/32 is subnetted, 1 subnets
R 3.3.3.3 [120/1] via 10.229.254.3, 00:00:07, Serial0/0
22.0.0.0/32 is subnetted, 1 subnets
R 22.22.22.22 [120/2] via 10.229.254.2, 00:00:00, Serial0/0
O 192.168.5.0/24 [110/2] via 192.168.3.11, 00:07:41, FastEthernet0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.228.254.0 [120/1] via 10.229.254.2, 00:00:01, Serial0/0
C 10.229.254.0 is directly connected, Serial0/0
11.0.0.0/32 is subnetted, 1 subnets
O 11.11.11.11 [110/2] via 192.168.3.11, 00:07:42, FastEthernet0/0
O 192.168.1.0/24 [110/2] via 192.168.3.11, 00:07:42, FastEthernet0/0
O 192.168.2.0/24 [110/2] via 192.168.3.11, 00:07:42, FastEthernet0/0
44.0.0.0/32 is subnetted, 1 subnets
O 44.44.44.44 [110/3] via 192.168.3.11, 00:07:42, FastEthernet0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
r1#
r1 is no longer recieving the route that was redistributed in from ospf with metric of 1 for 22.22.22.22 so it selects it internal (correct) rip path via r2
this will now work for any downstream networks which could have had similar problems we have stopped route that originated in rip went to ospf being
redistributed back into rip
S3
---
switch3#ping 22.22.22.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 22.22.22.22, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 67/67/67 ms
switch3#
No comments:
Post a Comment