Using an SGM Filter
This example shows a simple filter for one SGM. The route type is shown as a one letter code in the left-hand column. The route type codes show at the end of the list.
> asg_route -b 1_01
Collecting routing information, may take few seconds...
==============================================================================
Fetching Routes info from SGMs:
1_01
Routes:
C 127.0.0.0/8 is directly connected, lo
C 130.0.0.0/24 is directly connected, eth1-CIN
C 172.23.9.0/24 is directly connected, eth1-Mgmt4
C 192.0.2.0/24 is directly connected, Sync
S 0.0.0.0/0 via 172.23.9.4, eth1-Mgmt4, cost 0
Types: C - Connected, S - Static, R - RIP, B - BGP,
O - OSPF IntraArea (IA - InterArea, E - External, N - NSSA)
A - Aggregate, K - Kernel Remnant, H - Hidden, P - Suppressed
SBR - Source-Based Routes
Example 2
The next example shows a complex SGM filter that includes 4 SGMs. Note that the results show route inconsistencies between the 61000/41000 Security System database and the operating system.
> asg_route -b 1_1,2_1-2_3
Collecting routing information, may take few seconds...
==============================================================================
Fetching Routes info from SGMs:
1_01,2_01,2_02,2_03
-------------------------------------------------------
Status: DB Routes info is NOT identical on all SGMs
OS Routes info is NOT identical on all SGMs
-------------------------------------------------------
Identical DB Routes: (21 records)
C 10.33.86.0/24 is directly connected, bond2.160
C 10.33.87.0/24 is directly connected, bond2.163
C 10.33.89.0/24 is directly connected, bond2.165
C 127.0.0.0/8 is directly connected, lo
C 192.0.2.0/24 is directly connected, Sync
C 192.168.15.128/25 is directly connected, eth1-Mgmt4
C 192.168.33.0/24 is directly connected, bond1.33
C 192.168.34.0/24 is directly connected, bond1.34
C 198.51.100.0/25 is directly connected, eth1-CIN
C 198.51.100.128/25 is directly connected, eth2-CIN
C 2.2.2.0/24 is directly connected, bond2.166
S 0.0.0.0/0 via 192.168.33.1, bond1.33, cost 0
S 16.0.0.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.1.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.2.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.3.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.4.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.5.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.6.0/24 via 10.33.86.16, bond2.160, cost 0
S 16.0.8.0/24 via 10.33.86.16, bond2.160, cost 0
S 194.29.40.138/32 via 192.168.15.254, eth1-Mgmt4, cost 0
Inconsistent DB Routes:
1_01:
-
2_01:
R 10.33.96.0/24 via 192.168.33.96, bond1.33, cost 2, tag 13142
R 15.0.2.0/24 via 192.168.33.96, bond1.33, cost 2, tag 13142
2_02:
-
2_03:
R 10.33.96.0/24 via 192.168.33.96, bond1.33, cost 2, tag 13142
R 15.0.2.0/24 via 192.168.33.96, bond1.33, cost 2, tag 13142
Types: C - Connected, S - Static, R - RIP, B - BGP,
O - OSPF IntraArea (IA - InterArea, E - External, N - NSSA)
A - Aggregate, K - Kernel Remnant, H - Hidden, P - Suppressed
SBR - Source-Based Routes
|
