Milford, Delaware, USA

Posts made by adukes40
-
RE: Snap-in Replication
@Wayne-Workman so perhaps not fixed yet? if not thats fine. I was able to successfully image from the node, using the location plugin. So nice to see this start to come together.
-
RE: Issues after upgrade to trunk
http://<serverip>/fog/management have you tried typing that?
-
RE: Cannot PXE boot
It should have been fixed this morning. try updating to the latest version. i had this exact issue this morning.
-
Snap-in Replication
Image replication is working great, however, i get this during the snap-in rep:
mirror: Access failed: 553 Could not create file. (camdf.bat)
Version 7853
-
RE: QuickReg and Inventory issue
@george1421 agreed, but it ws already bought… so will work with what I got.
-
RE: QuickReg and Inventory issue
@george1421 ugg. apparently i was informed this was just bought, and waiting on the arrival:
http://www.waspbarcode.com/barcode-scanners/wws550i-freedom-barcode-scanner#
It says no drivers required, so hopefully the dongle works during the Reg phase. Will super suck if not.
-
RE: QuickReg and Inventory issue
@george1421 I dont think that will work… each of our asset tags is a different number. asset tags are our primary way of knowing what machine is what. When it comes time to name the machine during imaging, our PS script pulls the asset and server tag info from the bios, and puts it together how we want.
So sadly i think i will need to the scanner-keyboard-scanner option… but still sounds better than keying in everything.
And helps on fat-fingering characters.
-
RE: QuickReg and Inventory issue
@george1421 I was thinking about just doing the full reg, if the auto pop didnt work. That way I can just take care of the name then, instead of trying to match up mac addresses later. Plus our asset tag stickers have barcode on them, so if we have a external BC scanner, I might be able to scan the AT, type the hyphen, and then scan the back of the machine for the service tag. I will need to try that out.
Thanks for the idea.
-
RE: QuickReg and Inventory issue
At one point when i first started testing out FOG, it was pulling the Asset from the board. Sometimes i saw it in chassis, sometimes it was in MB… but now its no where.
-
RE: QuickReg and Inventory issue
@george1421 You mean you are just using the “other tag” fields? for Asset.
-
RE: QuickReg and Inventory issue
Sorry, its 1.2, 7847.
This would be awesome if it would work that way. That would make my boss happy lol. As well as registration quick and easy for new equipment.
Thanks for the info.
-
QuickReg and Inventory issue
Me again. Here is what is happening
- Host will not register manually if Auto pop is enabled
- Trying to use Auto pop Quick Reg, with custom naming field. (Quickreg Autopop doesnt seem to bring anything up, just the normal boot menu, which ends up booting to the HDD, acting like it doesn’t need to register)
We will end up either using {CASEASSET}-{SYSSERIAL} or {MBASSET}-{SYSSERIAL} - When the inventory is ran manually, it does not grab either Asset field. the Asset is set in the BIOS, but does not show in the host inventory.
Am I doing this wrong?
-
RE: Chainloading failed
@Tom-Elliott just updated Main and node. Chainloader seems to be working for registered and unregistered hosts now. Was able to register from remote location. Thanks.
Hopefully Falko has the same results
-
RE: Chainloading failed
Updated to 7845, chainloading seems to fail if host is not registered.
I tried from a remote site using the location plugin. the host was manually entered. It worked. I was able to get in the boot menu, I did a host unregister. the host removed itself, then it would not pxe back to the boot menu. Complained about the chainloader. Manually added, worked again. I also tried this at the Main’s site using a VM. I network booted from the VM and being it was not manually registered, it gets the chainloader error. As soon as I manually add the host to FOG, it works perfectly.
-
RE: Host/Group replication between FOG Servers
All I get is invalid syntax. No clue what I am doing wrong.
-
RE: Host/Group replication between FOG Servers
@Wayne-Workman this is what i get:
Sorry, I am new with Linux, so it is all a learning curve for me.
-
RE: Host/Group replication between FOG Servers
When i do the Main server I get this: I will try the other things in a bit. Do I simply just copy and paste those commands in putty and which server do I do this on?
#!ipxe
set fog-ip 10.103.72.49
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.103.72.49/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.quickimage Quick Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.103.72.49/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.103.72.49/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.quickimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.103.72.49/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://10.103.72.49/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot -
RE: Host/Group replication between FOG Servers
@Tom-Elliott I just upgraded the Main and reinstalled the storage node yesterday afternoon