Re: mpls switches

[Mark Tinka]

On 7/Apr/16 02:02, Mike wrote:

> Hi,
>
> Im looking to deploy more mpls in my network. I like the Cisco
> 3600X series but the low density of 10g ports has me wanting to
> consider perhaps others. I would love a minimum of 4 10g ports but of
> course more is better. Cost would also be a factor. What are people
> using these days?

Cisco ASR920.

4x 10Gbps uplink ports + 24x customer-facing ports. All IP/MPLS capable.

Mark.

Re: mpls switches

[Baldur Norddahl]

ZTE 5950 serie MPLS routing switches are about 1500 to 3000 USD depending
on configuration. They have a 4x 10G subcard. The CLI is very Cisco like.

The ZTE 5960 has 32 or 64 x 10G but starts at 5k-6k.

Regards

Baldur
Den 7. apr. 2016 02.05 skrev "Mike" :

> Hi,
>
> Im looking to deploy more mpls in my network. I like the Cisco 3600X
> series but the low density of 10g ports has me wanting to consider perhaps
> others. I would love a minimum of 4 10g ports but of course more is better.
> Cost would also be a factor. What are people using these days?
>
> Thanks.
>
> Mike-
>

Re: mpls switches

[David Bass]

Interesting.  What SDN controller are you using?

Seems like quite a few are moving to white box switches...

> On Apr 6, 2016, at 9:53 PM, Todd Crane  wrote:
> 
> Edge-Core 5712-54X

Re: mpls switches

[Todd Crane]

Mike,

Nor sure how much you know about SDN or if you are in anywhere near being able 
to make the transition, but white-label switches may be a deciding factor for 
you. In fact you may be able to do it without SDN, but I cannot say for sure as 
we have ours configured in SDN mode. We use Edge-Core 5712-54X switches for our 
10G (48x 10G and 6x 40G) and I cannot recommend them enough. Combined with 
Picos from Pica8, we can do SDN/SD-WAN as well as MPLS at around 6,000 per 
switch plus maintenance. If you want more information or contacts, hit me up 
offline (or rather off the mailing list).

-Todd



> On Apr 6, 2016, at 5:02 PM, Mike  wrote:
> 
> Hi,
> 
>Im looking to deploy more mpls in my network. I like the Cisco 3600X 
> series but the low density of 10g ports has me wanting to consider perhaps 
> others. I would love a minimum of 4 10g ports but of course more is better. 
> Cost would also be a factor. What are people using these days?
> 
> Thanks.
> 
> Mike-



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Best practices for sending network maintenance notifications

[Chris Grundemann]

On Wed, Apr 6, 2016 at 3:05 PM, Hal Ponton  wrote:

> I think there was a BCP being worked on. I seem to recall it was being
> discussed as a Facebook group.


True.

https://www.facebook.com/groups/maintnote/

Currently under development, but fairly far along...

Cheers,
~Chris

-- 
@ChrisGrundemann
http://chrisgrundemann.com

mpls switches

[Mike]

Hi,

Im looking to deploy more mpls in my network. I like the Cisco 
3600X series but the low density of 10g ports has me wanting to consider 
perhaps others. I would love a minimum of 4 10g ports but of course more 
is better. Cost would also be a factor. What are people using these days?


Thanks.

Mike-

Re: Best practices for sending network maintenance notifications

[Robert Drake]

I've been on hold a few times with some companies that had great 80's 
music.  I almost asked them to put me back on hold when they finally 
took me off.  Sometimes it's a party when one of the people on the call 
hits the hold button, it depends on how bad the outage is :)



On 4/6/2016 4:56 PM, Ray Orsini wrote:

"The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hold
button."


Now that you've said it it seems so obvious. But, honestly I'd never thought
it until right now. Thanks!

