Technical Reference Guide for iDX Release 3.3 Technical Reference Guide iDirect Satellite Routers iDX Release 3.3 January 05, 2017 ii Copyright © 2017, VT iDirect Inc All rights reserved Reproduction in whole or in part without permission is prohibited Information contained herein is subject to change without notice The specifications and information regarding the products in this document are subject to change without notice All statements, information and recommendations in this document are believed to be accurate, but are presented without warranty of any kind, express, or implied Users must take full responsibility for their application of any products Trademarks, brand names and products mentioned in this document are the property of their respective owners All such references are used strictly in an editorial fashion with no intent to convey any affiliation with the name or the product's rightful owner VT iDirect® is a global leader in IP-based satellite communications providing technology and solutions that enable our partners worldwide to optimize their networks, differentiate their services and profitably expand their businesses Our product portfolio, branded under the name iDirect, sets standards in performance and efficiency to deliver voice, video and data connectivity anywhere in the world VT iDirect is the world’s largest TDMA enterprise VSAT manufacturer and is the leader in key industries including mobility, military/government and cellular backhaul Company Web site: http://www.idirect.net ~ Main Phone: 703.648.8000 TAC Contact Information: Phone: 703.648.8151 ~ Email: tac@idirect.net ~ Web site: http://tac.idirect.net iDirect Government™, created in 2007, is a wholly owned subsidiary of iDirect and was formed to better serve the U.S government and defense communities Company Web site: http://www.idirectgov.com ~ Main Phone: 703.648.8118 TAC Contact Information: Phone: 703.648.8111 ~ Email: tac@idirectgov.com ~ Web site: http://tac.idirectgov.com Document Name: T0000598_REF_TRG_iDX 3.3_RevG_01052017.pdf Document Part Number: T0000598 ii Technical Reference Guide iDX Release 3.3 | T0000598 | Rev G Revision History Revision History The following table shows all revisions for this document To determine if this is the latest revision, check the TAC Web site at http://tac.idirect.net Revision Date Updates A 07/31/2014 First release of document for iDX 3.3 B 02/10/2015 Added Group Delay and Downstream Performance topic to the DVB-S2 Roll-off section C 02/11/2015 Added L2oS for iDX 3.3.1 D, E 09/21/2015 For iDX Release 3.3.3.1, added the following: • • • • • F 05/31/2016 For iDX 3.3.6, added the following: • • • G 01/05/2017 Technical Reference Guide iDX 3.3 | T0000598 | Rev G Added - X7 Multicast Fast Path on a Second Downstream Carrier on page 53 Added - Satellite Virtual Network and Service Delimiting Tags on page 225 Updated with Layer/Layer Use Cases - L2oS Examples including Layer and Layer Hybrid Mode on page 248 Updated section on RoHC - Configuring Advanced Header Compression on page 241 Added a section on SVNs and MAC address scalability - SVNs Scalability on page 227 and MAC Addresses Scalability on page 233 Added - CE Tag Transparency on page 224 Added - CE Tag Transparency Example on page 258 Added a note on telnet access and using default passwords Security Best Practices on page 119 Added a Multichannel Line Card restriction under Multichannel Line Cards on page 27 iii Revision History iv Technical Reference Guide iDX 3.3 | T0000598 | Rev G Contents Contents List of Figures xvi About xxi Purpose xxi Audience xxi Contents xxi Document Conventions xxii Getting Help xxiii Document Set xxiv Chapter iDirect System Overview System Overview IP Network Architecture Chapter DVB-S2 in iDirect Networks DVB-S2 Key Concepts DVB-S2 in iDirect DVB-S2 Downstream ACM Operation 10 Quality of Service in DVB-S2 ACM Networks 12 Remote Nominal MODCOD 12 Remote Maximum MODCOD 12 Fixed Bandwidth Operation 13 Enhanced Information Rate 13 Scaling Factors for Fixed Bandwidth Allocation 15 Technical Reference Guide iDX 3.3 | T0000598 | Rev G v Contents Bandwidth Allocation Fairness 16 DVB-S2 Configuration 16 DVB-S2 Performance Monitoring 17 Chapter Modulation Modes and FEC Rates 19 iDirect Modulation Modes And FEC Rates 19 DVB-S2 Modulation Modes and FEC Rates 19 2D 16-State Inbound Coding for DVB-S2 Networks 19 TDMA Waveform Enhancements 20 Chapter iDirect Spread Spectrum Networks 23 Overview of Spread Spectrum 23 Spread Spectrum Hardware Components 24 Supported Forward Error Correction (FEC) Rates 25 TDMA Upstream Specifications 25 SCPC Upstream Specifications 25 Chapter Multichannel Line Cards 27 Multichannel Line Card Model Types 27 Multichannel Line Card Receive Modes 27 Multichannel Line Card Restrictions and Limits 28 Chapter SCPC Return Channels 31 Hardware Support and License Requirements 31 Single Channel vs Multichannel SCPC Return 32 SCPC Return Feature on Remotes 32 VNO for SCPC Return 33 Chapter Adaptive TDMA 35 Theory of Operation 35 Short Term Adaptivity and Real-Time Resource Management 36 Medium Term Adaptivity 37 Long Term Adaptivity 38 vi Technical Reference Guide iDX 3.3 | T0000598 | Rev G Contents C/N0 and C/N 38 Fade Margin and Measurement Interval Calculations 40 C/N Dynamic Range for Individual Carriers 42 C/N0 Dynamic Range for Inroute Group 42 Power Control 43 Considerations of TDMA Frame-Filling Efficiency 43 Frame Filling 44 Adaptive TDMA Configuration and Constraints 44 Remote Configuration 46 Reference Carrier Parameters 46 Remote Carrier Constraint Parameters 47 47 Chapter Multicast Fast Path 49 Overview 49 Multicast Fast Path Streams 49 Multicast Fast Path Encryption 50 Multicast Fast Path Encryption Key Management 51 Enabling Multicast Fast Path Encryption 52 Multicast Fast Path Encryption Monitoring 52 X7 Multicast Fast Path on a Second Downstream Carrier 53 Enabling X7 Multicast Fast Path from a Second Downstream 53 Setting Up Multicast Fast Path Encryption Using a GKD Server 55 Configuring GKD for Encrypted Multicast Fast Path in Secondary Networks 55 Protocol Processor Configuration 56 Network Configuration 57 X7 Remote Configuration 58 Creating a GKD Options File for MCFPE for X7 Remotes with a Second Downstream Carrier 59 Supported List of Configurations 61 Chapter QoS Implementation Principles 65 Quality of Service (QoS) 65 Technical Reference Guide iDX 3.3 | T0000598 | Rev G vii Contents QoS Measures 65 iDirect QoS Profiles 66 Classification and Scheduling of Packets 68 Service Levels 68 Packet Scheduling 69 Priority Queues 70 Class-Based Weighted Fair Queues 70 Best Effort Queues 70 Application Throughput 71 Minimum Information Rate 71 Committed Information Rate (CIR) 72 Maximum Information Rate 72 Free Slot Allocation 73 Compressed Real-Time Protocol 73 Sticky CIR 73 Application Jitter 73 TDMA Slot Feathering 74 Packet Segmentation 74 Application Latency 74 Maximum Channel Efficiency vs Minimum Latency 75 Group QoS 75 Group QoS Structure 76 Bandwidth Pool 76 Bandwidth Group 76 Service Group 77 Application 77 Service Profiles 78 Remote Profiles 78 Group QoS Scenarios 79 Physical Segregation Scenario 79 CIR Per Application Scenario 80 Tiered Service Scenario 81 viii Technical Reference Guide iDX 3.3 | T0000598 | Rev G Contents Third Level of Segregation by VLAN Scenario 82 The Shared Remote Scenario 83 Remote Service Group Scenario 85 DVB-S2 ACM Scenario 1: Scaled Aggregate CIRs Below Partition’s CIR 87 DVB-S2 ACM Scenario 2: Scaled Aggregate CIRs Exceeds Partition’s CIR 89 Bandwidth Allocation Fairness Relative to CIR 90 Bandwidth Allocation Fairness Relative to MODCOD 91 Chapter 10 TDMA Initial Transmit Power 93 All Remotes Need To Transmit Bursts in the Same C/N Range 94 What Happens When Initial Tx Power Is Set Incorrectly? 94 When Initial Transmit Power is Too High 94 When Initial Transmit Power is Too Low 95 Chapter 11 Uplink Control Process 97 TDMA Uplink Control 97 Acquisition 97 Network Operation 99 UCP Correction Processing 99 UCP Symbol Timing 99 UCP Frequency Tracking 100 UCP Power Control and Fade Detection 100 SCPC Return Uplink Control 103 UCP Power Adjustment for SCPC Upstream Carriers 104 Viewing UCP Statistics in iMonitor 104 Chapter 12 Remote Idle and Dormant States 107 Overview 107 Feature Description 108 Chapter 13 Verifying Error Thresholds Using IP Packets 113 Introduction 113 TDMA Upstream Threshold Testing 113 Technical Reference Guide iDX 3.3 | T0000598 | Rev G ix Contents Upstream Example 114 Upstream Example 114 DVB-S2 Downstream Threshold Testing 115 Downstream Example 115 Chapter 14 Global NMS Architecture 117 How the Global NMS Works 117 Sample Global NMS Network 118 Chapter 15 Security Best Practices 119 Hub and NMS Server Security 119 Network Isolation and External Access 119 Server Password Security 119 Secure Server Connections 120 Encryption of Backup Files Before Archiving 120 Clearing Data from Decommissioned Servers 120 NMS Client Security 120 User Passwords and Permissions 120 Client Access 121 Remote Access 121 Console Password Security 121 Clearing Data from Decommissioned Remotes and Line Cards 122 DNS Queries on Satellite (SAT0) Interface of Remote 122 Chapter 16 Global Protocol Processor Architecture 123 Remote Distribution 123 De-coupling of NMS and Data Path Components 123 Chapter 17 Distributed NMS Server 125 Distributed NMS Server Architecture 125 iBuilder and iMonitor 126 x Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode L2oS Examples including Layer and Layer Hybrid Mode This section shows some L2oS use cases See Forwarding Rules on page 234 for additional information regarding how Ethernet frames are processed by the hub and remote Figure 31-16 shows VPWS connections between the hub and two remote sites with single access points to the iDirect modem Since the remotes act as access ports, no VLANs are required on the remote LAN PP Home/SOHO Router PC Satellite Network Upstream Layer Switch Remote Layer2 Access Port Hub System PC L2oS, VPWS Layer2 (SVN10) Layer2 (SVN20) Layer2 1qTrunk (VLAN10, VLAN20) Layer2 Access Port PC Remote Figure 31-16 VPWS Service with Remote Single End Points Hub configuration: • Default Mode: VPWS • SDT Mode: VLAN Remote configuration: • SDT Mode: Access • SVN ID: 10 Remote configuration: • SDT Mode: Access • SVN ID: 20 Hub forwarding: 248 Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode • Ethernet frames with VLAN ID 10 or VLAN ID 20 received from the upstream switch with a known destination MAC address in that SVN are sent over-the-air • Ethernet frames received over-the-air on SVN 10 or SVN 20 are forwarded to the upstream switch No remote-to-remote routing is performed by the iDirect hub Remote forwarding: • All Ethernet frames with non-local destination MAC addresses received by the remote on the local LAN are sent over-the-air on SVN 10 (Remote 1) or SVN 20 (Remote 2) • All Ethernet frames received over-the-air by a remote on its configured SVN that have a local destination MAC address are sent out on the remote LAN Figure 31-17 shows a VPWS connection between the hub and a remote site used to transport IPv6 packets Because Layer protocols are transparent to the Layer connection, IPv6 traffic can be transported over the satellite link Note that IPv6 traffic is not accelerated over the satellite link PP Satellite Network Upstream Layer Switch Remote Multiple PC Hub System L2oS, VPWS Layer2 1qTrunk VLAN10 Layer2 (SVN10) (VLAN10) IPv6 Figure 31-17 VPWS Service with IPv6 Traffic Hub configuration: • Default Mode: VPWS • SDT Mode: VLAN Remote configuration: • SDT Mode: VLAN • SVN ID: 10 Hub forwarding: • Ethernet frames with VLAN ID 10 received from the upstream switch on an 802.1q VLAN trunk with a known destination MAC address in SVN 10 are sent over-the-air • Ethernet frames received over-the-air on SVN 10 are forwarded to the upstream switch Technical Reference Guide iDX 3.3 | T0000598 | Rev G 249 L2oS Examples including Layer and Layer Hybrid Mode Remote forwarding: • Ethernet frames with VLAN ID 10 and non-local destination MAC address received by the remote on an 802.1q VLAN trunk on the local LAN are sent over-the-air on SVN 10 • Ethernet frames received over-the-air on SVN 10 by the remote with a local destination MAC address are sent out on the remote LAN on an 802.1q VLAN trunk tagged with VLAN 10 Figure 31-18 shows a VPWS connection between the hub and a single remote site with traffic from multiple VLANs PP PC Satellite Network Upstream Layer Switch Remote Hub System Layer Switch L2oS, VPWS Layer2 (.1qTrunk) VLAN10, VLAN20 Layer2 (SVN10) Layer2 (SVN20) Layer2 (.1qTrunk) VLAN10, VLAN20 PC Figure 31-18 VPWS Service with Multiple Remote VLANs Hub configuration: • Default Mode: VPWS • SDT Mode: VLAN Remote configuration: • SDT Mode: VLAN • SVN ID 1: 10 • SVN ID 1: 20 Hub forwarding: 250 • Ethernet frames with VLAN ID 10 or VLAN ID 20 received from the upstream switch on an 802.1q VLAN trunk with a known destination MAC address in the corresponding SVN are sent over-the-air • Ethernet frames received over-the-air on SVN 10 and SVN 20 are forwarded to the upstream switch on an 802.1q VLAN trunk Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode Remote forwarding: • All Ethernet frames with VLAN ID 10 and VLAN ID 20 and a non-local destination MAC address received by the remote on the local LAN are sent over-the-air on the corresponding SVN • All SVN 10 and SVN 20 traffic received over-the-air by the remote with a local destination MAC address for that SVN are sent out on the remote LAN on an 802.1q VLAN trunk Figure 31-19 shows a VPWS connections between the hub and two remote sites, each with a single VLAN Since the Default Mode is VPWS, the hub will not route traffic directly between the two remotes No hairpinning will occur within the iDirect network If there are multiple protocol processor blades at the hub, it is important to configure the upstream switch to disallow inter-blade communications to prevent the switch from replicating upstream traffic to the downstream before a Layer decision can be made PP Satellite Network Upstream Layer Switch Layer Remote PC Layer Switch Hub System (VLAN10) L2oS, VPWS Layer2 (SVN10) Layer2 1qTrunk (VLAN10, VLAN20) Layer2 (SVN20) Layer PC Layer Switch Remote (VLAN20) Figure 31-19 VPWS Service with Multiple VLANs Hub configuration: • Default Mode: VPWS • SDT Mode: VLAN Remote configuration: • SDT Mode: VLAN • SVN ID: 10 Remote configuration: • SDT Mode: VLAN Technical Reference Guide iDX 3.3 | T0000598 | Rev G 251 L2oS Examples including Layer and Layer Hybrid Mode • SVN ID: 20 The hub and remote forwarding rules are similar to those described for the example shown in Figure 31-17 and Figure 31-18 Figure 31-20 shows a VPLS connection between the hub and three remote sites, each using VLAN 10 Because the hub mode is VPLS, the hub performs remote-to-remote routing of upstream Ethernet frames received on SVN 10 that have a known destination MAC address at another remote site on the same SVN Multicast frames are handled as described in Forwarding Rules on page 234 PP Satellite Network VLAN10 Remote Router Layer Switch PC Layer2 (SVN1, VLAN10) Layer2 (VLAN10) Hub System VLAN10 Remote L2oS, VPLS Layer2 (SVN10) Layer2 (VLAN10) Layer Switch PC Layer2 (VLAN10) Layer2 (SVN1, VLAN10) VLAN10 Remote Layer Switch Layer2 (VLAN10) Layer2 (SVN1, VLAN10)) Figure 31-20 VPLS Service with Remote-to-Remote Routing Hub configuration: • Default Mode: VPLS • SDT Mode: VLAN Remote configuration (all remotes): 252 • SDT Mode: VLAN • SVN ID: 10 Technical Reference Guide iDX 3.3 | T0000598 | Rev G PC L2oS Examples including Layer and Layer Hybrid Mode Figure 31-21 shows VPWS connections between the hub and two remote sites, each using VLAN 10 Because the hub mode is VPWS, the hub does not perform remote-to-remote routing of upstream Ethernet frames received on SVN 10 All remote-to-remote routing decisions are made by the upstream router or switch PP Satellite Network Router R o ter VLAN10 Remote Hub System PC Layer Switch Layer2 (SVN1, VLAN10) Layer2 1qTrunk VLAN10 L2oS, VPWS Layer2 (SVN10) VLAN10 Remote PC Layer Switch Layer2 (SVN1, VLAN10) Figure 31-21 VPWS Service with Remote-to-Remote Routing by Upstream Router Hub configuration: • Default Mode: VPWS • SDT Mode: VLAN Remote configuration (all remotes): • SDT Mode: VLAN • SVN ID: 10 Technical Reference Guide iDX 3.3 | T0000598 | Rev G 253 L2oS Examples including Layer and Layer Hybrid Mode Figure 31-22 shows an L2oS network configured to use VLAN SDT Mode at the remote site and Q-in-Q SDT Mode at the hub The Local ID configured for the remote maps the VLAN IDs of Ethernet frames on the local LAN to the two-part SVN required to support Q-in-Q tags at the hub Local ID maps 1Q Trunk to Q-in-Q Layer Switch PP PC P Satellite Network Layer2 1Q Trunk (VLAN20) Layer Switch Customer Layer Switch Remote Layer Switch Hub System Layer2 1Q Trunk Layer2 Q-in-Q Trunk Q-in-Q L2oS, VPWS SVN100_10, Layer2 (SVN100: Q-in-Q:Q-in-Q OUTER VLAN100) SVN100_20, Q-in-Q SVN100_30, Q-in-Q Layer2 1Q Trunk (VLAN10, VLAN20, VLAN30) PC PC Layer Switch Figure 31-22 Hub-Side Q-in-Q and Remote VLAN Hub configuration: • Default Mode: VPWS • SDT Mode: Q-in-Q Remote configuration: • SDT Mode: VLAN • SVN 1: • • 254 • SVN ID: 100_10 • Local ID: 10 SVN 1: • SVN ID: 100_20 • Local ID: 20 SVN 1: • SVN ID: 100_30 • Local ID: 30 Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode Figure 31-23 shows an iDirect L2oS network and a terrestrial network using Border Gateway Protocol (BGP) for redundancy The Layer BGP protocol is transparent to the iDirect Layer network SP Terrestrial Network MPLS PE PP MPLS PE Upstream Router (MPLS CE) Managed CPE SP Satellite Network LAN Remote SP Core Network MPLS VPN Layer-3 IPv4 Hub System Layer2 1Q Trunk (VLAN10) L2oS, VPWS Layer2 (SVN10) Layer2 VLAN10 Layer-3 IPv4 BGP Session Figure 31-23 BGP Peering The iBuilder configuration for Figure 31-23 is similar to the configuration described for Figure 31-17 Technical Reference Guide iDX 3.3 | T0000598 | Rev G 255 L2oS Examples including Layer and Layer Hybrid Mode VLAN20 VLAN10 Figure 31-23 shows an example of the MPLS network extension with a VRF-lite session over the air PP MPLS PE ASR1k PoP CE Satellite Network CPE Switch Remote Hub System SP Core Network Layer2 1Q Trunk Q-in-Q: OUTER VLAN100 EoMPLS CPE Router L2oS, VPWS Layer2 (SVN100: Q-in-Q: OUTER VLAN100) Layer2 1Q Trunk Q-in-Q: OUTER VLAN100 VRF-Lite Figure 31-24 MPLS with VRF Lite Over the Air NOTE: VRF lite implies non-MPLS tagged frames Although over-the-air transport of MPLS tagged frames is supported, TCP acceleration and advanced header compression are not applied to these frames Layer 2/Layer Hybrid Mode with VLAN Tagging at Hub Figure 31-25 Layer 2/Layer Hybrid Mode with VLAN Tagging at Hub In this example, the hub side is connected to an 802.1Q trunk with six VLANs: • 256 Three Layer VLANs Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode • Two Layer VLANs (the term SVN used in the diagram includes both VLANs and Q-in-Q) • One Layer multicast only VLAN On the remote end, the X1 in this case is configured to output at the LAN port an 802.1Q trunk consisting of the following: • One Layer multicast only VLAN (there is only configured at the hub) • One Layer VLAN (chosen from the three configured at the hub) • One Layer VLAN (chosen from the two configured at the hub) The X7 is configured to use four of the eight switch ports: • Port - 802.1Q trunk with Layer VLANs • Port - One Layer VLAN • Port - One Layer VLAN • Port - One Layer Multicast only VLAN (there is only one configured at the hub) Layer 2/ Layer Hybrid Mode in Q-in-Q Tagging at Hub Figure 31-26 Layer 2/Layer Hybrid Mode with Q-in-Q Tagging at Hub In the above example, the hub is connected to an 802.1ad Q-in-Q trunk with seven SVNs: • Three Layer SVNs - Identified by the Reserved Outer Tag; the Reserved Outer Tag is removed immediately at the PP resulting in three Layer VLANs • Three Layer SVNs - These are used to transverse the iDirect network intact as Q-in-Q tagged SVNs • One Layer multicast only SVN - Identified by the Reserved Outer Tag The Reserved Outer Tag is removed immediately at the PP resulting in three Layer VLANs On the remote end, the X1 in this example is configured to output at the LAN port an 802.1ad Q-in-Q trunk consisting of L2 SVNs Only L2 SVNs can be part of any Q-in-Q trunk on the remote LAN side Technical Reference Guide iDX 3.3 | T0000598 | Rev G 257 L2oS Examples including Layer and Layer Hybrid Mode The X7 outputs on four out of its eight ports as follows: • Port 1- 802.1Q trunk with Layer VLANs and only one Layer Multicast only VLAN • Port - Layer VLAN • Port - Layer VLAN • Port - Layer VLAN CE Tag Transparency Example Figure 31-27 CE Tag Transparency In this example, end user's traffic is aggregated by a switch into a.1Q VLAN trunk and is in turn connected to an X7 switch port configured in CE_TT mode The X7 remote is configured to insert an outer or SP tag of 500 on every VLAN frame entering that port The network operator thus can use the SP tag of the resulting Q-in-Q SVN to direct the end user's traffic to its destination To configure the iDirect components for this example, one will first create a Q-inQ SVN with CE_TT enabled and an SP tag of 500 There is no need to configure the CE tag for this SVN since this SVN will accept all CE tag values The second step is to assign this SVN to an X7 switch port The benefits of this feature include: Increase L2oS SVN scale - using only pseudo wire per outer/SP tag Improve operators' operational efficiency - simplifying site commissioning and maintenance Allow operators to offer true port-based service 258 Technical Reference Guide iDX 3.3 | T0000598 | Rev G L2oS Examples including Layer and Layer Hybrid Mode Here are a few restrictions to consider when using this feature: This feature is only supported on the X7 and X7-EC remotes A port can either be CE Tag Transparent (CE_TT) or not There cannot be mixed modes on a port PP side Service Delineating Tag (SDT) must be Q-in-Q No VLAN access on a CE_TT port If a VLAN access is necessary, the operator can provision another non-CE_TT port No L2/L3 hybrid support on CE_TT port When large multicast streams are needed, operator should provision another non-CE_TT port All traffic going into a CE_TT port must be 1Q VLAN-tagged, that is, single tagged Local rewriting or remapping of VLAN tags is not supported Technical Reference Guide iDX 3.3 | T0000598 | Rev G 259 L2oS Examples including Layer and Layer Hybrid Mode 260 Technical Reference Guide iDX 3.3 | T0000598 | Rev G iDirect 13861 Sunrise Valley Drive, Suite 300 Herndon, VA 20171-6126 +1 703.648.8000 +1 866.345.0983 www.idirect.net Advancing a Connected World ... discrepancies For details, see the iMonitor User Guide Technical Reference Guide iDX 3.3 | T0000598 | Rev G 17 DVB-S2 in iDirect 18 Technical Reference Guide iDX 3.3 | T0000598 | Rev G iDirect Modulation... IP Architecture – Classic IP Configuration Technical Reference Guide iDX 3.3 | T0000598 | Rev G IP Network Architecture Technical Reference Guide iDX 3.3 | T0000598 | Rev G DVB-S2 Key Concepts... VLANs per Remote Technical Reference Guide iDX 3.3 | T0000598 | Rev G IP Network Architecture Figure 1-3 iDirect IP Architecture – VLAN Spanning Remotes Technical Reference Guide iDX 3.3 | T0000598