[c-nsp] %TRACKING-5-STATE:

2012-07-11 Thread Kevin Hatem
I am configuring an EEM applet which triggers on a syslog message for a tracked 
object.  I have discovered that the syslog message %TRACKING-5-STATE is not 
produced when the tracked object changes conditions and therefore my applet 
does not trigger.  Running 12.2.33 SXH8 on a SUP720-10G (vss mode).  I have 
other 6500's running SXI and SXJ and they do produce the %TRACKING-5-STATE 
syslog message.  Is SXI the first release that the %TRACKING-5-STATE syslog 
message appears?

Thanks.
-kevin

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] 2960S w/10G uplinks

2010-09-01 Thread Kevin Hatem
Anyone have these boxes and pumping a lot (1G thru most of the ports) of 
traffic thru it?  I've seen some older threads reagarding high CPU utilization 
issues, low buffer concerns, etc.  They are fairly iniexpensive  and the oversub is basically 1:1.



This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] 6500 policing

2010-08-02 Thread Kevin Hatem
> I'm having some trouble with policing on a 6500 (sup720-3bxl) on a 
> WS-X6416-GBIC port.  The port is supposed to be rate-limited to 40mbit/s. 
> The physical port is configured as a layer 2 port tied to a single vlan 
> (switchport access vlan ...).  Egress policing is applied to the SVI port


i think the physical interface needs to be configured for vlan-based qos:

!
int g1/1/1
mls qos vlan-based
!

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] Multicast issues on 7600s with WS-6748-sfp blades

2010-07-30 Thread Kevin Hatem
>It never worked, when I sent that reply I had mistakenly thought it 
>was an internal email.

I feel sorry for you Tim :-) ... you continue to get beat up for a simple 
mistake from many many moons ago!

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] BGP default route only

2010-07-23 Thread Kevin Hatem
> > ip prefix-list annonce-C1 seq 100 permit 0.0.0.0/0
> 
> Shouldn't it be '... permit 0.0.0.0/32' ? IMHO, 0/0 is "all".

no, it should be 0.0.0.0/0 which matches the default route
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] arista 7500 versus cisco nexus

2010-07-22 Thread Kevin Hatem
Has anyone seen any actual (real network) performance stats on Arista's 7500 
"flagship" switch or have one in production?  I cannot seem to find anyone who 
has one of these boxes or any info on how they really perform under a load, 
especially compared to the Nexus 7k (or even the 5k).

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] OSPF Default Route Injection

2010-03-18 Thread Kevin Hatem
Injected default routes are always type-5 from the advertising router.  Summary 
LSAs within the area (as they are advertised to other areas).



-Original Message-
From: Leah Lynch (Contractor) [mailto:leah.ly...@clearwire.com] 
Sent: Thursday, March 18, 2010 13:54
To: Kevin Hatem; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] OSPF Default Route Injection

I am pretty sure default routes are always type-5 because they contain
no native link data. But, I don't think the spec calls this out
specifically. I am wondering if anyone out there has seen a default
route that was not a type-5, and if so, could they post a snippet of
that LSA database?



This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] OSPF Default Route Injection

2010-03-18 Thread Kevin Hatem
If two routers are injecting a default route under OSPF then each router will 
retain their own default route in the route table as each other's injected 
default route has the same distance as its self advertised default.  You could 
set a higher/lower distance on inbound advertisements from the neighbors to 
influence the installation of the default route into the RIB.

HTH
-kevin

-Original Message-
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of David Granzer
Sent: Thursday, March 18, 2010 09:13
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] OSPF Default Route Injection

Hello,

please could someone explain what exactly command "default-information
originate always" under ospf process works ?  When you have more than
one router configured with this default route injection is correct
behavior that you don't see on these routers default route in their ip
routing table from other routers and you see only external lsa for
0.0.0.0 in ospf database ?

Thanks,
David
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


[c-nsp] per-port price for 10G on c3750E

2010-02-12 Thread Kevin Hatem
What would be the cost per 10G port on a 3750E-48?  It's simplified on a 
platform/line card with all 10G ports, but the 3750E has 48 1G ports and only 2 
10G ports.

Thanks.

-kevin hatem

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] [SUMMARY]: 4900M vs. 4503 for core

