Jun 13, 2014 2.โปรแกรม Symantec Ghost Multicast Server 3.แผ่น CD หรือ USB Hiren Boot เพื่อ Boot Ghost Network support. Symantec Ghost Solution Suite Server Configuration Utility 8 Symantec Ghost Solution Suite Server Configuration Utility Table 1-1 Options on the Symantec Ghost Solution Suite Server. It seems that using the multicast function in Ghost will cause the ADT product to stop responding and prevent users from using their keycards to access the building! Now this can be solved by either using Symantec's Unicast or Subnet targeted broadcast or just leaving enterNET off your network.
I'm running MultiCast Imaging with Symantec Ghost. The image I'm pushing out is 500GB. It was taking me over 24 hours to push the image out as I was only getting 200MB per minute.
My network was gigabit with a HP ProCurve Switch 2810-48G switch and gigabit NIC's in all the workstations.This gets me towards my actual question: Symantec Ghost is on it's best when it uses Mulitcast or even Directed Broadcast. However, both traffic doesn't reach the clients. The clients can connect to the GhostCast Server (I can see them in their respected IGMP- Multicast groups on RAR), the server actually 'starts the process', but nothing happens. Clonezilla server edition: A DRBL server must first be set up in order to use Clonezilla to do massive clone (Both unicast and multicast are supported) Clonezilla Homepage. PING (Ping is not Ghost) is a live Linux ISO, based on the excellent Linux From Scratch (LFS) documentation. Symantec Ghostcast Server Download symantec ghostcast server download Dec 04, 2013 Free Download Symantec Ghost Solution Suite 2.5.1 - A popular and reliable corporate imaging and deployment solution that helps companies ensure tha.Symantec Ghost™ Solution Suite is an award-winning software solution for imaging and deploying. Like Ghost Cast Server and DeployAnywhere.
Why was it going so slow?Norton Ghost Multicast Server
After doing some research I found out that the HP switches have IGMP (Internet Group Management Protocol) disabled by default. IGMP is used to manage the membership of Internet Protocol multicast groups. A ghost cast session is an IGMP group, workstations need to join the IGMP session on the switch to participate in IGMP group traffic. When IGMP is disabled on the switch, the switch treats the multicast traffic as broadcast traffic sending it out over all ports in the specified VLAN - meaning every PC on the network receives the communication. Every PC or device on the VLAN recieves every packet sent from the ghost cast session as they do not have an application listening on the specified port; they will drop the packets.
This network is one big VLAN. Some devices on the VLAN could not support high speed network connectivity even though they had a gigabit NIC. One of these devices was a PACom WebGuard Camera Video Surveillance system. This Camera System was also receiving every packet from the ghost cast session - however because it is not designed to deal with such a large amount of data it was dropping packets meaning the ghostcast server needed to slow down to ensure every PC on the network received the data. A broadcast will only go the speed of the slowest device on the network. Bad cables will also effect the speed of the broadcast. Multicasts have the same principal, they will only go the speed of the slowest device in its multicast group, however you have narrowed it down to a group of devices instead of all devices in a specified VLAN.
To enable IGMP on a VLAN you just enter ip igmp
into the switches config under the right area:ProCurve Switch 2810-48G# show run
Running configuration:
; J9022A Configuration Editor; Created on release #N.11.15
hostname 'ProCurve Switch 2810-48G'
snmp-server contact 'Clint Boessen'
ip default-gateway 192.168.30.2
snmp-server community 'public' Unrestricted
vlan 1
name 'DEFAULT_VLAN'
untagged 1-48
Symantec Ghost Multicast
ip address 192.168.30.50 255.255.255.0
ip igmp
exit
spanning-tree
password manager
You can also enable IGMP using the HP Web Interface if you have it enabled. Notice when I made the config change in the switches command shell it also updated it in the GUI:
If you have IGMP turned on but you are still experiancing slow ghosting speeds there may be another feature enabled called Automatic Broadcast Control (ABC). When you enable ABC, it automatically sets the broadcast limit (Bcast Limit) on all switch ports to 30% (except for any ports for which you have already set the Bcast Limit manually to a nonzero value). Please do some research into ABC if you have IGMP enabled but are still experiancing slow speeds.
Now with IGMP on we are getting awesome speeds:
The below performance monitor graph shows my Disk Speed in Megabytes per second (MBPS) on the ghost server. As you see my ghost session is getting between 20 to 30.
I'm running MultiCast Imaging with Symantec Ghost. The image I'm pushing out is 500GB. It was taking me over 24 hours to push the image out as I was only getting 200MB per minute.
My network was gigabit with a HP ProCurve Switch 2810-48G switch and gigabit NIC's in all the workstations.
Why was it going so slow?
After doing some research I found out that the HP switches have IGMP (Internet Group Management Protocol) disabled by default. IGMP is used to manage the membership of Internet Protocol multicast groups. A ghost cast session is an IGMP group, workstations need to join the IGMP session on the switch to participate in IGMP group traffic. When IGMP is disabled on the switch, the switch treats the multicast traffic as broadcast traffic sending it out over all ports in the specified VLAN - meaning every PC on the network receives the communication. Every PC or device on the VLAN recieves every packet sent from the ghost cast session as they do not have an application listening on the specified port; they will drop the packets.
This network is one big VLAN. Some devices on the VLAN could not support high speed network connectivity even though they had a gigabit NIC. One of these devices was a PACom WebGuard Camera Video Surveillance system. This Camera System was also receiving every packet from the ghost cast session - however because it is not designed to deal with such a large amount of data it was dropping packets meaning the ghostcast server needed to slow down to ensure every PC on the network received the data. A broadcast will only go the speed of the slowest device on the network. Bad cables will also effect the speed of the broadcast. Multicasts have the same principal, they will only go the speed of the slowest device in its multicast group, however you have narrowed it down to a group of devices instead of all devices in a specified VLAN.
To enable IGMP on a VLAN you just enter ip igmp into the switches config under the right area:ProCurve Switch 2810-48G# show run
Running configuration:
; J9022A Configuration Editor; Created on release #N.11.15
hostname 'ProCurve Switch 2810-48G'
snmp-server contact 'Clint Boessen'
ip default-gateway 192.168.30.2
snmp-server community 'public' Unrestricted
vlan 1
name 'DEFAULT_VLAN'
untagged 1-48
ip address 192.168.30.50 255.255.255.0
ip igmp
exit
spanning-tree
password manager
You can also enable IGMP using the HP Web Interface if you have it enabled. Notice when I made the config change in the switches command shell it also updated it in the GUI:
If you have IGMP turned on but you are still experiancing slow ghosting speeds there may be another feature enabled called Automatic Broadcast Control (ABC). When you enable ABC, it automatically sets the broadcast limit (Bcast Limit) on all switch ports to 30% (except for any ports for which you have already set the Bcast Limit manually to a nonzero value). Please do some research into ABC if you have IGMP enabled but are still experiancing slow speeds.
Now with IGMP on we are getting awesome speeds: