06-13-2010 11:13 PM - edited 03-04-2019 08:46 AM
is it possible to initiate a dhcp-request over different ip-segments over the llc-layer? is there a config like ip-helper on cisco devices? dhcp-server and client are in different ip-segments.
see details in the capture-file (wireshark) -- set filter: eth.addr == 08:00:09:F2:2a:61
when dhcp-server an client are in the same ip-segment --> no problem. how can i tell the nw-device, that all boot-request from this ip-segment (rmp-protokol) should be send to the dhcp-server?
thanks in advance for your replies!
kind regards,
thomas
Solved! Go to Solution.
06-14-2010 12:10 AM
This is what i got from HP resources,
Remote Maintenance Protocol (RMP) is an HP-proprietary boot and file transfer protocol used in early Series 700 workstations and in the Datacommunications and Terminal Controllers (DTC/9000). The rbootd daemon allows BOOTP servers to serve clients that use RMP. rbootd must be run on a BOOTP server on the same subnet as the RMP client. That is, both rbootd and bootpd must run on the same system.
The rbootd daemon translates RMP bootrequests into a BOOTP bootrequest using the client's hardware address. rbootd then forwards the bootrequest to bootpd. bootpd can send a bootreply back to rbootd if it finds the client's boot information in its database. Or, it can relay the bootrequest to other BOOTP servers if it has relay information for the client in its database. rbootd translates the BOOTP bootreply back to RMP and sends it to the client.
Im unable to find any UDP port number associated with RMP, If you have one than it can be forwarded to desired server.
Here is the link for further information
http://docs.hp.com/en/B2355-90685/ch05s03.html?btnNext=next%A0%BB
HTH
Hitesh Vinzoda
Pls rate useful posts.
06-14-2010 12:10 AM
This is what i got from HP resources,
Remote Maintenance Protocol (RMP) is an HP-proprietary boot and file transfer protocol used in early Series 700 workstations and in the Datacommunications and Terminal Controllers (DTC/9000). The rbootd daemon allows BOOTP servers to serve clients that use RMP. rbootd must be run on a BOOTP server on the same subnet as the RMP client. That is, both rbootd and bootpd must run on the same system.
The rbootd daemon translates RMP bootrequests into a BOOTP bootrequest using the client's hardware address. rbootd then forwards the bootrequest to bootpd. bootpd can send a bootreply back to rbootd if it finds the client's boot information in its database. Or, it can relay the bootrequest to other BOOTP servers if it has relay information for the client in its database. rbootd translates the BOOTP bootreply back to RMP and sends it to the client.
Im unable to find any UDP port number associated with RMP, If you have one than it can be forwarded to desired server.
Here is the link for further information
http://docs.hp.com/en/B2355-90685/ch05s03.html?btnNext=next%A0%BB
HTH
Hitesh Vinzoda
Pls rate useful posts.
06-14-2010 01:56 AM
hi hitesh,
thanks for your posting! that is the answer what i´m looking for.
kind regards,
thomas
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: