SPB 802.1aq switches....
Posted: Thu Aug 18, 2016 1:03 pm
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 ;)
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 ;)