Regards,
Ray Orsini – CEO
Orsini IT, LLC – Technology Consultants
VOICE DATA  BANDWIDTH  SECURITY  SUPPORT
P: 305.967.6756 x1009   E: r...@orsiniit.com   TF: 844.OIT.VOIP
7900 NW 155th Street, Suite 103, Miami Lakes, FL 33016
http://www.orsiniit.com | View My Calendar | View/Pay Your Invoices | View
Your Tickets

Re: Best practices for sending network maintenance notifications

[Eric Kuhnke]

And some genius at an ISP's NOC has put
rick_asley_never_gonna_give_you_up.mp3 in the their hold queue music
rotation list.

On Wed, Apr 6, 2016 at 1:56 PM, Ray Orsini  wrote:

> "The other "don't do that" is never configure Music on Hold for any NOC/SOC
> lines.  Few things are more annoying than a eight hour trouble shooting
> conference bridge, and one of the dozen NOC/SOCs on the bridge hits the
> Hold
> button."
>
>
> Now that you've said it it seems so obvious. But, honestly I'd never
> thought
> it until right now. Thanks!
>
> Regards,
> Ray Orsini – CEO
> Orsini IT, LLC – Technology Consultants
> VOICE DATA  BANDWIDTH  SECURITY  SUPPORT
> P: 305.967.6756 x1009   E: r...@orsiniit.com   TF: 844.OIT.VOIP
> 7900 NW 155th Street, Suite 103, Miami Lakes, FL 33016
> http://www.orsiniit.com | View My Calendar | View/Pay Your Invoices | View
> Your Tickets
>
>
>
>
> -Original Message-
> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Sean Donelan
> Sent: Wednesday, April 6, 2016 4:53 PM
> To: nanog@nanog.org
> Subject: Re: Best practices for sending network maintenance notifications
>
> On Wed, 6 Apr 2016, Dan Mahoney, System Admin wrote:
> > My question for the group -- does anyone know if there's a "best
> > practices"
> > for sending maint notifications like this?  An RFC sort of thing?
>
> It falls in the category of "Doctor, it hurts when I do this.  Don't do
> that."  Even the most dense CSR managers figure it out after a few
> attempts.
>
> The other "don't do that" is never configure Music on Hold for any NOC/SOC
> lines.  Few things are more annoying than a eight hour trouble shooting
> conference bridge, and one of the dozen NOC/SOCs on the bridge hits the
> Hold
> button.
>

RE: Best practices for sending network maintenance notifications

[Scott Weeks]

--- r...@orsiniit.com wrote:
From: Ray Orsini 

"The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hold
button."

Now that you've said it it seems so obvious. But, honestly I'd never thought
it until right now. Thanks!
---


It only takes one time on a hectic multi-party call to
learn this one.  It's painful and at the worst possible 
time, especially if they left the room and no one can 
be contacted to get it turned off.

scott

RE: Best practices for sending network maintenance notifications

[Ray Orsini]

"The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hold
button."


Now that you've said it it seems so obvious. But, honestly I'd never thought
it until right now. Thanks!

Regards,
Ray Orsini – CEO
Orsini IT, LLC – Technology Consultants
VOICE DATA  BANDWIDTH  SECURITY  SUPPORT
P: 305.967.6756 x1009   E: r...@orsiniit.com   TF: 844.OIT.VOIP
7900 NW 155th Street, Suite 103, Miami Lakes, FL 33016
http://www.orsiniit.com | View My Calendar | View/Pay Your Invoices | View
Your Tickets




-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Sean Donelan
Sent: Wednesday, April 6, 2016 4:53 PM
To: nanog@nanog.org
Subject: Re: Best practices for sending network maintenance notifications

On Wed, 6 Apr 2016, Dan Mahoney, System Admin wrote:
> My question for the group -- does anyone know if there's a "best
> practices"
> for sending maint notifications like this?  An RFC sort of thing?

It falls in the category of "Doctor, it hurts when I do this.  Don't do
that."  Even the most dense CSR managers figure it out after a few attempts.

The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting
conference bridge, and one of the dozen NOC/SOCs on the bridge hits the Hold
button.

Re: Best practices for sending network maintenance notifications

[Sean Donelan]

