Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84864members
354353posts

DCE alarm trigger not instantly for APC device

EcoStruxure IT forum

A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.

sesa157186_brid
Ensign Ensign
Ensign
0 Likes
1
512

DCE alarm trigger not instantly for APC device

Hi Team ,

 

We just refer as below K base for priority scanning and found some of APC device trigger alarm already ,

DCE inform alarm after 3~4 mins , we enable priority scanning by default in DCE .

 

In our lab , I found most of NMC2 device alarm response in DCE within 10 secs . NMC1 device alarm response in DCE within 5 mins ,almost need wait 3~4 mins .

 

In customer site , this situation also appear on NMC2 device ,almost need wait 3~4 mins . 

 

Can anyone advice on this ? Thank you.

 

https://www.se.com/in/en/faqs/FA271584/

Tags (1)
1 Reply 1
Cory_McDonald
Lieutenant Lieutenant
Lieutenant
0 Likes
0
476

Re: DCE alarm trigger not instantly for APC device

Hello @sesa157186_brid,

 

Priority scanning requires SNMP write access to properly work.  The first step in this case is to verify that the device actually has DCE assigned within the "Current ASISubscriber" in the [SecureInterface] section within the config.ini file for the device.  For information on how to pull the config.ini file, see knowledge base FA156131.

 

[SecureInterface]
;   APC Secure Interface (ASI): 
;   To add an ASI trap recipient, list the IP address in the following form:
;   <ip address>:<port>, <subscriber type>
;   CurrentASISubscriber=192.168.0.1
;   To remove an ASI trap recipient, list the IP or DNS name using the keyword:
;   RemoveASISubscriber=192.168.0.2
;   To remove all ASI trap recipients, use the keyword, value pair:
;   RemoveALLASISubscribers=yes
;   To change the Authentication Phrase, or the Encryption Phrase, 
;   use the AuthenticationPhrase, EncryptionPhrase keywords respectively. 
;   i.e., AuthenticationPhrase=ASI auth phrase
Access=disabled
AuthenticationProtocol=MD5
TrapPort=9952
CurrentASISubscriber=10.10.10.10, ISX Manager

 

Please note that DCE must set this value using SNMPwrite, so ensure that the SNMPwrite community string within the "SNMP Device Communication Settings > Device Scan Settings" matches an SNMP community string on the device with Write or Write+ access level.  If DCE is unable to write to the device, you should see that there is an unauthorized user attempting to access SNMP interface within device event log, as long as it is not blocked on the network.  This write of the DCE IP to CurrentASISubscriber should occur about every hour.

 

If this does not correct the issue, you will likely need to work through local escalation in order to run a packet capture to view packets for the time frame DCE should have received the alarm instance trap that the device should send when an alarm occurs.

 

Kind Regards,

Cory

Tags (1)