TFTP Server
Installation and
Initial
Configuration
TFTP for Windows
Table 17 Default TCP/IP and UDP Ports Used by EMS
Port
Description
21 (TCP/IP)
EMS-specific FTP daemon.
162 (UDP)
Used to accept SNMP Traps from network elements.
514 (TCP/IP)
EMS-specific syslog daemon.
1098 (TCP/IP)
Broadcast change notifications to all logged-in clients.
1099 (TCP/IP)
RMI interface.
5798 (TCP/IP)
EMS Client/Server communication.
8158 (TCP/IP)
Internal HTTP web server to facilitate GUI Help Panels and
server-generated reports.
On UNIX systems, EMS must be run with root privileges in order to
properly bind to the well-known TCP/IP ports (21, 162, 514).
EMS might not be able to properly bind to the well-known TCP/IP ports
(21, 162, 514) if another standard daemon is already running.
A TFTP Server must be running and the TFTP boot directory must be
specified whenever you want to perform a Backup, Restore, Agent
Update, or Golden Configuration operation using the EMS Server.
3Com recommends that the TFTP Server software be installed on the
same server running the EMS Server because EMS points to the TFTP
Server upload and download folders. The Windows 3Com TFTP server
is included on the EMS CD.
This section provides instructions on how to install and initially
configure it.
No matter which TFTP Server software is used with EMS, you will need to
configure the TFTP Server and EMS settings similarly as described in
sections
Initially Configuring the 3Com TFTP Server for Windows
Software
on
page 50
Server Software for Windows
TFTP Server Installation and Initial Configuration
and
Initially Configuring EMS for the 3Com TFTP
on
page
51.
49
Need help?
Do you have a question about the 3CR15600 - Enterprise Management Suite and is the answer not in the manual?