On Wed, 6 Apr 2016, Dan Mahoney, System Admin wrote:
My question for the group -- does anyone know if there's a "best practices" 
for sending maint notifications like this?  An RFC sort of thing?


It falls in the category of "Doctor, it hurts when I do this.  Don't do 
that."  Even the most dense CSR managers figure it out after a few 
attempts.


The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting 
conference bridge, and one of the dozen NOC/SOCs on the bridge hits

the Hold button.

Re: Best practices for sending network maintenance notifications

[joel jaeggli]

On 4/6/16 3:56 PM, Dan Mahoney, System Admin wrote:
> All,
> 
> We recently, at $dayjob, had one of our peers (at Symantec)  send out a
> network maint notification, putting 70 addresses in the "To:" field,
> rather than using BCC or the exchange's mailing list.
> 
> Naturally, when you mail 30 addresses, of the forms peering@ and noc@
> various organizations, you're likely to hit at least a few
> autoresponders and ticket systems...
> 
> And at least one or two of those autoresponders are of course brainded
> and configured to reply-all.  (In this case, Verizon's ServiceNow setup
> was such a stupid responder).  And that made things fun in our own
> ticket system, as our RT setup happily created a bunch of tickets.
> 
> My question for the group -- does anyone know if there's a "best
> practices" for sending maint notifications like this?  An RFC sort of
> thing?


In general I'd push for a little automation for the sending of
notifications as reducing the likelihood of mishap.

Targeting bcc is nice, but so does simply generating a message for each
peer precludes this. we store contact information which bgp neighbor
parameters in our config generation.

> While it would define a social protocol, rather than a truly technical
> one, if there's not such a document, it seems like it could useful.  And
> once such a thing exists, exchanges could of course helpfully point
> their members AT it (for both their humans, and ticket systems, to follow).
> 
> -Dan
> 




signature.asc
Description: OpenPGP digital signature

Re: Best practices for sending network maintenance notifications

[Michael J Wise]

> I think there was a BCP being worked on. I seem to recall it was being
> discussed as a Facebook group. But there's no RFC, at least that I know
> of.

And additionally, putting the recipients in the To: line sounds like a
really bad idea. Sharing PII without permission and stuff like that.

Make absolutely certain that all the SPF, DKIM and DMARC stuff is perfect.
Make sure that any links are to the corporate domain... always.

You want a neutral, paranoid 3rd party who is receiving the notice to be
absolutely convinced of its Bona Fides. Do not suppose that your abundance
of Sincerity excuses sloppiness. It won't. :(

>
> Regards,
>
> Hal Ponton
>
> Senior Network Engineer
>
> Buzcom / FibreWiFi
>
> Tel: 07429 979 217
> Email: h...@buzcom.net
>
>> On 6 Apr 2016, at 19:56, Dan Mahoney, System Admin
>>  wrote:
>>
>> All,
>>
>> We recently, at $dayjob, had one of our peers (at Symantec)  send out a
>> network maint notification, putting 70 addresses in the "To:" field,
>> rather than using BCC or the exchange's mailing list.
>>
>> Naturally, when you mail 30 addresses, of the forms peering@ and noc@
>> various organizations, you're likely to hit at least a few
>> autoresponders and ticket systems...
>>
>> And at least one or two of those autoresponders are of course brainded
>> and configured to reply-all.  (In this case, Verizon's ServiceNow setup
>> was such a stupid responder).  And that made things fun in our own
>> ticket system, as our RT setup happily created a bunch of tickets.
>>
>> My question for the group -- does anyone know if there's a "best
>> practices" for sending maint notifications like this?  An RFC sort of
>> thing?
>>
>> While it would define a social protocol, rather than a truly technical
>> one, if there's not such a document, it seems like it could useful.  And
>> once such a thing exists, exchanges could of course helpfully point
>> their members AT it (for both their humans, and ticket systems, to
>> follow).
>>
>> -Dan
>>
>> --
>>
>
>


