This is the expected behavior.
It’s important to understand that the PCS device is not a DHCP relay agent (i.e., it does not forward DHCP packets to/from the client and the backend DHCP server). Instead, it acts as a DHCP proxy. In other words, the PCS device acts as a DHCP client when talking to the backend DHCP server. As a result it reads the DHCP offer from the DHCP server, and then sends the DHCP request on behalf of the NC client.
During this process it determines the lease time offered by the DHCP server. The PCS device will then take care of renewing the lease when it is time for renewal.
For example, in the above scenario, you should see that the PCS device will send DHCP request packets to renew the lease at 50% of the lease duration or the Renewal time value set in the Offer Packet as per RFC.
Notes:
- PCS device does not send the server determined lease time to the NC client.
- The 7 day value that is leased on the client is an PCS determined value which cannot be changed.
- It is safe to ignore this value since the PCS takes care of all the DHCP related activities, including releasing the IP address when the lease time runs out.
If the PCS fails to renew the lease time, it reports the message in the user access logs on the PCS and disconnects the Network Connect Session.
Sample message:
Info ERR23565 : Username(Realm)[Role] - Network Connect: DHCP : Lease expired for user sida54e21ff0dbec57483e782d5f14ef323152d260700000000 IP xx.xx.xx.xx
