June 2009 - Test - lists.nanog.org

Telephones for Noisy Data Centers
by Rick 18 Jun '09

18 Jun '09

The ones I can recommend in that line are the headsets from David Clark. I've used these for decades in some of the harshest noise locations with great success. While most of the adaptors I use are home made I suspect that they can supply one for about any application. They have for me. http://www.davidclark.com/ regards Rick Try noice-canceling aviation headsets (GA or helicopter models have truly amazing noise suppression). High-end models come with cellphone interface. I don't think cellphones will work in many data centers, but I think rigging interface from a normal cordless phone to the headset is pretty simple. The better of these headsets (Bose X, Sennheiser HMC460, Zulu Lightspeed, etc) have additional digital signal processing for getting voice out of noise - if you don't mind expense:) --vadim > Michael J McCafferty wrote: > > All, > > I'd be OK if we were in a facility that was only average in terms of > > noise, but we are not. I need an exceptional phone for the data center. > > Something that doesn't transmit the horrible background noise to the > > other end, and something that is loud without being painful for the user > > of this phone. Cordless would be very fine, headset is excellent. > > Ordinary desk phone is OK... but the most important thing is that it > > works for clear communication. A loud ringer would great too... but if > > the best phone doesn't have one, I'll get an auxiliary ringer. > > > > Does anyone have a phone model that they find to be excellent in a > > louder than usual data center?

1 0

Cogent input
by Justin Shore 18 Jun '09

18 Jun '09

I'm in search of some information about Cogent, it's past, present and future. I've heard bits and pieces about Cogent's past over the years but by no means have I actively been keeping up. I'm aware of some (regular?) depeering issues. The NANOG archives have given me some additional insight into that (recurring?) problem. The reasoning behind the depeering events is a bit fuzzy though. I would be interested in people's opinion on whether or not they should be consider for upstream service based on this particular issue. Are there any reasonable mitigation measures available to Cogent downstreams if (when?) Cogent were to be depeered again? My understanding is that at least on previous depeering occasion, the depeering partner simply null-routed all prefixes being received via Cogent, creating a blackhole essentially. I also recall reading that this meant that prefixes being advertised and received by the depeering partner from other peers would still end up in the blackhole. The only solution I would see to this problem would be to shut down the BGP session with Cogent and rely on a 2nd upstream. Are there any other possible steps for mitigation in a depeering event? I also know that their bandwidth is extremely cheap. This of course creates an issue for technical folks when trying to justify other upstream options that cost significantly more but also don't have a damaging history of getting depeered. Does Cogent still have an issue with depeering? Are there any reasonable mitigation measures or should a downstream customer do any thing in particular to ready themselves for a depeering event? Does their low cost outweigh the risks? What are the specific risks? Thanks Justin

44 61

Re: WISP NMS recommendations
by Patrick Shoemaker 18 Jun '09

18 Jun '09

Although this would probably be better suited for one of the WISPA lists, I'll respond here anyhow since there seems to be some interest. For managing Canopy elements, Motorola Prizm is probably the way to go. First of all, you'll need it to handle element authentication for your PtMP system. It will also do configuration management, alerting, and all the usual NMS stuff. It's also *possible* to get it to work with other SNMP capable devices if you want to manage other vendors' equipment. It will work out of the box with the Canopy PtMP line, PtP devices, powerline carrier devices, and (I think) the MotoMESH line. It gives you all the info you need at a glance for each element: configuration history, RF power level plots, bandwidth utilization plots, alert history, etc. FYI if you haven't used it, Prizm is a pretty clunky and slow Java-based package. The features are nice, but configuring it can be a chore. Patrick Shoemaker Vector Data Systems LLC shoemakerp(a)vectordatasystems.com office: (301) 358-1690 x36 http://www.vectordatasystems.com nanog-request(a)nanog.org wrote: > Message: 5 > Date: Wed, 17 Jun 2009 21:31:29 -0700 > From: Freddie Sessler <nanogger(a)gmail.com> > Subject: WISP NMS recommendations > To: nanog(a)nanog.org > Message-ID: > <d0f4f2f20906172131i5f86c80ds993a943c4f0ddf4f(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Folks,I am looking for recommendations on an NMS system for use in > managing a multivendor wireless infrastructure. Specifically we run mostly > Motorola point to point, point to multipoint(Canopy platform) and mesh > radios devices We have looked at the One Point Wireless Manager but this > product in our evaluation doesn't seem to be ready for prime time and also > has the limitation of only being able to manage Motorola. Ideally we would > have something that could be used for configuration management in a multi > vendor environment as well as recieve SNMP traps about RF issues such as > latency and jitter. I am curious to what other shops are using out there. If > this is a top better suited to another list, my apologies and any pointers > to a different list would be greatly appreciated. > > Thanks > JT

1 0

