Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
cancel
Showing results for 
Search instead for 
Did you mean: 

ocd ip address

SOLVED
Go to solution
ITeam
Super Advisor

ocd ip address

The entry in DP quotes one ip address but when I run /etc/dpp /etc/ddfa/dp the ocd created has a different address to that in the dp file ? ps -ef | grep ocd shows this.
Any ideas gratefully accepted.
3 REPLIES
Fred Martin_1
Valued Contributor

Re: ocd ip address

Have you changed the dp file without rebooting, or restarting ddfa?

Make sure /etc/rc.config.d/netdaemons
contains: export DDFA=1
and try:
# /sbin/init.d/rbootd stop
# /sbin/init.d/rbootd start
# /sbin/init.d/ddfa start
fmartin@applicatorssales.com
Ray Krupinski_1
Occasional Contributor

Re: ocd ip address

This is what I do you don't have to rebootNote: Check for the existance of the OCD daemon:
rdtclist -d | grep dtcOWR1 | awk '{print $2}'
where "dtcOWR4" is the DTC name,
then ps -ef | grep 10.244.160.25

1) Make a backup copy of the dp file
bmoc cp /etc/ddfa/dp /etc/ddfa/dp.$( date +%m%d%y )

2) Create a new dp test file with the dtcname, board, and port (ie: /dev/pdOWR4b1p8 )
bmoc vi /etc/ddfa/dp.

3) Execute the Dedicated Port Parser (/usr/sbin/dpp) to scan your new /etc/ddfa/ file. This starts up the ocd daemon and assigns the dedicated ports for Telnet Port Identification. A warning at this point is OK.

bmoc /usr/sbin/dpp /etc/ddfa/DTC name -k

Example:
WARNING: Device file not specified in /dev/telnet
Many commands (such as ps) may not display the correct device file in their output

Task completed with:
0 port identification entries created
1 ocd pseudonyms removed
1 ocds started
Solution

Re: ocd ip address

Thanks for the replies - I (strangely enough) seem to have resolved the problem by removing spurious leading zeroes from the ip addresses ... Eg; 126.000.000.012 becomes 126.0.0.12 ... Hmmmmm!
I had already checked the ocd and dpp and found no problems with it - either when rebooting server or simply restarting the dpp and re-scanning the dp file.
Paul.