Thanks for getting back to me. I figured it out. OS_install is VERY particular about what things are named, and how it ends up being laidout. It must install to location=/csminstall
A couple of things that you can do to troubleshoot this is log the ipsec filtering activity.
lsfilt -v4 -O will list all the current rules - logging might be disabled on the rules. If so, you will need to modify the rules using smitty, or the chfilt command.
In /etc/syslogd.conf add a line like: local4.info /data/logs/syslog/local4.info rotate time 1d size 1m
and before refreshing the syslogd touch the file name. Files must exist beforehand or syslogd will not write to them.
then run the command:
mkfilt -g start -v 4
to actiually start the logging.
lsfilt -v4 -a lists the active filters - the dynamic deny filters are the ones created by the SHUN mechanism.
I didn't pick up on DNS being involved with it before, but if you have a DNS problem where the hostname being presented to AIX does not look up as it should, the symptoms are that you will get a a long hanging delay of some minutes from the telnet connection the screen clearing before any login prompt appears. By putting entries in your /etc/hosts and setting /etc/netsvc.conf to use that ahead of DNS, you can work around that.
Note the order in /etc/hosts is important - if you have lines with duplicated IPs or the same hostnames against several IPs, the first such line in the file is the one that is used. So where you've changed the hostname for the same IP, make sure you have the new hostname first if you don't delete the old one.
Check also whether you've been using tcp_wrappers in /etc/inetd.conf for the telnet line - check your /etc/hosts.allow settings if so - symptoms there are no connection with immediate error.
When I get my nim server started up (I am 5 hour plane trip from my nim server, now offline) I'll take a look. However, you might just try using: smitty nim ... Administer ... Manage Resources->Define Resources
In the dialog that is there linux_source - whatever it's name may be - is one of the resource types that can be defined. You will recognize it! and then press ESC-6 (Escape 6 - two key presses) to see the command it makes.
or, from the command line just type:
nim -o define
and read carefully the error/syntax message presented.
The CDE subsystem starts, and remembers the hostname. If there is nothing critical, a reboot is usually the easiest solution. However, before you do so you should get on a command prompt and make sure that host and nslookup return identical values for the hostname.
What is very important for AIX the start is the existence of at least two entries in /etc/hosts. localhost itself, plus the hostname and address.
regarding your hostname WebSM - capital letters are not just a pretty formatting on UNIX. And clients that do not support case (e.g. Windows) are undefined (but basically using lowercase) when connecting via cmd.exe and telnet.exe. From a linux desktop (that usually has not installed telnet - which is why I am thinking windows) your problem is probably because the windows client was communicating the name websm - AIX does a check of the IP address connecting to it, as well as the name sent to it to connect (I am assuming ping did work - meaning the DNS did find WebSM and return an IP address.)
Corrections: for CDE - stop and start the daemons. Easiest way is to reboot (it is so long ago I have forgotten which command I need to find to kill). For the hostname: use lowercase, or at least provide an alias in lowercase. Further, add the line: hosts=local4,bind4 (or local,bind for dual IPv4 and IPv6 - you can even get fancy and say local6,bind4,local4,bind6 - or any combination - also nis) in the file /etc/netsvc.conf.
Running AIX6.1 with oracle 10.2g. I am currently using aixpert to harden the OS. The high settings have been applied (with all the usual precautions i.e. not locking root), however there is one sticky point - using 'shun' host/port with the IPSec element of the 'high' level configuration.
As I understand it the shun config protects various ports, that is ok - but it seems to stop oracle working. I am not a DBA, but understand that oracle uses port 1521 (maybe others as an increment on this port) and not any of the ports that are configured to be protected by the 'shun' setting.
Any thoughts of how I may overcome this?
I guess I could potentially drop the IPSec config altogether, but I would like to understand why Oracle reacts as it does.
I suggest exportvg then importvg. Never seen anything like that either - hangs with locks yes, but not straight back to the prompt with no further error. Why is it apparently getting locked, not rootvg I assume, is it being shared in some way, is there a process running in cron say that kicks off to lock it when you leave the machine idle ?
No appology necessary, we like quick the to answer questions.
Everything there appears to be mirrored - Copies 2, as well as the fact of double the PPs for the LPs. But to prove it as to where the mirroring is exactly, run the map option:
lslv -m LVNAME
That will show you up to three columns of output, one for each possible physical PP copy of each logical LP in the LV. What you want to see is hdisk0 all in one column and hdisk1 say in the next column and no mixing of hdisks in a column - that would then show strict mirroring.
hd5 you mention specifically is just 1 LP big and so has 2 PPs to mirror it, each other one has X LPs and X*2 PPs too.
smit mirrorvg - one way to create a mirroring in rootvg
Note if you have physically the ability to attach the new disk as well as the existing ones, you might want to create the third copy on to the new disk, before you remove the going bad copy on the bad disk to drop back to 2 copies. smit mklvcopy - to add copies LV by LV, smit rmlvcopy - to remove a copy one by one.
smit unmirrorvg - to remove a complete VG mirror copy (make sure it's the good disk copy you keep of course)
Take the steps to remove all the data logically from the bad disk before you remove the bad disk physically, i.e. get it out of the volume group and completely remove all logical devices before physically doing anything with it.
The LV or LVs with those two STALE partitions are the ones affected of course,
