WEM Port and Hardware Information

This chapter provides information on various ports and their corresponding port numbers used by the WEM, and hardware sizing requirements of the WEM application.

This section includes the following:

IMPORTANT:

Unless otherwise specified, the information in this chapter applies to both Sun Solaris and Red Hat Enterprise Linux-based (RHEL) WEM systems.

Web Element Manager Network Considerations

To ensure proper installation and operation of the WEM, the following network considerations must be implemented:

  • The WEM server and the chassis must be located on the same network.
  • The Network Address Translation (NAT) protocol should not be used between the system and WEM server.
  • If there is a firewall installed between the WEM server and the system, then the port used by the WEM to access the system must be opened. Refer to the Default TCP/UDP Port Utilization section for additional information.
  • The WEM server must be able to send and receive Ping and ICMP packets from the system.
  • Configured application user account on WEM server.

Default TCP/UDP Port Utilization

Various TCP/UDP ports are used by the WEM for both client-server communication and communication with managed systems. If firewalls are used on these interfaces, these ports need to be opened. The following table lists the ports for which firewall must allow access for a port on that communication path.


Table 1. Default TCP/UDP/ICMP Port Utilization with Firewall
Port Number Communication Type Usage
TCP Port:
20 to 21
  • WEM Server to Chassis
  • Chassis to WEM Server
  • WEM Server to NMS
 Used by FTP server to transfer Bulkstats and in case of software upgrade, Config-backup, Config-update scheduler.
22
  • WEM Server to Chassis
  • Chassis to WEM Server
  • WEM Server to NMS
 Used by SSH or SFTP server for Config-backup, expect scripts.
80 WEM Client to WEM Server (Unsecured) Used by Apache server for downloading the WEM applet and property files. This port is configurable.
443 WEM Client to WEM Server (Secured) Used by Apache server for downloading the WEM applet and property files under secured connection. This port is configurable.
14131 to 14132 WEM Server to Chassis Used for CORBA communication. These ports are configurable.
15000 to 15002
  • WEM Client to WEM Server
  • Chassis to WEM Server
 Used for WEM client - server communication. WEM server receives requests on these ports from client. The chassis also sends notifications to the WEM server. The base port is configurable.
15015 NMS to WEM Server Used by NorthBound server to receive requests on this port from NMS (3GPP standard CORBA NorthBound Interface).
15017 WEM Server to NMS Used by CORBA Notification service for sending notifications to NMS (3GPP standard CORBA NorthBound Interface).
40000 to 40010 WEM Server to WEM Client Used for WEM server - client communication. The notifications such as alarms, config changes, monitor protocol, real-time graphs are done by WEM server to WEM client.
UDP Port:
69 Chassis to WEM Server Used by TFTP server. If the WEM server machine has the chassis image/config and if they are to be loaded using TFTP, then this port will be used.
162 Chassis to WEM Server Default port on which WEM receives SNMP traps from Chassis. This port is configurable.
514 Chassis to WEM Server Used by Syslog server. WEM server machine may be configured to act as a syslog server for the Chassis logs.
ICMP Port:
- WEM Server to Chassis WEM server to Chassis keep-alive


The following table lists the ports used by WEM for which there is no need for any firewall to open that port.
Table 2. Default TCP/UDP/ICMP Port Utilization
Port Number Usage
TCP Port:
5432 Used by PostgreSQL server for accepting SQL queries from various WEM processes.
22222 Used by WEM Server as "identity" port and is configurable.
22223 Used by Bulkstat Server (XML generator) as "identity" port and is configurable.
22224 Used by Bulkstat Parser as "identity" port and is configurable.
22225 Used by Script Server as "identity" port and is configurable.


WEM Server Hardware Sizing and Provisioning Guidelines

In addition to the minimum system requirements provided in the previous section, the following guidelines offer information that can help you plan hardware sizing needs, based on the exact deployment scenario that you will be using.

The information provided in this section is based on a typical installation that has the following characteristics:
  • The WEM server requirements listed elsewhere in this manual can support up to 100 Web Element Manager clients, managing up to 100 chassis.
  • The WEM application and the server it resides on are used to: Receive, process, correlate, and store SNMPv1 traps sent from the managed system. This operation involves the use of the event database, controlled by the PostgreSQL database engine, and any e-mail notifications configured for each alarm. Receive, process, and store Bulk Statistics information received from the managed system. This operation involves the use of the bulkstats database, controlled by the PostgreSQL database engine. Receive, display, and graph real-time Performance information for any number of statistical counters and polling periods. Administer WEM and CLI management users. This includes the addition, modification, and deletion of WEM-based management users, stored in the users database, controlled by the PostgreSQL database engine. Store, retrieve, and perform various configuration management operations on the managed system. This includes the storage and transfer (via SFTP/FTP) of binary software images, configuration text files, and session license and feature use keys.
  • Hard Drive Partition Recommendations:
    • The WEM should not be installed in the root (/) partition.
    • The root partition (/) should be at least 1 gigabyte (GB).
    • The /usr partition should be at least 1 GB.
    • The /var partition should be at least 8 GB.
    • The swap partitions should be at least 10 GB.
    • The size of the partition on which the WEM is installed will depend on a variety of site-specific factors, including the number of Chassis to be managed, the average bulkstat file size, the bulkstat file transfer interval, the number of configuration changes per day per Chassis and other considerations. Cisco provides a WEM Sizing Calculator utility to assist with these estimates. Please contact your local Cisco representative during the sizing phase of the planning process to obtain assistance on hard drive partition and disk space estimates for the WEM application.

IMPORTANT:

It is strongly recommended that the WEM application, the Apache web server application, and the PostgreSQL database engine be configured in the same logical hard disk partition.