ahebert at pubnix
Mar 21, 2012, 5:33 AM
Post #4 of 4
As a Metro provider, trying to find devices to offer 802.1ad at the
customer (CE's) is a pricey proposition...
( Our pipes can pass thru anything from dark fiber to cup&string
The way the vendor are separating the 802.1ad, 802.1ah and MPLS
features from the 802.1Q is getting annoying.
Beside MPLS, the other are quite static in term of setup and from
my experience with FPGA, this shouldn't be a stopping block.
Right now the cheapest device for a CE is a Cisco ME3400EG ( 4 x
1Gbps ) at ~$4k each :( while 28 ports 10Gb switches only cost ~$7k.
PS: As for MPLS, the ~$10k tax most Vendor ask to have it in Core
devices is sickening...
Alain Hebert ahebert [at] pubnix
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
On 03/14/12 05:57, Nick Hilliard wrote:
> On 14/03/2012 08:46, Maxime Baudin wrote:
>> Finer granularity.....on a group of ports... Still searching
> This sort of thing is generally a hardware limitation caused by the fact
> that all the ethernet ports in a port group are controlled by a single
> asic. There are lots of limitations like this on the FI boxes. One that
> particularly annoys me is that sflow conflicts with port mirroring. i.e.
> if you need to monitor a single port in a port group, you need to disable
> sflow on all the ports in that port group. I've had to set up scripting to
> selectively re-enable sflow in this situation because it's caused me a lot
> of grief.
> foundry-nsp mailing list
> foundry-nsp [at] puck
foundry-nsp mailing list
foundry-nsp [at] puck