NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

EF & E-Series, SANtricity, and Related Plug-ins

SMcli Configuration File broken

A_Clutton
5,827 Views

Hey Guys

 

I wonder if anyone has seen this problem.  Basically when you run the command "SMcli -d" it shows you a list of the connected SANs the software knows about. Somehow one of our users has manged to add two of the same SAN to the configuration and now we can't remove it.  I can remove the last entry fine but not the first two (as they are the same).

Does anyone know where the configuration file is located?

See below (I redacted the names).  Any ideas?

 

netapp-failed1.png

Trying to remove it:

netapp-failed2.png

 

1 ACCEPTED SOLUTION

A_Clutton
5,755 Views

Thanks Jeff

 

Unfortunatley the document doesn't state where it keeps the configuration files or anything.

 

I did however, after doing some searching, found that the SMcli configuration files are kept in /var/opt/SM/ (under Linux).

The files are called emwdata_v04.bin and emwback_v04.bin for 08.30+.  Removing both of these files allowed us to setup the configuration file correctly.

View solution in original post

2 REPLIES 2

Jeff_Yao
5,784 Views

https://library.netapp.com/ecm/ecm_get_file/ECMP1394151

page 15-17 is talking about the syntax of smcli. hopefully helps

 

thanks

 

Jeff

A_Clutton
5,756 Views

Thanks Jeff

 

Unfortunatley the document doesn't state where it keeps the configuration files or anything.

 

I did however, after doing some searching, found that the SMcli configuration files are kept in /var/opt/SM/ (under Linux).

The files are called emwdata_v04.bin and emwback_v04.bin for 08.30+.  Removing both of these files allowed us to setup the configuration file correctly.

Public