Npm (Network Protocol Control: 3000-3299) - Fujitsu XG2000 Series User Manual

Xg2000 series compact, 20-port 10 gigabit ethernet layer 2 switch
Hide thumbs Also See for XG2000 Series:
Table of Contents

Advertisement

XG2000 series User's Guide
Message ID
Severity
S2226
WARNING
S2401
ERROR
A.2.4

npm (Network Protocol Control: 3000-3299)

Message ID
Severity
S3001
INFO
S3002
INFO
S3003
INFO
S3004
WARNING
S3005
WARNING
S3006
WARNING
P3009
INFO
P3010
INFO
Too Many CM Buffer SBE Errors. LOG Disabled.
Explanation
A correctable error was repeatedly detected in the switch chip. Logging for this event is disabled.
Solution
Note the message contents and contact the sales representative.
System Error: %1$
Explanation
A system error of Layer2 basic management module was detected.
[[Inserted string]]%1$: Supplementary code for the error
Solution
Note the message contents and contact the sales representative.
Cold Start or Warm Start.
Explanation
The system was turned on.
Link down %1$. (%2$)
Explanation
Port status changed from a link up to a link down state.
[[Inserted string]]%1$: Information on the port whose status changed to a link down.
[[Inserted string]]%2$: Cause of link down.
For details, refer to "Link Status Detail" of the "show interface" command.
Link up %1$.
Explanation
Port status changed to a link up state.
[[Inserted string]]%1$: Information on the port whose status changed to link up.
%1$ detected storm drop.
Explanation
A broadcast storm was detected.
[[Inserted string]]%1$: Information on the port that dropped broadcast frames.
Solution
A loop topology may exist on the network. Review the network configuration.
%1$ detected port security violation.
Explanation
A violating packet was detected by Port Security enabled.
[[Inserted string]]%1$: Information on the port that detected the violating packet.
Solution
Investigate the cause for receiving violating packets.
%1$ detected loopback alert.
Explanation
A packet loop was detected.
[[Inserted string]]%1$: Information on the port that detected the loop.
Solution
A loop topology may exist on the network. Review the network configuration.
A loopback alert can occur when the destination MAC address of a received frame was registered in the MAC
address table with the receiving port registered as a destination. In other words, a loopback alert can occur even
if there is no loop in the network.
%1$ has been attached to %2$.
Explanation
The physical port was attached to a link aggregation group.
[[Inserted string]]%1$: Physical port information
[[Inserted string]]%2$: Aggregation group information
%1$ has been detached.
Explanation
The physical port was detached from a link aggregation group.
[[Inserted string]]%1$: Information on physical port detached
All Rights Reserved, Copyright (C) PFU LIMITED 2009
Message/Explanation/Solution
Message/Explanation/Solution
288/315

Advertisement

Table of Contents
loading

Table of Contents