Snapdeploy PXE boot causing a loopback?

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 2

Hello everyone,

I've been having an intermittent issue, and i'm almost sure i'm not the only one...

Our local LAN's use a Cisco Catalyst 500 series switches, and about half the time when we PXE boot a computer to the PXE server, the Cisco switch administratively disables the port referencing STP. (Spanning Tree Protocol aka "Loopback"). As soon as the Switch does this, the PXE boot fails and pops an error message. You can reboot the client PC all day, but the switch will just keep disabling the port. In order to get the PXE boot to work and be ready for deployment, I have to disable Spanning Tree Protocol for the port the client PC is connected to. Since we have over 400 Cisco switches in use in the field, its a real pain to have to do this every time we deploy a PC.

Has anyone else figured out why this happens and how to fix it? For whatever reason is doesn't happen on every deployment, but I would say about 50%. I cant figure out why it happens on some PCs and not others.

On a side note... before I switched to Snap Deploy, I tested the IBM PXE solution. The IBM software would trigger STP to disable to post 100% of the time. This makes me think this may be more of a PXE issue than anything, but someone must have figured out a way to get it to work without disabling STP...

Help?

Mi, 01/13/2010 - 13:59
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Beiträge: 2
Kommentare: 843

Hello Niklaus,

Let me assist you with this situation.

As far as I understand, you have tried to boot from PXE server with disabled Loopback protocol, is that correct?

Actually, we haven't received any complaints regarding this, but it could be a common issue and we have to investigate it along with QA team.

Could you please make screenshot with the error and send it to us?

If you are not familiar with making screen shots, please read the below step-by-step instructions.

- Get to the window which you want to make a screen shot of;
- Hit the (Alt+)PrintScreen button on your keyboard;
- Run Paint usually available in Start\Programs\Accessories or another graphics application;
- Choose Paste command in Edit menu;
- Save the result picture in JPEG format being preferable.

Also, could you please provide me with the exact sequence of actions that lead to the issue you report, so that I can try to reproduce it?

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

Do, 01/21/2010 - 10:50
  • Anmelden, um Kommentare verfassen zu können
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 1
Kommentare: 2

I think in order to test it properly you would need a Cisco 500 series switch. When I disable Loopback protocol on the switch, I am able successfully PXE the client. (But then the network is vulnerable to loopbacks). When I try to PXE boot without Loopback disabled, it fails. Unfortunately it fails at different points in the PXE boot process, shows different error messages, and most of the time it doesn't show an error it all. Most of the time it comes up to the final screen where it would normally be ready for deployment, however on the server it never shows the computer ready to be deployed. Then when I connect to the Cisco switch it shows that it detected a loopback on that port, and administratively disabled it blocking any communication between the PXE server and the client. This is happening on different types of hardware as well. Workstations (IBM 4810-33H) and servers (E-Series 206M)

Do, 01/21/2010 - 15:49
  • Anmelden, um Kommentare verfassen zu können
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Beiträge: 24
Kommentare: 3268

Hello Niklaus!

Thank you for your detailed comment and please accept our apologies for the delay with the response. We will do our best to handle your request without any procrastination in the future.

Unfortunately due to the lack of investigation information it is hard to identify the exact reason, but I assume there are some conflict between the settings of the switch and PXE server. It is also hard to be sure in the cause since these issues doesn't have stable scenario and as you already mentioned shows different errors and fails at different time.

Anyway we need to check the connection logs to see what causes the breakdown. We have everything ready for reproducing the issue, but need to know some details of your environment. So could you please kindly specify me the following information:

  1. Settings of the switch in general
  2. Network connections logs - Wireshark

Please contact us with the information gathered, we will review it, reproduce the issue and find out the cause.

Let us know in case you have any additional questions or face any difficulties with obtaining diagnostic info - we will be glad to help you!

Thank you!

Fr, 03/12/2010 - 13:58
  • Anmelden, um Kommentare verfassen zu können