Hi, Can you verify what's the current status and threshold based on the screenshot i've provided? Thanks ... View more

Hi Peter, We've just put this "enforce-first-as disable" on our config and our bgp peering established.      ... View more

Hi Peter, Please see attached. #show bgp neighbor 206.41.73.1 Wed Sep  2 11:21:05.005 UTC BGP neighbor is 206.41.73.1  Remote AS, local AS, external link  Description: ::PEERING  Remote router ID 206.41.73.1   BGP state = Established, up for 1w1d   Last read 00:00:30, Last read before reset 00:00:00   Hold time is 180, keepalive interval is 60 seconds   Configured hold time: 180, keepalive: 60, min acceptable hold time: 3   Last write 00:00:00, attempted 19, written 19   Second last write 00:01:00, attempted 19, written 19   Last write before reset 00:00:00, attempted 0, written 0   Second last write before reset 00:00:00, attempted 0, written 0   Last write pulse rcvd  Sep  2 11:21:04.835 last full not set pulse count 26456   Last write pulse rcvd before reset 00:00:00   Socket not armed for io, armed for read, armed for write   Last write thread event before reset 00:00:00, second last 00:00:00   Last KA expiry before reset 00:00:00, second last 00:00:00   Last KA error before reset 00:00:00, KA not sent 00:00:00   Last KA start before reset 00:00:00, second last 00:00:00   Precedence: internet   Enforcing first AS is enabled   Neighbor capabilities:     Route refresh: advertised and received     4-byte AS: advertised and received     Address family IPv4 Unicast: advertised and received   Received 14057 messages, 0 notifications, 0 in queue   Sent 12480 messages, 0 notifications, 0 in queue   Minimum time between advertisement runs is 30 secs  For Address Family: IPv4 Unicast   BGP neighbor version 328579802   Update group: 0.36 Filter-group: 0.13  No Refresh request being processed   Inbound soft reconfiguration allowed (override route-refresh)   Private AS number removed from updates to this neighbor   Route refresh request: received 0, sent 0   Policy for incoming advertisements is PEERING-IN   Policy for outgoing advertisements is ALL-OUT   0 accepted prefixes, 0 are bestpaths   Cumulative no. of prefixes denied: 0.    Prefix advertised 669, suppressed 36, withdrawn 22   Maximum prefixes allowed 1048576   Threshold for warning message 75%, restart interval 0 min   An EoR was not received during read-only mode   Last ack version 328579802, Last synced ack version 0   Outstanding version objects: current 0, max 3   Additional-paths operation: None   Connections established 1; dropped 0   Local host: 206.41.73.39, Local port: 179   Foreign host: 206.41.73.1, Foreign port: 39574   Last reset 00:00:00 ... View more

Hi Peter,   Session is still not established, we're coordinating our peering right now to check on their end. ... View more

Hi Peter,   Please see bgp config below.   router#sh run router bgp <AS> neigh 206.41.72.1 Tue Sep  1 01:08:58.013 LAX router bgp <AS>  neighbor 206.41.72.1   remote-as 63022   description :: PEERING   address-family ipv4 unicast    route-policy PEERING-IN in    route-policy PEERING-OUT out    remove-private-AS    soft-reconfiguration inbound always   show bgp neighbor 206.42.72.1 BGP neighbor is 206.41.72.1  Remote AS 63022, local AS, external link  Description: ::PEERING  Remote router ID 0.0.0.0   BGP state = Idle   Last read 00:00:00, Last read before reset 00:04:32   Hold time is 180, keepalive interval is 60 seconds   Configured hold time: 180, keepalive: 60, min acceptable hold time: 3   Last write 00:00:18, attempted 53, written 53   Second last write 00:01:00, attempted 53, written 53   Last write before reset 00:04:32, attempted 72, written 72   Second last write before reset 00:05:12, attempted 53, written 53   Last write pulse rcvd  Sep  1 01:15:44.807 last full not set pulse count 46339   Last write pulse rcvd before reset 00:04:32   Socket not armed for io, not armed for read, not armed for write   Last write thread event before reset 00:04:32, second last 00:04:32   Last KA expiry before reset 00:00:00, second last 00:00:00   Last KA error before reset 00:00:00, KA not sent 00:00:00   Last KA start before reset 00:00:00, second last 00:00:00   Precedence: internet   Enforcing first AS is enabled   Received 13663 messages, 0 notifications, 0 in queue   Sent 25942 messages, 4559 notifications, 0 in queue   Minimum time between advertisement runs is 30 secs  For Address Family: IPv4 Unicast   BGP neighbor version 0   Update group: 0.20 Filter-group: 0.0  No Refresh request being processed   Inbound soft reconfiguration allowed (override route-refresh)   Private AS number removed from updates to this neighbor   Route refresh request: received 0, sent 0   Policy for incoming advertisements is PEERING-IN   Policy for outgoing advertisements is PEERING-OUT   0 accepted prefixes, 0 are bestpaths   Cumulative no. of prefixes denied: 0.    Prefix advertised 0, suppressed 0, withdrawn 0   Maximum prefixes allowed 524288   Threshold for warning message 75%, restart interval 0 min   An EoR was not received during read-only mode   Last ack version 0, Last synced ack version 0   Outstanding version objects: current 0, max 0   Additional-paths operation: None   Connections established 4550; dropped 4550   Local host: 206.41.72.39, Local port: 34367   Foreign host: 206.41.72.1, Foreign port: 179   Last reset 00:00:18, due to Peer closing down the session   Peer reset reason: Remote closed the session (Connection timed out)   Time since last notification sent to neighbor: 00:04:32   Error Code: invalid or corrupt AS path   Notification data sent:     40020A02 02000051 CC000040 F1  Total malformed UPDATE 4550   Last malformed UPDATE 00:04:32   Error subcode 11, attribute code 0, action reset session   Malformed UPDATE: 133 bytes     FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF     00850200 00002E40 01010040 020A0202     000051CC 000040F1 400304CE 294822C0     07080000 51CC172D 4359C008 0851CC01     9B51CC03 781317DD 6016B855 E41648F6     A01648F6 CC1748F7 EA14B855 4014173E     40141706 B014173E 501748F6 501417DE     A016173E 3817173E 361417CD C017B81C     2014173B 10 ... View more

Peter,   Let me clarify this on my peer. I'll get back as soon as I already have an update. Thank you for your assistance.  ... View more

Please see above updates ... View more

Hi Peter,    I've compared both working and non working BGP peer. Please see attached debug results.   Not working - refer to session.txt Working - refer to session-sea.txt   ... View more

I already tried to drop our IN and OUT policy but still no avail ... View more

is it possible that Netdisco will initiate or run if we have our aggregate routers / PE routers that isn't cisco? ... View more

Hi Joseph,   How can I start building this platform? My plan was to create an HTML website or MS Access to integrate into the router to get info and printed via html or in access  ... View more