Support executed upgrd-ckv10-96.bin

add it for the root account as well, although support typically logs-in with nasadmin and then su to root.

Yes indeed, OFFHOURS

Thank you sir.

I was affraid it was the actual upgrade itself. I would have been a little upset it was done during the day

On this subject, here is a nice snippet to put in nasdamin's ~/.bashrc for anybody wanting to be notified of logins to the Control station:

# User specific aliases and functions

echo "ALERT - Shell Access to ${HOSTNAME} on:" `date` `who` | mail -s "Alert: Shell Access from `who | cut -d'(' -f2 | cut -d')' -f1`" your@email.com

hehe..i would be too . Have you scheduled an upgrade ?

How does EMC access your systems?

Hi

The pre-upgrade health check script you see is run prior to executing the upgrade.  In order for the Celerra technician to get approval for the upgrade from EMC's internal change control process, they have to run the script and collect its output.  It is a non-invasive script that simply outputs specific health-related system command outputs and formats them for review at EMC.  It essentially ensures that the system is ready for upgrade. 

If the script were to find any conditions that might interfere with the upgrade, no work would be done to correct those issues without first consulting with you.

Additionally, if you are concerned about EMC personnel accessing your systems, you can change the conditions of access within the support system.  Call the Support Center at (800) SVC-4EMC for assistance.  You can set the access to "Unrestricted Access", "Customer Permission Required", "WebEx", or "Customer Refused".

Customer Permission Required means that the Support Center must contact someone onsite before any dial-in is allowed to take place.  If you don't use ESRS or modem to access the Celerra, WebEx or Customer Refused could be set.

If you use ESRS to allow EMC access to the system, you can set your access monitoring and permissions there.

-bill

William, thank you so much for the exhaustive information! I really do appreciate it.

I don't mind EMC doing it's job, I'm just a little bit of a control freak when it come to my systems

modem / dial-up

JS Labonte,

Nice script!

While we are on the topic of auditing via the Control Station, I simply wanted to remind everyone that you can also take advantage of the native Linux Audit System (auditd and the various au* commands used to configure and query).  It is enabled by default and besides the custom audit.rules file  (/etc/audit/audit.rules) from EMC that relate to the Celerra/VNX file system, processes, etc, it is a standard implementation of the Linux feature.  It will track user authentications, modifications, etc. (message types). 

As root, you can configure/query the logs as follows:

/sbin/ausearch

/sbin/aureport

/sbin/auditctl

For instance, for a quick summary of the event log (audit.log) you can simply run:

/sbin/aureport

To query the event log, for instance:

1) /sbin/ausearch -i -m

Lists all of the possible message types

2) /sbin/ausearch -i -m ALL

Basically lists every entry, just as if you simply ran:

/sbin/ausearch [-i | --interpret]

3) /sbin/ausearch -i -m <message type>

Refines by message type such as: LOGIN, SYSCALL, etc

Since it is the standard Linux implementation of the Linux Audit System, you can of course review the man pages (or --help) for more information.

Of course, this is better than relying on the shell history which can be easily cleared.