Frequently Asked Questions

This section addresses common questions about USDN implementation, operation, and troubleshooting. If you don't find the answer you're looking for, please contact our support team.

Network Reliability and Resilience

What happens if a node goes offline?

When a USDN node goes offline, the network implements several automatic recovery mechanisms:

Immediate Response (0-30 seconds):

• The USDN controller detects the node failure through control-plane heartbeat monitoring (WSS / health events)
• Traffic is automatically rerouted through alternative paths in the network topology
• Active connections are preserved through session failover mechanisms

Recovery Process:

Impact by Topology:

• Point-to-Point: Service interruption until node recovery or manual intervention
• Full Mesh: Automatic failover to alternative direct paths
• Hub and Spoke: Hub failure affects all spokes; spoke failure only affects local clients

Best Practices:

• Deploy redundant nodes in critical locations
• Use Full Mesh topology for high availability requirements
• Implement monitoring and alerting for proactive failure detection

Is data loss possible?

USDN implements multiple layers of protection against data loss:

USDN Chain protection (config plane):

• Network configuration and route advertisements are stored on USDN Chain authority streams
• Immutable transaction history ensures configuration integrity
• Authority cluster replication prevents loss of published config

Data Plane Protection:

• TCP Connections: Automatic retransmission handles temporary packet loss
• Session Persistence: Connection state is maintained during brief outages
• Buffer Management: Temporary buffering during path transitions

Scenarios and Protections:

Scenario	Risk Level	Protection Mechanism
Node Restart	🟢 None	Graceful shutdown with connection migration
Network Partition	🟡 Low	Automatic path discovery and rerouting
Controller Failure	🟡 Low	Distributed controller architecture
Hardware Failure	🟠 Medium	Depends on topology and redundancy
Complete Site Loss	🔴 High	Requires backup sites and disaster recovery

Data Loss Prevention:

• Enable application-level acknowledgments for critical data
• Implement proper backup and disaster recovery procedures
• Use redundant network paths and equipment
• Regular testing of failover scenarios

How does USDN handle network partitions?

USDN uses USDN Chain authority replication and controller HA to handle partitions:

Partition Detection:

• Controllers and authority nodes monitor cluster health and block propagation
• Loss of authority quorum or NLB reachability indicates control-plane stress
• Devices detect WSS loss within seconds

Partition Response:

• Data plane tunnels often continue with last-known routes (chain-bridge / FRR state)
• Edges reconnect to healthy controllers on :443 when paths return
• Minority or isolated edges may operate with cached config until authority is reachable

Partition Recovery:

• Automatic WSS and gRPC resubscribe when connectivity returns
• PropagateBlock / SyncBlocks reconcile authority state
• Gradual resumption of new orders and route updates

Integration and Compatibility

Can USDN integrate with existing VPNs?

Yes, USDN can integrate with existing VPN infrastructure in several ways:

Integration Methods:

1. VPN Replacement

Replace existing VPN infrastructure with USDN for enhanced security and performance:

2. Parallel Operation

Run USDN alongside existing VPNs for gradual migration:

• Route specific traffic through USDN
• Maintain VPN for legacy applications
• Gradual application migration to USDN

3. VPN Tunneling

Tunnel existing VPN traffic through USDN infrastructure:

• Enhanced security with double encryption
• Improved reliability through USDN routing
• Centralized management of all network traffic

Common VPN Integrations:

• IPSec VPNs: Direct replacement or tunnel encapsulation
• SSL/TLS VPNs: Application-level integration
• Site-to-Site VPNs: Infrastructure replacement
• Remote Access VPNs: Client integration with USDN nodes

Does USDN support IPv6?

Current Status: IPv4 Full Support, IPv6 Roadmap Development

IPv4 Support:

• Full native IPv4 support across all components
• NAT44 translation for legacy network integration
• IPv4 routing and policy management

IPv6 Roadmap:

• Q3 2025: IPv6 control plane support
• Q4 2025: IPv6 data plane implementation
• Q1 2026: Dual-stack operation (IPv4/IPv6)
• Q2 2026: IPv6-only network support

Current IPv6 Workarounds:

• Use IPv4 USDN tunnels to transport IPv6 traffic
• Implement IPv6-to-IPv4 translation at network edges
• Plan for future IPv6 migration during USDN deployment

Can USDN work with existing firewalls and security appliances?

Yes, USDN is designed to integrate seamlessly with existing security infrastructure:

Firewall Integration:

