Posts made by EduardoTSeoane

@benjamind It world for me bit i hace a little bit soecial case

@benjamind https://forums.fogproject.org/topic/13387/unable-to-change-multicast-nic

@fry_p Maybe too late, but in addition to complete a few:

You can configure the fog client to delayed-auto and to reboot the service on each error with the commands below recommended before start it:

sc.exe config FOGService start=delayed-auto
sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120.

@george1421 I confirm that exist powershell template :D:D:D .

@ayashkam You can do it, The automated snapin execution is basic for me, my images are living entities and my software requirements continously changes (Education environment with more than 250 different sites and more than 15.500 computers).

I have my image’s configured to install fogclient and start it on the first boot, you can do it with the unattended deployment procedures (setupcomplete.cmd) for example if you sysprep the images or use other ways like scheduling it at start up.

I download the installer with the postdownloadscript to ensure that the current version is installed. Take care because at the moment that you run the service the snapins start to be executed, you can have problems with another installations or the configuration can be disrupted by needed reboots. You know your systems and must take the cautions needed.

@benjamind @george1421

I’m using a master and nodes configuration with a lot of multihomed locations (140 as goal) with between 2 and 9 VLANS for node.

I solve this problem for my custom config with the procedure that i wrote on this link https://forums.fogproject.org/topic/13387/unable-to-change-multicast-nic/14 maybe it helps you.

It works for me, but i’m using a custom multihomed nodes installation with a beta customized location plugin to do all tasks locally on the VLAN.

I use custom modifications because if i try the next procedure i can get more than 350 locations/nodes.

Using that procedure as basis i think:

If you have a single multihomed master without nodes, maybe you can try to configure a StorageGroup for each VLAN, a StorageNode for each NIC and, using this data, a location for each VLAN and then configure pc’s on his VLAN location.

“TAKE A LOT OF CARE ON DISABLE REPLICATION!!!.”

If you need the Image replication service you can use a false user/password pair to avoid it or try to don’t assign images/snapins to that StorageGroups.

Reason to think that. MulticastManager also use management node ip to select the multicast iface. I think that I saw this on my experiments. Maybe @Sebastian-Roth can confirm it.

Try it at your own risk.

Plz wrote the test results.

@vanopstp15d try

mysqlcheck -r fog

@vanopstp15d
Restart service is for that question you do on the last post, maybe i missunderstood the question…
Is there any posibility to force the snapins with command line from the client (Windows)?

About the question:

I use persistent groups & location too but not Active Directory… and I haven’t that problem…

so… What about a database repair procedure?

[https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL](link url)

@JdenHartog said in Snapin File (exists):

.5.7 release.

do you try to restart de FOGSnapinHash service on the server?

@vanopstp15d
Fog service is an iteration of services, you can restart it and force to be executed with only stop/start the service. Take care, the services has an execution order, example if you put a task and a snapin, always be executed the task first. The order is by service list, not by launching time.

You can do it from the powershell console, locally or remotelly if you have remote powershell configured.

If you restart the fogservice you lost the useragent until you execute it again or restart the computer.

@aephk
This is not a solution, but maybe can help you.

All our images on the Images store are manually shrinked, we adjust the final size of the partitions from the postdownload script with our own criteria.

We are doing this from fog1.3.2, we are currently on FOG1.5.6.

We work a lot with scripts, we don’t use msi and exe, all our snapins are developed as scripts, usually powershell for windows and bash scripting for linux, we use sometimes php, python, perl… called from bash a so on.

Check the potential of the scripting for the 2 first points.
And as alternative to deploy software you can work with snapins+chocolatey

On the third point, we use fog snapins to start/stop services, deploy clients etc…

Currently we are using a reversed vnc server deployed/configured/started/stopped/removed as an unattended snapin, where we have firewalls, As GUI we use a Guacamole Gateway with a vnc-proxy, on the other side where we have not firewalls we are using Dameware and RDP to remote control. The services can be controlled with scripted snapins but the clients/servers/proxyes… must be provided as external services.

I only want to add, that with a deep knowledge of the targets, and with a good knowledge about scripting, and if you add a custom/complete toolset around FOG, you can get a pretty and usefull system admin/management environment.

Adding a comment:

Currently we are using false nodes to change the multicast tasks. I mean

To make multicast tasks on desired vlan we are creating a second master node to the location’s storage group, with nic an ip assigned on the vlan that we want to do the task and with false user/password to avoid a redundant synchronization.

By the moment, this solution is working with version 1.5.6 of Master and Nodes.

The node must be precedent on alphabetic order to the real node.

@Tom-Elliott Ok, I understand. That’s a problem to me because all the server’s ip on the service vlan’s are protected. Then i must have the StorageNode on the Management VLAN.

By the moment i’ve solved the problem like i said on the last post. It’s a valid solution for me. But when i have time i try to implement a plugin to handle this dinamically from the interface.

@blainey @george1421 Ok, i do some experiments with this.
I do that with a few modifications on default.ipxe and bootmenu.class.php to get the boot information from dnsmasq as proxydhcp. Take care with internal server routing.

@george1421 @Tom-Elliott Thank’s for the response.

Yes, I see that, by the moment I solve that with a few of dirty code modifying the multicasttask.class.php file to write multicast into the desired interface.

I’ll be pleased to work in a plugin that can do it dinamically.
But I need information about the hooks at least.

Great job!!!.

@Fernando-Gietz @Sebastian-Roth @george1421

Testing something more.

If i change the Storage Node’s ip then yes, multicast works into associated nic.

What is the purpouse of the nic interface on Storage Node General?

@Fernando-Gietz my previous version was 1.4.2 and we hsrdcode to force send by all nics. Current version is 1.5.6 without custom code. Only task typeedit location persidtengroups plugins

@Fernando-Gietz yes i try it but dont works.

@blainey It is possible to access your internal server using the router’s public IP address/forwarded port, but your router must support loopback network address translation (a.k.a. hairpin NAT) and be configured accordingly.

Without loopback translation in effect, IP packets destined for your router’s public IP address will arrive on its private network interface. Here the packets are simply dropped, usually because the router requires packets destined for its public IP address to arrive on its physical WAN interface (there are other possible ways this traffic may be handled, including NAT occurring, but the end result is always that the connection cannot be completed).

However, with loopback translation configured, when the packets destined for the public address arrive on the private interface, their destination address will be rewritten to be that of the internal server. Then the normal port translation will be applied, further resulting in the destination port being rewritten as well.

There are other options.

@Fernando-Gietz
This is the first i try but nothing, systemctl status FOGMulticastManager tellme than udp-sender is using eth0 and multicast continue to work on eth0.

Same if i change the nic on the NodeStorage Definition.