2269
Views
0
Helpful
3
Replies
received from neighbor X.X.X.X active 2/2 (peer in wrong AS) 0 bytes
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 07:21 PM
3 Replies 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 07:44 PM - edited 12-14-2018 07:51 PM
Duplicate post
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 09:23 PM
Hi
Cross checked neighbor peer, configuration is correct.
I am wondering
Cisco notification has (peer in wrong AS) 2/4 bytes etc but in this case
it's 0 bytes. Why it is so??
Cross checked neighbor peer, configuration is correct.
I am wondering
Cisco notification has (peer in wrong AS) 2/4 bytes etc but in this case
it's 0 bytes. Why it is so??
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2024 08:31 PM
Hi,
That's because the remote AS configured is different from the actual AS number on peer.
- Teck Sing

Topology Juniper(AS9498) -------(AS137671)
Cisco configuration matches as numbers on BGP speakers on juniper and vice versa.
-->>>Juniper-BGP notification :- received NOTIFICATION code 2 (Open Message Error) sub code 0 (unspecified error)
and on Cisco -%BGP-3-NOTIFICATION: received from neighbor X.X.X. X active 2/2 (peer in wrong AS) 0 bytes