As a general advice, avoid stacking unless more ports are needed in the same IDF. Definitely I wouldn't span stacked switches across multiple floors or buildings. Let L3 do it's job, the smaller your L2 domains are, the better.
Why not keeping both? :p
7000-series should be better particularly on the software side, and pretty much mandatory if you want to be seriously in business with IPv6 (IIRC, no SLAAC on the 6450 and 6610... or some other things IPv6-related).
The easiest way that I can think of is to use a linux box running Avahi with an interface on every VLAN where you want to listen and repeat the mDNS queries to. Be careful with the firewall rules on this machine, or it can be used to "jump" between networks.
I've used two Sunon MagLev KDE1204PKVX with two small capacitors between +12V and GND to smooth out the PWM noise... it's not silent by any means but it's bearable when you sit beside it and basically silent when closed inside a rack.
@dontwanna The serial cable is... well, serial :) You'd have to connect it to a serial port of you computer, not on the network (that's the management interface, a NIC essentially bound to the switch CPU); if you have a modern computer that doesn't have a serial port you can use a USB-DB9...
Can you specify the ONT model number?
The ones I've seen are basically an OpenWRT-stick packaged inside a SFP module, so as long as it's plugged in it has an interface up; the management interface runs on the native VLAN and the broadband connection is available on one (or more) tagged VLAN...
Yep, use a spare VLAN without a router interface defined on it, use it as the native/untagged VLAN (if your ethernet handoff doesn't require a tagged VLAN, I don't know the details of the FiOS offer) on a port connected to the ISP and as a tagged VLAN on the router-on-a-stick ;)
That's strange, unless your meter is measuring the apparent power... at low load I've seen that the PSU has a slightly poor power factor; mine draws around 30-35W of real power (ie. the one that the power company bills the user for, at least for domestic usage here in Italy) at idle w/o anything...
Remove "route-only" from your configuration.
http://docs.ruckuswireless.com/fastiron/08.0.50/fastiron-08050-commandref/GUID-D1A2B680-D9F4-4672-8C1B-072290462513.html
Because its configuration GUI won't let you configure DHCP scopes outside the networks that the firewall manages.
Technically the daemons underneath can do it, but there's no way to configure them accordingly; it's pretty easy however to install a small linux box with a DHCP server and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.