Photo tweaks - PicMonkey
Make photo books @http://www.blurb.co.uk/
Sunday, 27 January 2013
Sunday, 13 January 2013
Setting static IP address on Red Hat
RHEL / Red hat / Fedora / CentOS Linux Static IP Configuration
For static IP config you need to edit the following files using a text editor such as vi. I have a post with some simple vi commands to help you achieve this.
#cd /etc/sysconfig/
Sample of my config
# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=cucm.pub
GATEWAY=192.168.1.1
Edit /etc/sysconfig/network-scripts/ifcfg-eth1
Sample of my config
DEVICE=eth1
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:**:**:**:**:**
IPADDR=192.168.1.50
NETMASK=255.255.255.0
ONBOOT=yes
Then make sure you have your DNS services in /etc/resolv.conf
# cat /etc/resolv.conf
Sample of my configsearch home.local nameserver 8.8.4.4 nameserver 8.8.8.8
Now restart the service like this
# /etc/init.d/network restart
and finally test like this:
# ifconfig eth1 # route -n # ping 192.168.1.1 # ping google.com
Unbuntu \ Debian
open with gedit or any other editor you feel comfortable with /etc/network/interfaces sudo gedit /etc/network/interfaceIf you are using DHCP, you will see the following lines auto eth0
iface eth0 inet dhcp
Now change the settings as below
auto eth0
iface eth0 inet static
address 192.168.1.5
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
Restart the neworking service using the following command
sudo /etc/init.d/networking restart
or service /networking restart
vi useful commands
To Get Into and Out Of vi
To Start vi
To use vi on a file, type in vi filename. If the file named filename exists, then the first page (or screen) of the file will be displayed; if the file does not exist, then an empty file and screen are created into which you may enter text.
* vi filename edit filename starting at line 1
vi -r filename recover filename that was being edited when system crashed
To Exit vi
Usually the new or modified file is saved when you leave vi. However, it is also possible to quit vi without saving the file.
Note: The cursor moves to bottom of screen whenever a colon (:) is typed. This type of command is completed by hitting the <Return> (or <Enter>) key.
* :x<Return> quit vi, writing out modified file to file named in original invocation
:wq<Return> quit vi, writing out modified file to file named in original invocation
:q<Return> quit (or exit) vi
* :q!<Return> quit vi even though latest changes have not been saved for this vi call
Moving the Cursor
Unlike many of the PC and MacIntosh editors, the mouse does not move the cursor within the vi editor screen (or window). You must use the the key commands listed below. On some UNIX platforms, the arrow keys may be used as well; however, since vi was designed with the Qwerty keyboard (containing no arrow keys) in mind, the arrow keys sometimes produce strange effects in vi and should be avoided.
If you go back and forth between a PC environment and a UNIX environment, you may find that this dissimilarity in methods for cursor movement is the most frustrating difference between the two.
In the table below, the symbol ^ before a letter means that the <Ctrl> key should be held down while the letter key is pressed.
* j or <Return>
[or down-arrow] move cursor down one line
* k [or up-arrow] move cursor up one line
* h or <Backspace>
[or left-arrow] move cursor left one character
* l or <Space>
[or right-arrow] move cursor right one character
* 0 (zero) move cursor to start of current line (the one with the cursor)
* $ move cursor to end of current line
w move cursor to beginning of next word
b move cursor back to beginning of preceding word
:0<Return> or 1G move cursor to first line in file
:n<Return> or nG move cursor to line n
:$<Return> or G move cursor to last line in file
To Start vi
To use vi on a file, type in vi filename. If the file named filename exists, then the first page (or screen) of the file will be displayed; if the file does not exist, then an empty file and screen are created into which you may enter text.
* vi filename edit filename starting at line 1
vi -r filename recover filename that was being edited when system crashed
To Exit vi
Usually the new or modified file is saved when you leave vi. However, it is also possible to quit vi without saving the file.
Note: The cursor moves to bottom of screen whenever a colon (:) is typed. This type of command is completed by hitting the <Return> (or <Enter>) key.
* :x<Return> quit vi, writing out modified file to file named in original invocation
:wq<Return> quit vi, writing out modified file to file named in original invocation
:q<Return> quit (or exit) vi
* :q!<Return> quit vi even though latest changes have not been saved for this vi call
Moving the Cursor
Unlike many of the PC and MacIntosh editors, the mouse does not move the cursor within the vi editor screen (or window). You must use the the key commands listed below. On some UNIX platforms, the arrow keys may be used as well; however, since vi was designed with the Qwerty keyboard (containing no arrow keys) in mind, the arrow keys sometimes produce strange effects in vi and should be avoided.
If you go back and forth between a PC environment and a UNIX environment, you may find that this dissimilarity in methods for cursor movement is the most frustrating difference between the two.
In the table below, the symbol ^ before a letter means that the <Ctrl> key should be held down while the letter key is pressed.
* j or <Return>
[or down-arrow] move cursor down one line
* k [or up-arrow] move cursor up one line
* h or <Backspace>
[or left-arrow] move cursor left one character
* l or <Space>
[or right-arrow] move cursor right one character
* 0 (zero) move cursor to start of current line (the one with the cursor)
* $ move cursor to end of current line
w move cursor to beginning of next word
b move cursor back to beginning of preceding word
:0<Return> or 1G move cursor to first line in file
:n<Return> or nG move cursor to line n
:$<Return> or G move cursor to last line in file
Saturday, 12 January 2013
CUCM Upgrade
CUCM Upgrade 6.1.4 up to 8.6 - MCS to VMWare
- Enable peer firmware sharing on all phones
- Upgrade IOS on all voice gateways (VG224s included)
- Install Device Pack on current system to get phone loads to a level (8.5.2 I believe) where they will take the code in CUCM 8.5
- Change IP address on one server. Also change in DNS. Shutdown. Move to DC. Bring back up. Ensure everything working. Check DB replication. If this server is the TFTP server, change option 150 on all DHCP scopes
- Reset all phones so they get new configuration file with changed server IP address. Confirm either on a sampling of phones or via web browser to phones
- Change config on all IOS voice gateways to include new server IP address
- Change IP address of CUCM on Unity. Restart Unity sevice. Confirm Unity connectivity to both CUCM servers
- Change IP address on second server. Also change in DNS. Shutdown. Move to DC. Bring back up. Ensure everything working. Check DB replication. If this is the TFTP server, change option 150 on all DHCP scopes
- Reset all phones so they get new configuration file with changed server IP address. Confirm either on a sampling of phones or via web browser to phones
- Change config on all IOS voice gateways to include new server IP address
- Change IP address of CUCM on Unity. Restart Unity sevice. Confirm Unity connectivity to both CUCM servers
- Upgrade to 8.5 on physical boxes. Allow phones to download 9.x firmware
- Upgrade TSP drivers on Unity for new version of TSP on CUCM
- Backup CUCM system
- Shut down publisher
- Install 8.5 in VMWare with exact same settings as the shutdown publisher including hostname, IP address, certificate information, admin password, shared secret, application username/password
- Restore publisher and by extension entire cluster from backup. Restart all servers
- Ensure functionality
- Shut down subscriber server
- Install 8.5 in VMWare with exact same settings as the shutdown subscriber including hostname, IP address, certificate information, admin password, shared secret, application username/password
- Restore subscriber from backup. Restart subscriber
- Upgrade to 8.6 on both. Complete CUCM outage for a couple of hours. Change VMWare guest operating system to RHEL 5.
- Testing
Subscribe to:
Posts (Atom)