RE: spamhaus drop list
by Quinn Mahoney 18 Jun '09

18 Jun '09

Is there a competing droplist, that can be compared against Spamhaus's droplist? That seems like an extraordinary claim, so I'm not satisfied with the evidence provided. Is this not the best droplist? -----Original Message----- From: Dean Anderson [mailto:dean@av8.com] Sent: Monday, June 15, 2009 6:10 PM To: Quinn Mahoney Cc: nanog(a)nanog.org Subject: Re: spamhaus drop list I suggest you avoid spamhaus, MAPS, and SORBS. They are really spammers in disguise, using blacklists to harm their competition while presumably letting their own spam through. We know they have used trust of the anti-spam community to list-wash spam-trap addresses. See http://www.iadl.org/whitehat/whitehat-story.html add the IADL pages on Paul Vixie and MAPS. You might also look at http://www.av8.net/IETF-watch/People/JohnLevine/index.html Levine, long head of the Anti-spam Research Group, was also unmasked as a spammer. Fred Baker <fred(a)cisco.com> is on the ISC Board of Trustees, and is a Vixie supportor. --Dean On Mon, 15 Jun 2009, Quinn Mahoney wrote: > I'm looking to implement the Spamhaus drop list. > http://www.spamhaus.org/drop/index.lasso > > > > On their FAQ they have a script that looks like it grabs the lists text > file and connects to a given router, and tells you what has changed in > the list, and what your router is null routing. I'm not sure if it then > removes the null routes if a list entry has been removed. I haven't > found much documentation on the net regarding this. In the future it > looks like you will be able to peer with them and null route traffic > from a private AS, which will be routes from the drop list. Right now > though, it looks like you'd have to update an ACL manually for any > changes to the list. Or use this script which null routes the traffic > (I guess it's not a big deal getting the syn packets, as long as the > mail won't send because of the null route). I am not sure if this > script updates the null routes automatically, or how to use it, I can't > find to much documentation. > > > > Any documentation on this script or another script available. What are > your suggestions? > > > > thanks > > > > > > > -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000

8 9

IGP/BGP design question
by ML 17 Jun '09

17 Jun '09

We have three main cities wherein eyeballs live. Currently we have San Jose and San Francisco traffic egressing in SF, and Los Angeles egressing in LA. There is one private 2x1gig long haul linking SJC to LA and a 1x 10gig linking SJC to SF. i.e SF <-10gig-> SJC <-2gig-> LA Each area is a separate OSPF domain. Static routes define how to reach the RFC1918 space defined for each area. Currently SF and SJC exchange their public blocks in iBGP. There isn't an iBGP session between SF and SJC to LA. We would would like to place our public IP blocks into iBGP with LA and use the 2gig long haul as a backup path for critical traffic destined for the Internet.(Only certain prefixes originated from each egress point will be announced out the opposite egress point; Appropriately locally-pref down inside our common transit ASN) Using only one assigned ASN is this a good idea? Is our IGP setup foobared (I've been mulling around possible changing the IGP design)? I can think of a problem or two this IGP design might cause us but it's a huge change on our part if we do it. The egress points are not DFZs, so if either the 10gig or 2gig link go down the default route can be taken to reach the public blocks in either of the three regions. Thanks

1 0

RE: spamhaus drop list
by Michiel Klaver 17 Jun '09

17 Jun '09

Well, there is always the bogon-list from Team Cymru http://www.cymru.com/Documents/bogon-bn-agg.txt And the bogon-list from BGPmon http://bgpmon.net/showbogons.php?inet=4&global=yes&private=yes Both containing prefixes that should not be announced on the internet, but often used by spammers trying to deliver their content. -------- Original message -------- Subject: RE: spamhaus drop list Date: Tue, 16 Jun 2009 14:00:51 -0400 From: Quinn Mahoney <quinn(a)activehost.com> To: <nanog(a)nanog.org> > Is there a competing droplist, that can be compared against > Spamhaus's droplist? That seems like an extraordinary claim, > so I'm not satisfied with the evidence provided. Is this not > the best droplist? -- With kind regards, Michiel Klaver BA.ict GrafiX Internet B.V. Stationsplein 20 2907 MJ Capelle aan den IJssel The Netherlands Web: http://grafix.nl/ Tel: +31-(0)10-2640210 Fax: +31-(0)10-2640211 Providing high-end professional internet services at our privately owned net-neutral in-house Data Center Facilities in Capelle aan den IJssel and Alphen aan den Rijn. Connected at TeleCityRedbus2 (Amsterdam) and Spaanse Kubus (Rotterdam).

4 4

Verio taking twitter down during Iran Election Riots?
by Erik Fichtner 17 Jun '09

17 Jun '09

http://status.twitter.com/post/124145031/maintenance-window-tonight-9-45p-p… Am I reading that right? Is someone at Verio seriously going to take twitter out for 90 minutes at 9am in Tehran?

