Remove ASI IP

DCIM_Support · ‎2020-07-03

Hello,
I will be moving from an AP9470 to a VM. This will mean changing to a new IP. So I want to make sure that I can delete the ASI IP of the AP9470 from all of my devices. I've done the following testing:

I discovered a device in the VM.

By uploading the config.ini file I can see that Expert production and Expert VM are both installed in the device (150.203.4.136 is production, 130.56.15.17 is VM, I’ve removed the comment lines):

[SecureInterface]
Access=disabled
AuthenticationProtocol=MD5
TrapPort=9952
CurrentASISubscriber=150.203.4.136:162, ISX Manager
CurrentASISubscriber=130.56.15.17:162, ISX Manager

Then I downloaded this config.ini file to remove the Expert production:

[SecureInterface]
RemoveASISubscriber=150.203.4.136

This didn’t work and I’ve tried this several times over the last eight years and it’s never worked. Can you tell me how to make it work? I need to make it work as when I hand back the current production IP, it may get re-used and my devices therefore should not be sending it events.

Thanks, Geoff

DCIM_Support · ‎2020-07-03

Geoff,

The device would need to be removed from the old server first, or at least have the priority scanning option unchecked, which would stop the StruxureWare Data Center Expert server from automatically adding itself back into the NMC as an ASI Subscriber. You can then remove the setting from the NMC by making the following change in the config.ini file and putting it back onto the device via ftp:

from: CurrentASISubscriber=10.10.10.10:162, ISX Manager

to: RemoveASISubscriber=10.10.10.10:162, ISX Manager

Regards,

Cory

See Answer In Context

DCIM_Support · ‎2020-07-03

Hi Geoff, thanks for posting. Lets see who can be of assistance here. @community any ideas? Kind regards Ditte

DCIM_Support · ‎2020-07-03

Geoff,

The device would need to be removed from the old server first, or at least have the priority scanning option unchecked, which would stop the StruxureWare Data Center Expert server from automatically adding itself back into the NMC as an ASI Subscriber. You can then remove the setting from the NMC by making the following change in the config.ini file and putting it back onto the device via ftp:

from: CurrentASISubscriber=10.10.10.10:162, ISX Manager

to: RemoveASISubscriber=10.10.10.10:162, ISX Manager

Regards,

Cory

DCIM_Support · ‎2020-07-03

Hi Cory,

thank you very much. I never really spent the time playing with this, as it was only of academic interest. So I always followed the instructions in the config.ini, not knowing they were incorrect and not thinking to get creative.

I've tested what you said and now I've got full control of the ASI settings.

DCIM_Support · ‎2020-07-03

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.