.jpg "Opportunities, Appliacation, Openings"){kind=small}
.jpg "Hand Job, Blow Job, Job Search, Monster Job"){kind=small}
.jpg "pusat resume, daftar kerja, cari kerja"){kind=small}
.jpg "Project Manager, SOftware Engineer, SAP Consultant"){kind=small}
BGP Mystery
Yes, when the update source and peer to ip don’t jive.
Can you just write an acl and capture all “tcp any any eq 179 log” and just wait to see what address trys to peer with you?
-Joe
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Lee Glenn (leglenn) Sent: Tuesday, July 22, 2008 10:12 AM To: ccielab@groupstudy.com Subject: BGP Mystery
Here is the scenario, hopefully someone out there can help me solve this:
You are peering your router to an ISP router, you have total control over your router, but have no view into the ISPs router or configs, and you cannot call your ISP for help. You set up what you believe to be the proper peer address and remote-as but the peer session will not come up. The one and only debug message you get is below, 2.2.2.2 is the router you are trying to peer too:
BGP: 2.2.2.2 open active delayed 33704ms (35000ms max, 28% jitter)
Anyone run into this?