• Transparent Mode: USDN traffic appears as standard encrypted flows
• Policy Integration: Support for existing firewall rules and policies
• Deep Packet Inspection: Compatible with DPI-enabled firewalls
• Zone-Based Security: Integration with security zone architectures

Security Appliance Compatibility:

• IDS/IPS: Network intrusion detection and prevention systems
• WAF: Web application firewall integration
• SIEM: Security information and event management
• Endpoint Protection: Compatible with endpoint security solutions

Deployment Patterns:

Performance and Scalability

What is the maximum number of nodes supported?

USDN scalability depends on the chosen network topology:

Topology Limits:

Topology	Recommended Max	Theoretical Max	Performance Notes
Point-to-Point	2	2	Optimal performance
Full Mesh	8-10	50	Performance degrades with scale
Hub and Spoke	100+	1000+	Hub becomes bottleneck

Scaling Considerations:

• USDN Chain authority scale: More controllers/authority peers add replication overhead
• Control Plane Overhead: Network convergence time increases
• Bandwidth Requirements: Hub nodes require significant bandwidth
• Management Complexity: Configuration complexity grows exponentially

Large-Scale Deployments:

• Use hierarchical hub-and-spoke designs
• Implement regional USDN controllers
• Consider USDN federation for multi-thousand node networks

How much bandwidth overhead does USDN add?

USDN overhead varies by configuration and traffic patterns:

Encryption Overhead:

• Data Plane: 2-5% overhead for encryption and authentication
• Control plane: 1-3% overhead for WSS health, USDN Chain stream updates, and routing sync
• Tunnel Headers: Additional 40-60 bytes per packet

Typical Overhead by Traffic Type:

Traffic Type	Overhead	Notes
Large File Transfer	2-3%	Minimal relative overhead
Video Streaming	3-4%	Consistent packet sizes
Web Browsing	5-8%	Small packet overhead more noticeable
VoIP/Real-time	4-6%	Header overhead significant

Optimization Techniques:

• Enable packet compression for compatible traffic
• Use larger MTU sizes where possible
• Implement traffic shaping and QoS policies
• Monitor and tune encryption parameters

Does USDN support Quality of Service (QoS)?

Yes, USDN provides comprehensive QoS support:

QoS Features:

• Traffic Classification: Identify and classify different traffic types
• Priority Queuing: Multiple priority levels for traffic handling
• Bandwidth Management: Rate limiting and bandwidth guarantees
• Latency Control: Low-latency queues for real-time traffic

QoS Implementation:

Supported QoS Standards:

• DSCP Marking: Differentiated Services Code Point
• 802.1p: Layer 2 QoS marking
• Traffic Shaping: Token bucket and leaky bucket algorithms
• Admission Control: Connection-based QoS enforcement

Security and Compliance

How secure is the USDN Chain control plane?

USDN Chain on the controller cluster provides enterprise-grade security for configuration and routing metadata:

Security Features:

• Encryption: Payload encryption for stream items; mTLS on TCP/443 for gRPC and WSS
• Digital Signatures: Ed25519 cryptographic signatures
• Authority replication: Permissioned authority cluster with block propagation (PropagateBlock)
• Access Control: Role-based access control (RBAC)

Threat Protection:

• Man-in-the-Middle: End-to-end encryption prevents interception
• Replay Attacks: Timestamp and nonce validation
• Byzantine Attacks: Consensus algorithm handles malicious nodes
• Key Compromise: Automatic key rotation and revocation

Compliance Standards:

• FIPS 140-2: Cryptographic module validation
• Common Criteria: Security evaluation standards
• SOC 2 Type II: Service organization control audit
• ISO 27001: Information security management

What compliance certifications does USDN have?

Current Certifications:

• ✅ SOC 2 Type II - Security, availability, and confidentiality
• ✅ ISO 27001 - Information security management systems
• ✅ FIPS 140-2 Level 2 - Cryptographic module validation
• ✅ Common Criteria EAL4+ - Security functionality evaluation

Industry-Specific Compliance:

• 🚧 FedRAMP - Federal cloud security (in progress)
• 🚧 HIPAA - Healthcare data protection (planning)
• ✅ PCI DSS - Payment card industry security
• ✅ GDPR - European data protection regulation

Regional Certifications:

• ✅ CSA STAR - Cloud Security Alliance
• ✅ IRAP - Australian government security assessment
• 🚧 C5 - German cloud security standard (in progress)

