[c-nsp] cisco-nsp Digest, Vol 74, Issue 67

Wed Jan 21 19:26:48 EST 2009

can anyone please advice what does it mean and why  is an LACP port-channel
displays an alphabet along with an actual channel number ?

240    Po240(SD)       LACP
240    Po240A(SU)      LACP      Gi10/17(P) Gi10/18(P) Gi10/19(P) Gi10/20(P)
240    Po240C(SU)      LACP      Gi10/21(P)

On Tue, Jan 20, 2009 at 9:00 AM, <cisco-nsp-request at puck.nether.net> wrote:

> Send cisco-nsp mailing list submissions to
>        cisco-nsp at puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://puck.nether.net/mailman/listinfo/cisco-nsp
> or, via email, send a message with subject or body 'help' to
>        cisco-nsp-request at puck.nether.net
>
> You can reach the person managing the list at
>        cisco-nsp-owner at puck.nether.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of cisco-nsp digest..."
>
>
> Today's Topics:
>
>   1. Re: Acceptance Test Procedure for New Cisco Devices (Ziv Leyes)
>   2. Re: Acceptance Test Procedure for New Cisco Devices
>      (Rubens Kuhl Jr.)
>   3. What does mean Unknown state in Online diag.. 7609 Router
>      (omar parihuana)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 20 Jan 2009 16:36:59 +0200
> From: Ziv Leyes <zivl at gilat.net>
> Subject: Re: [c-nsp] Acceptance Test Procedure for New Cisco Devices
> To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Message-ID:
>        <EC993E87D960A541A66BF21D62AA42A622D4A5E79F at exch2k7.gilat.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Thank you all guys for your answers!
> I think Phil has hit the nail and gave me an idea about what I was looking
> for, anything more thorough than this will be a waste of time in our case
> and unnecessary long.
> But I guess we'll finally opt for letting the Cisco QA be enough as a
> guarantee the devices work (there's always RMA) and have Alex's suggestion
> be the winner here, just be as nebulous as you can and follow the
> "ill-defined and metaphysical characteristique" of such undefined term as
> "Acceptance Test Procedure"
> I'd ask the customer:
> Are you married? Did you fill an ATP form before you said "Yes, I do" ???
> No??? Then c'mon, gimme a break!!! It's just a darn router we're talking
> here, not chaining your entire life with the same woman!!
> A router can be replaced when malfunctioning, with a wife it's a bit more
> difficult, isn't it??
> Thak you all again!
> Ziv
>
>
>
> -----Original Message-----
> From: Alex Balashov [mailto:abalashov at evaristesys.com]
> Sent: Tuesday, January 20, 2009 3:38 PM
> To: Ziv Leyes
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Acceptance Test Procedure for New Cisco Devices
>
> But if it's attached to a legal statement, the more nebulous and elastic
> (aka BS) it is the more protection you have from incurring liability for
> actually having done or not done something.
>
> That gets easier when the "acceptance testing process" is ill-defined
> and metaphysical, not harder.
>
> Ziv Leyes wrote:
>
> > Ok, let me be more specific
> > When we buy devices for our own use, we just open it, plug it, and start
> using them, if there are any problems, we call the provider and they fix the
> problem (RMA or whatever)
> > In this case, we're going to sell the equipment as a kind of turn-key
> project, and the customer asked us to provide them with "our" ATP, which we
> don't really use for ourselves, so I'd like to implement one sort of testing
> procedure from now on for this type of cases. We're going to attach this to
> a legal statement so we can't just type some BS there and that's it, we want
> to actually implement it, and if we write we do a,b,c,d then we'll going to
> do a,b,c,d procedure for real.
> > I was thinking some of you guys may already use this kind of test
> routines and can help me creating one.
> > I don't need some really serious stuff, I can imagine I'll check the
> delivery status of the package, open it, check all the contents that need to
> be there are there, to plug the device and see it works, perhaps load some
> configuration, plug the hardware that is planned to hold if any (HWICS and
> so), perform some soft and hard reboots, see the device responds, there are
> links on all interfaces, and pack it back exactly as it was.
> > The problem is I don't know how exactly write it down on a kind of form
> that there's a checkbox for each test.
> > Does anybody have some ready to go stuff?
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Peter Rathlev [mailto:peter at rathlev.dk]
> > Sent: Tuesday, January 20, 2009 1:31 PM
> > To: Ziv Leyes
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] Acceptance Test Procedure for New Cisco Devices
> >
> > On Tue, 2009-01-20 at 12:13 +0200, Ziv Leyes wrote:
> >> Could anyone share if possible a kind of basic ATP you may use for new
> >> Cisco devices that you may receive?
> >> I'm in need of providing a customer with such procedure for two new
> >> devices, a Cisco 1861 router and a Cisco ASA5510
> >
> > Is it just the hardware that needs to be acceptance tested or is it some
> > kind of service depending on this hardware? I don't specifically recall
> > the term "ATP" but I guess Operational Acceptance Testing is the same.
> >
> > We only supply services, and the acceptance tests are defined by the
> > receiving end, typically with some help from a Service Manager and a
> > network engineer. The tests only check functionality not endurance of
> > the system. Typically the tests check everything defined in the SLA.
> >
> > When receiving hardware we use for ourselves we have no formal
> > acceptance tests; for core equipment it runs in a lab for some time and
> > the takes on a role as a standby unit in the production net. Sometimes
> > when time limits dictate it we end up just placing some new component in
> > an important role without testing. I hope the manufacturer does some
> > kind of burn in test. :-)
> >
> > HTH,
> > Peter
> >
> >
> >
> >
> >
> >
> >
> >
> ************************************************************************************
> > This footnote confirms that this email message has been scanned by
> > PineApp Mail-SeCure for the presence of malicious code, vandals &
> computer viruses.
> >
> ************************************************************************************
> >
> >
> >
> >
> >
> >
> >
> >
> >
> ************************************************************************************
> > This footnote confirms that this email message has been scanned by
> > PineApp Mail-SeCure for the presence of malicious code, vandals &
> computer viruses.
> >
> ************************************************************************************
> >
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> --
> Alex Balashov
> Evariste Systems
> Web    : http://www.evaristesys.com/
> Tel    : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
> Mobile : (+1) (678) 237-1775
>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
>
> ************************************************************************************
>
>
>
>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer
> viruses.
>
> ************************************************************************************
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 20 Jan 2009 13:02:24 -0200
> From: "Rubens Kuhl Jr." <rubensk at gmail.com>
> Subject: Re: [c-nsp] Acceptance Test Procedure for New Cisco Devices
> To: "Ziv Leyes" <zivl at gilat.net>
> Cc: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Message-ID:
>        <6bb5f5b10901200702w32053161xea726471acdcc2ef at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> > But I guess we'll finally opt for letting the Cisco QA be enough as a
> guarantee the devices work (there's always RMA) and have Alex's suggestion
> be the winner here, just be as nebulous as you can and follow the
> "ill-defined and metaphysical characteristique" of such undefined term as
> "Acceptance Test Procedure"
> > I'd ask the customer:
> > Are you married? Did you fill an ATP form before you said "Yes, I do" ???
> No??? Then c'mon, gimme a break!!! It's just a darn router we're talking
> here, not chaining your entire life with the same woman!!
> > A router can be replaced when malfunctioning, with a wife it's a bit more
> difficult, isn't it??
>
> Actually there are best practices to that also, see
> http://www.iambored.co.za/funny/girlfriend-v10-v20/
>
>
>
> Rubens
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 20 Jan 2009 11:26:30 -0500
> From: "omar parihuana" <omar.parihuana at gmail.com>
> Subject: [c-nsp] What does mean Unknown state in Online diag.. 7609
>        Router
> To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Message-ID:
>        <834c50110901200826o4bbad617q3f3f8560eb3dc9aa at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Folks,
>
> Recently I've installed a SPA-2XT3/E3 card (in module 7), but I get unknown
> state in online diagnostic, what does mean this "Unknow", because the led
> status in card is ok, and the sh diagbus also is ok:
>
> Mod  Sub-Module                  Model              Serial       Hw
> Status
> ---- --------------------------- ------------------ ----------- -------
> -------
> 7/0 2xOC3 ATM SPA               SPA-2XOC3-ATM      JAE1217FPTR  1.1    Ok
>  7/1 2xT3E3 SPA                  SPA-2XT3/E3        JAE1219H6QE  1.1    Ok
>
> Mod  Online Diag Status
> ---- -------------------
>  1  Pass
>  5  Pass
>  6  Pass
>  7  Pass
>  7/0 Not Applicable
>  7/1 Unknown   <<<<<<<<<<<<<<<<<<<<<<<<<<
>  8  Pass
>  8/0 Not Applicable
>  8/1 Not Applicable
>
>
> Slot 7: Logical_index 14
>        4-subslot SPA Interface Processor-200 controller
>        Board is analyzed ipc ready
>        HW rev 2.303, board revision C0
>        Serial Number: JAE1220HSI2 Part number: 73-10476-03
>
>        Slot database information:
>        Flags: 0x2004   Insertion time: 0x17E48 (1w4d ago)
>
>        Controller Memory Size:
>                832 MBytes CPU Memory
>                191 MBytes Packet Memory
>                1023 MBytes Total on Board SDRAM
>        Cisco IOS Software, cwlc Software (sip1-DW-M), Version 12.2(33)SRB3,
> RELEASE SOFTWARE (fc1)
>
>        SPA Information:
>        subslot 7/0: SPA-2XOC3-ATM (0x46E), status: ok
>        subslot 7/1: SPA-2XT3/E3 (0x40C), status: ok
>
> Thanks!!
> --
> Omar E.P.T
> -----------------
> Certified Networking Professionals make better Connections!
>
>
> ------------------------------
>
> _______________________________________________
> cisco-nsp mailing list
> cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
>
> End of cisco-nsp Digest, Vol 74, Issue 67
> *****************************************
>