how can I mass configure the Network Management Card (Type 9630) by using "FTP" to instead of "iniuti-v2"

[Anonymous user]

Because the "initti-v2"  will try to ping the NMC firstly, then upload/download the config.ini from NMC. 

Since the ping(icmp) protocol has already been blocked in the all over of our network,  we are only allowed to use the telnet/ftp in our network.     Therefore we can not use the initti-v2,  because it will stopped when it ping the NMC unsuccessfully.

So that , I am trying to use FTP to instead of "iniuti-v2".　I try to upload a new config.ini to the NMC by FTP,  however I could not overwrite the old config.ini.  Could you please give me some advice ?

or

Could you please upload a "revised edition" of iniuti-v2, that disabled its ping function.  so that I can bypass the ping , and directly upload/download config.ini by using iniuti-v2

ftp> dir

200 PORT Command okay.

150 File status okay; about to open data connection.

--wx-wx-wx  1 admin      admin      2288640 Nov 22 2011   apc_hw05_aos_517.bin

--wx-wx-wx  1 admin      admin      2190196 Dec  1 2011   apc_hw05_sumx_517.bin

-rw-rw-rw-  1 admin      admin        45000 Mar 17 10:16  config.ini

drwxrwxrwx  1 admin      admin            0 Feb  6 2136   db/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   ssl/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   ssh/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   logs/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   sec/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   dbg/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   lang/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   upsfw/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   rms/

drwxrwxrwx  1 admin      admin            0 Aug 31 2012   scg/

--w--w--w-  1 admin      admin          512 Mar 14 22:54  K2000.0

--w--w--w-  1 admin      admin        51617 Mar 17 10:16  config.ini

226 Closing data connection.

Thanks a lot

[BillP]

To clarify, the config.ini is not technically a "file" that resides on the Network Management Card all of the time. Via the dir output you showed, if you look at the first config.ini in the list, it is 45000 bytes in size. This is technically just a placeholder for the user to understand the file is available and you'll always see it at this size.

The config.ini is a "snapshot" of the configuration running in flash memory and is generated when you download it. Upon uploading a new, modified config.ini, the NMC parses and applies all of the values and then discards the file you uploaded. Thus, when you re-download it, any user comments would be removed and you'd download the new, current configuration assuming you made changes.

If the INI Util is not working because of the ICMP issue (which I'll go and verify and see what we can do), you could just create a script to automate FTP uploads if you want. Or, do them manually via FTP. You should just have to create a configuration you want, perhaps using the web UI since it is a bit easier, download the config.ini, and then you can upload it using FTP to make the changes you want. You can verify in the NMC event log that the changes have been applied or if there were any invalid values. You don't have to worry about there being two config.ini's in the FTP directory and it wouldn't prevent you from uploading the config.ini and overwriting the current configuration. If values did not change in the configuration upon checking by logging in or re-downloading, then we'll need to see if in the event log if it properly logged that a file was upload and if settings we changed.

[Anonymous user]

Thanks for your assistance!   I tried to upload a new config.ini to NMC.    It sounds the new config.ini overwrites the old config.ini.   Except the SNMP trap (the new config.ini  did not enable the snmp trap ), So it sounds the overwrite is not a fully overwrite.  Am I right ?  What item doesn't allow to be overwrited ? 

Thanks a again

[BillP · Accepted solution]

Everything is capable of being changed via config.ini. The only exception scenario is outlined here -> What are some features I need to be aware of while manipulating the config.ini file of a APC Network...

Do you mean you want to disable SNMP traps? What you've shown in the image (when you see a • in a column) is that at least 1 out of 4 recipients will receive the trap.

The ideal scenario is that you use the web GUI to make a configuration on one card, then download it, and cascade that config.ini.

So, please, confirm do you mean to disable traps or please be more specific about what is wrong with the trap configuration. Like is only one recipient receiving them and it should be more or did you just mean you wanted to disable.

Also, if you want, please provide the config.ini file you sent and then the one you get when you re-download it from this card. You can remove everything beyond [NetworkSNMP] and [EventActionConfig] sections if you'd like before posting.