Allied Telesis AT-PBC18 - Manual (Page 101)

AT-PBC18 Installation Guide
101
Optional Management Module
If an optional management module is install and a local management
session cannot be established, do the following:
❑ Check to be sure the management module is securely seated in
the chassis.
❑ Verify that you are using a straight-through RS-232 cable.
❑ Check to be sure that the RS-232 cable is securely connected to
the RS-232 port on the management module and the other end is
connected to a terminal or PC.
❑ Verify that the operating parameters for the terminal or the
terminal emulator program are configured correctly. The default
values for the RS-232 port can be found in the AT-S31 User’s
Guide. This guide is available at
www.alliedtelesyn.com .
If an optional management module is installed and a remote
management session cannot be established, do the following:
❑ Check to be sure the management module is securely seated in
the chassis.
❑ Verify that the twisted pair cable is Category 3 or better and that
it does not exceed 100 meters (328 feet).
❑ Check to be sure that the twisted pair cable is securely connected
to the RJ-45 port on the management module and the other end
is connected to a 10Base-T or 10/100Base-TX port on an Ethernet
hub or switch.
❑ Verify that an IP address has been assigned to the management
module and you are using the same IP address at the start of the
remote session. Refer to the AT-S31 User’s Guide for instructions
on assigning an IP address.
❑ If the LNK LED is OFF, change the setting of the MDI/MDI-X switch
on the management module.
❑ Ping the chassis from a workstation using a PING utility. If a ping
fails, either the chassis is not operating, the physical data path to
the chassis has experienced a failure, or the wrong IP address was
entered.
❑ Reset the management module by pressing and holding either
the Reset button on the front of the chassis or on the
management module for about 1 second. The Status LED will flash
once, after which the management module is ready for use.