Re: [c-nsp] Bug or feature? 7600s forgetting service policy

2014-01-15 Thread John Neiberger
It has pretty much always been on some flavor of 6748 card, but I don't know if it has only happened on, for example, SFP blades or copper blades. Thanks, John On Wed, Jan 15, 2014 at 5:50 AM, Xuhu jstuxuhu0...@gmail.com wrote: Which line card u r running, I tested previous and found some line

Re: [c-nsp] EARL_L2_ASIC-SP-4-DBUS_HDR_ERR

2014-01-15 Thread Dobbins, Roland
On Jan 15, 2014, at 10:25 PM, Sukumar Subburayan (sukumars) sukum...@cisco.com wrote: Error in the DBUS (data bus) header indicates that you have had hardware. Or that you need to re-seat the linecard(s)/RP(s) in question . . .

[c-nsp] Cisco Security Advisory: Multiple Vulnerabilities in Cisco Secure Access Control System

2014-01-15 Thread Cisco Systems Product Security Incident Response Team
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Cisco Security Advisory: Multiple Vulnerabilities in Cisco Secure Access Control System Advisory ID: cisco-sa-20140115-csacs Revision 1.0 For Public Release 2014 January 15 12:00 UTC (GMT

[c-nsp] snmp monitoring me3600 mpls pseudowire bytes xmit/rcv

2014-01-15 Thread Aaron
I need to monitor (graph) via snmp, bytes in bytes out of an mpls pw on a me3600... I think I've found the snmp oid that corresponds to the received bytes on that pw, but I'm unable to find the snmp oid that is for the sent bytes. Does anyone know what that would be or how could I find out what

Re: [c-nsp] snmp monitoring me3600 mpls pseudowire bytes xmit/rcv

2014-01-15 Thread Martin Moens
Stop.. my mistake, below are for service policy's Martin -Original Message- From: Martin Moens Sent: 15 January 2014 18:47 To: 'Aaron'; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] snmp monitoring me3600 mpls pseudowire bytes xmit/rcv Aaron, receive oid should be

Re: [c-nsp] snmp monitoring me3600 mpls pseudowire bytes xmit/rcv

2014-01-15 Thread Martin Moens
Aaron, receive oid should be 1.3.6.1.4.1.9.9.166.1.15.1.1.11.x.y transmit oid should be 1.3.6.1.4.1.9.9.166.1.15.1.1.18.x.y The x and y likely will change between reboots... gl... Martin -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of

[c-nsp] DWDM

2014-01-15 Thread steve
Can anyone give any pointers where to start on DWDM, any good books/blogs etc? Ideally looking for a 'idiots guide', I have a good handle of what DWDM can provide, but I need to be able to understand/explain the components that form part of a DWDM solution including things like protected

Re: [c-nsp] DWDM

2014-01-15 Thread chip
Likely a good place to start: http://www.nanog.org/meetings/abstract?id=2086 Ciena, Cyan, Adva, Infinera, Cube Optics, even some cisco ONS stuff. All have their pros and cons... --chip On Wed, Jan 15, 2014 at 12:44 PM, st...@itps.uk.net wrote: Can anyone give any pointers where to start on

Re: [c-nsp] ME3600 autoroute 10G EFP issues

2014-01-15 Thread Mark Tinka
On Wednesday, January 15, 2014 04:14:39 PM Eric Van Tol wrote: Not trying to beat a dead horse, but there wasn't any way I could do this - they were core nodes in the ring - for bi-directional communication across the ring, I needed them IP-adjacent to other core ring nodes. It's a moot

Re: [c-nsp] EARL_L2_ASIC-SP-4-DBUS_HDR_ERR

2014-01-15 Thread PlaWanSai RMUTT CPE IX
Could you specify which card is a problem? Thank you very much. -Original Message- From: Sukumar Subburayan (sukumars) [mailto:sukum...@cisco.com] Sent: Wednesday, January 15, 2014 10:25 PM To: PlaWanSai RMUTT CPE IX; cisco-nsp@puck.nether.net Cc: Panuwat Santukaw; Somphong Pokfai;

Re: [c-nsp] ME3600 autoroute 10G EFP issues

2014-01-15 Thread Eric Van Tol
Any caveats I should be aware of in a mixed Juniper/Cisco environment? Nothing major - the only thing I'd say that might sneak up on you is to enable Multi-Topology (MT) for IPv6 if IS-IS is your IGP. Juniper enable IPv6 in IS-IS by default, and it's Single Topology (ST) by default.

Re: [c-nsp] ME3600 autoroute 10G EFP issues

2014-01-15 Thread Mark Tinka
On Thursday, January 16, 2014 04:28:02 AM Eric Van Tol wrote: Cool beans. When we transitioned to ISIS years ago, we made the decision to go MT, so hopefully we should be fine. Yes, if you have MT already, there won't be any nasty surprises. And since the ME3600X now has working IPv6