The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter explains the following Prime Provisioning information for runtime configuration:
Prime Provisioning uses various Transmission Control Protocol (TCP) ports during its operation. Most TCP ports are configured during the installation. All other ports besides the ones mentioned in this section, can be safely turned off if required.
Note To list the ports and their respective Process names (or PIDs) currently used by Prime Provisioning, navigate to the Prime Provisioning Installation directory and execute the command:
./prime.sh listProcess
Table 5-1 Table 5-1 and Table 5-2 specify the most vital TCP primary and optional ports, respectively, their default values, and the direction.
|
|
|
|
---|---|---|---|
|
|
|
|
---|---|---|---|
The value selected during the installation can be retrieved from the file $PRIMEP_HOME/etc/install.cfg. Most of these ports only need to be allowed if you are allowing users to access Prime Provisioning from outside your firewall.
Prime Provisioning uses or can use the protocols specified in Table 5-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 Provisioning 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..
(listed alphabetically) |
|
---|---|
Between Prime Provisioning and TFTP or FTP server if server is on a different machine. (Can be blocked if you do not use FTP or TFTP.) |
|
Note Device creation is explained in the chapter Service Inventory—Inventory and Connection Manager, in the Cisco Prime Provisioning 7.0 User Guide.
Table 5-4 lists some important administrative ports and their respective protocols.
Table 5-4 Prime Provisioning Administrative Ports and Their Respective Protocals
|
|
|
---|---|---|
For secure remote administration which uses SSL to encrypt the transmission |
||
This section specifies the command-line interfaces (CLIs) used by Prime Provisioning. This list gives commands supported in IOS and IOS XR unless otherwise indicated: