I’m attempting to deploy a network to a large business park. I may accidentally get some residential customers, but most customers will be businesses. The terrain is large, flat, and covers a couple of sq miles. I have space on a nearby tower, and am ready to deploy. The question is;
Business customers want fixed IP addresses and sometimes will want a /28 network delivered to them, or multiples of networks. So, I was going to break this down into a Vlan per Static IP address or requested network. Once I send a Vlan Trunk into the CMM, how does the CMM switch know which VLAN to send to which AP, and once the AP has the info, how the AP know which SM to send only that VLAN info to. And, the AP, when communicating to the SM, must be smart enough to strip off the 802.1q headers to send it to the SM’s. Unless each customer has an 802.1Q compatible router, which probably isn’t going to be the case. I have a feeling I’m making this more complex than it needs to be, but nobody’s been able to answer this at the local Canopy dealer. They are radio guys more than network guys, and much beyond flat ethernet is out of their core expertise.
Help please.
jherraghty wrote: I’m attempting to deploy a network to a large business park. I may accidentally get some residential customers, but most customers will be businesses. The terrain is large, flat, and covers a couple of sq miles. I have space on a nearby tower, and am ready to deploy. The question is;
Business customers want fixed IP addresses and sometimes will want a /28 network delivered to them, or multiples of networks. So, I was going to break this down into a Vlan per Static IP address or requested network. Once I send a Vlan Trunk into the CMM, how does the CMM switch know which VLAN to send to which AP, and once the AP has the info, how the AP know which SM to send only that VLAN info to. And, the AP, when communicating to the SM, must be smart enough to strip off the 802.1q headers to send it to the SM’s. Unless each customer has an 802.1Q compatible router, which probably isn’t going to be the case. I have a feeling I’m making this more complex than it needs to be, but nobody’s been able to answer this at the local Canopy dealer. They are radio guys more than network guys, and much beyond flat ethernet is out of their core expertise.
Help please.
Hi,
AFAIK CMM didn't support 802.1q trunk, so CMM act like transparant switch n you must use manageable switch after the CMM n enable one port as 802.1q
so configuration :
Manageable Switch --- CMM ---- AP --- SM
so AP act like manageable switch too, that trunk to manageable switch, the configuration same with if you trunk between two manageable switch.
maybe you can download the tutorial at :
http://ben.cbccgroup.com/filez/
regards,
mrdlnf
Mrdlnf,
I downloaded the tutorial you directed me to, and saw all kinds of Vlan stuff I haven’t seen before on the Canopy Web GUI. So…I went back to the SM and under status, picked off this nugget…
CANOPY 3.1.5 Sep 06 2002 13:31:09 SM
Apparently the Eval unit I was given has 3 year old software. I didn’t notice that before. I haven’t fired up the AP in a week, but I bet I’ll I get something similar, as I’ve never seen anything about Vlans on it either. As I said before, my distributor is hip to radio’s, but definitely not a network guy.
Can you point me in the right direction to get thee software updated?
Thanks for yr help so far.
jherraghty wrote: Mrdlnf,
I downloaded the tutorial you directed me to, and saw all kinds of Vlan stuff I haven't seen before on the Canopy Web GUI. So.....I went back to the SM and under status, picked off this nugget..
CANOPY 3.1.5 Sep 06 2002 13:31:09 SM
Apparently the Eval unit I was given has 3 year old software. I didn't notice that before. I haven't fired up the AP in a week, but I bet I'll I get something similar, as I've never seen anything about Vlans on it either. As I said before, my distributor is hip to radio's, but definitely not a network guy.
Can you point me in the right direction to get thee software updated?
Thanks for yr help so far.
your software is very old :-)
try to upgrade to the latest software.
Moto recommended upgrade path like this :
3.x --> 4.x ---> 6.1 ---> 7.0 -- via 7.1 or direct to--> 7.2
the software you can download at :
http://motorola.canopywireless.com/soft ... hp?catid=1
make sure you download software update for CNUT (CNUT packages)
you need CNUT software to upgrade the unit, n can be downloaded at :
http://motorola.canopywireless.com/soft ... hp?catid=4
regards,
mrdlnf
Even with the old software the Canopy radios will pass 802.1q tagged packets - acting as a normal 2-port bridge. you will, or course, need something that will tag/untag the packets like a a VLAN aware NIC of switch in the devices you plan to communicate with.
If you upgrade to new software the SM’s will tag/untag packets as you specify at the subscriber location. It is a good idea then to have a router at the host end that will also tag/untag packets (SM’s can be set up to pass multiple VID’s but will only tag/untag one VID, at least from my experience so far). You can then leave all of your Ap’s and managment gear on one managment VLAN.
On my network, I have all of my tower sites on separate VLAN’s - for a couple of reasons. It reduces the size of the broadcast domain, and it increases the managability of the network - smaller zones to track down a possible threat in. I also have a few industrial customers that wanted only network transport instead of internet service (say from an office in town to a remote facility) and I can give them a private VLAN (so everything looks trasnparent to them).
If you have any specific VLAN questions don’t hesitate to ask. I have learned a lot about them over the last couple of years.
Aaron
All,
Have a VLAN problem with Canopy Advantage SM 5700’s… we put a default VID of 1 (unused), a management VID of 10 (10.10.x.x), and a public IP address VLAN ID of 98 (70.x.x.x). Dynamic learning of VLAN’s can be ON or OFF, as soon as we reboot an SM, it loses all the VLAN information except the permanet VID of 1, which makes us lose management capability and we lose our clients on the other end with real internet IP’s since the SM no longer passes VID 98.
Our topology is following; Cisco 4006 switch with VLAN’s 1, 10, 98… we can plug in a laptop and give it a 10.10.x.x (VID 10) or 70.x.x.x (VID 98) and all is good. We have 6 Canopy Advantage 5750 AP’s on the roof hooked to a CMMicro down to the Cisco 4006 trunk port. SM’s then connect to the AP’s on the roof and a variety of things can be plugged into an SM… Tropos Outdoor AP (which is VLAN aware/and tags), end user equipment (switch, router, PC).
NOTE: just talked to Motorola tech support and told us configuration source mush be set to SM (only) not BAM or BAM+SM… need to do some research on what this setting does to VLAN’s but apparently it was our problem… anyone done any advanced VLAN stuff with Canopy like this?
Hi,
tlangham wrote: we put a default VID of 1 (unused), a management VID of 10 (10.10.x.x), and a public IP address VLAN ID of 98 (70.x.x.x). Dynamic learning of VLAN’s can be ON or OFF, as soon as we reboot an SM, it loses all the VLAN information except the permanet VID of 1, which makes us lose management capability and we lose our clients on the other end with real internet IP’s since the SM no longer passes VID 98.
Our topology is following; Cisco 4006 switch with VLAN’s 1, 10, 98… we can plug in a laptop and give it a 10.10.x.x (VID 10) or 70.x.x.x (VID 98) and all is good. We have 6 Canopy Advantage 5750 AP’s on the roof hooked to a CMMicro down to the Cisco 4006 trunk port. SM’s then connect to the AP’s on the roof and a variety of things can be plugged into an SM… Tropos Outdoor AP (which is VLAN aware/and tags), end user equipment (switch, router, PC).
can u give the full your vlan config? you said that your already put VID 1,10,98 on VLAN membership at SM, but what untagged VID in VLAN config page? n what frame type that you assign (all frames or tagged only or untagged only --> this option only available at 7.2.9, at previous software there is only enable/disable allow only tagged)
regards,
mrdlnf
We finally talked to someone at Motorola who knew VLAN’s on Canopy and enough VLAN on Cisco to make a difference. We then talked to Tropos enough to find out their VLAN setup/rules… enough to find out that although the PRINCIPAL of VLAN’s never changes, the implementation per vendor varies greatly. Apparently VLAN 1 is VERY important to Canopy, and although we had on on the switch by default, we weren’t using it for anything and it wasn’t on our trunk port… which was problem #1. Then there were a few Canopy config issues… check this box, uncheck this other box on a seemingly unrelated other page. BAM! Now it all works save we can only manage the Canopy equipment from VLAN 1 which is kind of a pain since our NAT’d (default client) VLAN is VLAN 10. Anyway, thanks for the help from the forum folks we contacted, etc. You’re all great.