MNS-BB Software User Guide
-123-
A topology loop can also cause excessive network activity. The event log messages can be indicative
of this type of problem. Please see ‘Using the Event Log to Identify Problem Sources’ section of this
chapter for more details.
23.5 General Problems
If you experience problems such as “the network runs slow; processes fail; or users cannot access
servers or other devices” then Broadcast storms may be occurring in the network. These may be due
to redundant links between nodes.
23.5.1 Duplicate IP Addresses
This is indicated by this Event Log message:
TCP/IP: duplicate IP Addresses [IP address] sent from Ethernet address [MAC address].
The IP Address above is the same IP address of both devices, indicating the Switch’s IP address has
been duplicated somewhere on the network.
23.5.2 SNTP or Gateway Problems
If problems such as “The Switch Cannot Find the SNTP Server or the Configured Gateway” occur
then your primary VLAN to the ports may have moved. SNTP and Gateway access are through the
VLAN, which in the default configuration is the DEFAULT-VLAN. If the primary VLAN has been
moved to another VLAN, it may be disabled or does not have ports assigned to it.
23.6 Using the Event Log To Identify Problem Sources
The Event Log records operating events as single-line entries listed in chronological order, and serves
as a tool for isolating problems. Each Event Log entry is composed of four fields:
Severity Date Time Description
Severity is one of the following levels:
I (Information) indicates routine events.
A (Activity) indicates the activity on Switch.
D (Debug). reserved for internal diagnostic information.
C (Critical) indicates that a severe Switch error has occurred.
F (Fatal). indicates that a service has behaved unexpectedly.
Date is the date in mm/dd/yy format (as per configured) that the entry was placed in the log.
Time is the time in hh:mm:ss format (as per configured) that the entry was placed in the log.
Source Name is the name of the node, computer, device or the user.
Description is a brief description of the operating event.
The event log holds up to 1000 lines in chronological order, from the oldest to the newest. Each line
consists of one complete event message. Once the log has received 1000 entries, it discards the
current oldest line (with information level severity only) each time a new line is received. The event
log window contains 22 log entry lines and can be positioned to any location in the log.
Note: The event log is saved since last SAVE command. Rest of the entries will stay in volatile
memory until you will SAVE.
CLI Command to see the Event Log
Type Syntax: show log <option>
----------------------------------------------------------------------------------------------
Severity Date Time Log Description
----------------------------------------------------------------------------------------------
D 21-09-2001 11:18:18 AM System X System is resetted
I 21-09-2001 11:18:18 AM Rajesh Rajesh is now on line
I 21-09-2001 11:18:18 AM Server1 network enabled on 192.168.1.16
A 22-09-2001 12:00:03PM Device Port 17 disabled
----------------------------------------------------------------------------------------------
To Next Page
Loading...
