- Index
- Preface
- Overview
- Using Homepage
- Using ANM Guided Setup
- Using Application Configuration Templates
- Importing and Managing Devices
- Configuring Virtual Contexts
- Configuring Virtual Servers
- Configuring Real Servers and Server Farms
- Configuring Stickiness
- Configuring Parameter Maps
- Configuring SSL
- Configuring Network Access
- Configuring High Availability
- Configuring Traffic Policies
- Configuring Application Acceleration and Optimization
- Using Configuration Building Blocks
- Monitoring Your Network
- Administering the Cisco Application Networking Manager
- Using ANM Mobile
- Troubleshooting Cisco Application Networking Manager Problems
- ANM Ports Reference
- Using ANM With Virtual Data Centers
- Glossary
User Guide for the Cisco Application Networking Manager 5.2
Chapter: ANM Ports Reference
ANM Ports Reference
ANM uses specific ports for its processes. Figure A-1 illustrates a typical ANM server deployment in a network. This illustration identifies the protocols and ports used by the different network devices in a typical deployment.
•
Table A-1 lists the ports used for ANM client (browser) or ANM server and ANM high availability communication.
•Table A-2 lists the ports used for communication between ANM and managed devices.
Figure A-1 ANM Server Deployment
|
|
|
|---|---|
TCP (80) |
Default port if ANM is configured for access using HTTP (using anm-installer). |
TCP (443) |
Default port if ANM is configured for access using HTTPS (using default install option). |
TCP (3306) |
MySQL Database system (ANM HA installation opens this port to communicate with the peer ANM). |
TCP (10444) and |
ANM License Manager (ANM HA installation opens these two ports to communicate with the peer ANM). |
TCP (25) |
Port used by ANM server to communicate to Email Gateway through SMTP. |
UDP (162) |
Port used by ANM server to send out trap notification to external NMS application. |
HTTP(8080) and HTTPS (8443) |
Web service ports. |
1 It is highly recommended that you run ANM on a stand-alone device. However, if you run ANM on a shared device, please note that ANM locally opens the following ports for internal communication: |
|
|
|
|
|---|---|---|
Chassis (Catalyst 6500 switch or Cisco 7600 router) |
SSH (TCP:22) or Telnet (TCP:23) |
Discover chassis configuration. |
ACE (appliance or module) |
HTTPS (TCP:443) |
For ACE module: XML/HTTPS interface on the device used to discover, configure, and monitor using specific show CLI commands. |
HTTPS (TCP:10443) |
For ACE appliance: XML/HTTPS interface on the device used to discover, configure, and monitor using specific show CLI commands. |
|
SSH (TCP: 22) |
Discovery and configuration of ACE licenses, certificates/keys (crypto) licensing, scripts, and checkpoints. |
|
SNMP (UDP: 161 & UDP:162) |
Monitor ACE through SNMP requests |
|
CSM |
SNMP (UDP: 161 & UDP:162) |
Monitor CSM through SNMP requests |
CSS |
SSH (TCP:22) or Telnet (TCP:23) |
Discover chassis configuration. |
SNMP (UDP: 161 & UDP:162) |
Monitor CSS through SNMP requests |
|
GSS |
SSH (TCP:22) |
Discover chassis configuration and monitoring operational status of DNS rules and VIP answers. |
RMI (TCP:2001 & TCP:3009) |
Activate/suspend DNS rules and VIP answers. |
|
vCenter Server |
Default HTTPS (TCP:443) |
Communicate with the vCenter Server and vSphere Client in a VMware virtual data center environment. For more information about using the plug-in that is available with ANM to integrate ANM with a VMware virtual data center environment, see "Using the ANM Plug-In With Virtual Data Centers." |
Feedback