Allied Telesis AT-SBx31CFC960 - Manual (Page 74)

Chapter 3: Overview of the AT-SBx31CFC960 Controller Fabric Card
74
NET MGMT Port
The controller card must have access to your network to perform the
features in Table 21. The features require that the controller card be able
to communicate with other devices on your network. For example, when
you remotely manage the chassis with Telnet, the controller card has to be
able to communicate with the Telnet client on your workstation located on
your network.
You can give the controller card access to your network two ways. One
way is with the NET MGMT port on the front panel of the card. When this
port is connected to another network device, such as another Ethernet
switch or router, the controller card can access your network to
communicate with network devices, such as TFTP servers and Telnet and
SSH client workstations.
Another way to give the controller card access to your network is by
configuring the in-band interface. The interface is a designated port on
one of the Ethernet line cards in the chassis from which the controller card
is to communicate with your network. You can specify only one port.
You may use either the NET MGMT port or in-band interface to provide
the controller card with access to your network, but you may not configure
both. The default is the NET MGMT port. For instructions on how to
configure the NET MGMT port and inband interface, refer to the Software
Reference for SwitchBlade x3100 Series Switches.
Table 21. Management Features Requiring Network Access
Feature Description
Ping Used to test for network
connectivity to the chassis.
FTP client Used with an FTP server on your
network to download files to or
upload files from the controller
card.
RADIUS client Used for remote management
authentication and 802.1x port-
based network access control.
RMON with SNMP Used with the RMON portion of
the MIB tree on an SNMP
workstation to remotely monitor
the switch.
Secure Shell server Used to remotely manage the
chassis with a Secure Shell client.