Re: [c-nsp] Link State Periodic SPF

2013-01-10 Thread Oliver Boehmer (oboehmer)
On 11/01/2013 03:02, "Dhamija Amit" wrote: >Hi > >I would like to know about Link state Periodic SPF's , I have seen in >Cisco IOS-XR and Juniper M/T -Series ( Junos) by default Periodic SPF >runs every 15 minutes. > >Going to concept of SPF whenever there is change in topology router runs >SP

Re: [c-nsp] Link State Periodic SPF

2013-01-10 Thread sthaug
> I would like to know about Link state Periodic SPF's , I have seen in Cisco > IOS-XR and Juniper M/T -Series ( Junos) by default Periodic SPF runs every 15 > minutes. > > Going to concept of SPF whenever there is change in topology router runs SPF > based on SPF interval configured. Also when

[c-nsp] Link State Periodic SPF

2013-01-10 Thread Dhamija Amit
Hi I would like to know about Link state Periodic SPF's , I have seen in Cisco IOS-XR and Juniper M/T -Series ( Junos) by default Periodic SPF runs every 15 minutes. Going to concept of SPF whenever there is change in topology router runs SPF based on SPF interval configured. Also when LSP/LS

Re: [c-nsp] WS-SUP720-3B and DOM/DDM enabled SFPs

2013-01-10 Thread Walter Keen
I can verify a generic one works on SUP720-3b running 12.2(33)SRE But not on any of the linecards we have, like 6724-sfp. This one's not in use. core-1#sh int gi8/1 transceiver Transceiver monitoring is disabled for all interfaces. ITU Channel not available (Wavelength not available),

[c-nsp] SUP720 Error

2013-01-10 Thread Craig Horchem
We have a few supervisors in our repair bin that keep showing up with the error "HW indicate it is sup3, but idprom is not" Has anyone ran across this error before? I could not find any records of it online. ___ cisco-nsp mailing list cisco-nsp@puc

Re: [c-nsp] 6509-NEB-A

2013-01-10 Thread Justin M. Streiner
On Thu, 10 Jan 2013, Blake Pfankuch wrote: I guess I should have phrased my question a little better. Given that the existing 6509's we have are 6+ year old chassis' and have soon to be End of Life Sup's (within 18 months), opinion based, is it justifiable to replace the sup's and line cards,

Re: [c-nsp] 6509-NEB-A

2013-01-10 Thread Blake Pfankuch
We have 7203BXL sup's currently, however these switches we think were put in early 2005. We definitely will have a large amount of 10gbit coming soon and with Cisco announcing that the 7203BXL EOL announcement, that means we want to be off them by end of SW Maintenance Date (Feb/11/2014). Ad

[c-nsp] 7200 NAT performance

2013-01-10 Thread Markus H
Hi, I currently plan on using a 7204VXR with an NPE-G1 at an event for NAT only and wonder what performance I could get out of it. Common to both secarios I am thinking about is the following: Two active intefaces (on the NPE): one to the ISP and one the core switch (proably GBICs on both). A few

Re: [c-nsp] MSTP issue. Isolation of core switch

2013-01-10 Thread cnsp
Hello! Thanks for you response. As I know MSTP does not send MSTI's information in separate BPDUs, this information is piggybacked into the IST's BPDUs using special M-Record fields. They are all send UNTAGGED. They may be filtered (bpdufilter enable) or Carrier-Eqiupment may be configured no

Re: [c-nsp] 6509-NEB-A

2013-01-10 Thread Chuck Church
Which Sups? I believe the Sup2T needs an E chassis, but the 720 will work with older ones. The 720s are supported for 2 more years FYI. The other modules might be nearing end of SW support though, depending on what you have... Chuck -Original Message- From: cisco-nsp-boun...@puck.neth

Re: [c-nsp] 6509-NEB-A

2013-01-10 Thread Mike Hale
The Nexus5k and fabric extenders really aren't that much coin if you're interested in basic 10gig connectivity. The extenders were ~4500 refurb, IIRC, and the units themselves ~11k refurb, all smartnet eligible. On Thu, Jan 10, 2013 at 12:38 PM, Blake Pfankuch wrote: > We are currently looking

[c-nsp] 6509-NEB-A

2013-01-10 Thread Blake Pfankuch
We are currently looking at replacing our datacenter core. Currently we have 2 6509-NEB-A's in core, and we are trying to weigh options on either upgrading sup's line cards to go 10gbit or looking at Nexus gear. Obviously there is a little bit of dollar pain when even thinking nexus so I am tr

Re: [c-nsp] MSTP issue. Isolation of core switch

2013-01-10 Thread Andrey Teslenko
Hello! Thanks for you response. As I know MSTP does not send MSTI’s information in separate BPDUs, this information is piggybacked into the IST’s BPDUs using special M-Record fields. So, I can have multiple MSTI or one with whole vlan range (1-4096) no matter. Also we not planned to use some loa

Re: [c-nsp] Cisco 867 SIP & NAT

2013-01-10 Thread Brian Turnbow
> > On Jan 10, 2013, at 8:40 AM, Richard Clayton > wrote: > > > I am currently running SIP ALG on 1000 devices without any problems, > a mixture of 857 and 887VA-M. I originally had a problem with the > 887VA-M but a bug fix was released after I raised a TAC case. > > > > Cheers > > Sledge > >

