Turns out this information is "kinda" hidden in various pdfs see for
example Cisco TAC time presentations or cisco live about "what does sw
version X bring over version Y to the table"
-pavel
Dňa 27.1.2017 11:24 používateľ "James Bensley"
napísal:
On 24 January 2017 at
On 24 January 2017 at 17:54, Lee wrote:
> On 1/24/17, James Bensley wrote:
>> Also a month or two after our bug scrub was completed the new major
>> milestone/stable versions of code for the devices we had tested was
>> released (our scrub was finished when
On 1/24/17, James Bensley wrote:
> On 24 January 2017 at 10:04, wrote:
>>> Simon Lockhart
>>> Sent: Tuesday, January 24, 2017 8:09 AM
>>>
>>> On Tue Jan 24, 2017 at 09:02:18AM +0100, Gert Doering wrote:
>>> > On Mon, Jan 23, 2017 at 07:33:08PM
On 24 January 2017 at 12:46, wrote:
>> James Bensley
>> Sent: Tuesday, January 24, 2017 11:15 AM
>>
>> On 23 January 2017 at 17:16, Rick Martin wrote:
>> >
>>
>> It’s fucking expensive to have fully loaded ASR9000 chassis just sitting
>>
> James Bensley
> Sent: Tuesday, January 24, 2017 11:15 AM
>
> On 23 January 2017 at 17:16, Rick Martin wrote:
> >
>
> It’s fucking expensive to have fully loaded ASR9000 chassis just sitting
> around
> in a cupboard ready to go.
That's what lab equipment is for,
On 24 January 2017 at 10:04, wrote:
>> Simon Lockhart
>> Sent: Tuesday, January 24, 2017 8:09 AM
>>
>> On Tue Jan 24, 2017 at 09:02:18AM +0100, Gert Doering wrote:
>> > On Mon, Jan 23, 2017 at 07:33:08PM -0500, Charles Sprickman via
> cisco-nsp
>> wrote:
>> > > I
On 23 January 2017 at 17:16, Rick Martin wrote:
>
> I am under pressure to consider third party maintenance providers for our
> significant Cisco inventory, and I am quite leery of such an arrangement. I
> suppose third party maintenance may be OK for products that we
> Simon Lockhart
> Sent: Tuesday, January 24, 2017 8:09 AM
>
> On Tue Jan 24, 2017 at 09:02:18AM +0100, Gert Doering wrote:
> > On Mon, Jan 23, 2017 at 07:33:08PM -0500, Charles Sprickman via
cisco-nsp
> wrote:
> > > I have to say, I haven???t been impressed with their support in a
> > > long
Hi,
On Tue, Jan 24, 2017 at 08:08:43AM +, Simon Lockhart wrote:
> Yes, really, they want us to pay them more money to find
> out how buggy their code releases are...
When I was young and naive, too many years ago, I wondered why I would have
to pay Vendors to be able to report their bugs to
On Tue Jan 24, 2017 at 09:02:18AM +0100, Gert Doering wrote:
> On Mon, Jan 23, 2017 at 07:33:08PM -0500, Charles Sprickman via cisco-nsp
> wrote:
> > I have to say, I haven???t been impressed with their support in a long
> > time. We have smartnet really just for hardware, and recently I figured
Hi,
On Mon, Jan 23, 2017 at 07:33:08PM -0500, Charles Sprickman via cisco-nsp wrote:
> I have to say, I haven???t been impressed with their support in a long
> time. We have smartnet really just for hardware, and recently I figured
> that since we have support, I???d actually try and offload a
--- Begin Message ---
> On Jan 23, 2017, at 3:05 PM, Jared Mauch wrote:
>
> On Mon, Jan 23, 2017 at 02:28:37PM -0500, Shawn L wrote:
>> I guess it all depends on what you utilize support for. We tend to have
>> in-house spares, etc. that we can swap in in the event of a
On 23/01/2017 17:16, Rick Martin wrote:
I am under pressure to consider third party maintenance providers for
our significant Cisco inventory, and I am quite leery of such an
arrangement. I suppose third party maintenance may be OK for
Ask yourself a couple of things:
1. Do you make use of
>From the support side I always advise my customers to also get support from
>the vendor. Almost all issues are down to software problems, bar a select few
>where the problem is either a typo or lack of planning and understanding the
>requirements.
Access to support from vendor is essential
On Mon, Jan 23, 2017 at 02:28:37PM -0500, Shawn L wrote:
> I guess it all depends on what you utilize support for. We tend to have
> in-house spares, etc. that we can swap in in the event of a failure. But,
> there are times when you need to talk to someone at TAC to get the bottom
> of an
"cisco-nsp@puck.nether.net" <cisco-nsp@puck.nether.net>
Sent: Monday, January 23, 2017 12:16 PM
Subject: [c-nsp] Tabo Topic? Third party Maintenance
I am under pressure to consider third party maintenance providers for our
significant Cisco inventory, and I am quite leery
I guess it all depends on what you utilize support for. We tend to have
in-house spares, etc. that we can swap in in the event of a failure. But,
there are times when you need to talk to someone at TAC to get the bottom
of an issue.
On Mon, Jan 23, 2017 at 12:36 PM, Jared Mauch
On Mon, Jan 23, 2017 at 05:16:01PM +, Rick Martin wrote:
>
> I am under pressure to consider third party maintenance providers for our
> significant Cisco inventory, and I am quite leery of such an arrangement. I
> suppose third party maintenance may be OK for products that we have plenty
I am under pressure to consider third party maintenance providers for our
significant Cisco inventory, and I am quite leery of such an arrangement. I
suppose third party maintenance may be OK for products that we have plenty of
spare inventory for such as customer edge routers or switches but
19 matches
Mail list logo