15 19

Hotmail Postmaster
by Bill Blackford 17 Jun '09

17 Jun '09

Can someone from Hotmail contact me off list? Sorry for the SPAM posting, we've tried other methods. Thanks -b -- Bill Blackford Senior Network Engineer Technology Systems Group Northwest Regional ESD my /home away from home

1 0

[NANOG-announce] change in roles on the program committee
by Todd Underwood 16 Jun '09

16 Jun '09

today, at our lunchtime meeting, the nanog program committee selected a new chair, david meyer of cisco and university of oregon, and a new vice-chair, tom daly of dynamic network services. please join me in cogratulating them in person if you're here at nanog. for the past two years, ren provo has served as vice-chair of the program committee, a role that was basically created specifically for her. she has been critical in the development of the program committee into the open, active, and even somewhat-organized group that it is today. i'm proud to have worked with her on this project for the past two years and am extremely grateful for everything she has done. ren and i decided to resign our positions prior to the october meeting to ensure a smooth transition. we will both continue to serve as members of the program committee through the end of our current terms in october. NANOG has been getting better and better for the last several years. we're announcing locations much earlier and we're continuing to develop and experiment with the content to make it more relevant and more interesting for attendees. credit for these efforts certainly go to members of the steering and mailing list committees and to merit staff, but they also go to the program committee. the nanog program committee is full of some of the smartest, best people that i've ever worked with. it's a pleasure to be associated with them. eight (8) of the slots on the program committee will be opening up this october. if you'd like to work with other interesting people to make the nanog conference better, please consider submitting your name to be considered for one of these slots. the steering committee will announce details, or you can come see almost any member of the PC for more information. again, congratulations to dave and tom. cheers, todd underwood, outgoing chair for the program committee spots opening up in october _______________________________________________ NANOG-announce mailing list NANOG-announce(a)nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-announce

1 0

ADMIN: List FAQ/Monthly Post.
by NANOG Mail List Committee 15 Jun '09

15 Jun '09

This 100-line document contains 62% of what you need to know to avoid annoying 10,000 people in your email to the NANOG list. It also contains pointers to another 23%. Please take 5 minutes to read it before you post [again]. General Information =================== About NANOG: http://www.nanog.org/about/ NANOG News: http://www.nanog.org/ NANOG lists and AUP: http://www.nanog.org/mailinglist/ NANOG List FAQ: http://www.nanog.org/mailinglist/listfaqs/ To Subscribe or Unsubscribe from the list: http://mailman.nanog.org/mailman/listinfo/nanog To contact the list's admins: admins(a)nanog.org Posting Policy ============== The NANOG list has over 10,000 subscribers so it is very easy for a thread to have scores of posts while being off-topic and only of interest to only a small proportion of subscribers. Please consider before each post if your email will be of interest to the majority of members or might alternatively be emailed directly the people of interest or posted to another forum. Please read the FAQ and AUP policy before posting for more details. Especially the following are discouraged: * Is a certain site down? Other Outages not affecting half the Internet. Please use http://downforeveryoneorjustme.com/ or a similar site. Please post to the Outages mailing list: http://wiki.outages.org * Spam Please use SPAM-L - http://www.claws-and-paws.com/spam-l * Contacting People * http://puck.nether.net/netops/ * http://www.peeringdb.com * Please try other methods of contacting sites before you post to NANOG. Saying something like "I tried calling 213-555-3333 but no answer" shows you _have_ tried alternative methods first. * Political Issues * Topics such as ICANN policy, Government Policy or Law changes that do not have short term Operational impact should be avoided. * Operation topics with more specific lists * DNS - http://lists.oarci.net/mailman/listinfo/dns-operations * Email - http://www.mailop.org/ * NANOG Mailing list policy Please use the nanog-futures list or contact admins(a)nanog.org Please also avoid ================= * Sending posts to the list relevant to only one or two people on this list, such as tests or traceroutes in response to another post for comparison to those originally posted. * Jokes, Puns, amusing observations, spelling corrections. Other NANOG related lists ========================= * NANOG-futures - for discussion of the evolution of NANOG, including organizational structure, policies and procedures, and agendas for NANOG meetings. Such topics aren't appropriate for the main NANOG mailing list. http://mailman.nanog.org/mailman/listinfo/nanog-futures * nanog-attendee - For discussion of venue-specific issues relevant to attendees of the current NANOG physical meeting. http://mailman.nanog.org/mailman/listinfo/nanog-attendee * nanog-announce - For announcements of NANOG meetings an other Important NANOG related announcements. Low traffic and all posts are also sent to main list. http://mailman.nanog.org/mailman/listinfo/nanog-announce Other Mailing Lists =================== Information about related lists: http://www.nanog.org/mailinglist/listfaqs/otherlists.php

1 0