# Configure network connectivity for ServiceNow

Before you protect ServiceNow data, make sure your environment meets the following requirements for access nodes, network connectivity, and indexing.

- If you deploy your own access node in your internal network, IP allowlisting is typically not required. Follow the access node deployment documentation, and make sure the Commvault infrastructure can reach your access node.

- If you use a Commvault-managed access node, allowlist the access node IP address so it can connect to your ServiceNow endpoint (`https://<instance>.service-now.com`). For information about IP allowlisting, see IP Allowlist for Controlling Access to the Command Center.

- Verify that your ServiceNow instance is not in hibernate mode. Development instances can hibernate after periods of inactivity and return HTML instead of JSON responses, which causes backup failures.

## Required ports

Source | Destination | Port | Protocol | Purpose
--- | --- | --- | --- | ---
Commvault access node | `https://<instance>.service-now.com` | 443 | HTTPS | ServiceNow Table API calls (backup and restore)
Primary Copy MediaAgent | Object storage (S3-compatible) | 443 | HTTPS | Backup data transfer to storage destination

The access node does not connect directly to object storage. Storage I/O is routed through the Primary Copy MediaAgent with the CVS3Service package installed.

Note

This workload requires a backup plan whose Primary Copy MediaAgents have the CVS3Service package installed. For details, see Configure and validate backups for ServiceNow.

×

Loading...