Dear all,
I am quite new to this products(Canopy). Though its very easy to install a link in canopy, yet I am facing some problems as the network is growing up. I need your guidance to design a smooth network. I have few queries…
looking forward for some positive response…
thank you
the first query is : how much SMs does one AP (AP2450APBC) can support??
Theoretically 253…realaisticly…around 100 give or take few depending on your bandwidth profiles per SM.
I want to monitor the bandwidth of my customer’s end {MRTG GRAPH}. how should i configure the SM??
After applying VLAN in my network I am unable to access SM from local machine. For any change in SMs configuration I have to access them through my APs… how to resolve this issue? VLANs are working fine…
Software versions are changing frequently. I dont have PRIZM. APs and Backhauls can be upgraded from any point of my network, but how to deal with all the SMs which are distributed as many as 70 remote places? How can I upgrade them? Till 8.1.5 i was doing it by visiting those places…but things has become very tough now… 
Download and use CNUT to remotely update your Canopy APs,SMs,BHs,etc. It works great.
You probably cannot access the SM locally because you have the mangement ID set to a value of 1. This means that the SM will open its web interface only when it sees an Ethernet Frame with a VID of 1.
Suppose your SM is set with a VID of 100. You could also set the management ID of that SM to 100 to allow for local access, but then you would not be able to access the SM via the AP as a LUID. There is a trade-off here.
You could keep the example SM at a VID of 100, and keep its Management VID set to 1. This would allow access from the AP’s, and in addition you could purchase a VLAN aware NIC. Set the NIC’s properties to tag its outbound Ethernet Frames with a VID of 1, and then you would be able to access the SM locally.
while enabling auto update in one of my AP i got following error message…
05/07 15:38:23 INFO CANOPY82_DES_V2.pkg2 loaded.
09/05/07 15:38:23 INFO Starting Update Process …
09/05/07 15:38:23 INFO Using Active FTP for File Transfer
09/05/07 15:38:23 INFO Queue AP:172.16.8.53 enable SM autoupdate.
09/05/07 15:38:24 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Checking Network Element Status ( SITE= Canopy Basestation )
09/05/07 15:38:24 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Current = CANOPY 8.2 AP-DES, CANOPYBOOT 3.0, 060407 ( SITE= Canopy Basestation )
09/05/07 15:38:24 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Using Package C:'Documents and Settings’gautam’My Documents’manuals’canopy’Canopy Updates’8.2 v2’Canopy 8.2 DES V2’CANOPY82_DES_V2.pkg2 ( SITE= Canopy Basestation )
09/05/07 15:38:28 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Transferring Files SMboot.bin;block.bin;DES_P8_070529_S40_epc.jbi to AP ( SITE= Canopy Basestation )
09/05/07 15:38:48 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Enabling AutoUpdate ( SITE= Canopy Basestation )
09/05/07 15:38:58 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Enabling AutoUpdate ( Retry ) ( SITE= Canopy Basestation )
09/05/07 15:39:08 INFO Host: 172.16.8.53;ESN: 0A003E237404;Message: Enabling AutoUpdate ( Retry ) ( SITE= Canopy Basestation )
09/05/07 15:39:18 WARN Host: 172.16.8.53;ESN: 0A003E237404;Message: TimeOut Error. No response from Host ( SITE= Canopy Basestation )
09/05/07 15:39:18 INFO Node: 172.16.8.53 Update Complete
I was doing it remotely from my NOC. The one I tested in LAB works fine… what is the solution?
I have seen this problem trying updates from a computer behind NAT.
gautam wrote: I want to monitor the bandwidth of my customer's end {MRTG GRAPH}. how should i configure the SM??
First of all you should have access to the management ip of the subscriber. After that you could configure the MRTG, you have the MIB files in the update pakages and you know your comunity string.
I dont get PING response from remote SMs. How should I configure them?
What is your vlan configuration?
VLAN Configuration in my Network is as follows:
In AP:
General Tab: Configuration source> BAM+SM
VLAN Tab: VLAN enable, management VID: 1, SM Management VID Pass Through: Enable
VLAN Membership Tab: 8 Static VLANs : 10,20,30…
IN SMs
EXamle: To keep a client under VLAN 10
VLAN Tab: Dynamic Learning enable, Management VID: 10
VLAN Membership TAB: 10 static
in this configuration VLAN is working fine. I got response from PC to PC but unable to PING the AP or the associated SMs
Total Packets Overload Count : 528
Ethernet In Discards : 0
Ethernet Out Discards
(Statistics=>Ethernet=>outdiscards count) : 0
RF In Discards : 0
RF Out Discards
(Statistics=>Radio=>outdiscards count) : 528
Hi. I’m also having the problem with the autoupdates:
09/24/07 12:20:08 INFO Queue AP:192.168.201.13 enable SM autoupdate.
09/24/07 12:20:09 INFO Host: 192.168.201.13;ESN: …;Message: Checking Network Element Status ( SITE= Site Name )
09/24/07 12:20:09 INFO Host: 192.168.201.13;ESN: …;Message: Current = CANOPY 8.2 AP-DES, CANOPYBOOT 3.0, 060407 ( SITE= Site Name )
09/24/07 12:20:09 INFO Host: 192.168.201.13;ESN: …;Message: Using Package /home/root/Canopy pkgs/Canopy 8.2 DES V2/CANOPY82_DES_V2.pkg2 ( SITE= Site Name )
09/24/07 12:20:17 INFO Host: 192.168.201.13;ESN: …;Message: Transferring Files SMboot.bin;block.bin;DES_P8_070529_S40_epc.jbi to AP ( SITE= Site Name )
09/24/07 12:20:21 INFO Host: 192.168.201.13;ESN: …;Message: Enabling AutoUpdate ( SITE= Site Name )
09/24/07 12:20:31 INFO Host: 192.168.201.13;ESN: …;Message: Enabling AutoUpdate ( Retry ) ( SITE= Site Name )
09/24/07 12:20:41 INFO Host: 192.168.201.13;ESN: …;Message: Enabling AutoUpdate ( Retry ) ( SITE= Site Name )
09/24/07 12:20:51 WARN Host: 192.168.201.13;ESN: …;Message: TimeOut Error. No response from Host ( SITE= Site Name )
09/24/07 12:20:51 INFO Node: 192.168.201.13 Update Completed.
09/24/07 12:20:51 INFO Task canceled
09/24/07 12:20:51 INFO Update process has completed
Any ideas? To do this I’ve got CNut on the gateway of those IPs (192.168.201.1), I’ve successfully updated the AP to 8.2 (from 7.2.9) and, if I put in the IP of the SM, I can update the SMs successfully to 8.2 as well. However if I try to have CNut update the SM for me it cannot connect to the SM but it can to the APs no problem.
Any advice would be great.
gautam wrote: VLAN Configuration in my Network is as follows:
In AP:
management VID: 1
IN SMs
Management VID: 10
in this configuration VLAN is working fine. I got response from PC to PC but unable to PING the AP or the associated SMs
Your APs and SMs are in different management VLAN, it looks to me like this is the source of your problems.