June’s Course of the Month is now available! Experts Exchange’s Premium Members, Team Accounts, and Qualified Experts have access to a complimentary course each month as part of their membership—an extra way to sharpen your skills and increase training.
Course Of The Month
3 days, 13 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
PortFast impact on DHCP/PXE clients
Posted on 2012-03-28
I didn't where This question should go, it is a mixture of Portfast, PXE,Imaging software and DHCP:
First I need to know if the clients that are configured for PXE boot, whether they should have a static IP or Dynamic IP?
For instance if an image software is somewhere in the network and we need to make clients boot in PXE mode, do we need first to prestage those clients in the Imaging software.
Regarding Imaging software and PXE, if a client doesn't have any OS at all, just bare metal, would this be able to boot in PXE and connect to the imaging software?
Knowing that most of the environment use DHCP to handout IPs at least for workstations.
Does that mean all access ports on the switch need to be configured with Portfast, if so why Cisco didn't enable portfast automatically right after you configure a port as an access port?
Thanks
First I need to know if the clients that are configured for PXE boot, whether they should have a static IP or Dynamic IP?
For instance if an image software is somewhere in the network and we need to make clients boot in PXE mode, do we need first to prestage those clients in the Imaging software.
Regarding Imaging software and PXE, if a client doesn't have any OS at all, just bare metal, would this be able to boot in PXE and connect to the imaging software?
Knowing that most of the environment use DHCP to handout IPs at least for workstations.
Does that mean all access ports on the switch need to be configured with Portfast, if so why Cisco didn't enable portfast automatically right after you configure a port as an access port?
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Active 6 days ago
Re Portfast
Yes access ports connected to PC's should be configured with portfast this will enable them to transition to "forwarding" mode immediately on link up
Not all access ports can be enabled with portfast as this might cause a loop in the network - an example is an access port connected to another switch, this port should not be set to portfast mode.
Yes access ports connected to PC's should be configured with portfast this will enable them to transition to "forwarding" mode immediately on link up
Not all access ports can be enabled with portfast as this might cause a loop in the network - an example is an access port connected to another switch, this port should not be set to portfast mode.
PXE relies on DHCP. So you need DHCP IP addresses with PXE clients
Now, these can be purely dynamic or static addresses (DHCP reservation) this has no impact on the client side of things.
Regarding your imaging software, it depends on the software itself. But PXE is MADE to boot computers without needing a local disk drive. So, usually, they can be PXE-booted even with no OS on the local HDD
Portfast: This is to work-around an issue with SpanningTree Protocol (STP). Standard spanning tree can take up to one minute to accept to transfer the packets that PXE sends. ANd most PXE implementations time-out after 30 seconds. Portfast is a way to reduce the time to a couple of seconds. It is REQUIRED not to use standard spanning tree when you have PXE client.
Why did not cisco enabled it by default? This is a question that can be aksed to Cisco, but knowing its answer won't solve your problems if you do have STP and you try to PXE-Boot...
Now, these can be purely dynamic or static addresses (DHCP reservation) this has no impact on the client side of things.
Regarding your imaging software, it depends on the software itself. But PXE is MADE to boot computers without needing a local disk drive. So, usually, they can be PXE-booted even with no OS on the local HDD
Portfast: This is to work-around an issue with SpanningTree Protocol (STP). Standard spanning tree can take up to one minute to accept to transfer the packets that PXE sends. ANd most PXE implementations time-out after 30 seconds. Portfast is a way to reduce the time to a couple of seconds. It is REQUIRED not to use standard spanning tree when you have PXE client.
Why did not cisco enabled it by default? This is a question that can be aksed to Cisco, but knowing its answer won't solve your problems if you do have STP and you try to PXE-Boot...
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Windows 7 does not have the best desktop search built in. This is something Windows 7 users have struggled with. You type something in, and your search results don’t always match what you are looking for, or it doesn’t actually work at all. There ar…
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…
Hi friends,
in this video I'll show you how new windows 10 user can learn the using of windows 10.
Thank you.
Suggested Courses
Course of the Month3 days, 13 hours left to enroll
Earn Certification
CompTIA Linux+ (LX0-103 & LX0-104)
$147.00$132.30
Earn Certification
70-742: Identity with Windows Server 2016
$197.00$177.30
690 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.