Hi @Boopathi S ,
This is mostly likely due to the lack of correct network drivers in the boot image.
To verify, we should enable command-prompt support in the boot image and then perform an ipconfig and/or examine the smsts.log.
About adding Network (and Storage) Drivers to Boot Images in SCCM, refer to this article:
https://emeneye.wordpress.com/2017/01/13/adding-network-and-storage-drivers-to-boot-images-in-sccm/
Note: Non-Microsoft link, just for the reference.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.