Prime Fulfillment Runtime Configuration Information
This appendix explains the following Prime Fulfillment information for runtime configuration:
•Default TCP Port Values and Protocol Directions Used by Prime Fulfillment
•Command-Line Interfaces Used by Prime Fulfillment
Default TCP Port Values and Protocol Directions Used by Prime Fulfillment
Prime Fulfillment uses various Transmission Control Protocol (TCP) ports during its operation. Most TCP ports are configured during the installation. Table E-1 and Table E-2 specify the most vital TCP primary and optional ports, respectively, their default values, and the direction.
Table E-1 Prime Fulfillment Primary TCP Ports, Their Default Values, and Direction
TCP Primary Ports (listed alphabetically)
|
|
|
|
HTTP |
8030 |
Web browser to Prime Fulfillment |
Used for Web GUI and NBI |
Tibco RVA |
7600 |
Prime Fulfillment to web browser |
Used by some applications |
Tomcat |
8031 |
Web browser to Prime Fulfillment |
HTTP port value + 1 |
Table E-2 Prime Fulfillment Optional TCP Ports, Their Default Values, and Direction
TCP Optional Ports (listed alphabetically)
|
|
|
|
HTTPS |
8443 |
Web browser to Prime Fulfillment |
If HTTPS activated |
Oracle |
1521 |
Prime Fulfillment to Oracle Server |
If Oracle database is used |
Tibco RVA Admin |
7630 |
Web browser to Prime Fulfillment |
If RVA config required |
Tibco RVD or RVRD |
7530 |
Bi-directional between Prime Fulfillment and Cisco Configuration Engine server |
If using CNS transport mechanism for device access |
Tibco RVRD Admin |
7580 |
Web browser to Prime Fulfillment |
If RVRD config required |
The values selected during the installation can be retrieved from the file $PRIMEF_HOME/etc/install.cfg. Most of these ports only need to be allowed if you are allowing users to access Prime Fulfillment from outside your firewall.
Prime Fulfillment uses or can use the protocols specified in Table E-3 to communicate with the routers under its configuration control.
Note The selected protocol for each of the following categories must be able to pass through any firewalls between Prime Fulfillment and the devices:
1. Terminal Session Protocol - default: Telnet; SSH; CNS*; rsh
2. Configuration Access Protocol - default: selected Terminal Session Protocol; TFTP; FTP; rcp
3. SNMP - default: SNMPv1/v2c; SNMPv3
* CNS is a transport mechanism that uses the TIB/Rendezvous event bus to communicate with a Cisco Configuration Engine server..
Table E-3 Protocols and Directions with Prime Fulfillment
Protocols
(listed alphabetically)
|
|
FTP |
Devices to FTP server |
NFS |
Between Prime Fulfillment and TFTP or FTP server if server is on a different machine. (Can be blocked if you do not use FTP or TFTP.) |
rcp |
Prime Fulfillment to devices |
rsh |
Prime Fulfillment to devices |
SSH |
Prime Fulfillment to devices |
SSHv2 |
Prime Fulfillment to devices |
SNMP |
Prime Fulfillment to devices |
SNMPv3 |
Prime Fulfillment to devices |
Telnet |
Prime Fulfillment to devices |
TFTP |
Devices to TFTP server |
Note Device creation is explained in the chapter Service Inventory—Inventory and Connection Manager, in the Cisco Prime Fulfillment User Guide 6.2.
Command-Line Interfaces Used by Prime Fulfillment
This section specifies the command-line interfaces (CLIs) used by Prime Fulfillment. This list gives commands supported in IOS and IOS XR unless otherwise indicated:
•commit (not supported in IOS)
•configure exclusive (not supported in IOS)
•config term
•copy (many variations)
•enable (not supported in IOS XR)
•end
•exit
•ping [vrf]
•reload
•show diag (not supported in IOS XR)
•show diags (not supported in IOS)
•show etherchannel port (not supported in IOS XR)
•show interfaces switchport (not supported in IOS XR)
•show modules (not supported in IOS XR)
•show port (not supported in IOS XR)
•show running
•show startup (not supported in IOS XR)
•show ver
•term (length, width, editing) (editing not supported in IOS XR)
•write mem (not supported in IOS XR)
•[no] logging console
Note The CLIs used by the Cisco Prime Diagnostics are listed in the Cisco Prime Fulfillment User Guide 6.2.