Enterasys Networks 700 Switch User Manual


 
The MultiSwitch 700 Device View
2-4 Viewing Device Information
General Device Information
In addition to the main interface display, the Device View window provides the
following device information:
IP
The Device View window title displays the device’s IP (Internet Protocol)
Address; this will be the MultiSwitch 700 module IP address used to define the
device icon. The IP address is assigned to the MultiSwitch 700 module via the
Device Configuration portion of Local Management; it cannot be changed via
NetSight Element Manager. Note that although each interface in the MultiSwitch
700 module has its own MAC, or physical, address, only a single IP address is
assigned to the device.
Connection Status
This color-coded area indicates the current state of communication between
NetSight Element Manager and the MultiSwitch 700 module.
Green indicates the MultiSwitch 700 module is responding to device polls
(valid connection).
Magenta indicates that the MultiSwitch 700 module is in a temporary stand-by
mode while it responds to a physical change in the hub (such as when a
module is inserted). Note that module and port menus are inactive during this
stand-by state.
Blue indicates an unknown contact status; polling has not yet been established
with the MultiSwitch 700 module.
Red indicates the MultiSwitch 700 module is not responding to device polls
(device is off line, or device polling has failed across the network for some
other reason).
Chassis Type
The model of chassis — MultiSwitch 700—þin which the monitored
MultiSwitch 700 module is installed.
Location
A descriptive field you can use to identify where the chassis is physically located.
You can edit this field through the device’s System Group window; refer to the
Generic SNMP User’s Guide for details.
UpTime
The amount of time, in a days hh/mm/ss format, that the MultiSwitch 700
module has been running since the last start-up. Note that when distributed
chassis management is available, this field will indicate the time that the longest
active module has been running since start-up.