2010-01-29 Thread Kevin Hatem
The 4900m is a robust switch with plenty of BW on the fabric. Port density is 
not plentiful but...Using the twinG is a choice - just check on the 
limitation of use not only with using them on the onboard X2 slots, but also 
ASIC restrictions.  I know that the SUP6E (the 4900m SUP?) uses stub asics to 
the fabric and has limitations for combining 1G and 10G on the same asic.

The Juniper and HP boxes that others have suggested are good boxes too.  It 
appears you have some time to investigate many solutions.  The shortage of the 
4900 and other such products are derived as a result of limited component 
production from Cisco's manufacturing plants (overseas).  But the suggestion 
that Cisco is pushing other products (Nexus) is plausible.

-nuff said.
-kevin.



-Original Message-
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jason Gurtz
Sent: Thursday, January 28, 2010 15:34
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] [SUMMARY]: 4900M vs. 4503 for core

> Is there anything glaringly wrong with choosing the 4900M using twin-gig
> based connections to the access layer over the 4503 Sup6 and 46xx line
> cards in our situation?

Thanks all for the replies!  A person also responded privately with the
opinion that most people want Netflow down the road.  Unfortunately, since
Netflow has been removed from the 45xx with the Sup6 it would require 65xx
at $$++.  Squarely in the want vs. need bucket for us

Unfortunately, I left out that that most of the gig uplink connections are
fiber so a 3560G doesn't have enough SFP ports.  I did find the
WS-C3750G-12S-E which looks like the good low-cost option.  On the minuses
side, it's a softswitch, and no 10G uplinks for linking in the server
access switches.  The main downside here is advocating for their
replacement and purchasing strategies around here.  eBay, used equip.,
etc... are pretty much verboten.  Basically, if we buy these now, they'll
be here in 5 years and forklifting the network core could be painful.

Point well taken on the stacking related maintenance downtime issue.  We
plan on doing pure routing and GLBP so thankfully this wouldn't affect us.
This issue will bite us with the server access layer. :(  I'll join the
many who want this problem to go away.

The availability issues with 45xx and 49xx shouldn't be a problem as
4507's are being spec'ed for some access switches and we have until
summertime to do this.  It's interesting though, makes me wonder if it's
just really high demand, or C pushing other platforms.

I discovered the 4928-10G, but the 4900M config comes in cheaper,
apparently due to only needing one 8 port card.  I'm assuming the 2:1
oversubscription is not an issue when running these 10G ports at 1G.  Only
thing is 2000W of power supply vs. 600W.  It does seem silly to do the
twingig thing; if only there was a 20-port sfp halfcard!

Thanks again,

~JasonG
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] 4900M vs. 4503 for core

2010-01-28 Thread Kevin Hatem
The 4900m are is very short supply as Jeff mentions.  I waited 3 months for the 
chassis (fall 2009) and just ordered the 20 port 1G module and is back ordered 
to March.

The 4900m is very good if you need to aggregate your 10G as top of rack, then 
maybe out to a metro E.  The 3560G is a great mid-core solution for small 
shops.  I also agree that using a stack in the core is bad.

-kevin

-


-Original Message-
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mark Tinka
Sent: Wednesday, January 27, 2010 20:19
To: cisco-nsp@puck.nether.net
Cc: Jeff Bacon
Subject: Re: [c-nsp] 4900M vs. 4503 for core

On Thursday 28 January 2010 07:30:38 am Jeff Bacon wrote:

> You could probably use a pair of 3560Gs for your core and  get away 
> with it, without having to spend any real  money. I wouldn't actually 
> stack the cores - too easy  for one to take out the other via the 
> stack cable... but  that's a personal preference.

I tend to agree with this one - stacking (using proprietary
technologies) core switches could get risky when things get hairy. Besides, how 
much can you stack before a chassis makes sense, and not just in ports?

I've used 3560G's as core switches in relatively small PoP's (pushing about 
1Gbps or more with LACP). They're solid!

> If you _need_ to buy now once and for all, then you've  got a problem. 
> But if you don't, don't.

Agree.

If you're not averse to other vendors, you could consider Juniper's EX3200's 
and EX4200's as well.

Cheers,

Mark.

This e-mail, including any attachments and response string, may contain 
proprietary information which is confidential and may be legally privileged. It 
is for the intended recipient only. If you are not the intended recipient or 
transmission error has misdirected this e-mail, please notify the author by 
return e-mail and delete this message and any attachment immediately. If you 
are not the intended recipient you must not use, disclose, distribute, forward, 
copy, print or rely on this e-mail in any way except as permitted by the author.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/