Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Have these in MM rdevmi -sockfd 5 -r
- Thread starter jimbomlac
- Start date
Instances of ltid on hosts with the same shared drive configured create rdevmi (remote device management interface) connections to the scan host, to receive drive status information from the scan host. This information is used to maintain the multihosted drive information on the remote hosts.
RDEVMI Overview:
The SSO scan host will start one rdevmi (which is actually oprd with the -r option) per registered media server except for itself. rdevmi is used to remotely communicate with registered media servers. For example, if the master is the scan host and there are five additional media servers, the scan host will show five rdevmi processes.
rdevmi was specifically started with a process name differing from oprd, even though its binary is otherwise identical to oprd, so that one can differentiate between rdevmi running normally in an SSO configuration, versus oprd processes that are coming and going, or oprd processes that may be unexpectedly running.
Example of rdevmi starting message in daemon log:
09:38:37.199 [5717] <4> process_request: client requested command=52, version=1
09:38:37.199 [5717] <4> process_request: START_OPRD requested
09:38:37.199 [5717] <2> start_oprd: starting rdevmi, sockfd = 7, nosig = yes
09:38:37.240 [5717] <4> start_oprd: rdevmi, pid=6031
09:38:37.279 [6031] <4> rdevmi: INITIATING
09:38:37.340 [6031] <2> rdevmi: got CONTINUE, connecting to ltid
Example of rdevmi terminating in daemon log:
14:18:06.112 [6031] <2> rdevmi: in ltidtermsig
14:18:06.112 [6031] <2> rdevmi: detach shared memory
14:18:06.112 [6031] <2> rdevmi: DriveStatId shm_nattch = 4
14:18:06.117 [6031] <2> rdevmi: rdevmi exiting since ltid has been stopped
If /usr/openv/volmgr/VM_MQ_DEBUG has been touched, which turns on the ltid message queue logging, the following messages will be seen in the daemon log:
rdevmi/oprd sends a message to ltid on start (Type=100 means oprd start):
09:38:37.341 [5712] <4> LtidProcCmd: Pid=6031, Data.Pid=6031, Type=100, Param1=0, Param2=7, LongParam=300
rdevmi/oprd sends a message to ltid on stop (Type=101 means oprd terminate):
14:22:52.533 [14666] <4> LtidProcCmd: Pid=14833, Data.Pid=14833, Type=101, Param1=1, Param2=3, LongParam=1229870405
Bob Stump
Incorrigible punster -- Do not incorrige
RDEVMI Overview:
The SSO scan host will start one rdevmi (which is actually oprd with the -r option) per registered media server except for itself. rdevmi is used to remotely communicate with registered media servers. For example, if the master is the scan host and there are five additional media servers, the scan host will show five rdevmi processes.
rdevmi was specifically started with a process name differing from oprd, even though its binary is otherwise identical to oprd, so that one can differentiate between rdevmi running normally in an SSO configuration, versus oprd processes that are coming and going, or oprd processes that may be unexpectedly running.
Example of rdevmi starting message in daemon log:
09:38:37.199 [5717] <4> process_request: client requested command=52, version=1
09:38:37.199 [5717] <4> process_request: START_OPRD requested
09:38:37.199 [5717] <2> start_oprd: starting rdevmi, sockfd = 7, nosig = yes
09:38:37.240 [5717] <4> start_oprd: rdevmi, pid=6031
09:38:37.279 [6031] <4> rdevmi: INITIATING
09:38:37.340 [6031] <2> rdevmi: got CONTINUE, connecting to ltid
Example of rdevmi terminating in daemon log:
14:18:06.112 [6031] <2> rdevmi: in ltidtermsig
14:18:06.112 [6031] <2> rdevmi: detach shared memory
14:18:06.112 [6031] <2> rdevmi: DriveStatId shm_nattch = 4
14:18:06.117 [6031] <2> rdevmi: rdevmi exiting since ltid has been stopped
If /usr/openv/volmgr/VM_MQ_DEBUG has been touched, which turns on the ltid message queue logging, the following messages will be seen in the daemon log:
rdevmi/oprd sends a message to ltid on start (Type=100 means oprd start):
09:38:37.341 [5712] <4> LtidProcCmd: Pid=6031, Data.Pid=6031, Type=100, Param1=0, Param2=7, LongParam=300
rdevmi/oprd sends a message to ltid on stop (Type=101 means oprd terminate):
14:22:52.533 [14666] <4> LtidProcCmd: Pid=14833, Data.Pid=14833, Type=101, Param1=1, Param2=3, LongParam=1229870405
Bob Stump
Incorrigible punster -- Do not incorrige
- Status
Similar threads
- Locked
- Question