Re: [c-nsp] FDDI card for 7200 VXR

[Sascha Pollok]

Wonder if anyone uses those
kind of converter and how reliable are they?
I have a FDDI hand off.


I use a Cisco Catalyst 5500 for this purpose (and to translationally bridge 
from FDDI to Gigabit Ethernet).


The cheap solution, back in the day, was to use a 3Com CoreBuilder 2500.


We had Fore PowerHubs for this. They had 6x FE, 2x FDDI and other
cards and even did (do) OSPF :) Still got one around but unprovisioned
10 years ago or so.

-Sascha
___
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] SDM templates

[Tóth András]

Hi,

1) If all TCAM resources are allocated for a particular feature,
further entries will be stored in software, therefore packets hitting
those entries will be processed in software (IOW punted to CPU). SDM
templates are just repartitioning the TCAM space to be divided in
another way among different entries.

2) No, it does not. You can safely configure 128 routed interfaces
without any problem. Note that the more SVIs you configure, the more
processor memory you will use. Also, the CPU utilization might
increase with an increasing number of SVIs. While the total maximum of
supported SVI is 1000, keep in mind that the maximum number of STP
instances is 128 with PVST+ and Rapid-PVST+.

Quote from the 3750 Data Sheet:
128 switch virtual interfaces (SVIs) are recommended. Maximum of 1000
are supported (depending on the number of routes and multicast
entries). 468 routed ports are supported per stack.
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps5023/product_data_sheet0900aecd80371991.html

3) Routed interface includes L3 (no switchport) ports and SVIs as well.

If you want to read more details, refer to Understanding and
Configuring Switching Database Manager on Catalyst 3750 Series
Switches guide on the following link:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a00801e7bb9.shtml

Cheers,
Andras


On Thu, Oct 28, 2010 at 10:57 PM, Bill Blackford
 wrote:
> Ok, stupid questions about SDM.
>
> When I issue a 'sh sdm prefer' I see that my 3560 is using the "desktop 
> default" template. When I issue 'sh sdm prefer routing' I see that I get less 
> MACs and more IPV4 routes. This all begs the questions:
>
> 1. Is this showing me what resources are allocated to the TCAM (IOW, in 
> hardware) and anything exceeding is punted to the CPU?
>
> 2. In both cases above, I'm shown that "This template optimizes the resources 
> in the switch to support this level of features for 8 routed interfaces and 
> 1024 VLANs." Does this mean that the 9th routed interface is punted to the 
> CPU as well?
>
> 3. Does "routed interfaces" mean just that or is it also referring to SVI's?
>
>
> Thanks,
>
> -b
>
>
> --
> Bill Blackford
> Senior Network Engineer
> Technology Systems Group
> Northwest Regional ESD
>
> Logged into reality and abusing my sudo priviledges
>
>
> ___
> cisco-nsp mailing list  cisco-...@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

___
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] FDDI card for 7200 VXR

[Sridhar Ayengar]

Luan Nguyen wrote:

Ah, glad you brought that up.  I was looking into a FDDI to Fast Ethernet
converter: http://www.data-connect.com/RAD_AMC-101.htm
Wonder if anyone uses those
kind of converter and how reliable are they?
I have a FDDI hand off.


I use a Cisco Catalyst 5500 for this purpose (and to translationally 
bridge from FDDI to Gigabit Ethernet).


The cheap solution, back in the day, was to use a 3Com CoreBuilder 2500.

Peace...  Sridhar
___
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] SDM templates

[Bill Blackford]

Ok, stupid questions about SDM.

When I issue a 'sh sdm prefer' I see that my 3560 is using the "desktop 
default" template. When I issue 'sh sdm prefer routing' I see that I get less 
MACs and more IPV4 routes. This all begs the questions:

1. Is this showing me what resources are allocated to the TCAM (IOW, in 
hardware) and anything exceeding is punted to the CPU?

2. In both cases above, I'm shown that "This template optimizes the resources 
in the switch to support this level of features for 8 routed interfaces and 
1024 VLANs." Does this mean that the 9th routed interface is punted to the CPU 
as well? 

