** from emc eservice doc

The following is a Primus(R) eServer solution:

ID: emc262797
Domain: EMC1
Solution Class: 3.X Compatibility

Goal       How to correct Naviagent errors when Control Station is failed over to CS1

Fact       Product: Celerra

Fact       Product: VNX Series

Fact       Product: VNX Unified/File

Fact       Product: VNX VG8

Fact       Product: VNX VG2

Fact       EMC SW: NAS Code 6.x

Fact       EMC SW: NAS Code 7.x

Fact       EMC SW: NAS Code 5.6.50 and later

Symptom    Naviagent messages unexpectedly exited logged in /var/log/messages every five  minutes for Navisphere agent "cannot create messages directories"

Symptom    Naviagent errors occurs when Control Station is failed over to CS1.

Symptom    Call home message:

Slot 1 becomes primary because of timeout.

Symptom    /var/log/messages

CS_PLATFORM:NaviEventMonitor:CRITICAL:4:::::CLARiiON event number 0x0 to /etc/Unisphere/backup/navimon.log. ExtCode1=107373568<http://remedytools.rtp.lab.emc.com/nsgview.pl?entry=107373568>,; ExtCode2=log.

Symptom

/var/log/messages show the following errors:

Feb  11 11:22:19 emcnas_i0 EMCServer: nas_mcd: daemon "Apache daemon" unexpectedly exited (status = 0) ifexit=1 exitstatus=0 ifsignal=0 termsig=0 ifstop=0 stopsig=0 ifdump=0
Feb  11 11:22:19 emcnas_i0 EMCServer: nas_mcd: daemon "Naviagent" unexpectedly exited (status = 11) ifexit=0 exitstatus=0 ifsignal=1 termsig=11 ifstop=0 stopsig=0 ifdump=0
Feb  11 11:22:19 emcnas_i0 login(pam_unix)[27969]: session closed for user nasadmin
Feb  11 11:22:22 emcnas_i0 Navisphere Agent[31217]: Error: Cannot create messages directory /etc/Unisphere/messages/
Feb  11 11:22:22 emcnas_i0 Navisphere Agent[31217]: Error: Cannot create event log backup directory /etc/Unisphere/backup/
Feb  11 11:22:22 emcnas_i0 Navisphere Agent[31217]: Open application log failed

Error re-occurs after five minutes:

Feb  11 17:27:34 emcnas_i0 Navisphere Agent[1287]: Error: Cannot create messages directory /etc/Unisphere/messages/
Feb  11 17:27:34 emcnas_i0 Navisphere Agent[1287]: Error: Cannot create event log backup directory /etc/Unisphere/backup/
Feb  11 17:27:34 emcnas_i0 Navisphere Agent[1287]: Open application log failed

Cause      Installations at these code levels don't create the symbolic link for the Naviagent service to start properly on CS1. The symbolic links created from installation point at /etc/Navisphere instead of /etc/Unisphere on CS1, which is what the naviagent service is looking for on start-up.

Fix        Create the symbolic links and directories while the Control Station is failed over to CS1:

1.      ln -s /nas/etc/Navisphere/ /etc/Unisphere/
2.      mkdir /etc/Unisphere/messages
3.      mkdir /etc/Unisphere/backup

Monitor for naviagent service to start on next 5-minute interval:

$ ps -ef | grep -i navia
root      9198  2831  0 Feb11 ?        00:00:02 /nas/opt/Navisphere/bin/naviagent -d -f /nas/etc/Navisphere/agent.config -r /nas/log

Note       CS1 has been re-installed and problem persists.

This thing needs to be done with the CLI on the control station.

So here is howto do that.

ssh nasadmin@[vnx cs]
>/nas/log/webui/alert_log

The error should be removed, if not logout of Unisphere and log back in.

Accorting to cisco documentation the ASA will deny new sessions if you use TCP logging and that the syslog server is unreachable

If you are using TCP as the logging transport protocol, the ASA denies new network access sessions as a security measure if the ASA is unable to reach the syslog server, if the syslog server is misconfigured, or if the disk is full.

UDP-based logging does not prevent the ASA from passing traffic if the syslog server fails.

See the link

Set “logging permit-hostdown

1. Log on to the CS as root
2. Create the IP alias for the CS
   /nas/sbin/nas_conrig -IPalias -create 0
3. Answer no to the question “Do you want slot_0 IP address x as your alias.
   This will allow you to set another IP that points to the active unit, and still be able to talk to the standby unit.
4. Then specify the IP
5. Then view what you did with :
   /nas/sbin/nas_config -IPalias -list

Configuration Issues

The Local Tech Support Mode for the host localhost.localdomain has been enabled.

Remote Tech Support Mode(SSH) for the host <server> has been enabled

If the timeout setting to stop the service has been set to 0, effectively disabling the timeout, this warning is permanently displayed.

Resolution

Note: This article pertains to vSphere 4.x. For vSphere 5.0, see Cluster warning for ESXi Shell and SSH appear on an ESXi 5 host (2003637).

In vSphere 4.1, you can enable Remote Tech Support Mode (SSH) and Local Tech Support Mode on ESXi from the vSphere Client, as well as from the Direct Console User Interface (DCUI).

This message is a proactive security measure designed to ensure that administrators are aware that remote access has been enabled for the server.

Prior to vSphere 4.1 Update 2, disabling Remote Tech Support Mode (SSH) and Local Tech Support Mode is the only way to prevent this warning from appearing. In vSphere 4.1 Update 2, you can disable the Remote Tech Support Mode Remote (SSH) and Local Tech Support Mode warmings from appearing on the hosts.

To disable these warnings:

Select the ESXi host from the Inventory.

Select Advanced Settings from the Software menu.

Navigate to UserVars > UserVars.SupressShellWarning.

Set the value from 0 to 1.

Click OK.

via VMware KB: Cluster warning shown in vCenter Server when Remote Tech Support Mode (SSH) or Local Tech Support Mode is enabled.

via Remove the “host currently has no management network redundancy” warning from your whitebox HA enabled ESX cluster « Yuri’s Technology Blog.

VPN: Troubleshooting IPsec on IOS and ASA devices.

Video: Ask the Experts (vLog) ASA Version 8.3 NAT Configuration.

1. Create the access list that will tell what to capture
   access-list packetcapture-test permit ip any any
2. Create the capture “bucket”.
   capture captureitem access-list packetcapture-test interface [ifname]
3. Do traffic
4. Look at it
   show capture captureitem

Delete the capture

1. no capture captureitem access-list packetcapture-test interface [ifname]
2. no access-list packetcapture-test permit ip any any