Thank you very much for your assistance.
I'll wait until the next releases.

Best Reguard

unfortunately you cannot access actual varbinds from NXSL. I can change it in next release (change is really simple, information is there, just not exposed to NXSL). Then you'll be able to use simple script to extract necessary information.

Best regards,
Victor

Thank you very much for your reply.
But, I want to real-time output it.

Regards

You can get the values of the varbinds, but I don't think you can get the varbinds themselves.
I don't think you can query the SNMP Trap Log via NXSL either, but I guess you could trigger an action that calls a script on the server which pulls the information from the database or via nxshell (i.e. trigger an action on the event via event processing policies, with the action pulling the information out of the logs).

Alternatively you could:

• setup DCIs to actively monitor the status of your BGP peers via BGP SNMP table, but that won't be as "instant" as an SNMP trap.
• use Syslog, where you can grab the relevant information from the message

Some example syslog from a Cisco:

%BGP-3-NOTIFICATION: sent to neighbor 192.168.255.5 4/0 (hold time expired) 0 bytes
%BGP-5-NBR_RESET: Neighbor 192.168.255.5 reset (BGP Notification sent)
%BGP-5-ADJCHANGE: neighbor 192.168.255.5 Down BGP Notification sent
%BGP-5-ADJCHANGE: neighbor 192.168.255.5 Up

Someone else may have an easier solution?

Cheers