3. Does "routed interfaces" mean just that or is it also referring to SVI's?


Thanks,

-b


--
Bill Blackford 
Senior Network Engineer
Technology Systems Group   
Northwest Regional ESD 

Logged into reality and abusing my sudo priviledges


___
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] FDDI card for 7200 VXR

[Luan Nguyen]

Ah, glad you brought that up.  I was looking into a FDDI to Fast Ethernet
converter: http://www.data-connect.com/RAD_AMC-101.htm
Wonder if anyone uses those
kind of converter and how reliable are they?
I have a FDDI hand off.

Regards,

-Luan

On Thu, Oct 28, 2010 at 3:19 PM, Justin M. Streiner  wrote:

> On Thu, 28 Oct 2010, Luan Nguyen wrote:
>
>  I guess I have to look into buying a 7200 as well.
>>
>
> Not knowing your situation or needs, would it make more sense to replace
> the FDDI gear with something that speaks Ethernet?
>
>
> jms
> ___
> 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/
>
___
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] FDDI card for 7200 VXR

[Justin M. Streiner]

On Thu, 28 Oct 2010, Luan Nguyen wrote:


I guess I have to look into buying a 7200 as well.


Not knowing your situation or needs, would it make more sense to replace 
the FDDI gear with something that speaks Ethernet?


jms
___
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] FDDI card for 7200 VXR

[Justin M. Streiner]

On Thu, 28 Oct 2010, Luan Nguyen wrote:


Anyone  has a FDDI PA VIP2 card for the 7200VXR series router that I can
buy?


VIPs are (were) the carrier cards that would let you run 7200 port 
adapters in a 7500 series router.


Your best bet for finding what you need would probably be either ebay or 
one of the many resellers of used Cisco hardware.


jms
___
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] FDDI card for 7200 VXR

[Luan Nguyen]

Thanks guys.
I guess I have to look into buying a 7200 as well.

Regards,

-Luan

On Thu, Oct 28, 2010 at 2:25 PM, Mikael Abrahamsson wrote:

> On Thu, 28 Oct 2010, Luan Nguyen wrote:
>
>  Hi folks,
>>
>> Anyone  has a FDDI PA VIP2 card for the 7200VXR series router that I can
>> buy?
>>
>
> FDDI is not supported on the VXR afaik (only the non-VXR). VIP2 is 7500.
>
> http://www.cisco.com/en/US/ts/fn/000/fn3028.html
>
> Background
>
> When port adaptors without the Arbiter EPLD upgrade are installed in a 7200
> VXR router, they will not operate properly. The down-version Port Adapters
> will not be recognized, will fail diagnostics and will not pass traffic. Not
> all port adapters are upgradeable or supported in the 7200 VXR router.
>
> The Cisco 7200 VXR routers support all port adapters supported on the Cisco
> 7200, except for following:
>
> FDDI Port Adapters:
>
>*
>
>  PA-F-MM
>*
>
>  PA-F-SM
>*
>
>  PA-F/FD-MM
>*
>
>  PA-F/FD-SM
>
>
> --
> Mikael Abrahamssonemail: swm...@swm.pp.se
>
___
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] FDDI card for 7200 VXR

[Mikael Abrahamsson]

On Thu, 28 Oct 2010, Luan Nguyen wrote:


Hi folks,

Anyone  has a FDDI PA VIP2 card for the 7200VXR series router that I can
buy?


FDDI is not supported on the VXR afaik (only the non-VXR). VIP2 is 7500.

http://www.cisco.com/en/US/ts/fn/000/fn3028.html

Background

When port adaptors without the Arbiter EPLD upgrade are installed in a 
7200 VXR router, they will not operate properly. The down-version Port 
Adapters will not be recognized, will fail diagnostics and will not pass 
traffic. Not all port adapters are upgradeable or supported in the 7200 
VXR router.


The Cisco 7200 VXR routers support all port adapters supported on the 
Cisco 7200, except for following:


FDDI Port Adapters:

*

  PA-F-MM
*

  PA-F-SM
*

  PA-F/FD-MM
*

  PA-F/FD-SM


--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
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] FDDI card for 7200 VXR

