Re: Zayo zColo Xcon Pricing
Everything is negotiable. NRC on a cross-connect is ridiculous. The cost to run should be made up with the amount they're charging monthly. I wouldn't pay more than $200/mo for copper. Ian Mock On Wed, Mar 7, 2018 at 9:10 AM, James Laszko wrote: > One of our colo’s in San Diego was purchased by Zayo recently and I > requested a new copper Ethernet xcon to be placed. After a few days I > received a quote from my new rep quoting a MRC 3x what I’m currently paying > for existing xcon’s as well as a hefty NRC as well. Anyone have any > experience with this kind of thing? Anyone care to share what an average > copper xcon, single floor, meet-me-room to cage, Ethernet from carrier > circuit costs? (This xcon is approx 30 feet..) > > Thanks! > > James > > Sent from my iPad
RE: Google Captcha on web searches
We had an IP flagged where a new hire in our Marketing dept was doing some kind of SEO and was hammering Google's servers with API requests in the hundreds per minute. Google flagged it as malicious, got the captcha for all users behind that IP. After we found and stopped him, it returned to normal after a few hours. Ian Mock From: NANOG [nanog-boun...@nanog.org] on behalf of Mark Tinka [mark.ti...@seacom.mu] Sent: Wednesday, November 11, 2015 10:23 AM To: Christopher Morrow Cc: nanog list Subject: Re: Google Captcha on web searches On 11/Nov/15 18:15, Christopher Morrow wrote: > Yes, people also jump out of perfectly good airplanes... we can't fix > all the things :( > my point really is you assume some risk when you do odd things with > basic plumbing on the internet, if you don't actually know what you > are doing you're going to get burned. > > Quoted from Wikipedia: > "Dangers of Use[edit] > The dangers of using an unknown IP as a Smart DNS are similar to any > other rogue DNS server preforming DNS hijacking in that the user is > not aware which parts of his traffic are redirect and intercepted." No arguments from me there... Mark.
RE: APC vs TrippLite metered PDU's
+1 for APC, HTML based GUI, also supports major management protocols. Never had a problem with it. Ian Mock -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Aaron C. de Bruyn Sent: Tuesday, December 01, 2015 4:43 PM To: Dovid Bender Cc: NANOG Subject: Re: APC vs TrippLite metered PDU's If I recall correctly, they have an HTML-based GUI. I rarely use it. I mainly use SSH and SNMP which they support as well. -A On Tue, Dec 1, 2015 at 1:53 PM, Dovid Bender wrote: > Hello All, > > We currently use TrippLite and over all have been very happy with > their metered PDU's. When we first started out we had some minor > issues and their support went above and beyond. Lately the their Java > web interface has been becoming a real pain. More and more browsers > lock it by default and it takes a lot of work to get it working > correctly. Does anyone have any experience with APC? How are is > management of their devices and over all how do they operate? > > TIA. > > Dovid >
RE: Is it normal for your provider to withhold BGP peering info until the night of the cut?
Sounds like you need a little posturing with your sales team and account manager on the phone. Threaten to cancel the contract and site their lack of support and willingness to help you be successful. Say they're interfering with your company's ability to do business. If their sales team is worth anything they'll jump all over trying to fix the problem. If not, cancel the contract and move on. Do you and your company's mgmt want to deal with someone that unhelpful? Imagine what happens when you have a problem.. Ian Mock -Original Message- From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of c b Sent: Thursday, January 21, 2016 3:27 PM To: nanog@nanog.org Subject: Is it normal for your provider to withhold BGP peering info until the night of the cut? We have 4 full-peering providers between two data centers. Our accounting people did some shopping and found that there was a competitor who came in substantially lower this year and leadership decided to swap our most expensive circuit to the new carrier. (I don't know what etiquette is, so I won't name the carrier... but it's a well-known name) Anyways, we were preparing for the circuit cutover and asked for the BGP peering info up front like we normally do. This carrier said that they don't provide this until the night of the cut. Now, we've done this 5 or 6 times over the years with all of our other carriers and this is the first one to ever do this. We even escalated to our account manager and they still won't provide it. I know it's not a huge deal, but life is so much easier when you can prestage your cut and rollback commands. In fact, our internal Change Management process mandates peer review all proposed config changes and now we have to explain why some lines say TBD! Is this a common SOP nowadays? Anyone care to explain why they wouldn't just provide it ahead of time? Thanks in advance. CWB
