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.
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.
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!