Cyclops: an open eye to your network (beta release)
Hi, Just to let you know about Cyclops (beta for now), a tool for topology visibility and real-time routing anomaly detection/alerting for service providers and enterprise networks. Cyclops uses real time data from hundreds of vantage points of route-views, ripe-ris, packet clearing house and Univ. of Colorado bgpmon to assess how the rest of the world is reaching your network. Cyclops features include: - real-time alerting of prefix hijacks and misconfigured announcements - alerting of next-hop changes, AS in the middle (transit) and new prefix - alerting of new AS neighbor (false link announcement/leakages) - Global visibility on AS connectivity and prefix origins - Monitoring of routes to critical infrastructure, e.g. DNS TLDs - Anomaly listings (anomalous depeerings, bogus ASNs, bogon prefixes, long/short prefixes) To register for Cyclops please visit: http://cyclops.cs.ucla.edu/?l=reg To start configuring your network go to: http://cyclops.cs.ucla.edu/?v=ma&tab=1 (need to be logged in) You need to tell cyclops what are your prefixes, your ASNes and your neighbor ASNs. Please do not hesitate to contact me in case you have questions/ comments/bug reports. Thanks for being a Cycloper! --Ricardo In name of the Cyclops Team
RE: Redundant Array of Inexpensive ISP's?
The Talari device appears to operate like the old Routescience Pathcontrol BGP load balancer circa 2002 (Routescience is now owned by Avaya I believe). Routescience was able to compile the best path to Internet BGP prefixes so that a web site could connect to multiple 2nd tier ISPs (for circuit cost and redundancy reasons), and control the Mbps traffic over the best path, irrespective of the BGP feed supplied by the upstream ISP. In my experience devices such as Routescience automated the tedious work of using CAIDA tools to manually calculate the best BGP path to destination prefixes, and eliminated the almost daily reconfiguration of BGP route maps on Internet border routers. Routescience was a great product that put dashboard BGP routing control in the hands of the network engineer, and saved MRC circuit costs to pay for itself within a few months. -Original Message- From: Tim Utschig [mailto:t...@tetro.net] Sent: Tuesday, March 10, 2009 4:02 PM To: nanog@nanog.org Subject: Redundant Array of Inexpensive ISP's? [Please reply off-list. I'll summarize back to the list if there is more than a little interest in me doing so.] I'm curious if anyone has experience with products from Talari Networks, or anything similar, and would like to share. Did they live up to your expectations? Caveats? -- - Tim Utschig
Re: Redundant Array of Inexpensive ISP's?
Good question. I'm also curious if anyone has experience with the Mushroom BBNA device and how it compares to Talari. Due to various premises and telco issues, I've been unable to get anything faster than a DSL connection pulled into a certain branch office. I'm considering any and every alternative at this point. On Tue, Mar 10, 2009 at 4:01 PM, Tim Utschig wrote: > > [Please reply off-list. I'll summarize back to the list if there > is more than a little interest in me doing so.] > > I'm curious if anyone has experience with products from Talari > Networks, or anything similar, and would like to share. Did they > live up to your expectations? Caveats? > > -- > - Tim Utschig > >
Re: Redundant Array of Inexpensive ISP's?
This seems similiar to Cisco performance routing. See http://www.cisco.com/en/US/products/ps8787/products_ios_protocol_option_home.html for more. Tim Utschig wrote: Talari Networks -- Charles N Wyble char...@thewybles.com (818)280-7059 http://charlesnw.blogspot.com CTO SocalWiFI.net
Redundant Array of Inexpensive ISP's?
[Please reply off-list. I'll summarize back to the list if there is more than a little interest in me doing so.] I'm curious if anyone has experience with products from Talari Networks, or anything similar, and would like to share. Did they live up to your expectations? Caveats? -- - Tim Utschig
RE: XO peering.
I did some preliminary tests static-routing some prefixes that were not working earlier over our XO connection and everything seemed fine. I went ahead and turned the session back up, no reports of trouble yet. I'll update if we have any issues. -- Regards, Jake Mertel Nobis Technology Group, L.L.C. Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417 Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701 -Original Message- From: Kevin Oberman [mailto:ober...@es.net] Sent: Tuesday, March 10, 2009 2:41 PM To: Mort, Eric Cc: Jake Mertel; John Martinez; nanog@nanog.org Subject: RE: XO peering. On Tue, 2009-03-10 at 11:41 -0500, Mort, Eric wrote: > We had some hardware issues in San Jose which triggered some other > ugliness. We believe we have the issues mitigated at this time. > Folks still seeing issues are encouraged to hit me up offline. > > Thanks, > > Eric J. Mort > XO Communications > Sr. Manager - IP Operations > Desk - 314-787-7826 > Cell - 314.486-9057 > em...@xo.com > > > -Original Message- > From: Jake Mertel [mailto:j...@nobistech.net] > Sent: Tuesday, March 10, 2009 11:34 AM > To: John Martinez; nanog@nanog.org > Subject: RE: XO peering. > > We had a number of issues in the Seattle area this morning, seemed to > be isolated to traffic transiting via Level 3. We were forced to turn > off the connection, and it's still disabled until we get an update from XO. > > > -- > Regards, > > Jake Mertel > Nobis Technology Group, L.L.C. > > > > Web: http://www.nobistech.net/ > Phone: (312) 281-5101 ext. 401 > Fax: (808) 356-0417 > > Mail: 201 West Olive Street > Second Floor, Suite 2B > Bloomington, IL 61701 > > > -Original Message- > From: John Martinez [mailto:jmarti...@zero11.com] > Sent: Tuesday, March 10, 2009 11:23 AM > To: nanog@nanog.org > Subject: Re: XO peering. > > We saw an issue with Level 3 hand off to XO in Chicago. > > Stefan Molnar wrote: > > > > There was a peering issue in San Jose with XO, that impacted our > > operations this morning. But looks like a side effect is after the > hand > > off to NTT. > > > > Anyone who has an XO link can reach areas insdie NTT? > > > > As an example our route to Salesforce /21 is via NTT and it is not > happy > > right now. > > > > Thanks, > > Stefan > > > > > > > > > No joy from our (AS293) perspective. I still see traffic to XO at SJ black-holed. eqx-sj-rt1-re1> traceroute 198.17.75.45 traceroute to 198.17.75.45 (198.17.75.45), 30 hops max, 40 byte packets ^C Works fine from Ashburn, though. I've pref'ed XO down at SJ until it is working again. -- R. Kevin Oberman Energy Sciences Network (ESnet) Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab) E-Mail: ober...@es.net Phone: +1 510-486-8634
RE: XO peering.
On Tue, 2009-03-10 at 11:41 -0500, Mort, Eric wrote: > We had some hardware issues in San Jose which triggered some other > ugliness. We believe we have the issues mitigated at this time. Folks > still seeing issues are encouraged to hit me up offline. > > Thanks, > > Eric J. Mort > XO Communications > Sr. Manager - IP Operations > Desk - 314-787-7826 > Cell - 314.486-9057 > em...@xo.com > > > -Original Message- > From: Jake Mertel [mailto:j...@nobistech.net] > Sent: Tuesday, March 10, 2009 11:34 AM > To: John Martinez; nanog@nanog.org > Subject: RE: XO peering. > > We had a number of issues in the Seattle area this morning, seemed to be > isolated to traffic transiting via Level 3. We were forced to turn off > the connection, and it's still disabled until we get an update from XO. > > > -- > Regards, > > Jake Mertel > Nobis Technology Group, L.L.C. > > > > Web: http://www.nobistech.net/ > Phone: (312) 281-5101 ext. 401 > Fax: (808) 356-0417 > > Mail: 201 West Olive Street > Second Floor, Suite 2B > Bloomington, IL 61701 > > > -Original Message- > From: John Martinez [mailto:jmarti...@zero11.com] > Sent: Tuesday, March 10, 2009 11:23 AM > To: nanog@nanog.org > Subject: Re: XO peering. > > We saw an issue with Level 3 hand off to XO in Chicago. > > Stefan Molnar wrote: > > > > There was a peering issue in San Jose with XO, that impacted our > > operations this morning. But looks like a side effect is after the > hand > > off to NTT. > > > > Anyone who has an XO link can reach areas insdie NTT? > > > > As an example our route to Salesforce /21 is via NTT and it is not > happy > > right now. > > > > Thanks, > > Stefan > > > > > > > > > No joy from our (AS293) perspective. I still see traffic to XO at SJ black-holed. eqx-sj-rt1-re1> traceroute 198.17.75.45 traceroute to 198.17.75.45 (198.17.75.45), 30 hops max, 40 byte packets ^C Works fine from Ashburn, though. I've pref'ed XO down at SJ until it is working again. -- R. Kevin Oberman Energy Sciences Network (ESnet) Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab) E-Mail: ober...@es.net Phone: +1 510-486-8634 signature.asc Description: This is a digitally signed message part
Re: XO peering.
Our office has XO, and sent an email out complainging about Salesforce.In Chicago. --chris Stefan Molnar wrote: It just cleared up for me. Nice to have a call center complain constantly. Thanks On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote: On Tue, Mar 10, 2009 at 9:35 PM, Stefan Molnar wrote: There was a peering issue in San Jose with XO, that impacted our operations this morning. But looks like a side effect is after the hand off to NTT. Anyone who has an XO link can reach areas insdie NTT? As an example our route to Salesforce /21 is via NTT and it is not happy right now. This is from a host in XO AS2828 I can reach, for example, www.verio.net 204.202.20.3 / AS2914 NTT-COMMUNICATIONS-2914 just fine. www.salesforce.com is also reachable, through NTT -- Suresh Ramasubramanian (ops.li...@gmail.com) No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.9/1993 - Release Date: 03/10/09 07:19:00
Re: XO peering.
It just cleared up for me. Nice to have a call center complain constantly. Thanks On Tue, 10 Mar 2009, Suresh Ramasubramanian wrote: On Tue, Mar 10, 2009 at 9:35 PM, Stefan Molnar wrote: There was a peering issue in San Jose with XO, that impacted our operations this morning. But looks like a side effect is after the hand off to NTT. Anyone who has an XO link can reach areas insdie NTT? As an example our route to Salesforce /21 is via NTT and it is not happy right now. This is from a host in XO AS2828 I can reach, for example, www.verio.net 204.202.20.3 / AS2914 NTT-COMMUNICATIONS-2914 just fine. www.salesforce.com is also reachable, through NTT -- Suresh Ramasubramanian (ops.li...@gmail.com)
RE: XO peering.
We had some hardware issues in San Jose which triggered some other ugliness. We believe we have the issues mitigated at this time. Folks still seeing issues are encouraged to hit me up offline. Thanks, Eric J. Mort XO Communications Sr. Manager - IP Operations Desk - 314-787-7826 Cell - 314.486-9057 em...@xo.com -Original Message- From: Jake Mertel [mailto:j...@nobistech.net] Sent: Tuesday, March 10, 2009 11:34 AM To: John Martinez; nanog@nanog.org Subject: RE: XO peering. We had a number of issues in the Seattle area this morning, seemed to be isolated to traffic transiting via Level 3. We were forced to turn off the connection, and it's still disabled until we get an update from XO. -- Regards, Jake Mertel Nobis Technology Group, L.L.C. Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417 Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701 -Original Message- From: John Martinez [mailto:jmarti...@zero11.com] Sent: Tuesday, March 10, 2009 11:23 AM To: nanog@nanog.org Subject: Re: XO peering. We saw an issue with Level 3 hand off to XO in Chicago. Stefan Molnar wrote: > > There was a peering issue in San Jose with XO, that impacted our > operations this morning. But looks like a side effect is after the hand > off to NTT. > > Anyone who has an XO link can reach areas insdie NTT? > > As an example our route to Salesforce /21 is via NTT and it is not happy > right now. > > Thanks, > Stefan >
Re: XO peering.
Do you have the XO ticket number? Jake Mertel wrote: > We had a number of issues in the Seattle area this morning, seemed to be > isolated to traffic transiting via Level 3. We were forced to turn off the > connection, and it's still disabled until we get an update from XO. > > > -- > Regards, > > Jake Mertel > Nobis Technology Group, L.L.C. > > > > Web: http://www.nobistech.net/ > Phone: (312) 281-5101 ext. 401 > Fax: (808) 356-0417 > > Mail: 201 West Olive Street > Second Floor, Suite 2B > Bloomington, IL 61701 > > > -Original Message- > From: John Martinez [mailto:jmarti...@zero11.com] > Sent: Tuesday, March 10, 2009 11:23 AM > To: nanog@nanog.org > Subject: Re: XO peering. > > We saw an issue with Level 3 hand off to XO in Chicago. > > Stefan Molnar wrote: >> There was a peering issue in San Jose with XO, that impacted our >> operations this morning. But looks like a side effect is after the hand >> off to NTT. >> >> Anyone who has an XO link can reach areas insdie NTT? >> >> As an example our route to Salesforce /21 is via NTT and it is not happy >> right now. >> >> Thanks, >> Stefan >> > > >
RE: XO peering.
We had a number of issues in the Seattle area this morning, seemed to be isolated to traffic transiting via Level 3. We were forced to turn off the connection, and it's still disabled until we get an update from XO. -- Regards, Jake Mertel Nobis Technology Group, L.L.C. Web: http://www.nobistech.net/ Phone: (312) 281-5101 ext. 401 Fax: (808) 356-0417 Mail: 201 West Olive Street Second Floor, Suite 2B Bloomington, IL 61701 -Original Message- From: John Martinez [mailto:jmarti...@zero11.com] Sent: Tuesday, March 10, 2009 11:23 AM To: nanog@nanog.org Subject: Re: XO peering. We saw an issue with Level 3 hand off to XO in Chicago. Stefan Molnar wrote: > > There was a peering issue in San Jose with XO, that impacted our > operations this morning. But looks like a side effect is after the hand > off to NTT. > > Anyone who has an XO link can reach areas insdie NTT? > > As an example our route to Salesforce /21 is via NTT and it is not happy > right now. > > Thanks, > Stefan >
Re: XO peering.
We saw an issue with Level 3 hand off to XO in Chicago. Stefan Molnar wrote: > > There was a peering issue in San Jose with XO, that impacted our > operations this morning. But looks like a side effect is after the hand > off to NTT. > > Anyone who has an XO link can reach areas insdie NTT? > > As an example our route to Salesforce /21 is via NTT and it is not happy > right now. > > Thanks, > Stefan >
Re: XO peering.
On Tue, Mar 10, 2009 at 9:35 PM, Stefan Molnar wrote: > There was a peering issue in San Jose with XO, that impacted our operations > this morning. But looks like a side effect is after the hand off to NTT. > Anyone who has an XO link can reach areas insdie NTT? > As an example our route to Salesforce /21 is via NTT and it is not happy > right now. This is from a host in XO AS2828 I can reach, for example, www.verio.net 204.202.20.3 / AS2914 NTT-COMMUNICATIONS-2914 just fine. www.salesforce.com is also reachable, through NTT -- Suresh Ramasubramanian (ops.li...@gmail.com)
XO peering.
There was a peering issue in San Jose with XO, that impacted our operations this morning. But looks like a side effect is after the hand off to NTT. Anyone who has an XO link can reach areas insdie NTT? As an example our route to Salesforce /21 is via NTT and it is not happy right now. Thanks, Stefan
