Also, my bad this replication is from VNX5700 to another VNX5700.

@Ernes

- by doing "unalias echo", would that impact any existing setting (Replication) on either VNX?

- and, more importantly (read: curiously), why is this 'suddenly' happening?

i definitely don't see this on my two VNX5700. Is it in root's history or nasadmin ?

Ignore the unalias command since i misunderstood your question. You don't have an alias created for echo

@Ernes - no worries thank you for checking and clarifying.

@Dynamox - this is output when i log in, so i assume this is under the "root" directory. I do login as 'nasadmin'. Not sure if that answers your question (?)

Output of ALIAS below:

[nasadmin@xxxxxxx ~]$ alias

alias groupadd='echo Please use EMC Unisphere for User/Group management.'

alias groupdel='echo Please use EMC Unisphere for User/Group management.'

alias groupmod='echo Please use EMC Unisphere for User/Group management.'

alias l.='ls -d .* --color=tty'

alias ll='ls -l --color=tty'

alias ls='ls --color=tty'

alias useradd='echo Please use EMC Unisphere for User/Group management.'

alias userdel='echo Please use EMC Unisphere for User/Group management.'

alias usermod='echo Please use EMC Unisphere for User/Group management.'

alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'

Run the following command on the control station and paste the output: alias

It's nasadmin based on the output he provided. I checked on my VNX as well and don't see it as well. Try a control station reboot and see if that solves it.

[nasadmin@CONTROLSTATIONNAME~]$ history

One more thing. If you see the echo command when you run the above command then you can simply unalias the echo command. Just run: unalias echo

hi Dynamox,

Don't want to keep it lengthy, but here's a snippet from the Control Station. Its a VNX5700

[nasadmin@CONTROLSTATIONNAME~]$ history

    3  04/08/14 20:10:06 echo

    4  04/08/14 20:15:11 echo

    5  04/08/14 20:15:11 echo

    6  04/08/14 20:20:16 echo

    7  04/08/14 20:20:16 echo

    8  04/08/14 20:25:20 echo

    9  04/08/14 20:25:20 echo

  10  04/08/14 20:30:26 echo

  11  04/08/14 20:30:26 echo

  12  04/08/14 20:35:30 echo

  13  04/08/14 20:35:30 echo

  14  04/08/14 20:40:35 echo

  15  04/08/14 20:40:35 echo

  16  04/08/14 20:45:39 echo

  17  04/08/14 20:45:40 echo

  18  04/08/14 20:50:44 echo

  19  04/08/14 20:50:44 echo

  20  04/08/14 20:55:48 echo

  21  04/08/14 20:55:48 echo

  22  04/08/14 21:00:53 echo

  23  04/08/14 21:00:53 echo

  24  04/08/14 21:05:57 echo

  25  04/08/14 21:05:57 echo

  26  04/08/14 21:11:02 echo

  27  04/08/14 21:11:02 echo

  28  04/08/14 21:16:06 echo

  29  04/08/14 21:16:06 echo

  30  04/08/14 21:21:11 echo

  31  04/08/14 21:21:11 echo

  32  04/08/14 21:26:15 echo

  33  04/08/14 21:26:15 echo

  34  04/08/14 21:31:19 echo

  35  04/08/14 21:31:19 echo

  36  04/08/14 21:36:23 echo

  37  04/08/14 21:36:23 echo

  38  04/08/14 21:41:28 echo

  39  04/08/14 21:41:28 echo

  40  04/08/14 21:46:32 echo

  41  04/08/14 21:46:32 echo

  42  04/08/14 21:51:36 echo

  43  04/08/14 21:51:36 echo

  44  04/08/14 21:56:41 echo

  45  04/08/14 21:56:41 echo

  46  04/08/14 22:01:47 echo

  47  04/08/14 22:01:47 echo

  48  04/08/14 22:06:52 echo

  49  04/08/14 22:06:52 echo

  50  04/08/14 22:11:56 echo

  51  04/08/14 22:11:56 echo

  52  04/08/14 22:17:00 echo

  53  04/08/14 22:17:00 echo

  54  04/08/14 22:22:05 echo

  55  04/08/14 22:22:05 echo

  56  04/08/14 22:27:09 echo

  57  04/08/14 22:27:09 echo

  58  04/08/14 22:32:14 echo

  59  04/08/14 22:32:14 echo

I just saw your reply to dynamox and I misunderstood what you were asking. I thought that you said whenever you run an echo command a ping is being issues.

I haven't sen this one before. Rebooting the control station is the only thing I can think of. Won't impact anything and the other control station will become primary.