[Gert Doering]

Hi,

On Thu, Oct 28, 2010 at 01:00:51PM -0400, Luan Nguyen wrote:
> Anyone  has a FDDI PA VIP2 card for the 7200VXR series router that I can
> buy?

I think I'd like to see a video of you trying to stuff a VIP2 into a
7200... :)

Of course there's the PA-F-* cards for the 7200, *but* Cisco says they
are not supported in the VXR series:

http://www.cisco.com/en/US/docs/interfaces_modules/port_adapters/install_upgrade/fddi/pa-f-mm-sm_half-duplex_install_config/3499pref.html

gert
-- 
USENET is *not* the non-clickable part of WWW!
   //www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025g...@net.informatik.tu-muenchen.de


pgpXlltF2RyZF.pgp
Description: PGP signature
___
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] Change routing if path delay increases ( was Re: Assurared BW to customer)

[Mindaugas Kubilius]

Hello,
Although not identical but I feel like facing a similar problem in nature.

We have two sites connected over two providers SP_A and SP_B. Both can 
take a route which is geographically short (let's name it "short path"). 
SP_A also can take the alternative path which is considerably longer (a 
"long path"). The difference in latency between short and long paths is 
several hundreds milliseconds, so it has an impact.


Such setup is used for redundancy because there is a single points of 
failure in the "short path". We peer via BGP to both (it's a MPLS VPN 
services). In case the short path goes away, we still have a route over 
"long path". We need sometimes to prefer SP_A, and there is a problem. 
If SP_A decides to switch over to long path due to some problems in 
their core, the latency significantly increases BUT at the same time 
short path is still available and can be used via SP_B. BGP does not 
detect that because routes are perfectly valid learned over both 
providers, we do not have increased AS_PATH or whatever.


How to signal such event and direct traffic over SP_B if SP_A routes 
increase in latency while BGP attributes stay the same ? I am thinking 
of OER, but is this the only way to go ?


As usual there might be some clever knob to play with IPSLA+EEM, don't 
have much experience with EEM hence bit cautious will it handle such 
switchovers reliably. Any experiences would be helpful to hear.


Regards,
Mindaugas

On 2010.10.26 08:56, jack daniels wrote:

Hi guys,

I have a EOSDH as a primary link in which GE is mapped to 4 STM-1

and backup path is another GE Link.

In case 2 STM-1 out of 4 STM-1 in EOSDH fail my routing will not be
aware of that and will not reroute the traffic to backup GE.
This will lead to congestion on Primary link , while backup path not
at all be used.
  Is there any way to work out this issue.
___
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/



___
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] Fun problem affecting only even-numbered ports

[Tim Stevenson]

At 09:00 AM 10/28/2010, Mack McBride uttered:

The 6748-SFP use one Rohini for even and one Rohini for odd ports 
not consecutive, IIRC.

This could vary by revision.  I don't have one handy to check against.
The Janus and SSA are for ports 1-24 and 25-48.


It's even/odd all the way back to the fabric on the 6748-SFP, one 
janus/SSA handles odd ports, the other even ports.


Tim



There are four Rohini on the board, two connected to each Janus/SSA pair.

You can use 'sh int  cap | inc Ports" to list the ports.
And 'sh asic slot " to list the asics.

This is example output of a 6724 which is consecutive.

#sh int Gi1/1 cap | inc Ports
  Ports-in-ASIC (Sub-port ASIC) : 1-24 (1-12)

The first port list is the Janus and SSA.  The second is the Rohini.

#sh asic-version slot 1
Module in slot 1 has 3 type(s) of ASICs
ASIC Name  Count  Version
JANUS  1  (1.0)
  SSA  1  (9.0)
   ROHINI  2  (1.5)

Mack

-Original Message-
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] 
On Behalf Of Benjamin Lovell

Sent: Thursday, October 28, 2010 9:38 AM
To: John Neiberger
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Fun problem affecting only even-numbered ports

Nothing that I can think of. One Super Santa Anna and Janus run ports
1-24 and another pair of them run ports 25-48. One Rohini runs each
consecutive group of 12 ports. The only thing I could guess at is the
path take across the switchbar fabric but I don't recall how we select
FPOE right now.

-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this bizarre
> behavior. At the urging of the TAC engineer, we tried moving receivers
> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a WS-6748-SFP
> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/


___
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/


___
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/





Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759

The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.


___
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] FDDI card for 7200 VXR

[Luan Nguyen]

Hi folks,

Anyone  has a FDDI PA VIP2 card for the 7200VXR series router that I can
buy?

Thanks.

-Luan
___
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] Fun problem affecting only even-numbered ports

[Benjamin Lovell]

Ahh. I was looking at the block diagram for the GE-TX and just assumed  
it was the same for SFP.


Thanx for the correction.

-Ben

On Oct 28, 2010, at 12:10 PM, Tim Stevenson wrote:

On the fiber (SFP) card, ports are indeed mapped in groups of 12  
consecutive odd/12 consecutive even ports per rohini, with 24 odd  
ports on one janus & 24 even ports on the other.


I'd guess you're just running out of replication bandwidth. A bit  
more detail about the traffic pattern etc would help. How many L3  
replications are occurring here, and for what input rate? Ingress or  
egress replication?


As a general rule you should spread the receivers as evenly as  
possible among odd & even ports to spread the replication load.


Hope that helps,
Tim

At 08:37 AM 10/28/2010, Ben Lovell (belovell) uttered:


Nothing that I can think of. One Super Santa Anna and Janus run ports
1-24 and another pair of them run ports 25-48. One Rohini runs each
consecutive group of 12 ports. The only thing I could guess at is the
path take across the switchbar fabric but I don't recall how we  
select

FPOE right now.

-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this  
bizarre
> behavior. At the urging of the TAC engineer, we tried moving  
receivers

> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What  
part of

> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a  
WS-6748-SFP

> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/


___
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/





Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759

The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.



___
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] Fun problem affecting only even-numbered ports

[John Neiberger]

On Thu, Oct 28, 2010 at 10:10 AM, Tim Stevenson  wrote:
> On the fiber (SFP) card, ports are indeed mapped in groups of 12 consecutive
> odd/12 consecutive even ports per rohini, with 24 odd ports on one janus &
> 24 even ports on the other.
>
> I'd guess you're just running out of replication bandwidth. A bit more
> detail about the traffic pattern etc would help. How many L3 replications
> are occurring here, and for what input rate? Ingress or egress replication?
>
> As a general rule you should spread the receivers as evenly as possible
> among odd & even ports to spread the replication load.
>
> Hope that helps,
> Tim

Tim,

We haven't been able to find any drops on the Janus or fabric for this
module. I'd have to tally up the total amount of traffic on this
blade, but my guess is that we're seeing close to 3 or 4 Gbps of
multicast video crossing through that module. I'll verify that later
and let you know.

John
___
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] Fun problem affecting only even-numbered ports

[Jim Getker (getker)]

Actually on this card one Janus handles the even ports, and the other
handles the odd ports.

Jim

-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Ben Lovell
(belovell)
Sent: Thursday, October 28, 2010 11:38 AM
To: John Neiberger
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Fun problem affecting only even-numbered ports

Nothing that I can think of. One Super Santa Anna and Janus run ports  
1-24 and another pair of them run ports 25-48. One Rohini runs each  
consecutive group of 12 ports. The only thing I could guess at is the  
path take across the switchbar fabric but I don't recall how we select  
FPOE right now.

-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this bizarre
> behavior. At the urging of the TAC engineer, we tried moving receivers
> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a WS-6748-SFP
> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/

___
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/

___
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] Fun problem affecting only even-numbered ports

[Keegan Holley]

Must be haunted.  Try it again after Halloween.


On Wed, Oct 27, 2010 at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this bizarre
> behavior. At the urging of the TAC engineer, we tried moving receivers
> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a WS-6748-SFP
> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/
>
>
>
___
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] Fun problem affecting only even-numbered ports

[Mack McBride]

The 6748-SFP use one Rohini for even and one Rohini for odd ports not 
consecutive, IIRC.
This could vary by revision.  I don't have one handy to check against.
The Janus and SSA are for ports 1-24 and 25-48.
There are four Rohini on the board, two connected to each Janus/SSA pair.

