[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

3816.0. "Can't REGISTER SNMP device with WIN/TCP " by CSC32::ORTIZ () Mon Sep 28 1992 15:41

    I have a specialist that has WIN/TCP V5.2.1 and running DECmcc BMS
    V1.2.1. He followed the release notes to link in the WIN/TCP within
    DECMcc. He is not able to register a SNMP entity. The following error
    is generated:
    
    PARTIAL REGISTRATION SUCCESS
    PLEASE RETRY LATER TO COMPLETE THE REGISTRATION
    
    REASON:  INTERNET COMMUNICATION DEVICE ERROR
    	     %C-F-EBADF  BAD FILE NUMBER
    
    
    Has anyone seen this problem? He uses the password "public" in the
    ACCESS QUALIFIER in the iconic map.
    		
    Any help would be appreciated..
    
    Thanks,
    Richard
T.RTitleUserPersonal
Name		DateLines
3816.1WIN/TCP 5.3 should work with MCC SNMPCSC32::ORTIZTue Sep 29 1992 17:006
    I found out that WIN/TCP V5.2.1 wasn't really tested with the SNMP AM. 
    Wollongong seemed to be aware of this and is planning to come out with a 
    new version WIN/TCP 5.3 by the end of the year that should work with the 
    SNMP AM. 
    
    Richard
3816.2YAHEY::BOSETue Sep 29 1992 17:3511
	Richard,

		That's good news. The SNMP AM should work with any TCP 
	implementation which provides the standard socket interface. We
	have already seen it work with TGV Multinet (which does not even
	require relinking the AM). Unfortunately, due to resource constraints,
	we have not been able to test the SNMP AM with other TCP implementations
	on VMS, such as Woolongong and Fusion.

	Rahul.