Hi, David,
OEM doesnt discover IA, configured to non-standard port. This is expected behaviour. You have to configure OEM manually (after automatic discovery fails, you'll get an option to to this).
Hope this helps,
Vadim Gorbounov
Oracle DBA
 
 
-----Original Message-----
From: David A. Owens [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 6:11 PM
To: Multiple recipients of list ORACLE-L
Subject: Moving Intell. Agent Ports?

Anyone have any luck in reassigning the dbsnmp process to use different port numbers than the default 1748 and 1754? 
 
The setup:
 
OMS and OEM 2.2 install on NT box, -->  Ora 8.1.6 w/ Intell Agent installed on AIX
 
The unix box has 3rd party apps that do not allow ports 1748 and 1754 open but instead I have listed in the snmp_rw.ora file on unix:
 
dbsnmp.address=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=new_port_number)))
dbsnmp.spawnaddress=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=another_port_number)))
I bounced the Agent and did:
 
netstat -an | grep 11900
netstat -an | grep 11910
 
add the Agent was listening!  Fine.  I go to the Windoze NT box and do:
 
tnsping (ADDRESS=(PROTOCOL=TCP)(PORT=11900)(HOST=MTW2))
 
It comes back with < 300ms
 
I fire up OEM Console and try to discover the unix box.
 
But all I get is VNI-4044  (failed to discover).  I added the above line to snmp_rw.ora on the NT box but no good result.  There must be a way to configure the OMS to communicate with the IAgent on the non-standard port numbers.  I can't believe these ports are hardcoded are they?
 

   David Owens
   <[EMAIL PROTECTED]>
   Certified Oracle DBA
   (603) 635-8770
 
 

Reply via email to