product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.400
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.525
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.520
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.523
metric mismatch on cisco-7200-cr1-ln2 and c180x-ge2-l01 (network 10.19.48.112/29)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.114 is 1
c180x-ge2-l01 (10.19.48.121): metric on interface 10.19.48.118 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.265
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.266
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.627
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.599
metric mismatch on cisco-7200-cr1-ln2 and c180x-sl1-l02 (network 10.19.48.184/29)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.186 is 1
c180x-sl1-l02 (10.19.42.245): metric on interface 10.19.48.190 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.268
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.631
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.254
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.52
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.520
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.261
metric mismatch on cisco-7200-cr1-ln2 and c180x-cn1-l02 (network 10.19.42.0/28)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.42.2 is 1
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.599
metric mismatch on cisco-7200-cr1-ln2 and c180x-ic1-l03 (network 10.19.48.128/29)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.130 is 1
c180x-ic1-l03 (10.19.48.137): metric on interface 10.19.48.134 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.255
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.258
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.599
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.258
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.264
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.259
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.267
metric mismatch on cisco-7200-cr1-ln2 and c180x-po2-l01 (network 10.19.41.8/29)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.41.11 is 1
c180x-po2-l01 (10.19.41.12): metric on interface 10.19.41.12 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.637
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.259
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.599
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.242
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.519
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.214
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.184
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.600
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.242
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.276
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.637
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.599
metric mismatch on cisco-7200-cr1-ln2 and c180x-mr6-l03 (network 10.19.42.232/29)
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.42.234 is 1
c180x-mr6-l03 (10.19.42.242): metric on interface 10.19.42.238 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.260
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.330
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.289
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.274
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.300
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.253
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-cr1-ln2 on link GigabitEthernet2/0.280
router 10.19.32.242 (cisco-7200-cr1-ln2) has 87 neighbors (recommended maximum is 60)
router 10.19.32.242 (cisco-7200-cr1-ln2) is connected to 15 areas (recommended maximum is 3)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-co1-l01 and c180x-abl01 (network 10.19.37.0/24)
c180x-co1-l01 (10.19.37.21): metric on interface 10.19.37.21 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.21 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-l03 and c180x-abl01 (network 10.19.37.0/24)
c180x-l03 (10.19.37.10): metric on interface 10.19.37.10 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.10 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-ge2-l01 and cisco-7200-cr1-ln2 (network 10.19.48.112/29)
c180x-ge2-l01 (10.19.48.121): metric on interface 10.19.48.118 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.114 is 1
router 10.19.58.76 uses a physical interface as router id (recommended is loopback)
router 10.19.58.76 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-ks1-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-ks1-l01 (10.19.37.16): metric on interface 10.19.37.16 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.37.16 uses a physical interface as router id (recommended is loopback)
router 10.19.51.228 uses a physical interface as router id (recommended is loopback)
router 10.19.51.228 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-mr6-l03 and cisco-7200-cr1-ln2 (network 10.19.42.232/29)
c180x-mr6-l03 (10.19.42.242): metric on interface 10.19.42.238 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.42.234 is 1
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-lns1 on link GigabitEthernet0/0.45
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-lns1 on link GigabitEthernet0/0.44
metric mismatch on c180x-tl1-l01 and c180x-cn1-l02 (network 10.19.42.0/28)
c180x-tl1-l01 (10.19.42.169): metric on interface 10.19.42.10 is 1
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.393
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
metric mismatch on cisco-7200-ar1-ln3 and c180x-abl01 (network 10.19.37.0/24)
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.37.2 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
metric mismatch on cisco-7200-ar1-ln3 and c180x-if1-l07 (network 10.19.53.204/30)
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.53.205 is 1
c180x-if1-l07 (10.19.53.206): metric on interface 10.19.53.206 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
metric mismatch on cisco-7200-ar1-ln3 and c180x-ce3-l01 (network 10.19.44.0/30)
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.44.1 is 1
c180x-ce3-l01 (10.19.44.2): metric on interface 10.19.44.2 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln3 on link
router 10.211.81.27 (cisco-7200-ar1-ln3) has 164 neighbors (recommended maximum is 60)
metric mismatch on cisco-1700-mr6-pc1 and cisco-2800-if1-l02 (network 10.211.80.0/24)
cisco-1700-mr6-pc1 (10.19.42.243): metric on interface 10.211.80.31 is 64
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
router 10.19.47.148 uses a physical interface as router id (recommended is loopback)
router 10.19.47.148 uses a physical interface as router id (recommended is loopback)
router 10.211.80.29 uses a physical interface as router id (recommended is loopback)
router 10.211.80.29 uses a physical interface as router id (recommended is loopback)
router 10.211.80.29 uses a physical interface as router id (recommended is loopback)
router 10.211.80.29 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-1700-ui2-pc1 and cisco-2800-if1-l02 (network 10.211.80.0/24)
cisco-1700-ui2-pc1 (10.211.80.29): metric on interface 10.211.80.29 is 64
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
router 10.211.80.29 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1-ln3 on link GigabitEthernet6/1.53
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1-ln3 on link GigabitEthernet6/1.45
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1-ln3 on link GigabitEthernet6/1.52
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1-ln3 on link GigabitEthernet6/1.1124
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1-ln3 on link GigabitEthernet1/5
router 10.19.32.243 (cisco-7600-er1-ln3) is connected to 7 areas (recommended maximum is 3)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-ti2-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-ti2-l01 (10.19.37.44): metric on interface 10.19.37.44 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.19.37.44 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.211.81.11 uses a physical interface as router id (recommended is loopback)
router 10.19.62.12 uses a physical interface as router id (recommended is loopback)
router 10.19.62.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.211.81.10 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-bt1-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-bt1-l01 (10.19.37.20): metric on interface 10.19.37.20 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.20 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-ml2-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-ml2-l01 (10.19.37.25): metric on interface 10.19.37.25 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
router 10.19.37.25 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2800-if1-l02 and cisco-1700-ab1-pc2 (network 10.211.80.0/24)
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
cisco-1700-ab1-pc2 (10.211.80.19): metric on interface 10.211.80.19 is 64
router 10.211.80.21 uses a physical interface as router id (recommended is loopback)
router 10.211.80.21 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2800-if1-l02 and cisco-1700-ui2-pc1 (network 10.211.80.0/24)
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
cisco-1700-ui2-pc1 (10.211.80.29): metric on interface 10.211.80.29 is 64
router 10.211.80.21 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2800-if1-l02 and cisco-1700-mr6-pc1 (network 10.211.80.0/24)
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
cisco-1700-mr6-pc1 (10.19.42.243): metric on interface 10.211.80.31 is 64
router 10.211.80.21 uses a physical interface as router id (recommended is loopback)
router 10.211.80.21 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.211.81.12 uses a physical interface as router id (recommended is loopback)
router 10.19.54.238 uses a physical interface as router id (recommended is loopback)
router 10.19.54.238 uses a physical interface as router id (recommended is loopback)
router 10.19.61.150 uses a physical interface as router id (recommended is loopback)
router 10.19.61.150 uses a physical interface as router id (recommended is loopback)
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-hl1-l04 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-hl1-l04 (10.19.37.42): metric on interface 10.19.37.42 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-eh2-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-eh2-l01 (10.19.37.28): metric on interface 10.19.37.28 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-bt1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-bt1-l01 (10.19.37.20): metric on interface 10.19.37.20 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-ml2-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-ml2-l01 (10.19.37.25): metric on interface 10.19.37.25 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-7200-ar1-ln3 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.37.2 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-wl1-l02 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-wl1-l02 (10.19.34.57): metric on interface 10.19.37.36 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and c180x-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
c180x-l01 (10.19.37.11): metric on interface 10.19.37.11 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and c180x-co1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
c180x-co1-l01 (10.19.37.21): metric on interface 10.19.37.21 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and c180x-ze1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
c180x-ze1-l01 (10.19.37.27): metric on interface 10.19.37.27 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and c180x-l03 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
c180x-l03 (10.19.37.10): metric on interface 10.19.37.10 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-mr1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-mr1-l01 (10.19.37.31): metric on interface 10.19.37.31 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-ks1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-ks1-l01 (10.19.37.16): metric on interface 10.19.37.16 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-tl1-l03 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-tl1-l03 (10.19.38.41): metric on interface 10.19.37.43 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-cn1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-cn1-l01 (10.19.47.65): metric on interface 10.19.37.38 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-hl1-l02 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-hl1-l02 (10.19.37.30): metric on interface 10.19.37.30 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-b6-l1 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-b6-l1 (10.19.37.26): metric on interface 10.19.37.26 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-fa1-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-fa1-l01 (10.19.37.29): metric on interface 10.19.37.29 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and c180x-er2-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
c180x-er2-l01 (10.19.37.35): metric on interface 10.19.37.35 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-abl01 and cisco-2801-ti2-l01 (network 10.19.37.0/24)
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
cisco-2801-ti2-l01 (10.19.37.44): metric on interface 10.19.37.44 is 1
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
router 10.19.37.15 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-er2-l01 and c180x-abl01 (network 10.19.37.0/24)
c180x-er2-l01 (10.19.37.35): metric on interface 10.19.37.35 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.37.35 uses a physical interface as router id (recommended is loopback)
router 10.19.43.230 uses a physical interface as router id (recommended is loopback)
router 10.19.43.230 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-sl1-l02 and cisco-7200-cr1-ln2 (network 10.19.48.184/29)
c180x-sl1-l02 (10.19.42.245): metric on interface 10.19.48.190 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.186 is 1
router 10.19.38.198 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-cn1-l02 and cisco-2801-ci1-l01 (network 10.19.42.0/28)
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
cisco-2801-ci1-l01 (10.19.42.81): metric on interface 10.19.42.9 is 1
metric mismatch on c180x-cn1-l02 and cisco-7200-ls1-ln2 (network 10.19.42.0/28)
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
cisco-7200-ls1-ln2 (10.211.81.24): metric on interface 10.19.42.3 is 1
metric mismatch on c180x-cn1-l02 and c180x-cm1-l01 (network 10.19.42.0/28)
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
c180x-cm1-l01 (10.19.47.1): metric on interface 10.19.42.11 is 1
metric mismatch on c180x-cn1-l02 and cisco-7200-cr1-ln2 (network 10.19.42.0/28)
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.42.2 is 1
metric mismatch on c180x-cn1-l02 and c180x-tl1-l01 (network 10.19.42.0/28)
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
c180x-tl1-l01 (10.19.42.169): metric on interface 10.19.42.10 is 1
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-eh2-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-eh2-l01 (10.19.37.28): metric on interface 10.19.37.28 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
router 10.19.37.28 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-po2-l01 and cisco-7200-cr1-ln2 (network 10.19.41.8/29)
c180x-po2-l01 (10.19.41.12): metric on interface 10.19.41.12 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.41.11 is 1
router 10.19.41.12 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-po2-l01 and cisco-7200-ls1-ln2 (network 10.19.41.8/29)
c180x-po2-l01 (10.19.41.12): metric on interface 10.19.41.12 is 10
cisco-7200-ls1-ln2 (10.211.81.24): metric on interface 10.19.41.10 is 1
router 10.19.41.12 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-ze1-l01 and c180x-abl01 (network 10.19.37.0/24)
c180x-ze1-l01 (10.19.37.27): metric on interface 10.19.37.27 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.19.37.27 uses a physical interface as router id (recommended is loopback)
router 10.211.80.19 uses a physical interface as router id (recommended is loopback)
router 10.211.80.19 uses a physical interface as router id (recommended is loopback)
router 10.211.80.19 uses a physical interface as router id (recommended is loopback)
router 10.211.80.19 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-1700-ab1-pc2 and cisco-2800-if1-l02 (network 10.211.80.0/24)
cisco-1700-ab1-pc2 (10.211.80.19): metric on interface 10.211.80.19 is 64
cisco-2800-if1-l02 (10.211.80.21): metric on interface 10.211.80.21 is 1
router 10.211.80.19 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-ic1-l03 and cisco-7200-cr1-ln2 (network 10.19.48.128/29)
c180x-ic1-l03 (10.19.48.137): metric on interface 10.19.48.134 is 10
cisco-7200-cr1-ln2 (10.19.32.242): metric on interface 10.19.48.130 is 1
router 10.19.39.34 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-mr1-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-mr1-l01 (10.19.37.31): metric on interface 10.19.37.31 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
router 10.19.37.31 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1 on link GigabitEthernet1/1.44
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1 on link GigabitEthernet2/1
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1 on link GigabitEthernet1/1.1124
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1 on link GigabitEthernet1/1.53
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7600-er1 on link GigabitEthernet2/2
router 10.19.32.240 (cisco-7600-er1) is connected to 5 areas (recommended maximum is 3)
metric mismatch on cisco-2801-cn1-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-cn1-l01 (10.19.47.65): metric on interface 10.19.37.38 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.51.52 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-if1-l07 and cisco-7200-ar1-ln3 (network 10.19.53.204/30)
c180x-if1-l07 (10.19.53.206): metric on interface 10.19.53.206 is 10
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.53.205 is 1
router 10.19.53.206 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-wl1-l02 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-wl1-l02 (10.19.34.57): metric on interface 10.19.37.36 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.38.70 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-b6-l1 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-b6-l1 (10.19.37.26): metric on interface 10.19.37.26 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.19.37.26 uses a physical interface as router id (recommended is loopback)
router 10.211.97.147 uses a physical interface as router id (recommended is loopback)
router 10.211.97.147 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.6 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.4 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.5 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
router 10.211.81.7 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-tl1-l03 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-tl1-l03 (10.19.38.41): metric on interface 10.19.37.43 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-hl1-l04 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-hl1-l04 (10.19.37.42): metric on interface 10.19.37.42 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
router 10.19.37.42 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.520
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.330
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.520
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.600
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.519
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.631
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.599
router 10.211.81.24 and 10.19.32.242 are not in FULL state (in state 2way) on link 10.19.32.128/29
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.259
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.258
metric mismatch on cisco-7200-ls1-ln2 and c180x-cn1-l02 (network 10.19.42.0/28)
cisco-7200-ls1-ln2 (10.211.81.24): metric on interface 10.19.42.3 is 1
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.599
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.258
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.599
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.230
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.627
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.259
metric mismatch on cisco-7200-ls1-ln2 and c180x-po2-l01 (network 10.19.41.8/29)
cisco-7200-ls1-ln2 (10.211.81.24): metric on interface 10.19.41.10 is 1
c180x-po2-l01 (10.19.41.12): metric on interface 10.19.41.12 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.637
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.253
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.300
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.637
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.242
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.276
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.599
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.242
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.400
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.523
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.525
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ls1-ln2 on link GigabitEthernet0/1.599
router 10.211.81.24 (cisco-7200-ls1-ln2) has 95 neighbors (recommended maximum is 60)
router 10.211.81.24 (cisco-7200-ls1-ln2) is connected to 53 areas (recommended maximum is 3)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-l01 and c180x-abl01 (network 10.19.37.0/24)
c180x-l01 (10.19.37.11): metric on interface 10.19.37.11 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
router 10.19.37.11 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-2801-da1-l03-b on link FastEthernet0/0
router 10.19.61.158 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-er1 on link GigabitEthernet0/3.1125
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-er1 on link GigabitEthernet0/1
router 10.211.81.68 (cisco-7200-er1) is connected to 8 areas (recommended maximum is 3)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-hl1-l02 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-hl1-l02 (10.19.37.30): metric on interface 10.19.37.30 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
router 10.19.37.30 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.393
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.393
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
metric mismatch on cisco-7200-ar1-ln1 and c180x-abl01 (network 10.19.37.0/24)
cisco-7200-ar1-ln1 (10.211.105.238): metric on interface 10.19.37.3 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
router 10.211.105.238 uses a physical interface as router id (recommended is loopback)
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/3.526
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/3.526
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.283
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.283
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/3.1101
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/3.1001
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.99
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/3.1107
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
product of metric and bandwidth (OSPF reference-bandwidth) is not equal on all links
check router cisco-7200-ar1-ln1 on link GigabitEthernet0/2.362
router 10.211.105.238 (cisco-7200-ar1-ln1) has 155 neighbors (recommended maximum is 60)
router 10.19.51.246 uses a physical interface as router id (recommended is loopback)
router 10.19.51.246 uses a physical interface as router id (recommended is loopback)
router 10.19.44.58 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.211.81.14 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-fa1-l01 and c180x-abl01 (network 10.19.37.0/24)
cisco-2801-fa1-l01 (10.19.37.29): metric on interface 10.19.37.29 is 1
c180x-abl01 (10.19.37.15): metric on interface 10.19.37.15 is 10
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
router 10.19.37.29 uses a physical interface as router id (recommended is loopback)
metric mismatch on c180x-cm1-l01 and c180x-cn1-l02 (network 10.19.42.0/28)
c180x-cm1-l01 (10.19.47.1): metric on interface 10.19.42.11 is 1
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
metric mismatch on c180x-ce3-l01 and cisco-7200-ar1-ln3 (network 10.19.44.0/30)
c180x-ce3-l01 (10.19.44.2): metric on interface 10.19.44.2 is 10
cisco-7200-ar1-ln3 (10.211.81.27): metric on interface 10.19.44.1 is 1
router 10.19.44.2 uses a physical interface as router id (recommended is loopback)
router 10.19.56.123 uses a physical interface as router id (recommended is loopback)
router 10.19.56.123 uses a physical interface as router id (recommended is loopback)
metric mismatch on cisco-2801-ci1-l01 and c180x-cn1-l02 (network 10.19.42.0/28)
cisco-2801-ci1-l01 (10.19.42.81): metric on interface 10.19.42.9 is 1
c180x-cn1-l02 (10.19.42.161): metric on interface 10.19.42.7 is 10
router 10.19.43.150 uses a physical interface as router id (recommended is loopback)
router 10.19.43.150 uses a physical interface as router id (recommended is loopback)
area 10.211.101.216 has only 2 active links. Do you really nead such a small area?
area 10.211.74.208 has only 2 active links. Do you really nead such a small area?
area 10.211.70.112 has only 4 active links. Do you really nead such a small area?
area 10.211.93.200 has only 1 active link. Do you really nead such a small area?
area 10.211.105.112 has only 4 active links. Do you really nead such a small area?
area 10.19.44.56 has only 2 active links. Do you really nead such a small area?
area 10.211.104.248 has only 2 active links. Do you really nead such a small area?
area 10.211.92.216 has only 2 active links. Do you really nead such a small area?
area 10.19.51.128 has only 1 active link. Do you really nead such a small area?
area 10.19.61.152 has only 2 active links. Do you really nead such a small area?
area 10.211.104.208 has only 2 active links. Do you really nead such a small area?
area 10.211.70.208 has only 4 active links. Do you really nead such a small area?
area 10.19.63.48 has only 4 active links. Do you really nead such a small area?
area 10.19.44.0 has only 2 active links. Do you really nead such a small area?
area 10.211.104.128 has only 2 active links. Do you really nead such a small area?
area 10.211.71.16 has only 4 active links. Do you really nead such a small area?
area 10.19.58.24 has only 4 active links. Do you really nead such a small area?
area 10.19.61.96 has only 1 active link. Do you really nead such a small area?
area 10.211.104.64 has only 4 active links. Do you really nead such a small area?
area 10.19.56.96 has only 2 active links. Do you really nead such a small area?
area 10.19.40.128 has only 1 active link. Do you really nead such a small area?
area 10.211.104.112 has only 2 active links. Do you really nead such a small area?
area 10.211.101.136 has only 4 active links. Do you really nead such a small area?
area 10.19.53.204 has only 2 active links. Do you really nead such a small area?
area 10.211.70.144 has only 4 active links. Do you really nead such a small area?
area 10.211.101.200 has only 2 active links. Do you really nead such a small area?
area 10.211.101.232 has only 4 active links. Do you really nead such a small area?
area 10.19.39.124 has only 2 active links. Do you really nead such a small area?
area 10.211.70.160 has only 4 active links. Do you really nead such a small area?
area 10.19.48.40 has only 1 active link. Do you really nead such a small area?
area 10.211.97.160 has only 2 active links. Do you really nead such a small area?
area 10.211.71.216 has only 1 active link. Do you really nead such a small area?
area 10.211.70.184 has only 4 active links. Do you really nead such a small area?
area 10.211.70.64 has only 4 active links. Do you really nead such a small area?
area 10.211.105.64 has only 4 active links. Do you really nead such a small area?
area 10.211.71.24 has only 4 active links. Do you really nead such a small area?
area 10.211.71.136 has only 4 active links. Do you really nead such a small area?
area 10.211.71.152 has only 4 active links. Do you really nead such a small area?
area 10.211.71.208 has only 2 active links. Do you really nead such a small area?
area 10.211.98.8 has only 2 active links. Do you really nead such a small area?
area 10.211.91.144 has only 4 active links. Do you really nead such a small area?
area 10.19.51.48 has only 2 active links. Do you really nead such a small area?
area 10.19.35.112 has only 4 active links. Do you really nead such a small area?
area 10.211.105.144 has only 2 active links. Do you really nead such a small area?
area 10.211.105.224 has only 2 active links. Do you really nead such a small area?
area 10.211.105.240 has only 2 active links. Do you really nead such a small area?
area 10.211.70.48 has only 4 active links. Do you really nead such a small area?
area 10.211.104.232 has only 2 active links. Do you really nead such a small area?
area 10.19.39.96 has only 4 active links. Do you really nead such a small area?
area 10.211.105.160 has only 4 active links. Do you really nead such a small area?
area 10.211.104.32 has only 4 active links. Do you really nead such a small area?
area 10.211.70.32 has only 4 active links. Do you really nead such a small area?
area 10.211.105.0 has only 4 active links. Do you really nead such a small area?
area 10.19.51.32 has only 2 active links. Do you really nead such a small area?
area 10.19.42.32 has only 1 active link. Do you really nead such a small area?
area 10.211.71.64 has only 4 active links. Do you really nead such a small area?
area 10.19.38.184 has only 1 active link. Do you really nead such a small area?
area 10.211.92.232 has only 1 active link. Do you really nead such a small area?
area 10.19.39.32 has only 2 active links. Do you really nead such a small area?
area 10.211.97.192 has only 2 active links. Do you really nead such a small area?
area 10.19.39.192 has only 2 active links. Do you really nead such a small area?
area 10.211.97.92 has only 4 active links. Do you really nead such a small area?
area 10.211.104.48 has only 2 active links. Do you really nead such a small area?
area 10.19.42.192 has only 4 active links. Do you really nead such a small area?
area 10.211.70.232 has only 4 active links. Do you really nead such a small area?
area 10.211.71.240 has only 2 active links. Do you really nead such a small area?
area 10.19.53.0 has only 4 active links. Do you really nead such a small area?
area 10.211.97.176 has only 2 active links. Do you really nead such a small area?
area 10.211.105.200 has only 2 active links. Do you really nead such a small area?
area 10.211.71.184 has only 2 active links. Do you really nead such a small area?
area 10.211.74.96 has only 2 active links. Do you really nead such a small area?
area 10.211.104.96 has only 4 active links. Do you really nead such a small area?
area 10.211.71.0 has only 4 active links. Do you really nead such a small area?
area 10.211.74.144 has only 1 active link. Do you really nead such a small area?
area 10.211.69.0 has only 2 active links. Do you really nead such a small area?
area 10.19.32.240 has 1 router (recommended minimum is 20)
area 10.19.32.242 has 1 router (recommended minimum is 20)
area 10.19.32.243 has 1 router (recommended minimum is 20)
area 10.19.34.32 has 1 router (recommended minimum is 20)
area 10.19.35.112 has 1 router (recommended minimum is 20)
area 10.19.35.120 has 1 router (recommended minimum is 20)
area 10.19.35.224 has 1 router (recommended minimum is 20)
area 10.19.36.160 has 2 routers (recommended minimum is 20)
area 10.19.36.216 has 2 routers (recommended minimum is 20)
area 10.19.37.0 has 19 routers (recommended minimum is 20)
area 10.19.38.0 has 1 router (recommended minimum is 20)
area 10.19.38.208 has 1 router (recommended minimum is 20)
area 10.19.38.32 has 1 router (recommended minimum is 20)
area 10.19.38.64 has 1 router (recommended minimum is 20)
area 10.19.38.72 has 1 router (recommended minimum is 20)
area 10.19.39.124 has 2 routers (recommended minimum is 20)
area 10.19.39.32 has 1 router (recommended minimum is 20)
area 10.19.40.108 has 1 router (recommended minimum is 20)
area 10.19.40.128 has 1 router (recommended minimum is 20)
area 10.19.41.0 has 1 router (recommended minimum is 20)
area 10.19.41.168 has 1 router (recommended minimum is 20)
area 10.19.41.208 has 1 router (recommended minimum is 20)
area 10.19.41.48 has 2 routers (recommended minimum is 20)
area 10.19.41.64 has 1 router (recommended minimum is 20)
area 10.19.41.8 has 3 routers (recommended minimum is 20)
area 10.19.42.136 has 1 router (recommended minimum is 20)
area 10.19.42.144 has 1 router (recommended minimum is 20)
area 10.19.42.160 has 2 routers (recommended minimum is 20)
area 10.19.42.168 has 1 router (recommended minimum is 20)
area 10.19.42.192 has 2 routers (recommended minimum is 20)
area 10.19.42.200 has 1 router (recommended minimum is 20)
area 10.19.42.240 has 1 router (recommended minimum is 20)
area 10.19.42.241 has 1 router (recommended minimum is 20)
area 10.19.42.242 has 1 router (recommended minimum is 20)
area 10.19.42.244 has 2 routers (recommended minimum is 20)
area 10.19.42.245 has 2 routers (recommended minimum is 20)
area 10.19.42.246 has 1 router (recommended minimum is 20)
area 10.19.42.247 has 1 router (recommended minimum is 20)
area 10.19.42.80 has 2 routers (recommended minimum is 20)
area 10.19.43.144 has 1 router (recommended minimum is 20)
area 10.19.43.192 has 1 router (recommended minimum is 20)
area 10.19.43.232 has 1 router (recommended minimum is 20)
area 10.19.44.0 has 1 router (recommended minimum is 20)
area 10.19.44.32 has 2 routers (recommended minimum is 20)
area 10.19.44.56 has 1 router (recommended minimum is 20)
area 10.19.44.72 has 1 router (recommended minimum is 20)
area 10.19.44.80 has 1 router (recommended minimum is 20)
area 10.19.45.72 has 2 routers (recommended minimum is 20)
area 10.19.45.80 has 1 router (recommended minimum is 20)
area 10.19.46.0 has 1 router (recommended minimum is 20)
area 10.19.47.0 has 1 router (recommended minimum is 20)
area 10.19.47.128 has 1 router (recommended minimum is 20)
area 10.19.47.144 has 1 router (recommended minimum is 20)
area 10.19.47.184 has 2 routers (recommended minimum is 20)
area 10.19.47.248 has 1 router (recommended minimum is 20)
area 10.19.47.48 has 2 routers (recommended minimum is 20)
area 10.19.48.0 has 1 router (recommended minimum is 20)
area 10.19.48.120 has 1 router (recommended minimum is 20)
area 10.19.48.136 has 1 router (recommended minimum is 20)
area 10.19.48.152 has 1 router (recommended minimum is 20)
area 10.19.48.192 has 1 router (recommended minimum is 20)
area 10.19.48.196 has 2 routers (recommended minimum is 20)
area 10.19.48.197 has 1 router (recommended minimum is 20)
area 10.19.49.0 has 1 router (recommended minimum is 20)
area 10.19.49.128 has 1 router (recommended minimum is 20)
area 10.19.49.152 has 1 router (recommended minimum is 20)
area 10.19.49.168 has 1 router (recommended minimum is 20)
area 10.19.49.216 has 1 router (recommended minimum is 20)
area 10.19.49.32 has 1 router (recommended minimum is 20)
area 10.19.49.64 has 1 router (recommended minimum is 20)
area 10.19.49.72 has 1 router (recommended minimum is 20)
area 10.19.49.80 has 1 router (recommended minimum is 20)
area 10.19.50.128 has 3 routers (recommended minimum is 20)
area 10.19.50.192 has 1 router (recommended minimum is 20)
area 10.19.50.240 has 1 router (recommended minimum is 20)
area 10.19.51.0 has 2 routers (recommended minimum is 20)
area 10.19.51.184 has 1 router (recommended minimum is 20)
area 10.19.51.224 has 3 routers (recommended minimum is 20)
area 10.19.51.48 has 2 routers (recommended minimum is 20)
area 10.19.51.56 has 1 router (recommended minimum is 20)
area 10.19.53.16 has 1 router (recommended minimum is 20)
area 10.19.53.192 has 1 router (recommended minimum is 20)
area 10.19.53.204 has 1 router (recommended minimum is 20)
area 10.19.53.48 has 1 router (recommended minimum is 20)
area 10.19.53.88 has 1 router (recommended minimum is 20)
area 10.19.54.192 has 1 router (recommended minimum is 20)
area 10.19.54.232 has 1 router (recommended minimum is 20)
area 10.19.56.120 has 1 router (recommended minimum is 20)
area 10.19.56.48 has 1 router (recommended minimum is 20)
area 10.19.56.88 has 1 router (recommended minimum is 20)
area 10.19.57.64 has 1 router (recommended minimum is 20)
area 10.19.58.24 has 2 routers (recommended minimum is 20)
area 10.19.58.72 has 1 router (recommended minimum is 20)
area 10.19.61.144 has 1 router (recommended minimum is 20)
area 10.19.61.152 has 2 routers (recommended minimum is 20)
area 10.19.61.76 has 1 router (recommended minimum is 20)
area 10.19.62.8 has 1 router (recommended minimum is 20)
area 10.211.68.192 has 1 router (recommended minimum is 20)
area 10.211.68.68 has 1 router (recommended minimum is 20)
area 10.211.70.224 has 1 router (recommended minimum is 20)
area 10.211.70.96 has 1 router (recommended minimum is 20)
area 10.211.80.0 has 4 routers (recommended minimum is 20)
area 10.211.81.0 has 8 routers (recommended minimum is 20)
area 10.211.81.104 has 1 router (recommended minimum is 20)
area 10.211.81.108 has 1 router (recommended minimum is 20)
area 10.211.81.116 has 1 router (recommended minimum is 20)
area 10.211.81.148 has 1 router (recommended minimum is 20)
area 10.211.81.24 has 1 router (recommended minimum is 20)
area 10.211.81.69 has 1 router (recommended minimum is 20)
area 10.211.81.88 has 1 router (recommended minimum is 20)
area 10.211.97.144 has 1 router (recommended minimum is 20)
this domain has 114 areas (recommended maximum is 60)
multiple links exist between cisco-7600-er1 and cisco-7600-er1-ln3 on
networks 10.19.32.216/29, 10.19.58.24/29, 10.211.81.76/30, 10.211.81.76/30, 10.19.58.24/29, 10.19.32.216/29.
All links have the same metric/bandwidth - are they really multiple paths on different cables or just Vlans running over the same trunk link?
multiple links exist between cisco-7200-ar1-ln3 and cisco-7200-ar1-ln1 on
networks 10.19.47.144/29, 10.19.43.144/29, 10.19.49.72/29, 10.19.37.0/24, 10.19.39.96/29, 10.19.41.0/29, 10.19.39.192/29.
All links have the same metric/bandwidth - are they really multiple paths on different cables or just Vlans running over the same trunk link?
multiple links exist between cisco-7200-ls1-ln2 and cisco-7200-cr1-ln2 on
networks 10.19.32.176/28, 10.19.36.104/29, 10.19.36.80/29, 10.19.42.128/29, 10.19.42.24/29, 10.19.36.144/29, 10.19.42.216/29, 10.19.42.224/29, 10.19.42.0/28, 10.19.36.128/29, 10.19.32.224/28, 10.19.41.40/29, 10.19.41.112/29, 10.19.41.8/29, 10.19.39.224/28, 10.19.34.0/27, 10.19.42.192/29, 10.19.39.224/28, 10.19.36.144/29, 10.19.32.224/28, 10.19.36.128/29, 10.19.42.24/29, 10.19.42.224/29, 10.19.42.216/29, 10.19.42.128/29, 10.19.42.192/29, 10.19.34.0/27, 10.19.41.8/29, 10.19.41.112/29, 10.19.41.40/29, 10.19.32.176/28, 10.19.36.80/29, 10.19.36.104/29, 10.19.42.0/28.
All links have the same metric/bandwidth - are they really multiple paths on different cables or just Vlans running over the same trunk link?
This software does not know the routing policy of your site, so OSPFVIZ comes with no warranty in any form. It can not garantee that the analysis results apply to your network configuration. No diagnostic software can substitute a firm knowledge of routing operations in general and the OSPF routing protocol in particular.
OSPF analysis engine 2.45, run at 2014/04/17 14:02:10
These checks were excluded by configuration file: 01 (ping)