Aloha mai Nai`a.
-- 
" So this is how Liberty dies ...  http://kapu.net/~mjwise/
" To Thunderous Applause.

Re: Best practices for sending network maintenance notifications

[Hal Ponton]

I think there was a BCP being worked on. I seem to recall it was being 
discussed as a Facebook group. But there's no RFC, at least that I know of.

Regards,

Hal Ponton

Senior Network Engineer

Buzcom / FibreWiFi

Tel: 07429 979 217
Email: h...@buzcom.net

> On 6 Apr 2016, at 19:56, Dan Mahoney, System Admin  
> wrote:
> 
> All,
> 
> We recently, at $dayjob, had one of our peers (at Symantec)  send out a 
> network maint notification, putting 70 addresses in the "To:" field, rather 
> than using BCC or the exchange's mailing list.
> 
> Naturally, when you mail 30 addresses, of the forms peering@ and noc@ various 
> organizations, you're likely to hit at least a few autoresponders and ticket 
> systems...
> 
> And at least one or two of those autoresponders are of course brainded and 
> configured to reply-all.  (In this case, Verizon's ServiceNow setup was such 
> a stupid responder).  And that made things fun in our own ticket system, as 
> our RT setup happily created a bunch of tickets.
> 
> My question for the group -- does anyone know if there's a "best practices" 
> for sending maint notifications like this?  An RFC sort of thing?
> 
> While it would define a social protocol, rather than a truly technical one, 
> if there's not such a document, it seems like it could useful.  And once such 
> a thing exists, exchanges could of course helpfully point their members AT it 
> (for both their humans, and ticket systems, to follow).
> 
> -Dan
> 
> -- 
> 

Best practices for sending network maintenance notifications

[Dan Mahoney, System Admin]

All,

We recently, at $dayjob, had one of our peers (at Symantec)  send out a 
network maint notification, putting 70 addresses in the "To:" field, 
rather than using BCC or the exchange's mailing list.


Naturally, when you mail 30 addresses, of the forms peering@ and noc@ 
various organizations, you're likely to hit at least a few 
autoresponders and ticket systems...


And at least one or two of those autoresponders are of course brainded and 
configured to reply-all.  (In this case, Verizon's ServiceNow setup was 
such a stupid responder).  And that made things fun in our own ticket 
system, as our RT setup happily created a bunch of tickets.


My question for the group -- does anyone know if there's a "best 
practices" for sending maint notifications like this?  An RFC sort of 
thing?


While it would define a social protocol, rather than a truly technical 
one, if there's not such a document, it seems like it could useful.  And 
once such a thing exists, exchanges could of course helpfully point their 
members AT it (for both their humans, and ticket systems, to follow).


-Dan

--

GCN / DigiCell or Columbus Communications ?

[Faisal Imtiaz]

Hello,

We are looking for 10g wave between Puerto Rico to Trinidad (Maparippe).

Please contact me off list.

Thanks.

Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232

Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net

gmail for business email contact - server blacklisted

[Joseph Jenkins]

Anyone on here from gmail that can help with an issue. One of your email
servers has been blacklisted by spam cop and is still in rotation. It's
causing individual senders to be blocked on our side. If possible can you
remove that server from rotation?

IP is: 209.85.161.176

WEBCAST TODAY: NEDASNYC In-Building Wireless Summit

[Joly MacFie]

This is the second year I've streamed the NEDAS NYC conference. It's a very
high quality event that gets into nuts and bolts of bringing connectivity
to mobile devices in dense environments. Last year one panel
 was a
fascinating dialog on how best to bring wireless to NYC's subway. The first
panel today, already underway, is about how to bring "carrier-grade" upload
capability to stadiums. Speakers include engineers who have done the
Superbowl and the Olympics.


*Agenda: 
https://www.nedas.com/events/nedas-spring-in-building-wireless-summit-nyc
Webcast:
https://new.livestream.com/internetsociety/nedasnyc2016
*





-- 
---
Joly MacFie  218 565 9365 Skype:punkcast
--
-