The Interface Status Is null When eSight Receives a Link Down Alarm from a Third

Created: Mar 29, 2016 06:55:58Latest reply: Mar 29, 2016 10:12:57 1519 1 0 0 0

When using eSight to manage third-party devices, the interface status is null in a link down alarm sent by a third-party device.

x
convention：
Emotion(0)

Like (0) Dislike (0) Favorite(0) Report

 Previous: Why Is the Color of Device Icons on the Topology Page Updated 2 or 3 Minutes Aft

Next: When the Disk Space of the eSight Server Is Fully Occupied, eSight Runs Abnormal



(0) (0)

^2#

Selina742 Created Mar 29, 2016 10:12:57

Possible Causes
The alarm from the third-party device does not carry interface running status or management status parameters, so eSight cannot obtain the interface status and the actual interface status is different from that in the alarm.
Procedure
No action is required.

x
convention：

Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:

Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy

Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.

Please bind your phone number to obtain invitation bonus.

Enterprise

Consumer

Corporate

Carriers

The Interface Status Is null When eSight Receives a Link Down Alarm from a Third

Third Party’s Trade Secret

My Followers