the multicast works fine across VLAN’s. However it seems like it ‘broadcasts’ to the VLAN that the server is located on at the same time.
Posts made by pac1085
-
RE: Multicast session flooding vlan
-
Multicast session flooding vlan
We have a FOG server which resides on our server VLAN (vlan 2). We image clients across VLANs (for example, vlan 4). Recently, during multicast sessions, our network guys claimed it caused an outage due to a flood of traffic on the VLAN the server resides on. I do not have a whole lot of details from them yet, but they claimed it was flooding the interfaces of all devices on that VLAN, much like a broadcast.
I will attach a capture of the multicast.log file showing the udp-sender parameters that were run on Monday.
in the mean time, has anyone had any issues like this?
We use FOG at several of our sites and as the local IT team enjoy using it very much. They are threatening to make us use WDS if we can’t find a root cause on this.
-
RE: Feedback: Snap-in system
I do not feel that application virtualization is a sutible replacement. We have a very large VMWare infastructure in place here, with ThinApp, and while it does have it uses it can not be used for a lot of things.
-
FOG Server "selector" for FOG Agent
We have an environment with multiple sites across the USA, and often find ourselves transfering system images between them. However, we usually have to modify/reupload the image at each site so it points to the local FOG server. This wasn’t so much a problem in the past, but now that we are using the hostname changer/auto domain join feature, it is starting to be.
Has anyone thought of a solution for this? I’m hoping something that can be done where we could point the FOG client to a single hostname that can point the FOG agent to the correct FOG server based on certain criteria. In our environment that criteria would be the second octet of the IP address.
-
RE: Feedback: Snap-in system
The existing snapin system isnt that bad. I don’t mind making snapins, but deploying them is clumsy. And so is trying to train people on how to properly deploy them.
Maybe if there was some sort of “Host Profile” template system.
For example, create a template that contains everything that would be normally manually defined in a group and be able to apply to a new group with 1 click. Image assoc, os assoc, snapin associations, AD settings, etc.
If we had this I could simply tell my technicians “Image training room 1 with the HR template”. Without having to tell them which snapins that contains etc. When it gets applied to the group, it would clear any previous snapin associations, service settings and anything else host specific that was changed.
-
RE: Feedback: Snap-in system
I would like to see a way to remove all snapins from a whole group. we repurpose PC’s around here alot and sometimes we setup a group of PC’s that have all sorts of different snapins associated to them. The only way to remove them is to do it snapin-by-snapin. When we have 30+ snapins it can take quite a bit of time.
I would also like to be able to change the time snapins are checked for, and the time the client waits after starting to check for snapins.