Daz's bits and bobs …bytes bits
As per below. First you will need to install samba client.
In Fedora / Centos …
yum -y samba-client
then use the mount command to mount the share to a directory…
mount -t cifs -n //192.168.9.70/software /mnt/sharename -o username=guest,password=
It will be similar in other distros. Remember to create the /mnt/sharename directory before trying to mount any share to the directory. Directories are created like so;
mkdir /mnt/sharename
Or lack of.
You must insure that your drives are using the sata driver (if they are sata disks), quickest way to check is that they will be called sda sdb etc…. and not hda hdb, as this is the default IDE driver and will slow down the performance majorly.
How to check performance;
hdparm -tT /dev/hda
Modern drives should be getting over 50MB/s easily. If your getting about 5MB/s you have the problem.
How to Fix;
I had to change the sata mode to Enhanced in the bios and disable any of the on-board IDE controllers. When rebooting all your device names will change, and you will need to edit the /etc/fstab file as appropriate.
Apparently this is due to a conflict in the drivers, and them confusing your SATA drives as standard IDE disks.
Setting up a trunk between switches
Enable Switch to enable mode
Configure Terminal Enter global configuration mode
Interface FastEthernet0/1 Entering interface configuration for port 0/1. This is where you pick the port you want to trunk.
Switchport mode trunk Set port to trunking mode.
Switchport trunk encapsulation dot1q Set trunk type to 802.1q. If your switch only supports either ISL or 802.1q, this command does not exist because there is nothing to specify. This command only works when you can choose between the two.
Switchport trunk allow vlan 10-15,20 Allow only VLANs 10 through 15 and VLAN 20. It is important that you restrict the VLANs to only the ones you need for security best practices.
Exit Exit interface
Exit Exit global configuration
copy run start – save changes to nvram
Setting a switch up as a vtp client…. (VLAN client — cannot modify VLAN information)
vlan database enter vlan database
vtp client set switch vtp to client mode
vtp domain domain-name set switch to this domain – server switch will propergate vlan information across
possible to also set a password
Reset switch to factory defaults….
write erase
reload
Ensure you select NO to “do you wish to save changes”
How to make changes to multiple ports at same time;
interface range FastEthernet 0 – 23 (works on newer IOS)
Else its good ole notepad and terminal – rem that Ctrl-C (as it is sent to the session) does not work in terminial, you have to right cilck and copy. Though its easier to start a capture straight after you type show running-config, modify in notpad and paste back into config terminal.
What should I do after I successfully convert my virtual machine?
If you change from a multi-processor system to a uni-processor system you need to manually change the HAL on the Windows server after the conversion. To do this go into Device Manager after the machine first boots and discovers it’s new hardware and then click on Computer then right-click on the processor and select Update Driver. Then select Install from specific location and then Don’t search I will choose the driver to install. Then select show All compatible hardware and select the appropriate processor. For example, if you went from a dual cpu to a single cpu then select ACPI uni-processor PC instead of ACPI multi-processor PC. You will need to reboot once you change this. To verify what HAL you are using you right-click your hal.dll in c:\windows\system32 and select the Version tab and select Internal Name and it should say halmacpi.dll for multi-processor acpi and halacpi.dll for uni-processor acpi.
Next clean up all the non-present hardware after the P2V conversion. To do this go to a CMD prompt and type;
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
DEVMGMT.MSC
then select Show Hidden Devices. Delete any old grayed out hardware. Next remove any vendor specific applications/drivers. For example on a HP server you should go to Add/Remove programs and remove any HP management agents, survey utility, array config utility, version control agent, etc. Also check your NIC and make sure there are no vendor specific drivers there (ie. teaming). Check the Services to see if all there is anything vendor specific related there and disable any services that are.
these are tested from experience…. (the following is true on vmware server 1.0.6 on a linux host)
watch your pings – ping your guests… they should never loose a ping. If they do you are loading the cpu to high and the host cannot process the network queries. As above use only one virtual cpu. Also ensure you have the latest network driver loaded for your NIC on the host.