You can use 'sh int  cap | inc Ports" to list the ports.
And 'sh asic slot " to list the asics.

This is example output of a 6724 which is consecutive.

#sh int Gi1/1 cap | inc Ports
  Ports-in-ASIC (Sub-port ASIC) : 1-24 (1-12)

The first port list is the Janus and SSA.  The second is the Rohini.

#sh asic-version slot 1
Module in slot 1 has 3 type(s) of ASICs
ASIC Name  Count  Version
JANUS  1  (1.0)
  SSA  1  (9.0)
   ROHINI  2  (1.5)

Mack

-Original Message-
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Benjamin Lovell
Sent: Thursday, October 28, 2010 9:38 AM
To: John Neiberger
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Fun problem affecting only even-numbered ports

Nothing that I can think of. One Super Santa Anna and Janus run ports  
1-24 and another pair of them run ports 25-48. One Rohini runs each  
consecutive group of 12 ports. The only thing I could guess at is the  
path take across the switchbar fabric but I don't recall how we select  
FPOE right now.

-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this bizarre
> behavior. At the urging of the TAC engineer, we tried moving receivers
> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a WS-6748-SFP
> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/

___
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/

___
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] ASR-9000 and IPSEC

[Rubens Kuhl]

The problem with 7600 is the limited throughput of the IPSEC module
for SPA-600. It would require a grand total of 16 IPSEC modules in 8
SPA-600 carriers to achieve throughput goals...


Rubens

On Thu, Oct 28, 2010 at 1:40 PM, Benjamin Lovell  wrote:
> I was not aware that there was an IPSEC blade for the 9K like there is for
> the 7600. If there is not then obviously your would need to put something
> like an ASA in-line but then it should work fine.
>
> -Ben
>
> On Oct 27, 2010, at 6:36 PM, Rubens Kuhl wrote:
>
>> After reading ASR-9000 specs no CCO, seems to me that is not possible
>> to do Layer 2 transport with IPSEC with it, either using L2TPv3 (like
>> ASR-1000) or VPLS (like 7600). Is that really true, or am I missing
>> something ?
>>
>>
>> Rubens
>> ___
>> cisco-nsp mailing list  cisco-...@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>

___
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] Fun problem affecting only even-numbered ports

[Tim Stevenson]

On the fiber (SFP) card, ports are indeed mapped in groups of 12 
consecutive odd/12 consecutive even ports per rohini, with 24 odd 
ports on one janus & 24 even ports on the other.


I'd guess you're just running out of replication bandwidth. A bit 
more detail about the traffic pattern etc would help. How many L3 
replications are occurring here, and for what input rate? Ingress or 
egress replication?


As a general rule you should spread the receivers as evenly as 
possible among odd & even ports to spread the replication load.


Hope that helps,
Tim

At 08:37 AM 10/28/2010, Ben Lovell (belovell) uttered:


Nothing that I can think of. One Super Santa Anna and Janus run ports
1-24 and another pair of them run ports 25-48. One Rohini runs each
consecutive group of 12 ports. The only thing I could guess at is the
path take across the switchbar fabric but I don't recall how we select
FPOE right now.

-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:

> This is a good one. I'm working with TAC on it, but I thought i'd
> share it here, too, just because it's so unusual. We're seeing
> intermittent drops on a multicast video stream and we haven't been
> able to determine why. This is the second time we've seen this bizarre
> behavior. At the urging of the TAC engineer, we tried moving receivers
> to different ports and noticed that we only see the drops when the
> receiver is connected to even-numbered interfaces! Odd-numbered
> interfaces are not affected.
>
> This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
> the 6748 linecard architecture is responsible for a behavior
> difference between odd- and even-numbered ports? This is a WS-6748-SFP
> with a DFC-3BXL.
>
> Any thoughts?
> ___
> 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/


___
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/





Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759

The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.


___
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] pixhelp

[Michael K. Smith - Adhost]

Hey Deric:


