[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1773.0. "SNMP devices that do not use the default community name 'public'?" by RIVAGE::SILVA (Carl Silva - Telecom Eng - DTN 828-5339) Wed Nov 06 1991 09:19

Path: rock!mcnc!stanford.edu!unixhub!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!raven.alaska.edu!raven.alaska.edu!jeff
From: [email protected] (Jeff Harrison)
Newsgroups: vmsnet.networks.management.decmcc
Subject: DECmcc TCP/IP SNMP Acess Module community name problem
Message-ID: <[email protected]>
Date: 5 Nov 91 00:19:20 GMT
Sender: [email protected] (USENET News System)
Reply-To: [email protected] (Jeff Harrison)
Organization: University of Alaska Computer Network - Systems Programming Group
Lines: 13
Nntp-Posting-Host: raven.alaska.edu

I'm running DECmcc 1.1 with TCP/IP SNMP Access Module 1.0.  I am having
trouble accessing 
SNMP devices that do not use the default community name 'public'. 
Specifying a different 
password does not help.  Only when I change the SNMP community name on
the device to public
do any queries work.

Anyone else have this problem?
--
Jeff Harrison                                [email protected]
Systems Programmer III                       [email protected]
University of Alaska Computer Network        907.474.6329
T.RTitleUserPersonal
Name
DateLines
1773.1Known bug in V1.0DANZO::CARRWed Nov 06 1991 16:071
This is a know problem in the V1.0 access module.  It is fixed in V1.1
1773.2Jeff Harrison has the info.CHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Wed Nov 06 1991 18:012
Jeff has already been mailed an answer (from Bill Gassman) to
this question.
1773.3RIVAGE::SILVACarl Silva - Telecom Eng - DTN 828-5339Fri Nov 08 1991 10:354
>This is a know problem in the V1.0 access module.  It is fixed in V1.1

	Thanks for the info!