Re: [c-nsp] Cisco 867 SIP & NAT

2013-01-10 Thread Jared Mauch
On Jan 10, 2013, at 8:40 AM, Richard Clayton wrote: > I am currently running SIP ALG on 1000 devices without any problems, a > mixture of 857 and 887VA-M. I originally had a problem with the 887VA-M but > a bug fix was released after I raised a TAC case. > > Cheers > Sledge The challenge I

Re: [c-nsp] Cisco 867 SIP & NAT

2013-01-10 Thread Richard Clayton
I am currently running SIP ALG on 1000 devices without any problems, a mixture of 857 and 887VA-M. I originally had a problem with the 887VA-M but a bug fix was released after I raised a TAC case. Cheers Sledge On 9 January 2013 00:12, Jared Mauch wrote: > IOS automatically does SIP-ALG when d

Re: [c-nsp] Difference between ISIS NSR and ISIS NSF Cisco-Style

2013-01-10 Thread Oliver Boehmer (oboehmer)
Hi, well, I am not aware of any plans to implement ISIS NSR which would sync LSPDB to standby in IOS or IOS-XR, something which would not need the CSNP to rebuild the LSDB upon failover. So don't think we can fix this on our side if your ERX doesn't support the official "nsf ietf". Maybe you can

[c-nsp] Fw: Re: Difference between ISIS NSR and ISIS NSF Cisco-Style

2013-01-10 Thread Dhamija Amit
  --- On Thu, 1/10/13, Dhamija Amit wrote: > From: Dhamija Amit > Subject: Re: [c-nsp] Difference between ISIS NSR and ISIS NSF Cisco-Style > To: "Oliver Boehmer (oboehmer)" > Date: Thursday, January 10, 2013, 12:32 PM > Hi Oli, > > Many Thanks for your prompt response. > > We have one int

Re: [c-nsp] Difference between ISIS NSR and ISIS NSF Cisco-Style

2013-01-10 Thread Oliver Boehmer (oboehmer)
>I would like to know the difference between actuall ISIS NSR and ISIS NSF >cisco style. > >Most documentation says they are same , however thereare some differences >also and it's not real NSR. Also i have seen in some packet sniffer in >cisco style cisco router sends a dummy special CSNP pac

Re: [c-nsp] warning about important ERSPAN bug in 6500/7600 code (SX/SR trains)

2013-01-10 Thread Phil Mayers
On 01/10/2013 11:24 AM, Mikael Abrahamsson wrote: Hello. CSCsb70129 means an ERSPAN session which is in administrative shutdown ("shutdown" issued in the ERSPAN config), might start to ERSPAN traffic even though the config says otherwise. Triggers might be that the source port specified in the

Re: [c-nsp] WS-SUP720-3B and DOM/DDM enabled SFPs

2013-01-10 Thread Phil Mayers
On 01/10/2013 11:15 AM, Tóth András wrote: According to Gigabit Transceiver Matrix, DOM is not supported for SX/LH/ZX modules on 6500, neither Sup720 nor Sup2T nor 6824/6848 linecards. I guess that's not terribly surprising given the 6848 is just a 6748 with a DFC4; I doubt they rev'd the line

[c-nsp] Difference between ISIS NSR and ISIS NSF Cisco-Style

2013-01-10 Thread Dhamija Amit
Hi   I would like to know the difference between actuall ISIS NSR and ISIS NSF cisco style.   Most documentation says they are same , however thereare some differences also  and it's not real  NSR. Also i have seen in some packet sniffer in cisco style cisco router sends a dummy special

[c-nsp] warning about important ERSPAN bug in 6500/7600 code (SX/SR trains)

2013-01-10 Thread Mikael Abrahamsson
Hello. CSCsb70129 means an ERSPAN session which is in administrative shutdown ("shutdown" issued in the ERSPAN config), might start to ERSPAN traffic even though the config says otherwise. Triggers might be that the source port specified in the ERSPAN config goes down and comes up again (ther

Re: [c-nsp] WS-SUP720-3B and DOM/DDM enabled SFPs

2013-01-10 Thread Tóth András
According to Gigabit Transceiver Matrix, DOM is not supported for SX/LH/ZX modules on 6500, neither Sup720 nor Sup2T nor 6824/6848 linecards. http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6981.pdf Best regards, Andras On Wed, Jan 9, 2013 at 11:22

[c-nsp] VACL and SPAN load share on destination ports

2013-01-10 Thread Ben Hammadi, Kayssar (NSN - TN/Tunis)
Dears , I am trying to load balance on destination port with SPAN and VACL , Below the configuration : interface GigabitEthernet9/24 switchport switchport trunk encapsulation dot1q switchport mode trunk switchport nonegotiate switchport capture interface GigabitEthernet9/46 switchport switchpo

Re: [c-nsp] IOS XR PIC (+ multipath)

2013-01-10 Thread Adam Vitkovsky
> Do you use max-path eigbp to ignore the IGP metric to the next-hop/egress PE and to loadshare across these paths? Or do you actually have the requirement to load-share across a direct/ebgp and a remote PE path? Well it's both actually, in order to take care of all scenarios upfront. It's mostl