Can USDN be audited and monitored?

Yes, USDN provides comprehensive auditing and monitoring capabilities:

Audit Features:

• USDN Chain audit trail: Immutable record of published configuration and route transactions
• Configuration Tracking: Complete history of network configurations
• Access Logging: Detailed logs of all administrative access
• Transaction logging: Record of USDN Chain submissions and stream grants

Monitoring Capabilities:

• Real-time Metrics: Network performance and health monitoring
• Alerting: Configurable alerts for security and performance events
• Compliance Reporting: Automated compliance report generation
• Third-party Integration: SIEM and log management system integration

Supported Monitoring Tools:

• Prometheus/Grafana: Open-source monitoring stack
• Splunk: Enterprise log management and analysis
• ELK Stack: Elasticsearch, Logstash, and Kibana
• Custom APIs: RESTful APIs for custom monitoring solutions

Deployment and Management

What are the minimum hardware requirements?

Hardware requirements vary by deployment size and performance needs:

Minimum Requirements (Small Deployment):

• CPU: 2 cores, 2.0 GHz
• RAM: 4 GB
• Storage: 20 GB SSD
• Network: 100 Mbps interface
• OS: Ubuntu 20.04 LTS or CentOS 8

Recommended Requirements (Production):

• CPU: 4 cores, 2.5 GHz
• RAM: 8 GB
• Storage: 50 GB SSD
• Network: 1 Gbps interface
• OS: Ubuntu 22.04 LTS

High-Performance Requirements:

• CPU: 8+ cores, 3.0 GHz
• RAM: 16+ GB
• Storage: 100+ GB NVMe SSD
• Network: 10+ Gbps interface
• Hardware Acceleration: AES-NI support recommended

Container Deployment:

• Docker: 2 CPU, 4 GB RAM minimum
• Kubernetes: 3 node cluster recommended
• Resource Limits: Configurable based on traffic

How long does initial deployment take?

Deployment time varies by complexity and preparation:

Typical Deployment Timeline:

Phase	Duration	Activities
Planning	1-2 weeks	Network assessment, design, documentation
Preparation	3-5 days	Hardware procurement, software installation
Configuration	1-3 days	USDN setup, testing, validation
Migration	1-7 days	Traffic cutover, monitoring, optimization
Total	2-4 weeks	Complete deployment and stabilization

Factors Affecting Timeline:

• Network Complexity: Number of sites and connections
• Integration Requirements: Existing system integration needs
• Team Experience: Familiarity with USDN technology
• Testing Requirements: Validation and acceptance testing needs

Accelerated Deployment:

• Use USDN professional services for faster implementation
• Pre-configure hardware before shipping to sites
• Implement phased rollout for large deployments
• Leverage automation tools for configuration management

What ongoing maintenance is required?

USDN is designed for minimal ongoing maintenance:

Regular Maintenance Tasks:

Monthly:

• Review system logs and performance metrics
• Update monitoring dashboards and alerts
• Validate backup and disaster recovery procedures
• Security patch assessment and planning

Quarterly:

• Software updates and security patches
• Performance optimization and tuning
• Capacity planning and scaling assessment
• Compliance audit and reporting

Annually:

• Hardware refresh planning
• Security assessment and penetration testing
• Disaster recovery testing
• Technology roadmap review

Automated Maintenance:

• Self-Healing: Automatic recovery from common failures
• Auto-Updates: Configurable automatic software updates
• Health Monitoring: Continuous system health checks
• Performance Optimization: Automatic performance tuning

Support Options:

• Community Support: Free community forums and documentation
• Professional Support: 24/7 enterprise support with SLA
• Managed Services: Fully managed USDN deployment and operations
• Training Programs: Administrator and operator training courses

---

Sales

How do I get in touch with the sales team?

Our sales team is available to answer questions, provide demos, and discuss pricing:

• Email: sales@usdatanetworks.com
• Phone: (954) 361-1682

---

Getting Help

If you have additional questions not covered in this FAQ:

• Documentation: Check our comprehensive documentation
• Support & Escalation: Review our Support and Escalation Levels for detailed information about available support options
• Support Portal: Submit support tickets for technical issues at support.usdatanetworks.com
• Professional Services: Contact our team for deployment assistance

For detailed information about support tiers, SLAs, and how to choose the right support level for your needs, visit our comprehensive Support and Escalation Levels page.

For urgent issues, our 24/7 support team is available for Enterprise and Premium support customers.