I've an issue with configuration on SRX650 running JunOS 9.5R1.8.
In fact, no BGP routes are received from the eBGP neighbor (Cisco Router) even if the BGP peering itself is UP (Estalished state from the 'show bgp neighbor' command).
The SRX650 also is exporting a route (0.0.0.0/0) to another eBGP peer (another Cisco router), this route is correctly advertised to the peer.
Conclusion
1. The SRX650 doesn't import any routes from iBGP/eBGP peer.
2. The routes exported by the SRX650 are received by the other peer (iBGP/eBGP).
Here's the info I can get from the trace file
Jul 20 15:54:02.416359 BGP RECV 194.154.198.157+22579 -> 194.154.198.158+179
Jul 20 15:54:02.416420 BGP RECV message type 2 (Update) length 72
Jul 20 15:54:02.416463 BGP RECV flags 0x40 code Origin(1): IGP
Jul 20 15:54:02.416512 BGP RECV flags 0x40 code ASPath(2) length 6: 6661 1000
Jul 20 15:54:02.416557 BGP RECV flags 0x40 code NextHop(3): 194.154.198.157
Jul 20 15:54:02.416625 BGP RECV 193.153.201.0/30 , 205.205.205.0/24 , 204.204.204.0/24 , 203.203.203.0
/24
Jul 20 15:54:02.416687 BGP RECV 202.202.202.0/24 , 201.201.201.0/24 , 200.200.200.0/24
Jul 20 15:54:02.416746 bgp_should_merge_as2_and_as4_path():2142 AS4-Peer 194.154.198.157 (External AS 6661)(RE
CV): No AS4 Path or Aggregator4 Path Attribute received
Jul 20 15:54:02.416824 bgp_process_aspath_and_aggr_attr():2506 AS4-Peer 194.154.198.157 (External AS 6661)(REC
V): bgp_should_merge_as2_and_as4_path() says NO
---(more 64%)--- Jul 20 15:54:02.416924 bgp_process_aspath_and_aggr_attr():2543 AS4-Peer 194.154.198.157 (External AS 6661)(REC
V): Merged asp: path_len 8, path_seg_len 2, path2_len 0, path2_seg_len 0, path4_len 0, path4_seg_len 0, path_a
ttr_len 0, path_aggr_len 0, path4_aggr_len 0, path4_flags 0x0, path_flags 0x0
Jul 20 15:54:02.416990 bgp_rcv_nlri: Peer 194.154.198.157 (External AS 6661)
Jul 20 15:54:02.417039 bgp_rcv_nlri: 193.153.201.0/30
Jul 20 15:54:02.417147 bgp_rcv_nlri: 205.205.205.0/24
Jul 20 15:54:02.417256 bgp_rcv_nlri: 204.204.204.0/24
Jul 20 15:54:02.417365 bgp_rcv_nlri: 203.203.203.0/24
Jul 20 15:54:02.417473 bgp_rcv_nlri: 202.202.202.0/24
Jul 20 15:54:02.417582 bgp_rcv_nlri: 201.201.201.0/24
Jul 20 15:54:02.417690 bgp_rcv_nlri: 200.200.200.0/24
Jul 20 15:54:02.417826 bgp_read_v4_message: done with 194.154.198.157 (External AS 6661) received 125 octets 2
updates 8 routes
Jul 20 15:54:02.417882 task_job_delete: delete background job Read peer for task BGP_6661.194.154.198.157+2257
9
Jul 20 15:54:02.417982 background dispatch completed job Read peer for task BGP_6661.194.154.198.157+22579
Jul 20 15:54:02.418421 task_process_events: recv ready for BGP_6661.194.154.198.157+22579
Jul 20 15:54:02.418473 task_job_create_background: create prio 4 job Read peer for task BGP_6661.194.154.198.1
57+22579
---(more 66%)--- Jul 20 15:54:02.418590 background dispatch running job Read peer for task BGP_6661.194.154.198.157+22579
Jul 20 15:54:02.418635 bgp_read_v4_message: receiving packet(s) from 194.154.198.157 (External AS 6661)
Jul 20 15:54:02.418696
Jul 20 15:54:02.418696 BGP RECV 194.154.198.157+22579 -> 194.154.198.158+179
Jul 20 15:54:02.418756 BGP RECV message type 4 (KeepAlive) length 19
Jul 20 15:54:02.418807 bgp_read_v4_message: done with 194.154.198.157 (External AS 6661) received 19 octets 0
updates 0 routes
Any idea ??
Hedi