SPB 802.1aq switches....

[rebelwireless]

bringing this one up again. How about SPB 802.1aq?

A couple of cases for this.
a) wasting public IP addresses really sucks. A fully routed network wastes public IP addresses somehow. Either with the gw, net, and broadcast addresses on the AP, the backhaul /29-/30 networks (unless you use some private addresses here). waste of a limited commodity.

b) IP address management becomes a bit complicated and inflexible. Once the network is deployed, it's pretty difficult to change up IP ranges used for various things.

c) even on private networks (100.64/10), subnet management is extra effort that takes away from running your company.

d) NAC is hard/manual on routed networks. on an SPB network, something like packetfence could run your wISP. No keeping track of MAC addresses, just a simple login to get authenticated and get a DHCP reserved IP address in the proper network range for that particular client. Add an 802.1x device at the CPE for business customers to tighten things up, residential would be good enough just getting put into a residential VLAN and having a DHCP reservation to their MAC.

e) No more EoIP, GRE, MPLS/VPLS, or bridged VLANs for VPN's. an iSID works like a VPLS id and is an instant (sub 100ms usually) VPN between any number of points.

f) imagine a tower site with nothing but a Netonix Switch w/ SPB and a few batteries +radios. No routers, no routes.

g) top-tier recovery times for broken links. SPB is as fast or faster than OSPF+BFD and discovering down links, and vastly faster re-convergence times.

the list goes on. SPB is eating MPLS for lunch in modern systems. If Netonix can be the first to put out an SPB capable switch for the masses... you'd have to hire a few people ;)

[Dave]

thanks for your suggestion...I will look into it.

[mike99]

SPB or trill, that would be awsome but like I already writed for trill, netonix don't do switch chip and I doubt vitesse support any of the two protocol. From what I saw, seem like only Avaya and HP support it but at software level, seem like IP Infusion also support it in ZebOS (new routing deamon replacing Quagga for MPLS signaling support on Ubnt Edgerouter line with probably a custom kernel since linux currently, last time I checked, don't support MPLS forwarding).

http://www.ipinfusion.com/products/zebo ... hernet/SPB

Seem like the're work by Avaya for SPB support on OpenVSwitch
http://openvswitch.org/support/ovscon20 ... attach.pdf

[quantumx]

This would be a game changer.....

[rebelwireless]

Avaya's support for openvswitch and spb is only to allow openvswitch to be an endpoint. No actual spb support.

As far as zebos, it completely replaces iptables.

I can't find anything on whether vitesse supports spb or not.

[mike99]

Seem like Broadcom and Marvell support it, but only and high end switch for data center (10 and 40 Gb/s for broadcom and 10/40/100 Gb/s for Marvell).

Enables spanning-tree-free and CLOS-style network topologies through TRILL, SPB and ECMP with SmartHash™ technology
https://www.broadcom.com/products/Switc ... 850-Series
https://www.broadcom.com/collateral/pb/56850-PB03-R.pdf

Other key features include VPWS, IP-VPN, MPLS LER/LSR, IEEE 802.1ad Provider Bridging (QinQ), Fiber Channel over Ethernet (FCoE), Priority Flow Control (PFC), Edge Virtual Bridging (VEPA/Multichannel), and Shortest Path Bridging (SPB)
http://www.marvell.com/switching/assets ... 0brief.pdf

Marvell have 2.5 Gb/s switch on the Prestera DX line that support. Maybe it could be affordable and 2.5 Gb/s SFP are widespread and cheap. I personnaly think that 2.5 Gb/s could be a good alternative if 10Gb/s switch cost too much.
http://www.marvell.com/switching/prestera-dx/

[russw@countrynet.co.nz]

Hi,
Yes 802.1AQ Shortest path bridging SPB is what is needed. From PBBR provider backbone bridging... we don't need Cisco leveraging of ancient TRILL and MPLS designed to overcome the cpu overload on frame relay before LSI large scale integration..... a 1980's computer development.. That's 40 years gone....
Russ