> -Original Message-
> From: Deric Kwok [mailto:deric.kwok2...@gmail.com]
> Sent: Wednesday, October 27, 2010 3:45 PM
> To: Michael K. Smith - Adhost; tn...@internode.com.au
> Cc: Cisco Network Service Providers
> Subject: Re: [c-nsp] pixhelp
> 
> Hi
> 
> The verion is Cisco PIX Firewall Version 6.3(1)
> 
> I used the same ssh logon and pw info. It can use ssh but won't work
https
> 
> The blank one user and pw won't work
> 
> How can I setup the https logon and pw?
> 
> Thank you so much
> 
> 

You will be using the PDM, sorry.  :-)

! If you want to use https
aaa authentication secure-http-client
! you can also put a server in before LOCAL below if you are using
TACACS
aaa authentication http console LOCAL 
http server enable
http  

Mike



___
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] VLAN-based EoMPLS

[Lee Riemer]

Can you see the far end in your arp table?

On 10/28/2010 1:46 AM, Manaf Al Oqlah wrote:


Hi,

I have established an EoMPLS circuit on ME3750 switches as below. everything 
seems to be working fine as my virtual circuit is UP
but my problem is that I cant ping IP address CE02 from CE01

PC01---CE01---PE01---PE02---CE02---PC02

I have applied the following configuration on PE01&  PE02 ES ports

interface loopback 0
ip address 1.1.1.1 255.255.255.255
!
interface GigabitEthernet1/1/1
description to PE02
  ip address 10.0.0.1 255.255.255.252
  mpls ip
!
interface GigabitEthernet1/1/2
description to CE01
switchport mode access
switchport access vlan 100
!
vlan 100
!
interface vlan 100
xconnect 2.2.2.2 100 encapsulation mpls

where could me my problem!

Regards,
Manaf Al Oqlah
___
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/


--
Lee Riemer
Director of Technical Operations
Bestline Communications, L.P.
Voice: 1+512.328.9095
Fax: 1+512.328.0038

___
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] ASR-9000 and IPSEC

[Benjamin Lovell]

I was not aware that there was an IPSEC blade for the 9K like there is  
for the 7600. If there is not then obviously your would need to put  
something like an ASA in-line but then it should work fine.


-Ben

On Oct 27, 2010, at 6:36 PM, Rubens Kuhl wrote:


After reading ASR-9000 specs no CCO, seems to me that is not possible
to do Layer 2 transport with IPSEC with it, either using L2TPv3 (like
ASR-1000) or VPLS (like 7600). Is that really true, or am I missing
something ?


Rubens
___
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/


___
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] VLAN-based EoMPLS

[Rubens Kuhl]

My 3750ME foo is slowly fading, but are those ports Enhanced ports ?
Only the enhanced ports can be MPLS uplinks.


Rubens


On Thu, Oct 28, 2010 at 4:46 AM, Manaf Al Oqlah  wrote:
>
>
> Hi,
>
> I have established an EoMPLS circuit on ME3750 switches as below. everything 
> seems to be working fine as my virtual circuit is UP
> but my problem is that I cant ping IP address CE02 from CE01
>
> PC01---CE01---PE01---PE02---CE02---PC02
>
> I have applied the following configuration on PE01 & PE02 ES ports
>
> interface loopback 0
> ip address 1.1.1.1 255.255.255.255
> !
> interface GigabitEthernet1/1/1
> description to PE02
>  ip address 10.0.0.1 255.255.255.252
>  mpls ip
> !
> interface GigabitEthernet1/1/2
> description to CE01
> switchport mode access
> switchport access vlan 100
> !
> vlan 100
> !
> interface vlan 100
> xconnect 2.2.2.2 100 encapsulation mpls
>
> where could me my problem!
>
> Regards,
> Manaf Al Oqlah
> ___
> cisco-nsp mailing list  cisco-...@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

___
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] Fun problem affecting only even-numbered ports

[Benjamin Lovell]

Nothing that I can think of. One Super Santa Anna and Janus run ports  
1-24 and another pair of them run ports 25-48. One Rohini runs each  
consecutive group of 12 ports. The only thing I could guess at is the  
path take across the switchbar fabric but I don't recall how we select  
FPOE right now.


