Is it possible that dude show canopy`s
THX
please read up on SNMP in the manual. OID is the identification name(number) of a value.
IF you have SNMP enabled on the canopy device, and if it is actually working, you should see something like this in the dude:
the table shows all kind of information that you have on the router. then just copy the OID that shows the value you need, and make a new probe/graph/label by using this OID in the appropriate menu
IF you have SNMP enabled on the canopy device, and if it is actually working, you should see something like this in the dude:
the table shows all kind of information that you have on the router. then just copy the OID that shows the value you need, and make a new probe/graph/label by using this OID in the appropriate menu
please read up on SNMP in the manual. OID is the identification name(number) of a value.
IF you have SNMP enabled on the canopy device, and if it is actually working, you should see something like this in the dude:
the table shows all kind of information that you have on the router. then just copy the OID that shows the value you need, and make a new probe/graph/label by using this OID in the appropriate menu
The Canopy works fine,I can read the snmp per the CNUT-TOOL from Canopy.
Ping,telnet etc works fine with DUDE and the Canopy. But per Snmp no response!!!
The community String in the Canopy ist CANOPY.IS this the Problem?
THX a lot...
Canopy and The Dude
The Dude and Canopy work very well together, and The Dude is probably the best thing that ever happened for Canopy network monitoring. Dont get a big head MT, you know what you still have to do...
I can assure you, that after you master certain 'Dude' features like generating functions to make Canopy labels display better, you will see that everything works and there is a reason why things work the way they do.
BTW, Remember, its SNMP v2.
It took a while, but I now have all the necessary operational parameters displaying in Canopy devices. Be advised, certain things have 'values' but must be converted into useful information, like mileage.
Certain values display too long and therefore essentially affect size of the device object. For those, and other values, you must resort to code trickery in order to display values effectively. For the devices to be small enough, and contain everything you really need to be useful, values must be abbreviated and you must resort to 'short notation'. This ends up packing whats really needed off the Canopy status other pertinent web pages into a compact but very powerful display.
However, after many coding hours, I now have a more useful network display of all BHs, APs and SMs, their signals, code, etc. than available from any other source. Just seeing all the parameters of multiple APs on one map simultaneously makes life much easier when you start changing things. (I advise exporting to PDF or PNG regularly to save yourself asking 'What did that look like when it worked yesterday?' or 'I know I had that working yesterday!')
Be advised though, when using SNMP, certain integrated [device.xxxxx] labels are more useful, like name, since if you lose the connection and use SNMP for the name, that isnt much help.
Just keep on banging on the SNMP door, again, remember its version 2 SNMP, and be prepared to figure out innovative ways to make things happen. Whenever you think 'It doesnt work', try another angle. 'No response' is invariably because your default SNMP setup is not the Canopy setup. Because programmers developed the way SNMP data is stored, trying to optimize, that just confuses the issue with many facts. Many times I have tested '(If x=x, then true, otherwise false')' only too many times to have it tell me its false. I can only attribute this to the idiosyncrasies of datatypes...
With effort, you will see more about your network than you might even have wanted to know...
I can assure you, that after you master certain 'Dude' features like generating functions to make Canopy labels display better, you will see that everything works and there is a reason why things work the way they do.
BTW, Remember, its SNMP v2.
It took a while, but I now have all the necessary operational parameters displaying in Canopy devices. Be advised, certain things have 'values' but must be converted into useful information, like mileage.
Certain values display too long and therefore essentially affect size of the device object. For those, and other values, you must resort to code trickery in order to display values effectively. For the devices to be small enough, and contain everything you really need to be useful, values must be abbreviated and you must resort to 'short notation'. This ends up packing whats really needed off the Canopy status other pertinent web pages into a compact but very powerful display.
However, after many coding hours, I now have a more useful network display of all BHs, APs and SMs, their signals, code, etc. than available from any other source. Just seeing all the parameters of multiple APs on one map simultaneously makes life much easier when you start changing things. (I advise exporting to PDF or PNG regularly to save yourself asking 'What did that look like when it worked yesterday?' or 'I know I had that working yesterday!')
Be advised though, when using SNMP, certain integrated [device.xxxxx] labels are more useful, like name, since if you lose the connection and use SNMP for the name, that isnt much help.
Just keep on banging on the SNMP door, again, remember its version 2 SNMP, and be prepared to figure out innovative ways to make things happen. Whenever you think 'It doesnt work', try another angle. 'No response' is invariably because your default SNMP setup is not the Canopy setup. Because programmers developed the way SNMP data is stored, trying to optimize, that just confuses the issue with many facts. Many times I have tested '(If x=x, then true, otherwise false')' only too many times to have it tell me its false. I can only attribute this to the idiosyncrasies of datatypes...
With effort, you will see more about your network than you might even have wanted to know...
Re: Motorola Canopy and DUDE
I am once again struggling with Dude, Canopy and SNMP. I got it to pretty much work a year or so ago, now I am attempting to talk someone through the process who is thousands of miles away and is a native speaker of something other than English.
Is there anyone who has an FAQ or step by step notes for this process to save me the effort of firing up my canopy lab once again. The spiders who have gathered on the AP's and SM's are going to be very annoyed if I have to resort to that.
jayr
Is there anyone who has an FAQ or step by step notes for this process to save me the effort of firing up my canopy lab once again. The spiders who have gathered on the AP's and SM's are going to be very annoyed if I have to resort to that.
jayr
Re:
[oid("iso.org.dod.internet.private.enterprises.mot.whispRoot.whispProducts.whispSm.whispSmStatus.radioDbm.0")] this one is working for me (edit view of object end paste this oid).But when i copy the oid and make a probe of dBM, i can`t see the value.I only that dBm is okay?