Handling Process
published 1. check the corresponding destination BGP route priority.
<NE80E> display BG prouting, table X.X.X.252
BGPlocalrouterID: X.X.X.37
LocalASnumber: 64800
Paths: 2available, 1best, 1select
BGProutingtableentryinformationofX.X.X.252 / 30:
From. X.X.X.1 (X.X.X.1)
RouteDuration 00h39m23s .
RelayIPNexthop: X.X.X.129
RelayIPOut - Interface: GigabitEthernet1 / 0/0
Originalnexthop: X.X.X.70
Qosinformation: 0x80000006
Community: < X: 61530 >
AS-pathNil, originigp MED0 localpref 100, pref-val0, valid, and internal, best, select, pre 255, IGPcost 80
(Single choice) Which. X.X.X.32
Clusterlist: X.X.X.160
Notadvertisedtoanypeeryet
2. check configurations, route policy configurations are correct, and are also configured under the corresponding interface. the configurations are right.
In Live network, slot 2 is LPUK (which is also called LPUG -21). The LPUG -21, LPUG -20, LPUG -41 board, are use IP - precedence.
interface GigabitEthernet2/1/9
undo shutdown
ip address X.X.X.49 255.255.255.252
isis enable 100
isis circuit-level level-2
isis authentication-mode md5 cipher %$%$Cj]@4/2{S!f#I+)\%VaPCR6N%$%$
isis cost 40
qppb-policy ip-precedence destination
bgp 64800
router-id X.X.X.37
group PgRR_L1 internal
#
ipv4-family unicast
undo synchronization
peer PgRR_L1 route-policy qppb-policy import
route-policy qppb-policy permit node 60
if-match community-filter Qos-ZhongYaoJiKe
apply ip-precedence 6
#
ip community-filter basic Qos-ZhongYaoJiKe permit X:61530
3. Check the ip routing table, then find that the active route is an ISIS route, BGP route is inactive.
<NE80E>display ip routing-table X.X.X.252 verbose
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public
Summary Count : 3
Destination: X.X.X.252/30
Protocol: ISIS-L2 Process ID: 100
Preference: 140 Cost: 90
NextHop: X.X.X.242 Neighbour: 0.0.0.0
State: Active Adv Age: 05h50m55s
Tag: 0 Priority: low
Label: NULL QoSInfo: 0x0
IndirectID: 0x0
RelayNextHop: 0.0.0.0 Interface: Pos10/1/0
TunnelID: 0x0 Flags: D
Destination: X.X.X.252/30
Protocol: ISIS-L2 Process ID: 100
Preference: 140 Cost: 90
NextHop: X.X.X.246 Neighbour: 0.0.0.0
State: Active Adv Age: 05h50m55s
Tag: 0 Priority: low
Label: NULL QoSInfo: 0x0
IndirectID: 0x0
RelayNextHop: 0.0.0.0 Interface: Pos11/1/0
TunnelID: 0x0 Flags: D
Destination: X.X.X.252/30
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 0
NextHop: X.X.X.70 Neighbour: X.X.X.1
State: Inactive Adv Relied Age: 02h34m15s
Tag: 0 Priority: low
Label: NULL QoSInfo: 0x80000006
IndirectID: 0x95
RelayNextHop: X.X.X.129 Interface: GigabitEthernet1/0/0
TunnelID: 0x0 Flags: R
RelayNextHop: X.X.X.242 Interface: Pos10/1/0
TunnelID: 0x0 Flags: R
RelayNextHop: X.X.X.246 Interface: Pos11/1/0
TunnelID: 0x0 Flags: R
RelayNextHop: X.X.X.250 Interface: Pos9/1/0
TunnelID: 0x0 Flags: R
4. We make remote device does not publish this route in ISIS, then the problem is solved.
Root Cause
QOS is published in BGP route, but the ISIS route takes effect, bgp routes does not take effect, so QPPB does not take effect.Solution
Make the remote device ip not release in the ISIS route, and the BGP route of the peer devcie takes effect then the problem solved.
