Posts from category "2010"

iSCSI storage - enable JUMBO frames for ESXi 4

You must create the vSwitch and change the MTU to 9000.  For this example, vSwitch7 will be the name you would replace with your own:

esxcfg-vswitch -a vSwitch7

Then, set the MTU of the vSwitch:

esxcfg-vswitch -m 9000 vSwitch7

esxcfg-vswitch -l - will list all the vSwitches on actual ESXi. It should look something like this:

Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks

     vSwitch7             64                  1            64                 9000

iSCSI access is controlled by a VMkernel interface and assigned to a port group on the vSwitch.

So create the portgroup:

esxcfg-vswitch -A vSwitch7

Then create the VMkernel interface:

esxcfg-vmknic -a -i -n -m 9000

If you named the port group "iSCSI_storage", for example, and your IP is 192.168.0.1/24, the command would be like this:

esxcfg-vmknic -a -i 192.168.0.1 -n 255.255.255.0 -m 9000 iSCSI_storage

The last step is to add a physical NIC to the vSwitch.  This can be done via the GUI optionally:

esxcfg-vswitch -L vSwitch7

You must enable jumbo frames on your physical switch for this to work!

Backup ESXi firmware (configuration) with PowerCLI

Login directly to ESXi (or through vCenter server) with PowerCLI shell:

Connect-VIserver -Server IP_address

See help from cmdlet Set-VMHostFirmware:

Get-Help Set-VMHostFirmware

No more PERL scripts and nothing else...just PowerCLI and go...

For restore procedure you must put ESXi host into MAINTENANCE mode.

Example

BACKUP:

Set-VMHostFirmware -VMHost esxi_IP_address -BackupConfiguration -DestinationPath C:\ -Server vCenter_IP_address

RESTORE:

Set-VMHostFirmware -VMHost esxi_IP_address -Restore -SourcePath C:\ -HostUser -HostPassword -Server vCenter_IP_address

VMware ESXi SSH access

After installing ESXi first thing to do...by default it is disabled. By enabling it you must strictly know what are you doing. Here are basic steps:

- go to the ESXi console and press alt+F1

- type: unsupported

- enter the root password

- type vi /etc/inetd.conf

- look for the line that starts with #ssh

- uncoment - remove the #

- save /etc/inetd.conf by typing :wq!

- restart the management service /sbin/services.sh restart

Call restriction in Cisco Callmanager

For solving problems related to call restriction in term of "you can call international countries and you can't, you can call only local numbers etc" the best way in callmanager configuration is to use calling search space. Following are the basic steps included in this kind of configuration - just one way to accomplish that fast:

- define Partition (Class of Control-->Partition...) with appropriate name INT, LOC for example

- define calling search space and join predefined partitions that are already created

- in Route pattern join adequate partition to it

- in Device under local number define calling search space that is already created

That's it...it should work now...

Callmanager VMware - virtual MAC address change

Useful for some Voice tests and Demo labs in virtual environments - and off course totally unsupported:

- boot the CUCM server with CentOS Disk1 (for me it was CentOS, you could use something else...

- type linux rescue at the boot: prompt

use the chroot command to change the root to the CUCM partition

- chroot /mnt/sysimage

edit the eth0 configuration file

- vim /etc/sysconfig/network-scripts/ifcfg-eth0

add or change the MACADDR variable in the ifcfg-eth0 file

- MACADDR=xx:xx:xx:xx:xx:xx

- save and close (or write and quit) with the :wq option inside vim

edit the hardware config file

- vim /etc/sysconfig/hwconf

change the network.hwaddr variable

network.hwaddr: xx:xx:xx:xx:xx:xx

- save and close with the :wq option inside vim

- exit Linux rescue mode

After all, test to see if it's OK now

- login at CM console

- show network eth0 detail...