{"id":77,"date":"2014-01-05T21:16:26","date_gmt":"2014-01-05T21:16:26","guid":{"rendered":"http:\/\/ethernetsupport.com\/?p=77"},"modified":"2014-01-06T00:07:36","modified_gmt":"2014-01-06T00:07:36","slug":"using-the-bootpdhcp-server-rslinx","status":"publish","type":"post","link":"http:\/\/ethernetsupport.com\/?p=77","title":{"rendered":"Using the BootP\/DHCP Server (RSLinx)"},"content":{"rendered":"

A new Ethernet module (such as the 1756-ENBT) has no initial IP Address.\u00a0 When replacing an Ethernet Module, there are a couple methods that are normally used to issue this IP Address.<\/p>\n

One way would be to configure the DF1 Driver (or a driver to another communication module), and in RSWho, browse across the backplane to locate the Ethernet Module.\u00a0 You can then right-click the module, and choose “Module Configuration”, and then enter the IP address on the “Port Configuration” tab.<\/p>\n

The method discussed in this document will be the “BootP” (Bootstrap Protocol) method.\u00a0 This will allow you to assign the IP address directly over the Ethernet Network.<\/p>\n

To summarize these steps…\u00a0 When we power up the module, it will begin sending out the Ethernet Address, some also call this a MAC ID or Hardware Address.\u00a0 In the BootP server utility you will see these requests, and we just double-click the Ethernet Address to assign the IP Address.\u00a0 Don’t forget to disable BootP after the IP address has been assigned if you need the IP Address to remain static!!<\/p>\n

1)\u00a0 Write down the Ethernet Address of the Device.\u00a0 This is a six-byte hexadecimal number embedded by the device manufacturer.\u00a0 This can be usually be found documented on the device itself once it’s removed from the chassis.\u00a0 If your device also has an alpha-numeric display, and no IP Address has been assigned yet, you might find this ID scrolling on the face of your device.\u00a0 An example of an Ethernet Address might be:\u00a0 00:00:BC:1E:98:D9.<\/p>\n

2)\u00a0 Open the BootP Server.\u00a0 This is usually installed when you install RSLinx Classic.\u00a0 This is under Start | All Programs | Rockwell Software | BootP\/DHCP Server.<\/p>\n

\"OpenServer\"<\/a><\/p>\n

3)\u00a0 Once the server is open you may have to enter some network details such as the Subnet Mask and Default Gateway.\u00a0 Usually, just the Subnet Mask is required.\u00a0 A common Subnet Mask is 255.255.255.0<\/p>\n

4) Power up your processor, and you should see the device begin to request an IP Address:<\/p>\n

\"AddressRequest\"<\/a><\/p>\n

5)\u00a0 Double click the MAC ID of your device.\u00a0 Be sure you are on the correct MAC ID.\u00a0 Entering the wrong IP Address into the wrong device could have disastrous consequences!!!\u00a0 Some sites will even have procedures in place to disable all other network adapters, and plug directly into the device with a cross over cable to minimize the chance of getting the wrong IP Address in the wrong device.\u00a0 You can also enter a hostname and description at this time if required.\u00a0 Most sites I’ve seen only require the IP Address.\u00a0 Be sure to hit “OK”.<\/p>\n

\"AssignIP\"<\/a><\/p>\n

6)\u00a0 Now you can attempt to ping the device to verify the IP Address is responding.\u00a0 You can do this from the command prompt using the PING command.<\/p>\n

\"ping\"<\/a><\/p>\n

7)If you wish for this IP to be static, be sure to disable BootP for this device.\u00a0 You can right-click the MAC ID in the relation list (in the bottom frame of the BootP Server), or highlight the MAC ID in the relation list, and use the “Disable BootP\/DHCP” button.\u00a0 If you happen to get an error when doing this, just attempt the request again.<\/p>\n

8)\u00a0 If possible, cycle power to ensure the device held the IP Address.<\/p>\n","protected":false},"excerpt":{"rendered":"

A new Ethernet module (such as the 1756-ENBT) has no initial IP Address.\u00a0 When replacing an Ethernet Module, there are a couple methods that are normally used to issue this IP Address. One way would be to configure the DF1 Driver (or a driver to another communication module), and in RSWho, browse across the backplane…<\/p>\n","protected":false},"author":1,"featured_media":83,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/posts\/77"}],"collection":[{"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=77"}],"version-history":[{"count":1,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/posts\/77\/revisions"}],"predecessor-version":[{"id":82,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/posts\/77\/revisions\/82"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=\/wp\/v2\/media\/83"}],"wp:attachment":[{"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=77"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=77"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/ethernetsupport.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=77"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}