Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
I had trouble following the RMON-upgrade instructions for using V1.7 of the code in the DECswitch series to do basic RMON. The ONLY way that I got it to work was to set the device community string to "string"-RMON. (i.e. public-rmon) ALL of the instructions simply say to append "-rmon" to the community string in the RMON manager software. It did *NOT* say that you needed to CHANGE THE DEVICE community string to "string"-RMON. Nasty glitch in the documentation if that is true...because it is NOT called out anywhere.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
4199.1 | NETCAD::GALLAGHER | Wed Feb 05 1997 09:00 | 16 | ||
> The ONLY way that I got it to work was to set the device community > string to "string"-RMON. (i.e. public-rmon) > > ALL of the instructions simply say to append "-rmon" to the community > string in the RMON manager software. It did *NOT* say that you needed > to CHANGE THE DEVICE community string to "string"-RMON. > > Nasty glitch in the documentation if that is true...because it is NOT > called out anywhere. That's not true. You should not change the community string. You should only have to append -rmon to the community string if you want to access Frontier's FULL RMON. The basic RMON should have worked without any messing with the community string. If you tell me the official name of the document you were using I'll check it out. -Shawn | |||||
4199.2 | Sorry, it didn't work the other day! | PTOJJD::DANZAK | Pittsburgher � | Fri Feb 07 1997 19:59 | 7 |
Shawn, The ONLY way that I got it to work was to *CHANGE* the community string to "mumble-rmon" and it worked. I'll try it again this weekend, but that was honestly the ONLY way. j |