Reviewing the path that the traffic follows from source to destination, we see that the network 201.125.120.128/25 appears with the message "DIscard" in the inet.0 routing table.
root@router1> show route table inet.0 201.125.120.128/25
inet.0: 7611 destinations, 12932 routes (7611 active, 0 holddown, 0 hidden)
@ = Routing Use Only, # = Forwarding Use Only
+ = Active Route, - = Last Active, * = Both
201.125.120.128/25 *[OSPF/10] 2w3d 21:34:15, metric 16777215
Discard <------------------------------------------------------------------here
201.125.120.128/26 @[OSPF/150] 3d 09:07:29, metric 5, tag 0
> to 201.154.113.110 via ae4.0
#[LDP/9] 3d 09:07:28, metric 1
> to 201.154.113.110 via ae4.0, Push 236669
201.125.120.192/26 @[OSPF/150] 3d 09:07:29, metric 5, tag 0
> to 201.154.113.110 via ae4.0, Push 236670
201.125.120.244/32 *[OSPF/10] 10:04:31, metric 30
201.125.120.245/32 *[OSPF/10] 3d 09:07:29, metric 30
201.125.120.247/32 *[OSPF/10] 3d 09:07:29, metric 20
201.125.120.248/32 *[OSPF/10] 3d 09:07:29, metric 30
201.125.120.250/32 *[Direct/0] 92w5d 14:33:09
> via lo0.0
When checking configuration, we can observed that routes are configure as area-range for a nssa area. All routes configure as area-range shows the same on inet.0 routing table.
area 4.3.46.1 {
nssa;
area-range 201.125.120.128/25;
area-range 189.246.170.128/28;
area-range 201.154.113.192/26;
network-summary-export TRIARA_QRO;
interface ae4.0 {
interface-type p2p;
metric 10;
authentication {
root@router1> show route table inet.0 189.246.170.128/28
inet.0: 7614 destinations, 12938 routes (7614 active, 0 holddown, 0 hidden)
189.246.170.128/28 *[OSPF/10] 3d 06:30:30, metric 16777215
Discard
189.246.170.128/30 @[OSPF/10] 3d 06:30:31, metric 12110
#LDP/9 3d 06:30:30, metric 1
root@router1>show route table inet.0 201.154.113.192/26
201.154.113.192/26 *[OSPF/10] 4w1d 13:07:23, metric 16777215