[c-nsp] cisco-nsp Digest, Vol 103, Issue 17
Mostafa Feteha
mfeteha at juniper.net
Sun Jun 5 02:06:38 EDT 2011
P
Thanks
Mostafa Feteha
--------------------------
Sent from my BlackBerry Wireless Handheld
----- Original Message -----
From: cisco-nsp-bounces at puck.nether.net <cisco-nsp-bounces at puck.nether.net>
To: cisco-nsp at puck.nether.net <cisco-nsp at puck.nether.net>
Sent: Sat Jun 04 21:54:34 2011
Subject: cisco-nsp Digest, Vol 103, Issue 17
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: EoMPLS Remote Port Shutdown (Arie Vayner (avayner))
2. DWDM Optics use (Keegan Holley)
3. Re: IPv6 Prefix inbound filter (Mark Tinka)
4. Re: IPv6 Prefix inbound filter (Mark Tinka)
5. Re: IPv6 Prefix inbound filter (Mark Tinka)
6. Re: EoMPLS Remote Port Shutdown (Mark Tinka)
7. Re: DWDM Optics use (Brandon Applegate)
8. Re: DWDM Optics use (Keegan Holley)
----------------------------------------------------------------------
Message: 1
Date: Sat, 4 Jun 2011 19:54:30 +0200
From: "Arie Vayner (avayner)" <avayner at cisco.com>
To: "Yuri Bank" <yuribank at gmail.com>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] EoMPLS Remote Port Shutdown
Message-ID:
<FDD1CDB3FB499E4087CC7670BBCA22C60456B555 at XMB-AMS-101.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Yuri, what is the CE device you are using? Does it have E-LMI support?
Tnx
Arie
From: Yuri Bank [mailto:yuribank at gmail.com]
Sent: Friday, June 03, 2011 21:38
To: Arie Vayner (avayner)
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] EoMPLS Remote Port Shutdown
I'm trying to achieve a function similar to LFP,link pass through (this
is what its called on Alcalu Ethernet/MPLS switches). If one side of the
psudowire is down, I would like the adjacent port to also go down to
prevent black holing traffic. Obviously lowering hold timers, or using
PFR with IP SLA could prevent such behaviors, but LFP is a nice feature
to have.
-Yuri
On Fri, Jun 3, 2011 at 7:51 AM, Arie Vayner (avayner)
<avayner at cisco.com> wrote:
Yuri,
7600 support Remote Port Shutdown per the below documentation reference,
but it does not actually shutdown the whole port, but actually used
E-OAM to signal to the CPE that the PW is down...
What are you trying to achieve?
Thanks
Arie
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Yuri Bank
Sent: Thursday, June 02, 2011 22:00
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] EoMPLS Remote Port Shutdown
Does anyone know if this feature is in fact supported on the
7600(RSP720-3C-GE)?
There seems to be conflicting information between the Feature Navigator
and other related documents.
According to this article, it is supported as of 12.2(33)SRB, for the
7600.
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_remote
prtshtdn.html
<http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_remot
e%0Aprtshtdn.html>
I was curious if anyone knows off hand, or has the resources to easily
find out.
-Yuri
_______________________________________________
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/
------------------------------
Message: 2
Date: Sat, 4 Jun 2011 14:47:38 -0400
From: Keegan Holley <keegan.holley at sungard.com>
To: Cisco NSPs <cisco-nsp at puck.nether.net>
Subject: [c-nsp] DWDM Optics use
Message-ID: <BANLkTimVT_K83wa4VMYc4S8iKP+dQ97xFg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
I'm struggling with a use for DWDM optics. I understand the concept of
DWDM/CWDM and phase shifting to create more links over a single fiber. Once
that is done the ASIC/FPGA bandwidth allocated to the port remains the same,
correct? So if I create multiple 1G connections on a single port with these
magic sfp's am I still limited by the 1g/2g chip in the device. Are all the
logical connections forced to be sub-rate? I know the larger equipment
handles this differently, so I'm only concerned with the 3750/3560 size
boxes.
Thanks,
------------------------------
Message: 3
Date: Sun, 5 Jun 2011 03:37:26 +0800
From: Mark Tinka <mtinka at globaltransit.net>
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IPv6 Prefix inbound filter
Message-ID: <201106050337.26635.mtinka at globaltransit.net>
Content-Type: text/plain; charset="us-ascii"
On Friday, June 03, 2011 11:04:38 PM arulgobinath emmanuel
wrote:
> I thought the memory requirement might high but the total
> memory for /48 range routes and couple of static routes
> [show memory summary | inc IPv6] summing up only around
> ~4mb
There's only +/-6,000 IPv6 entries in the BGP routing table
today.
Of course, expect this number to grow - it's grown more in
the past 12 months than it has in the last couple of years.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20110605/18620d75/attachment-0001.pgp>
------------------------------
Message: 4
Date: Sun, 5 Jun 2011 03:33:23 +0800
From: Mark Tinka <mtinka at globaltransit.net>
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IPv6 Prefix inbound filter
Message-ID: <201106050333.27565.mtinka at globaltransit.net>
Content-Type: text/plain; charset="us-ascii"
On Friday, June 03, 2011 06:55:38 PM Justin M. Streiner
wrote:
> That said, there are some
> people who don't filter (much), so it's not unusual to
> see smaller prefixes show up in the global v6 view.
I suppose old habits die very hard!
Clearly, v4 hasn't taught some of us anything.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20110605/bd2cd0b4/attachment-0001.pgp>
------------------------------
Message: 5
Date: Sun, 5 Jun 2011 03:35:04 +0800
From: Mark Tinka <mtinka at globaltransit.net>
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IPv6 Prefix inbound filter
Message-ID: <201106050335.05174.mtinka at globaltransit.net>
Content-Type: text/plain; charset="us-ascii"
On Friday, June 03, 2011 10:25:30 PM arulgobinath emmanuel
wrote:
> Hi all,
> what is the current industry practices in IPv6 inbound
> prefix filter is it /32 or /48 ? or it depends on the
> global IPv6 prefix growth vs memory ?
We filter up to a /48.
/48 tends to be the informally agreed limit, but different
networks may have varying strategies.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20110605/aed06d8e/attachment-0001.pgp>
------------------------------
Message: 6
Date: Sun, 5 Jun 2011 03:43:55 +0800
From: Mark Tinka <mtinka at globaltransit.net>
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] EoMPLS Remote Port Shutdown
Message-ID: <201106050343.56071.mtinka at globaltransit.net>
Content-Type: text/plain; charset="us-ascii"
On Saturday, June 04, 2011 02:38:22 AM Yuri Bank wrote:
> I'm trying to achieve a function similar to LFP,link pass
> through (this is what its called on Alcalu Ethernet/MPLS
> switches). If one side of the psudowire is down, I would
> like the adjacent port to also go down to prevent black
> holing traffic.
My memory is rather vague on this, but I think I recall a
customer once asking us about this capability. We checked
with our SE and were told support wasn't there for this
feature.
An LFP search, at the time, turned up something about this
being supported on Cisco's ONS platforms, which I'm certain
isn't what you're looking for.
Again, it's been a very long time since I last talked about
this with my SE, but if memory serves, that was the
conversation.
Of course, things could be much more different now.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20110605/3074fc41/attachment-0001.pgp>
------------------------------
Message: 7
Date: Sat, 4 Jun 2011 16:45:16 -0400 (EDT)
From: Brandon Applegate <brandon at burn.net>
To: Keegan Holley <keegan.holley at sungard.com>
Cc: Cisco NSPs <cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] DWDM Optics use
Message-ID: <alpine.DEB.2.00.1106041635510.2039 at orbital.burn.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Sat, 4 Jun 2011, Keegan Holley wrote:
> I'm struggling with a use for DWDM optics. I understand the concept of
> DWDM/CWDM and phase shifting to create more links over a single fiber. Once
> that is done the ASIC/FPGA bandwidth allocated to the port remains the same,
> correct? So if I create multiple 1G connections on a single port with these
> magic sfp's am I still limited by the 1g/2g chip in the device. Are all the
> logical connections forced to be sub-rate? I know the larger equipment
> handles this differently, so I'm only concerned with the 3750/3560 size
> boxes.
>
Hmm, I may be misunderstanding - but I think you are misunderstanding how
DWDM tuned optics works. A 1g or 10g DWDM optic is still a singe 1 or 10
interface. It's just that that transmit laser is tuned to a channel (i.e.
1546.12).
Router#sh int tenGigabitEthernet 7/1 | inc media
Full-duplex, 10Gb/s, media type is DWDM-46.12
The reason you may need this is to connect this port directly to a
(R)OADM. There are (at least) two ways on the DWDM transport side to
handle this:
a) Use a *sponder (transponder = 1:1, muxponder = n:1, etc). You can use
'grey' optics now (i.e. good ole SX/LX etc). These cards on the DWDM side
are expensive though.
or
b) Buy DWDM optics, and go directly into the mux/demux on the DWDM.
We are doing option b) in parts of our network because the cost of a) was
too much, and these links aren't going to do any moving around or going
away any time soon.
Again, apologies if I've misunderstood you.
--
Brandon Applegate - CCIE 10273
PGP Key fingerprint:
7407 DC86 AA7B A57F 62D1 A715 3C63 66A1 181E 6996
"SH1-0151. This is the serial number, of our orbital gun."
------------------------------
Message: 8
Date: Sat, 4 Jun 2011 16:53:53 -0400
From: Keegan Holley <keegan.holley at sungard.com>
To: Brandon Applegate <brandon at burn.net>
Cc: Cisco NSPs <cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] DWDM Optics use
Message-ID: <BANLkTinN6dB7v2vBZWtAOXLLuWg5X9zm_Q at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
No this is exactly what I was looking for. I can definitely understand the
usefulness of having your routers transmit on a specific channel. Thanks!
2011/6/4 Brandon Applegate <brandon at burn.net>
> On Sat, 4 Jun 2011, Keegan Holley wrote:
>
> I'm struggling with a use for DWDM optics. I understand the concept of
>> DWDM/CWDM and phase shifting to create more links over a single fiber.
>> Once
>> that is done the ASIC/FPGA bandwidth allocated to the port remains the
>> same,
>> correct? So if I create multiple 1G connections on a single port with
>> these
>> magic sfp's am I still limited by the 1g/2g chip in the device. Are all
>> the
>> logical connections forced to be sub-rate? I know the larger equipment
>> handles this differently, so I'm only concerned with the 3750/3560 size
>> boxes.
>>
>>
> Hmm, I may be misunderstanding - but I think you are misunderstanding how
> DWDM tuned optics works. A 1g or 10g DWDM optic is still a singe 1 or 10
> interface. It's just that that transmit laser is tuned to a channel (i.e.
> 1546.12).
>
> Router#sh int tenGigabitEthernet 7/1 | inc media
> Full-duplex, 10Gb/s, media type is DWDM-46.12
>
> The reason you may need this is to connect this port directly to a (R)OADM.
> There are (at least) two ways on the DWDM transport side to handle this:
>
> a) Use a *sponder (transponder = 1:1, muxponder = n:1, etc). You can use
> 'grey' optics now (i.e. good ole SX/LX etc). These cards on the DWDM side
> are expensive though.
>
> or
>
> b) Buy DWDM optics, and go directly into the mux/demux on the DWDM.
>
> We are doing option b) in parts of our network because the cost of a) was
> too much, and these links aren't going to do any moving around or going away
> any time soon.
>
> Again, apologies if I've misunderstood you.
>
> --
> Brandon Applegate - CCIE 10273
> PGP Key fingerprint:
> 7407 DC86 AA7B A57F 62D1 A715 3C63 66A1 181E 6996
> "SH1-0151. This is the serial number, of our orbital gun."
>
>
>
>
------------------------------
_______________________________________________
cisco-nsp mailing list
cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
End of cisco-nsp Digest, Vol 103, Issue 17
******************************************
More information about the cisco-nsp
mailing list