Request for Comments, the IETF's standards documents. NSX takes 100.64.0.0/10 from RFC 6598 for internal Tier-0 to Tier-1 transit links unless given another block at deployment, and VCF design guidance advises RFC 1918 private IPv4 space for infrastructure subnets.
Also called Request for Comments.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains RFC in context, with comparison tables and the common traps.
Terms in this definition
- NSX
Software that handles networking and security across VCF, covering firewalling, load balancing, NAT, VPCs, overlay segments and Tier-0/1 gateways.
- Internal
The API Management VNet mode where the gateway can be reached solely through a private IP address.
- Model deployment
Inside a resource, each deployment is a named copy of a Foundry model with its own TPM quota and deployment type. Requests identify the model by this deployment name.
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- RFC 1918
Defines 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 as private IPv4 space; Microsoft advises using these blocks when you choose address spaces for virtual networks.
- IPv4
The 32-bit version of IP addressing. It remains the address format you will see most often in log data and threat indicators.
Related terms
- log standard
Starting in VCF 9.0, services such as the VCF Operations adapter and collector, VCF Operations for networks and the VCF Identity Broker write entries in one structured pattern derived from RFC 5424. Parsers built for earlier layouts could need rework.
- MIB
Describes what an SNMP trap contains. When using SNMPv3, Veeam ONE's traps follow CISCO-SNMP-USM-OIDS-MIB as set out in RFC 3414.
- RCODE
Result code inside a DNS response. For vSphere 9.x, answering an AAAA query for an IPv4-only name must give RCODE 0 with nothing returned (per RFC 4074); a NXDOMAIN reply makes installs and upgrades fail.
- syslog server
Collects event messages sent with the syslog protocol, which is how SIEM systems get Veeam events. With a paid licence, Veeam Backup & Replication can forward to a single such server in RFC 5424 format over TCP or UDP port 514 or TLS port 6514.