1 of 1 people found this helpful
blasadmin -s _pxe show/set pxe all
so if I have to set up multiple PXE servers for the different sites, what is the easiest way to do this? The infrastructure management doesn't let you add additional pxe server instances.
Incidentally, for my test PXE server (located on the app server), blasadmin -s _pxe show pxe all
just comes back with
blasadmin now running against deployment: _pxe
I assume that the syntax of these is the same as for the values in blasadmin show database all?
Run this across all the pxe boxes...
Hmm, that show have a connect string in it..mine does...
I checked on my remote system and it has entries in blasadmin - it's just the central one that doesn't and it does work - strange.
I am now having trouble with this. I have installed the PXE and TFTP server on 2 separate Linux boxes. However, both seem to be writing the same entry into the DB, so if I run blasadmin -s _pxe on either machine, I get the same settings shown! This is obviously not good and I am wondering why?
The only other consideration is that we forward the requests to the DB through a single server for security reasons and this NATs the request to the DB. Not sure if this should make any difference though.
Do I need to modify the instance names to be _pxe1 and _pxe2? Not sure how to do this either, but can probably work it out?
my understanding is that the stuff showing up in the infrastrucutre manager for pxe is useless. you could try changing the instance name on one box (i think just move the directory to _pxe2). the nat could be screwing it up too of course.
even w/ all of that, are either of the pxe servers working?
If I change the pxe.conf to use the config file to get around this (I was trying to avoid doing this), does this mean the PXE server no longer talks to the DB at all?
pxe server will still talk to the db w/ the config file turned on. it has to to figure out what boot images to hand out.