-Ben

On Oct 27, 2010, at 12:54 PM, John Neiberger wrote:


This is a good one. I'm working with TAC on it, but I thought i'd
share it here, too, just because it's so unusual. We're seeing
intermittent drops on a multicast video stream and we haven't been
able to determine why. This is the second time we've seen this bizarre
behavior. At the urging of the TAC engineer, we tried moving receivers
to different ports and noticed that we only see the drops when the
receiver is connected to even-numbered interfaces! Odd-numbered
interfaces are not affected.

This is on a 7600 with SUP 720-3BXL and a 6748 linecard. What part of
the 6748 linecard architecture is responsible for a behavior
difference between odd- and even-numbered ports? This is a WS-6748-SFP
with a DFC-3BXL.

Any thoughts?
___
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/


___
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] VLAN-based EoMPLS

[Benjamin Lovell]

In "show mpls l2transport vc 100 detail" do you see packet counters 
(send/receive) incrementing on either side? What IOS version are you  
running? Can you post the output from that command from each PE.


-Ben


On Oct 28, 2010, at 2:46 AM, Manaf Al Oqlah wrote:




Hi,

I have established an EoMPLS circuit on ME3750 switches as below.  
everything seems to be working fine as my virtual circuit is UP

but my problem is that I cant ping IP address CE02 from CE01

PC01---CE01---PE01---PE02---CE02---PC02

I have applied the following configuration on PE01 & PE02 ES ports

interface loopback 0
ip address 1.1.1.1 255.255.255.255
!
interface GigabitEthernet1/1/1
description to PE02
ip address 10.0.0.1 255.255.255.252
mpls ip
!
interface GigabitEthernet1/1/2
description to CE01
switchport mode access
switchport access vlan 100
!
vlan 100
!
interface vlan 100
xconnect 2.2.2.2 100 encapsulation mpls

where could me my problem!

Regards,
Manaf Al Oqlah
___
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/


___
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] Routing performance of ME3400

[Eric Van Tol]

> -Original Message-
> From: Garry [mailto:g...@gmx.de]
> Sent: Thursday, October 28, 2010 9:22 AM
> To: Eric Van Tol
> Cc: cisco-nsp@puck.nether.net
> Subject: Re: [c-nsp] Routing performance of ME3400
> 
> On 27.10.2010 16:42, Eric Van Tol wrote:
> > Hello,
> > Check your SDM template - you probably have it set to 'layer-2' when it
> should be 'default' for layer 3 routing.
> 
> Customer confirmed ... did some more performance tests, switch is now
> operating at decent performance ... :)
> 
> Thanks again for the hint! s...@cks though that the option isn't shown in
> the config ...
> 
> -garry

No problem - we ran into this on a few of our switches, too.  I always thought 
it was counterintuitive that they named the Layer 3 SDM 'default' even though 
it really isn't the default SDM template.

-evt

___
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] IOS upgrade on 6500 yields wacky result.

[Drew Weaver]

I noticed that one of our 6500s was running 12.2(17d)SXB and I wanted to 
upgrade it to SXI3.

I did my normal procedure of changing the boot variables and then reloading the 
slave, the slave booted into SXI3 normally so I then forced switchover to the 
slave and the old-master rebooted and came up in SXI3 normally (as I have done 
so many times before). So now I had a system in SSO with 2x Supervisor 720s 
with SXI3.

The switch was up for about maybe an hour, and then I noticed that the ports on 
the (now master) Supervisor 720 were down so I checked and it seems that it 
failed back over to the original active SUP and now the following oddness is 
occurring.

1: The slave sup is now back to 12.2(17d)SXB (???)
2: In sh bootvar I see:

Standby BOOT variable is unobtainable due to IPC error
Standby CONFIG_FILE variable is unobtainable due to IPC error
Standby BOOTLDR variable is unobtainable due to IPC error
Standby Configuration register is 0x2102 unobtainable due to IPC error

3: In show log I see:

