Search our Knowledge Base sites to find answers to your questions.
Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles[Subscriber Management] Pings fail from upstream router or from the Internet
ICMP pings on a subscriber IP from the router goes through, but fails when when pinging it from the upstream router or from the Internet
Pings work from the router but they fail from upstream devices.
FPC swap, FPC offline/online, or simultaneous flapping of multiple ports on a FPC can trigger the issue.
Example scenario:
[MASTER] lab@MX960-Test> start shell pfe network fpc8 RMPC platform (1200Mhz QorIQ P2020 processor, 3584MB memory, 512KB flash) RMPC8(MX960-Test vty)# show jnh 0 exceptions terse Reason Type Packets Bytes ================================================================== Error Parcels ---------------------- from WAN M2L ERROR 2 PFE State Invalid ---------------------- sw error DISC( 64) 16005 21038715 invalid fabric token DISC( 75) 1307 300863 unknown family DISC( 73) 216855 15270668 unknown iif DISC( 1) 8 720 egress pfe unspecified DISC( 19) 13838958 1992808325 invalid outgoing paths/interfaces DISC( 98) 228 301292 dv discard DISC( 50) 126756 27086650 <> RMPC8(MX960-Test vty)# show jnh 0 exceptions terse Reason Type Packets Bytes ================================================================== Error Parcels ---------------------- from WAN M2L ERROR 2 PFE State Invalid ---------------------- sw error DISC( 64) 16005 21038715 invalid fabric token DISC( 75) 1307 300863 unknown family DISC( 73) 216938 15275288 unknown iif DISC( 1) 8 720 egress pfe unspecified DISC( 19) 13843691 1993352455 <-- increments invalid outgoing paths/interfaces DISC( 98) 228 301292 dv discard DISC( 50) 126842 27092543 <>
A problematic subscriber is identified. Checking its DHCP binding and pinging it from the router looks good:
[MASTER]
lab@MX960-Test> show dhcp server binding 138.88.70.201
IP address Session Id Hardware address Expires State Interface
138.88.70.201 459914 20:c0:47:e6:d0:4e 5682 BOUND demux0.3221428609
[MASTER]
lab@MX960-Test> show dhcp server binding 138.88.70.201 verbose
Client IP Address: 138.88.70.201
Hardware Address: 20:c0:47:e6:d0:4e
State: BOUND(LOCAL_SERVER_STATE_BOUND)
Protocol-Used: DHCP
Lease Expires: 2019-05-03 16:53:17 UTC
Lease Expires in: 5677 seconds
Lease Start: 2019-05-03 07:37:10 UTC
Last Packet Received: 2019-05-03 14:53:17 UTC
Incoming Client Interface: demux0.3221428609
Client Interface Svlan Id: 84
Client Interface Vlan Id: 32
Server Identifier: 138.88.70.1
Session Id: 459914
Client Pool Name: DHCP050
Client Profile Name: DP-DEFAULT
Lease Binding Type: active
Client Id Length: 7
Client Id: /0x0120c047/0xe6d04e
Client Secondary Key (Incoming Intf):
Option Data: 537074519
Hardware Type: HTYPE_ETHER
Client LS/RI: default/default
General Client Information: Flags: 10010030, Flags2: 00080080, Flags3: 00000000
[MASTER]
lab@MX960-Test> ping 138.88.70.201
PING 138.88.70.201 (138.88.70.201): 56 data bytes
64 bytes from 138.88.70.201: icmp_seq=0 ttl=64 time=3.080 ms
64 bytes from 138.88.70.201: icmp_seq=1 ttl=64 time=3.285 ms
^C
--- 138.88.70.201 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.080/3.183/3.285/0.102 ms
Checking the subscriber demux0 IFL shows that it is running on ae11 with its member links on slot 8.
[MASTER]
lab@MX960-Test> show interfaces demux0.3221428609
Logical interface demux0.3221428609 (Index 537074519) (SNMP ifIndex 200203607)
Flags: VLAN-Tag [ 0x8100.84 0x8100.32 ] Encapsulation: ENET2
Demux:
Underlying interface: ae11 (Index 139)
Link:
xe-8/1/4
xe-8/1/5
Targeting summary:
xe-8/1/4, primary, Physical link is Up
Bandwidth: 0
Input packets : 102332
Output packets: 1130
Protocol inet, MTU: 1500
Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
Flags: uRPF, Unnumbered
Donor interface: lo0.100 (Index 322)
Preferred source address: 71.178.245.1
Addresses, Flags: Is-Primary
Local: 71.178.245.1
Checking the subscriber distribution and the targeting info of ae11 shows that the subscriber count is not evenly distributed. However, this should not cause the routing issue.
[MASTER] lab@MX960-Test> show interfaces targeting ae11 Aggregated interface: ae11 Targeting Type: Auto Redundancy mode: Fpc Level Redundancy Total number of distribution groups: 1 Total number of distributed interfaces: 1714 Distribution Group name: default Number of distributed interfaces: 1714 Physical interface: xe-8/1/4, Link status: Up Number of primary distributions: 1698 Number of backup distributions: 0 Physical interface: xe-8/1/5, Link status: Up Number of primary distributions: 16 Number of backup distributions: 0
Suspecting the traffic might be dropping on the uplinks while ingressing into the router, check for any suspected drops in the PFE on the uplink slots. In this case, slot 7 and 8 are the uplink slots.
Check on the second uplink slot as well to see if it also reports similar drops:
[MASTER] lab@MX960-Test> start shell pfe network fpc7 RMPC platform (1200Mhz QorIQ P2020 processor, 3584MB memory, 512KB flash) RMPC7(MX960-Test vty)# show jnh 0 exceptions terse Reason Type Packets Bytes ================================================================== Error Parcels ---------------------- from WAN M2L ERROR 2272 PFE State Invalid ---------------------- sw error DISC( 64) 21 4901 invalid fabric token DISC( 75) 94 22513 unknown family DISC( 73) 57457647 5019380617 unknown iif DISC( 1) 117312 38612261 egress pfe unspecified DISC( 19) 103023962 75288766191 dv discard DISC( 50) 39882266 13392817827 <> RMPC7(MX960-Test vty)# show jnh 0 exceptions terse Reason Type Packets Bytes ================================================================== Error Parcels ---------------------- from WAN M2L ERROR 2272 PFE State Invalid ---------------------- sw error DISC( 64) 21 4901 invalid fabric token DISC( 75) 94 22513 unknown family DISC( 73) 57457688 5019383435 unknown iif DISC( 1) 117312 38612261 egress pfe unspecified DISC( 19) 103036879 75290474805 <-- Increments dv discard DISC( 50) 39882294 13392825659 <>
This confirms it may be having issues with NH programming in the PFE on the access slot where the subscriber is terminated. However, in this case, the subscriber is also on slot 8.
Get the NH index and check it in the PFE. From the output below, we realize that it is missing Selector information:
[MASTER] lab@MX960-Test> show route 138.88.70.201 detail inet.0: 15858 destinations, 19218 routes (14968 active, 0 holddown, 1945 hidden) 138.88.70.201/32 (1 entry, 1 announced) *Access-internal Preference: 12 Next hop type: Private unicast, Next hop index: 0 Address: 0xe228f84 Next-hop reference count: 704 Next-hop index: 6770 State: <Active Int NSR-incapable> Age: 7:48:49 Validation State: unverified Task: RPD Unix Domain Server./var/run/rpd_serv.local Announcement bits (3): 0-KRT 5-Resolve tree 2 9-Resolve tree 5 AS path: I dsx.inet.0: 30 destinations, 30 routes (30 active, 0 holddown, 0 hidden) 0.0.0.0/0 (1 entry, 1 announced) *Static Preference: 5 Next hop type: Discard, Next hop index: 0 Address: 0x29ebe64 Next-hop reference count: 132 State: <Active Int Ext> Age: 21w0d 7:09:04 [MASTER] lab@MX960-Test> start shell pfe network fpc8 RMPC platform (1200Mhz QorIQ P2020 processor, 3584MB memory, 512KB flash) RMPC8(MX960-Test vty)# show nhdb id 6770 ID Type Interface Next Hop Addr Protocol Encap MTU Flags PFE internal Flags ----- -------- ------------- --------------- ---------- ------------ ---- ------------------ ------------------ 6770 Unicast demux0.2147483697 default IPv4 Ethernet 1500 0x0000000000000000 0x0000102000000000 RMPC8(MX960-Test vty)# show nhdb id 6770 detail ID Type Interface Next Hop Addr Protocol Encap MTU Flags PFE internal Flags ----- -------- ------------- --------------- ---------- ------------ ---- ------------------ ------------------ 6770 Unicast demux0.2147483697 default IPv4 Ethernet 1500 0x0000000000000000 0x0000102000000000 BFD Session Id: 0 Interface: 688 Topo-link: [pfe-0]: 0x08e0c6cc00080000 CallNH:desc_ptr:0x3831b3, mode=0, count=0x9 0x3831a3 0 : 0x16c0000000000000 0x3831ab 1 : 0x1441e1e890201a72 nh_mode: UCAST Dram Bytes : 404 Flags : 0x0000000000000000 Parent NHID : 0 Route Table ID : 0 PreComputed MTU: 0 Tunnel Self ID : 0x0 Tunnel Parent ID : 0x0 Parent NHID : 0 NH Ingress: Feature List: NH Ingress [pfe-0]: 0x08e0c6cc00080000; f_mask:0x240000000000000; c_mask:0xc000000000000000; f_num:13; c_num:2, inst:0xffffffff Idx#6 vbf: [pfe-0]: 0x16c0000000000000 Idx#9 set-nh-token: [pfe-0]: 0x1441e1e890201a72 NH Egress/Fabric: Feature List: NH [pfe-0]: 0xd3fffffc1000001c; f_mask:0x40000000000; c_mask:0x8000000000000000; f_num:25; c_num:1, inst:0xffffffff Idx#21 vbf: [pfe-0]: 0xd3fffffc1000001c PFE:0 Encap-ptr chain: ---------------- PtrType Ptr RefCount JnhAddr Key ------- ---------- -------- ------- --- Load balance flags: per member accounting : OFF inline jflow : OFF random mode : OFF rotate hash : OFF adaptive lb : OFF Selector : Selector Not found <-- Selector missing Dram Bytes: 548 RMPC8(MX960-Test vty)# exit
Connect to the BBE shell and check for ae11 details:
[MASTER] lab@MX960-Test> start shell % vty -s 7208 0x1 vty-bbe# show targeted ifd ae11 detail Detailed IFD Info IFD handle: 0xd60238c IFD Name: ae11 IFD Index: 139 IFD BBE Index: 13 IFD RefCnt: 2489 Installed on PFE: TRUE IFD Flags: 0x28 IFD Local Flags: 0x0 AE member count: 2 AE targeted pair count: 2 AE targeted redundancy mode: 1 AE targeted max granularity: 500 AE targeted rebalance mode: Modified AE targeted max slots chassis: 12 AE targeted rebalance count: 10 AE targeted redistribute: 5 AE targeted generation number 10 AE targeted backup member valid: No AE targeted client count 3420 AE targeted pseudo ifl count 7 AE targeted bucket count 8 AE targeted rebalance interval 0 AE targeted new db valid: No AE targeted new config pending: No Member IFD Name: ifd_index 613, xe-8/1/4, primary weight 1694, backup weight 16, link state down 0, fpc slot 8, chassis 0, elig 1 ifd_index 614, xe-8/1/5, primary weight 16, backup weight 1694, link state down 0, fpc slot 8, chassis 0, elig 1 IFD Target Info: Target set 0, primary ifd_index 613, backup ifd_index 0, total_weight 1694, ref_count 3388, bucket_cnt 7, pseudo_cnt 6, elig 1 Bucket Info: weight 482, ref_count 964, bucket_offset 0, pseudo_ifl_index 536 Bucket Info: weight 350, ref_count 700, bucket_offset 1, pseudo_ifl_index 688 Bucket Info: weight 0, ref_count 0, bucket_offset 2, pseudo_ifl_index 0 Bucket Info: weight 1, ref_count 2, bucket_offset 3, pseudo_ifl_index 682 Bucket Info: weight 51, ref_count 102, bucket_offset 4, pseudo_ifl_index 711 Bucket Info: weight 471, ref_count 942, bucket_offset 5, pseudo_ifl_index 681 Bucket Info: weight 339, ref_count 678, bucket_offset 6, pseudo_ifl_index 687 Target set 0: delta weight 0, delta ref_count 0, passed verification. Target set 1, primary ifd_index 614, backup ifd_index 0, total_weight 16, ref_count 32, bucket_cnt 1, pseudo_cnt 1, elig 1 Bucket Info: weight 16, ref_count 32, bucket_offset 0, pseudo_ifl_index 616 Target set 1: delta weight 0, delta ref_count 0, passed verification. IFD Target db passed verification.
AE11 seems to have 7 Pseudo IFLs each pointing to a certain number of subscriber IFLs to share among them.
Obtain the info on a couple of Pseudo IFLs under ae11:
vty-bbe# show ifl ifl-index 688 IFL handle: 0x12215fcc IFL Name: demux0.2147483697 IFL Type: PSEUDO IFL Index: 688 IFL BBE Index: 25751 IFL RefCnt: 396 IFL Flags: 0x0 IFL Local Flags: 0x0 vty-bbe# show ifl ifl-index 682 IFL handle: 0x11366f4c IFL Name: demux0.2147483691 IFL Type: PSEUDO IFL Index: 682 IFL BBE Index: 19462 IFL RefCnt: 4 IFL Flags: 0x0 IFL Local Flags: 0x0
Obtain all the Pseudo IFLs to display their names and index numbers:
vty-bbe# show ifls pseudo Walk all pseudo IFLs IFL handle: 0xde1af8c IFL Name: demux0.2147483649 IFL Type: PSEUDO IFL Index: 573 IFL BBE Index: 256 IFL RefCnt: 12 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde72c0c IFL Name: demux0.2147483650 IFL Type: PSEUDO IFL Index: 574 IFL BBE Index: 266 IFL RefCnt: 22 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde11a4c IFL Name: demux0.2147483651 IFL Type: PSEUDO IFL Index: 575 IFL BBE Index: 303 IFL RefCnt: 6 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde1240c IFL Name: demux0.2147483652 IFL Type: PSEUDO IFL Index: 576 IFL BBE Index: 307 IFL RefCnt: 6 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde12dcc IFL Name: demux0.2147483653 IFL Type: PSEUDO IFL Index: 577 IFL BBE Index: 311 IFL RefCnt: 18 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd7d758c IFL Name: demux0.2147483654 IFL Type: PSEUDO IFL Index: 578 IFL BBE Index: 358 IFL RefCnt: 8 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde10f0c IFL Name: demux0.2147483655 IFL Type: PSEUDO IFL Index: 579 IFL BBE Index: 374 IFL RefCnt: 14 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde1ab0c IFL Name: demux0.2147483656 IFL Type: PSEUDO IFL Index: 580 IFL BBE Index: 400 IFL RefCnt: 38 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde124cc IFL Name: demux0.2147483657 IFL Type: PSEUDO IFL Index: 572 IFL BBE Index: 546 IFL RefCnt: 986 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde12c4c IFL Name: demux0.2147483659 IFL Type: PSEUDO IFL Index: 631 IFL BBE Index: 576 IFL RefCnt: 936 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde73c8c IFL Name: demux0.2147483660 IFL Type: PSEUDO IFL Index: 632 IFL BBE Index: 604 IFL RefCnt: 1000 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd7d734c IFL Name: demux0.2147483661 IFL Type: PSEUDO IFL Index: 643 IFL BBE Index: 683 IFL RefCnt: 992 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd76dc4c IFL Name: demux0.2147483662 IFL Type: PSEUDO IFL Index: 653 IFL BBE Index: 857 IFL RefCnt: 124 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd7d578c IFL Name: demux0.2147483663 IFL Type: PSEUDO IFL Index: 654 IFL BBE Index: 860 IFL RefCnt: 38 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xb25480c IFL Name: demux0.2147483664 IFL Type: PSEUDO IFL Index: 655 IFL BBE Index: 861 IFL RefCnt: 182 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xb2548cc IFL Name: demux0.2147483665 IFL Type: PSEUDO IFL Index: 656 IFL BBE Index: 864 IFL RefCnt: 996 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd7d53cc IFL Name: demux0.2147483666 IFL Type: PSEUDO IFL Index: 657 IFL BBE Index: 867 IFL RefCnt: 1440 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xd7d794c IFL Name: demux0.2147483667 IFL Type: PSEUDO IFL Index: 658 IFL BBE Index: 929 IFL RefCnt: 2060 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde1990c IFL Name: demux0.2147483668 IFL Type: PSEUDO IFL Index: 659 IFL BBE Index: 943 IFL RefCnt: 991 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xde190cc IFL Name: demux0.2147483669 IFL Type: PSEUDO IFL Index: 660 IFL BBE Index: 1287 IFL RefCnt: 30 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xf1dd10c IFL Name: demux0.2147483670 IFL Type: PSEUDO IFL Index: 661 IFL BBE Index: 6153 IFL RefCnt: 1004 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xf1dd58c IFL Name: demux0.2147483671 IFL Type: PSEUDO IFL Index: 662 IFL BBE Index: 6155 IFL RefCnt: 1006 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xf33f64c IFL Name: demux0.2147483672 IFL Type: PSEUDO IFL Index: 663 IFL BBE Index: 7060 IFL RefCnt: 806 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xf33ef8c IFL Name: demux0.2147483673 IFL Type: PSEUDO IFL Index: 664 IFL BBE Index: 7062 IFL RefCnt: 802 IFL Flags: 0x0 IFL Local Flags: 0x0 IFL handle: 0xffb05cc IFL Name: demux0.2147483674 IFL Type: PSEUDO IFL Index: 665 IFL BBE Index: 11805 IFL RefCnt: 288 IFL Flags: 0
Check a couple of Pseudo IFLs under ae11 on the PFE. It shows they are all missing their children:
[MASTER] lab@MX960-Test> start shell pfe network fpc8 RMPC platform (1200Mhz QorIQ P2020 processor, 3584MB memory, 512KB flash) RMPC8(MX960-Test vty)# show ifl 688 Logical interface demux0.2147483697 (Index 688, Alias-Index 0 Peer-Index 0 ifl address 0x2261ee88) Channel Mode DISABLED 0 0 Flags: (0x0001000600004000) Up Accurate-Accounting Stacked-ifl Pseudo-ifl GEN Flags: (0x0000) LAG Enhanced Addresses: Media address: Family: Unspecified (0), Chan: 0, Length: 0 IRB ifl BD index 65535 Reroute Ref: 0, Restore Ref: 0, LRID: 0 Residue Stats in: 0 out: 0 Accounting Residue Stats in: 0 out: 0 Protocols: Protocol: IPv4, MTU: 1500 bytes, TCP MSS 0 bytes, Flags: 0x0010000200000002, Route table: 0 Maximum labels: 0 Input filter: 0, Output filter: 0, Interface class: 0, Dialer Filter: 0 Input Simple Filter: 0, Output Simple Filter: 0 Input implicit filters: None Output implicit filters: None L2 Input policer: 0, L2 Output policer: 0 Input policer: 0, Output policer: 0 RPF fail-filter: 0, Reroute Ref: 0, Restore Ref: 0 Service filters in: 0, 0, 0, 0, 0, 0, out: 0, 0, 0, 0, 0, 0, psf: 0 Protocol: IPv6, MTU: 1500 bytes, TCP MSS 0 bytes, Flags: 0x0110000000000002, Route table: 0 Maximum labels: 0 Input filter: 0, Output filter: 0, Interface class: 0, Dialer Filter: 0 Input Simple Filter: 0, Output Simple Filter: 0 Input implicit filters: None Output implicit filters: None L2 Input policer: 0, L2 Output policer: 0 Input policer: 0, Output policer: 0 RPF fail-filter: 0, Reroute Ref: 0, Restore Ref: 0 Media: Type: Ethernet, Encapsulation: Ethernet (0x0000000E) MTU: 9192 bytes, Flags: 0x0000 Dependencies: Underlying ifl index: 374 L2 ifl index: 374 Parent ifl index: 688 Aggregate: (child_list) Index Child name Channel ----- ----------------- -------- Forwarding options: Empty Storm control: BC: 0, UC: 0, Flags: 0x0 Creation time: May 03 05:58:52 2019 RMPC8(MX960-Test vty)# show ifl 682 Logical interface demux0.2147483691 (Index 682, Alias-Index 0 Peer-Index 0 ifl address 0x211267f8) Channel Mode DISABLED 0 0 Flags: (0x0001000600004000) Up Accurate-Accounting Stacked-ifl Pseudo-ifl GEN Flags: (0x0000) LAG Enhanced Addresses: Media address: Family: Unspecified (0), Chan: 0, Length: 0 IRB ifl BD index 65535 Reroute Ref: 0, Restore Ref: 0, LRID: 0 Residue Stats in: 0 out: 0 Accounting Residue Stats in: 0 out: 0 Protocols: Protocol: IPv4, MTU: 1500 bytes, TCP MSS 0 bytes, Flags: 0x0010000200000002, Route table: 0 Maximum labels: 0 Input filter: 0, Output filter: 0, Interface class: 0, Dialer Filter: 0 Input Simple Filter: 0, Output Simple Filter: 0 Input implicit filters: None Output implicit filters: None L2 Input policer: 0, L2 Output policer: 0 Input policer: 0, Output policer: 0 RPF fail-filter: 0, Reroute Ref: 0, Restore Ref: 0 Service filters in: 0, 0, 0, 0, 0, 0, out: 0, 0, 0, 0, 0, 0, psf: 0 Protocol: IPv6, MTU: 1500 bytes, TCP MSS 0 bytes, Flags: 0x0110000000000002, Route table: 0 Maximum labels: 0 Input filter: 0, Output filter: 0, Interface class: 0, Dialer Filter: 0 Input Simple Filter: 0, Output Simple Filter: 0 Input implicit filters: None Output implicit filters: None L2 Input policer: 0, L2 Output policer: 0 Input policer: 0, Output policer: 0 RPF fail-filter: 0, Reroute Ref: 0, Restore Ref: 0 Media: Type: Ethernet, Encapsulation: Ethernet (0x0000000E) MTU: 9192 bytes, Flags: 0x0000 Dependencies: Underlying ifl index: 374 L2 ifl index: 374 Parent ifl index: 682 Aggregate: (child_list) Index Child name Channel ----- ----------------- -------- Forwarding options: Empty Storm control: BC: 0, UC: 0, Flags: 0x0 Creation time: May 03 05:58:46 2019
The same can be also be confirmed from CLI:
[MASTER]
lab@MX960-Test> show interfaces demux0.2147483697
Logical interface demux0.2147483697 (Index 688) (SNMP ifIndex 1837)
Flags: Up 0x4000 Encapsulation: ENET2
Demux:
Underlying interface: ae11.32767 (Index 374) <-- missing their links
Bandwidth: 0
Input packets : 0
Output packets: 210964
Protocol inet, MTU: 1500
Max nh cache: 75000, New hold nh limit: 75000, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
Flags: No-Redirects, No-neighbor-learn
Addresses, Flags: Is-Default Is-Primary
Local: 0.0.0.0
Protocol inet6, MTU: 1500
Max nh cache: 75000, New hold nh limit: 75000, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
Flags: No-Redirects, No-neighbor-learn
Addresses
Local: fe80::e86:10ff:feeb:8fcb
Missing of the member links under the Pseudo IFLs should be the cause of the routing issue. The Workaround to recover from the issue is to toggle a member under the problematic AE (ae11 in this case). We can disable/enable a member link to force the BBE to republish the Pseudo IFLs under the AE with the correct information to the PFE. This should resolve the issue.
Getting Up and Running with Junos
Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search