Ping, traceroute does not work but nslookup works

Have you ever came across a situation when nslookup works for name resolution but ping or traceroute does not work. Traditional unix commands does not rely on dns for name resolution unless specifically instructed via /etc/nsswitch.conf file. You will have to make an entry in front of hosts parameter:

hosts files dns

Comments

Post a Comment

Popular posts from this blog

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Linux LVM with EMC powerpath

How you plan to use Linux LVM with a multipathing software like EMc powerpath? The trick is to mask out the non emcpower devices from LVM view. This is to ensure any path failure is handled by the multipathing software rather than LVM itself. The underlying path management complexity is offloaded to multipathing software. When the command pvscan, is issued you see only the emcpower devices. You will have to enable the filter for accepting the emcpower devices and reject all the non emcpower devices inside /etc/lvm/lvm.conf file filter =[ "a|/dev/emcpower.*|", "r|/dev/sd*|", "r|/dev/cdrom|" ] Ensure only one filter is enabled.
Read more

Clariion storage processor IP address change

We recently spinned off to a new company from the parent one. As a result a major infrastructure change had to be performed on all our equipments. We had a few Clariions for which the storage processors IP address had to change, as were assigned a new block of IP address. Their are a few things that had to be taken care before undergoing an IP address change of he storage processor IP address. 1. If the Clariion is master node of the global domain, then someone else had to be promoted to be domain master before changing the IP address. That is it has to be demoted as a master domain node. 2. Then the clarrion has to be removed from the domain. That is the domain security has to be reset 3. The storage processor has to be rebooted Briefly, the steps are as follows: 1. Promote some other Clariion to be the master node of the domain. (This can be achieved through the Navisphere web based console). 2. Remove the Clariion from the domain. (This can be done through the Navisphere web conso...
Read more