.Oct 28 08:12:30.310 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:12:30.310 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:12:30.310 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:12:30.470 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:16:09.237 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:16:09.241 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:16:09.241 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:16:09.241 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:37:13.604 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:37:13.604 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:37:13.604 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]
.Oct 28 08:37:13.604 EST: %HA_CONFIG_SYNC-3-IPC: IPC operation failed for [ cann
ot open standby port ] with error code [ no such port ]

4: The ports on the slave supervisor are up and are passing traffic and routing 
protocols even though it seems that the master and slave are not communicating.

5: at the tail end of the log I see:

Oct 28 08:08:44.362 EST: %PFREDUN-SP-4-PHYSMEM_MISMATCH: Asymmetrical redundant
configuration: Active SP has (524288/65536K) memory, Standby has (458752/65536K)
.
Oct 28 08:08:44.362 EST: %PFREDUN-SP-4-PHYSMEM_MISMATCH: Asymmetrical redundant
configuration: Active RP has (524288/65536K) memory, Standby has (458752/65536K)
.

(they're the same card...)

and

.Oct 28 08:08:57.570 EST: %MLS_RATE-4-DISABLING: The global switching mode is no
w 'truncated'. Disabling the Layer2 Rate Limiters.

It also seems that the slave supervisor in slot 6 is not responding to the 
console, either.

Anyone have any clue what I did wrong here?

Prior to this upgrade this box was up for over 3 years and working fine but I 
needed some new functionality.

-Drew



___
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] Routing performance of ME3400

[Garry]

On 27.10.2010 16:42, Eric Van Tol wrote:
> Hello,
> Check your SDM template - you probably have it set to 'layer-2' when it 
> should be 'default' for layer 3 routing.

Customer confirmed ... did some more performance tests, switch is now
operating at decent performance ... :)

Thanks again for the hint! s...@cks though that the option isn't shown in
the config ...

-garry
___
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] Are these DWDM optics compatible?

[Andrew Gallo]

On 10/27/2010 4:38 PM, Michael K. Smith - Adhost wrote:
> Here is the ITU 100 GHZ grid.
>
> http://www.telecomengineering.com/downloads/DWDM%20ITU%20Table%20-%20100
> %20GHz.pdf
>
> ITU 52 is 35.82.   Whether or not it will work at .92 is moot, IMO.  I
> would tell your vendor to give you optics that follow the ITU grid.  .92
> doesn't show up anywhere in the ITU grid, even at 50 Ghz.  The spectral
> width on the optics is .2nm, but I wouldn't want to be sitting on the
> edge of the acceptable limit.
>
> Mike
>
> --
> Michael K. Smith - CISSP, GSEC, GISP
> Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com
> w: +1 (206) 404-9500 f: +1 (206) 404-9050
> PGP: B49A DDF5 8611 27F3  08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
>
>
>> -Original Message-
>> From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-
>> boun...@puck.nether.net] On Behalf Of Steven Raymond
>> Sent: Wednesday, October 27, 2010 11:20 AM
>> To: Cisco Network Service Providers
>> Subject: [c-nsp] Are these DWDM optics compatible?
>>
>> Ordered part number DWDM-X2-35.82 , and received part labeled DWDM-
>> X2-35.92 (non-Cisco branded X2 optics).  Vendor says oh they are close
>> enough to work, there's a .2nm working range for ITU channel 52
> signaling.
>> In fact they claim that DWDM-X2-35.82 is the very same part, just with
> a
>> different (or in this case typoed) label on it.  Does anyone have
> experience to
>> confirm or reject the vendor's claim?
>>
>> Looking here:
>> http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6576/data
>> _sheet_c78_489725.html
>> I can almost buy their argument, and google perhaps confirms by
> returning
>> "No results found for "DWDM-X2-35.92"."  Makes me wonder if all these
>> parts are simply the same hardware, and upon ordering they simply tune
> the
>> frequency into an eprom for whatever was ordered, apply a label and
> ship it
>> out?
>>
>> Thanks!
>>
>>
>>
>> ___
>> 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/
> ___
> 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/
>
The tolerances are tight, sure enough, but should work.  We've seen
Cisco branded optics start drifting outside of the channel plan.  If
this starts happening, the filters will clip the signal and the receiver
will start complaining about low power.
___
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/