VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
January 2013
- 57 participants
- 176 messages
Level 3 On the west coast
by mjacobs76@gmail.com
Any one seeing packet loss or other issue on the west coast with Level 3?
Jan. 22, 2013
Pre-deployment/upgrade and Constant Quality Monitoring
by carlos@televolve.com
+1
On Mon, Jan 21, 2013 at 11:36 AM, Hiers, David <David.Hiers at adp.com> wrote:
> One caveat...
>
> Packet stats are great, as far as they go. Some of our worst audio
> quality problems have occurred on networks that had perfect packet stats.
>
>
> David
>
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
> On Behalf Of Ryan Delgrosso
> Sent: Sunday, January 20, 2013 11:45
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] Pre-deployment/upgrade and Constant Quality
> Monitoring
>
> Ill second the AcmePacket QOS solution. We store QOS stats historically in
> our CDR database per call. It makes reporting for network management
> purposes easy, as well as being able to push this data down to CSR's on the
> front lines to help customers troubleshoot. It does create a bit of
> overhead from a CDR storage perspective but the trade-off is well worth it.
>
> The only thing I have not yet come up with a good solution for is
> measuring audio quality where the far end TDM connection (not on my
> network) is the problem, since packet stats will look clean but the audio
> quality will still be poor due to problems not occurring on the packet
> network.
>
>
> On 01/20/2013 10:59 AM, Jason L. Nesheim wrote:
> > IxLoad is a great tool. However, I've never found it well suited for
> post deployment quality monitoring as it's primarily an engineering R&D
> test tool. Great for lab environment testing or for troubleshooting a
> specific load based problem in being experienced but it's not something you
> can move around much or deploy to a customer site easily.
> >
> > For post deployment quality monitoring I've used both Empirix XMS and
> the Acme Packet SBC QoS functionality in different ways with good success.
> Emprix is a great tool for overall network quality measurements and
> signaling data retention and allows a moderately skilled customer service
> team investigate call quality issues. On the Acme side, the CDR feed via
> radius or flat file with the end to end QoS statistics is very useful in
> building reports, validating SLA compliance, and tasks of this sort. In my
> case I used a custom FreeRadius perl module which did some data parsing and
> fed that into a database in real time for both Acme and Broadworks CDRs.
> This provided a good trap and trace tool as well as the database was near
> real time.
> >
> > My two cents at least...
> >
> > --
> > Jason Nesheim
> > 702-885-0815
> >
> > ----- Original Message -----
> > From: ghenry at suretec.co.uk
> > To: voiceops at voiceops.org
> > Sent: Sunday, January 20, 2013 12:06:35 PM
> > Subject: [VoiceOps] Pre-deployment/upgrade and Constant Quality
> > Monitoring
> >
> > Hi all,
> >
> > I was wondering what commercial product folks are using for an
> > automated test suite pre deployment and before upgrade roll outs
> >
> > I'm also looking for constant monitoring of things like call setup
> delays, RTP issues, Jitter, MOS,PESQ Echo etc. other than service status
> checking, for us and to go on our public service status pages.
> >
> > Had a call about IxLoad already and interested in what others do.
> >
> > Cheers.
> >
> > --
> > Kind Regards,
> >
> > Gavin Henry.
> > Managing Director.
> >
> > T +44 (0) 1224 279484
> > M +44 (0) 7930 323266
> > F +44 (0) 1224 824887
> > E ghenry at suretec.co.uk
> >
> > Open Source. Open Solutions(tm).
> >
> > http://www.suretecsystems.com/
> >
> > Suretec Systems is a limited company registered in Scotland.
> > Registered
> > number: SC258005. Registered office: 24 Cormack Park, Rothienorman,
> > Inverurie, Aberdeenshire, AB51 8GL.
> >
> > Subject to disclaimer at http://www.suretecgroup.com/disclaimer.html
> >
> > Do you know we have our own VoIP provider called SureVoIP? See
> > http://www.surevoip.co.uk
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> e-mail and delete the message and any attachments from your system.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 21, 2013
Pre-deployment/upgrade and Constant Quality Monitoring
by David.Hiers@adp.com
One caveat...
Packet stats are great, as far as they go. Some of our worst audio quality problems have occurred on networks that had perfect packet stats.
David
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ryan Delgrosso
Sent: Sunday, January 20, 2013 11:45
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] Pre-deployment/upgrade and Constant Quality Monitoring
Ill second the AcmePacket QOS solution. We store QOS stats historically in our CDR database per call. It makes reporting for network management purposes easy, as well as being able to push this data down to CSR's on the front lines to help customers troubleshoot. It does create a bit of overhead from a CDR storage perspective but the trade-off is well worth it.
The only thing I have not yet come up with a good solution for is measuring audio quality where the far end TDM connection (not on my
network) is the problem, since packet stats will look clean but the audio quality will still be poor due to problems not occurring on the packet network.
On 01/20/2013 10:59 AM, Jason L. Nesheim wrote:
> IxLoad is a great tool. However, I've never found it well suited for post deployment quality monitoring as it's primarily an engineering R&D test tool. Great for lab environment testing or for troubleshooting a specific load based problem in being experienced but it's not something you can move around much or deploy to a customer site easily.
>
> For post deployment quality monitoring I've used both Empirix XMS and the Acme Packet SBC QoS functionality in different ways with good success. Emprix is a great tool for overall network quality measurements and signaling data retention and allows a moderately skilled customer service team investigate call quality issues. On the Acme side, the CDR feed via radius or flat file with the end to end QoS statistics is very useful in building reports, validating SLA compliance, and tasks of this sort. In my case I used a custom FreeRadius perl module which did some data parsing and fed that into a database in real time for both Acme and Broadworks CDRs. This provided a good trap and trace tool as well as the database was near real time.
>
> My two cents at least...
>
> --
> Jason Nesheim
> 702-885-0815
>
> ----- Original Message -----
> From: ghenry at suretec.co.uk
> To: voiceops at voiceops.org
> Sent: Sunday, January 20, 2013 12:06:35 PM
> Subject: [VoiceOps] Pre-deployment/upgrade and Constant Quality
> Monitoring
>
> Hi all,
>
> I was wondering what commercial product folks are using for an
> automated test suite pre deployment and before upgrade roll outs
>
> I'm also looking for constant monitoring of things like call setup delays, RTP issues, Jitter, MOS,PESQ Echo etc. other than service status checking, for us and to go on our public service status pages.
>
> Had a call about IxLoad already and interested in what others do.
>
> Cheers.
>
> --
> Kind Regards,
>
> Gavin Henry.
> Managing Director.
>
> T +44 (0) 1224 279484
> M +44 (0) 7930 323266
> F +44 (0) 1224 824887
> E ghenry at suretec.co.uk
>
> Open Source. Open Solutions(tm).
>
> http://www.suretecsystems.com/
>
> Suretec Systems is a limited company registered in Scotland.
> Registered
> number: SC258005. Registered office: 24 Cormack Park, Rothienorman,
> Inverurie, Aberdeenshire, AB51 8GL.
>
> Subject to disclaimer at http://www.suretecgroup.com/disclaimer.html
>
> Do you know we have our own VoIP provider called SureVoIP? See
> http://www.surevoip.co.uk
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Jan. 21, 2013
IPSec VPN server
by jjackson@aninetworks.net
We too like the cisco ASA platforms for this function. Unfortunately some orgs like Sprint require VPN parameters that the ASA does not support. Just ran into this issue and had to deploy a 1700 router just for their tunnel configuration. Sprint drives me nuts.
Joseph
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Hiers, David
Sent: Monday, January 21, 2013 12:30 PM
To: Paul Timmins; Eric Wieling
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] IPSec VPN server
We like Cisco ASAs for this role.
David
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Sunday, January 20, 2013 19:53
To: Eric Wieling
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] IPSec VPN server
Cisco router with redundant power supply. Running recent versions of IOS.
On Jan 20, 2013, at 22:48 , Eric Wieling <EWieling at nyigc.com> wrote:
> We are looking for something which crashes LESS than once per year. "had a few stability problems" doesn't give me a warm fuzzy feeling about the product. Configuration management is nice, but how important is it for a device which is never modified and has only one tunnel?
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Anderson
> Sent: Sunday, January 20, 2013 4:10 PM
> To: 'Faisal at snappydsl.net'; 'voiceops at voiceops.org'
> Subject: Re: [VoiceOps] IPSec VPN server
>
> +1 for MikroTik RouterOS. It has admittedly had a few stability issues in past versions, but is getting better all the time. The feature set you get for the price is insane, and device configuration and management is fantastic.
>
> Out of curiosity, what are you currently using, and what is your budget like for its replacement?
>
> MikroTik makes the RB1100AHx2 for $500, which is a dual-core PowerPC product with encryption/IPsec acceleration built-into the CPU; they claim you can forward 800+Mbit/s of IPsec traffic through the thing. (I haven't verified this.) They also just recently came out with a series of products based on Tilera's TILE-Gx multicore CPUs, with models in the $650-1000 range. For something a little cheaper, I can highly recommend the RB450G; the board itself is $100, and you can find places that will sell you a completely assembled kit with case + power supply for ~$130. No HW crypto, but I've heard of people doing ~20Mbit/s of IPsec through it.
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Faisal Imtiaz
> Sent: Sunday, January 20, 2013 10:49 AM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] IPSec VPN server
>
> How about a Mikrotik Router ... ?
>
> Faisal Imtiaz
> Snappy Internet & Telecom
>
> On 1/20/2013 1:05 PM, Eric Wieling wrote:
>> We currently have SIP service with VZB, they require signaling go over an IPSec VPN tunnel. Our current VPN box (which is somewhat old) crashes about once per year and we would like to replace it with something which is more reliable.
>>
>> Can anyone recommend rock solid boxes which can handle 10Mbps of IPSec traffic? Our current usage is about 1/2 of that, but I want room to grow.
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 21, 2013
IPSec VPN server
by David.Hiers@adp.com
We like Cisco ASAs for this role.
David
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Sunday, January 20, 2013 19:53
To: Eric Wieling
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] IPSec VPN server
Cisco router with redundant power supply. Running recent versions of IOS.
On Jan 20, 2013, at 22:48 , Eric Wieling <EWieling at nyigc.com> wrote:
> We are looking for something which crashes LESS than once per year. "had a few stability problems" doesn't give me a warm fuzzy feeling about the product. Configuration management is nice, but how important is it for a device which is never modified and has only one tunnel?
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Anderson
> Sent: Sunday, January 20, 2013 4:10 PM
> To: 'Faisal at snappydsl.net'; 'voiceops at voiceops.org'
> Subject: Re: [VoiceOps] IPSec VPN server
>
> +1 for MikroTik RouterOS. It has admittedly had a few stability issues in past versions, but is getting better all the time. The feature set you get for the price is insane, and device configuration and management is fantastic.
>
> Out of curiosity, what are you currently using, and what is your budget like for its replacement?
>
> MikroTik makes the RB1100AHx2 for $500, which is a dual-core PowerPC product with encryption/IPsec acceleration built-into the CPU; they claim you can forward 800+Mbit/s of IPsec traffic through the thing. (I haven't verified this.) They also just recently came out with a series of products based on Tilera's TILE-Gx multicore CPUs, with models in the $650-1000 range. For something a little cheaper, I can highly recommend the RB450G; the board itself is $100, and you can find places that will sell you a completely assembled kit with case + power supply for ~$130. No HW crypto, but I've heard of people doing ~20Mbit/s of IPsec through it.
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Faisal Imtiaz
> Sent: Sunday, January 20, 2013 10:49 AM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] IPSec VPN server
>
> How about a Mikrotik Router ... ?
>
> Faisal Imtiaz
> Snappy Internet & Telecom
>
> On 1/20/2013 1:05 PM, Eric Wieling wrote:
>> We currently have SIP service with VZB, they require signaling go over an IPSec VPN tunnel. Our current VPN box (which is somewhat old) crashes about once per year and we would like to replace it with something which is more reliable.
>>
>> Can anyone recommend rock solid boxes which can handle 10Mbps of IPSec traffic? Our current usage is about 1/2 of that, but I want room to grow.
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Jan. 21, 2013
911 address policy for company phones at home
by marylou@backuptelecom.com
Thanks Frank....good to know! I'm sure I just wasn't searching with the
right key words to find that. I wonder if they offer it as a stand alone
product or you can only get it when you sign up for their VOIP 911 service.
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001
-----Original Message-----
From: Frank Bulk [mailto:frnkblk at iname.com]
Sent: Saturday, January 19, 2013 7:10 PM
To: 'Mary Lou Carey'; 'Jay Hennigan'; 'VoiceOps'
Subject: RE: [VoiceOps] 911 address policy for company phones at home
It looks like there are vendors that make it possible for PSAPs to access
near-realtime info:
http://www1.911enable.com/resource-center/faq (see "What is a VoIP
Positioning Center?")
Frank
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Mary Lou Carey
Sent: Saturday, January 19, 2013 8:17 AM
To: 'Jay Hennigan'; 'VoiceOps'
Subject: Re: [VoiceOps] 911 address policy for company phones at home
PBXs can associate a single line for one location or have multiple lines,
one for each location so that there is an address in the ALI database for
each location. These lines are all fixed though so it's very different from
VOIP because the end user can move their phone to any location that has
internet access and use it without the switch being re-programmed. That's
why there is a requirement for the CLEC to offer a way for the customer to
update their information in the ALI database themselves.
Someone asked me about who provides the VOIP ALI update solution and I
couldn't find a provider, but in researching it I did find that there
appears to be an issue with this method because the ALI database doesn't
update in real time and since users could plug their phone in and update the
address, it didn't mean that the ALI database identified the location
correctly. YMAX commented to the FCC in November 2011 (see the link below)
that they had a solution that could work. It involved attaching a GSM
cellular transceiver to their MagicJack device so the location could be
identified but it also relied on having some type of database with customer
locations to help it identify which PSAP needed to be contacted so it
doesn't appear that is totally thought out either. It appears to me that
even though there are some requirements that the FCC put out about updating
the ALI database, the details of exactly how that will work aren't totally
worked out because of the issue with the ALI database. To me......that seems
like a great business opportunity for someone! If you could figure out how
to get a VOIP phone to automatically identify the exact location of the
phone whenever its plugged in and transmit that location to a VOIP ALI
database (which you'd need to create), then you could sell the service to
both PSAPs AND VOIP providers!
http://apps.fcc.gov/ecfs/document/view;jsessionid=c1M1QZvLvW9XfyYDpTwlMGN1QK
T7yhs21npc4ThYvwR61R6JK4yv!-56284754!-224088840?id=7021744691
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jay Hennigan
Sent: Friday, January 18, 2013 6:33 PM
To: VoiceOps
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On 1/18/13 3:46 PM, Mike Ray wrote:
> The difference here is the demarcation point. If you're handing off
> analog lines, there are two important differences:
>
> 1. You're not providing the PBX functionality as part of the telephone
> service and, 2. You're using a technology that is incapable of sending
> a different ANI than what's in your switch for each line.
An extension-only SIP phone doesn't have a unique ANI.
> So the requirement here is that the e911 ALI address must match the
> physical location where you have those lines installed.
But there are no "lines" for DID-less extensions or for that matter an
"installation" in the case of softphones.
The company HQ where the main ANI is answered is the ALI address. Call it
and talk to the receptionist. Drive there in a police car and visit the
same receptionist.
> If you are looking to protect yourself from the customer moving to a
> new location, ATA, PBX and all, you just use a contract provision
> requiring them to notify you of address changes. You could also
> require them to have you move the service to the new location for more
security there.
Yes, and you should.
> So, different animal that the hosted PBX question...
ATA, PBX and all is indeed a different animal than an extension-only remote
phone.
The problem, and I don't know if there is a full solution, is that PSTN
telephone numbers have always been used to identify the destination of a
call. 9-1-1 assumes that this identifier of a destination positively and
unequivocally also identifies the origin.
Think in terms of laptops with softphones. There is no way to make that
work with the present 9-1-1 infrastructure.
--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse
Internet Service - http://www.impulse.net/ Your local telephone and
internet company - 805 884-6323 - WB6RDV
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 21, 2013
IPSec VPN server
by EWieling@nyigc.com
-----Original Message-----
From: Nathan Anderson [mailto:nathana at fsr.com]
Sent: Monday, January 21, 2013 3:43 AM
To: 'Jimmy Hess'; Eric Wieling
Cc: 'voiceops at voiceops.org'
Subject: RE: [VoiceOps] IPSec VPN server
We also still have not gotten an answer from Eric on what product he is currently using that is so unstable that it has to be rebooted once annually, or even what class of product it is. There are days where I would kill for products that only had to be rebooted once a year...again, not excusing those that do need that reboot, but just trying to put things in perspective a little. :-) As Jimmy I believe accurately pointed out, if that kind of uptime is important to someone, then you need to be investing in a high-availability/hardware-redundancy/failover-pair solution of some kind.
===========================
Juniper Netscreen 25
Jan. 21, 2013
Pre-deployment/upgrade and Constant Quality Monitoring
by lakmalfdo@ymail.com
You may check Arptel, www.arptel.com. ?They are having a system to test your?requirements.
Best Regards,
Lakmal Fernando?
Jan. 21, 2013
IPSec VPN server
by nathana@fsr.com
Hear, hear. Surely I'm not the only one who has read through Cisco errata for kicks and thought to myself after reading some of them, "how in the heck did this manage to get past QA?" (Speaking of...some of you may have seen this before, but: http://etherealmind.com/cisco-culture-of-buggy-code-and-the-failure-of-the-…)
As a former boss of mine once told me, "all hardware sucks, all software sucks...some just suck less than others."
You have to bear in mind that my history with MikroTik goes back to the 2.x days. Most of the bugs we would run into were eventually traced to code that they didn't even have a hand in engineering (e.g., Quagga), and most of that stuff has since been replaced with new implementations of the same features written by them from scratch. That's not to say that their own code is perfect, 'cause it isn't, but it is head-and-shoulders above the stuff they were using befor (there were some dark days a few years back where I was ready to swear off the product for good). I would say that most of the time, the routers we still encounter the occasional problem on are the ones where multiple features are being heavily used: route exchanges via BGP and OSPF, MPLS LDP exchanges, a bunch of VPLS tunnels, several hundred simultaneous PPP sessions, a complex queue tree plus individual rate-limiting queues for each PPP tunnel... I'm not saying this to excuse it when we do have problems that are obviously software-related, but rather to illustrate the point that based on my past experience, you are much less likely to encounter a problem if you are only using a single feature (say, IPsec) or a small handful of features.
As an example, the MikroTik router doing double-duty as the gateway to both our office and one of our NOCs -- which itself is hardly simplistically configured -- has been up for 300 days now, and the last time it was rebooted was so that we could perform a software upgrade to fix a sporadic problem we were having with random OSPF neighbor adjacency resets (and the upgrade did fix it).
We also still have not gotten an answer from Eric on what product he is currently using that is so unstable that it has to be rebooted once annually, or even what class of product it is. There are days where I would kill for products that only had to be rebooted once a year...again, not excusing those that do need that reboot, but just trying to put things in perspective a little. :-) As Jimmy I believe accurately pointed out, if that kind of uptime is important to someone, then you need to be investing in a high-availability/hardware-redundancy/failover-pair solution of some kind.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jimmy Hess
Sent: Sunday, January 20, 2013 9:37 PM
To: Eric Wieling
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] IPSec VPN server
On 1/20/13, Eric Wieling <EWieling at nyigc.com> wrote:
There are very few networking products in existence that haven't had
some kind of software stability problem or bad hardware design
problem at one time or another; so don't mark down earlier version
experience against MicroTik.
I can tell you with certainty, that PIX515s crash too, and in certain
configurations have very serious stability issues in certain
situations; so do ASAs, and just about any router from any vendor.
There aren't many non-trivial devices you can't say that kind of thing
about. Manufacturer instructions, and running appropriate firmware
versions, are very important.
If it's a requirement that you have less than 1 crash a year, then
that would most likely require something that can be used in a
failover pair; possibly two of those PIX 51xx s.
Otherwise, there is really no way on earth to have a significant
level of assurance of availability.
If you don't require an extensive feature set; usually using the
simplest device and simplest software possible, will give you fewer
things that can break.
Using devices with more complex elements, like general purpose
computers with spinning disks, would be asking for trouble, even
though off the shelf servers that can run Linux are cheap.
Make sure the configuration will be simple, a common configuration for
the device, and fully supported and warranted by the manufacturer.
I definitely do expect the mature appliance products on stable
codebases, which have more engineering into them, when used in fully
supported configurations to be on average a lot more reliable than
some MicroTik components -- but the fact of the matter is you might
have the bad luck of the draw, in regards to hardware, even with a
competitors' device costing 100x as much.
Regardless of manufacturer, some percentage of the components will
have defects, it could be a hardware defect so minor that it just
causes on average 2 crashes a year.
> We are looking for something which crashes LESS than once per year. "had a
> few stability problems" doesn't give me a warm fuzzy feeling about the
> product. Configuration management is nice, but how important is it for a
> device which is never modified and has only one tunnel?
--
-JH
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 21, 2013
IPSec VPN server
by mysidia@gmail.com
On 1/20/13, Eric Wieling <EWieling at nyigc.com> wrote:
There are very few networking products in existence that haven't had
some kind of software stability problem or bad hardware design
problem at one time or another; so don't mark down earlier version
experience against MicroTik.
I can tell you with certainty, that PIX515s crash too, and in certain
configurations have very serious stability issues in certain
situations; so do ASAs, and just about any router from any vendor.
There aren't many non-trivial devices you can't say that kind of thing
about. Manufacturer instructions, and running appropriate firmware
versions, are very important.
If it's a requirement that you have less than 1 crash a year, then
that would most likely require something that can be used in a
failover pair; possibly two of those PIX 51xx s.
Otherwise, there is really no way on earth to have a significant
level of assurance of availability.
If you don't require an extensive feature set; usually using the
simplest device and simplest software possible, will give you fewer
things that can break.
Using devices with more complex elements, like general purpose
computers with spinning disks, would be asking for trouble, even
though off the shelf servers that can run Linux are cheap.
Make sure the configuration will be simple, a common configuration for
the device, and fully supported and warranted by the manufacturer.
I definitely do expect the mature appliance products on stable
codebases, which have more engineering into them, when used in fully
supported configurations to be on average a lot more reliable than
some MicroTik components -- but the fact of the matter is you might
have the bad luck of the draw, in regards to hardware, even with a
competitors' device costing 100x as much.
Regardless of manufacturer, some percentage of the components will
have defects, it could be a hardware defect so minor that it just
causes on average 2 crashes a year.
> We are looking for something which crashes LESS than once per year. "had a
> few stability problems" doesn't give me a warm fuzzy feeling about the
> product. Configuration management is nice, but how important is it for a
> device which is never modified and has only one tunnel?
--
-JH
Jan. 21, 2013