Lecture 122: DX Virtual Interfaces (VIF) creation parameters
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：09:17
- 来源：Udemy Lecture 27896534
- Slide 数量：29
- 画面切换：00:27、00:58、01:09、01:17、01:40、02:03、02:07、02:29、02:46、03:08、03:26、03:33、03:57、04:14、05:22、05:33、05:46、06:13、06:24、06:59、07:20、07:35、08:05、08:11、08:16、08:20、08:45、08:54
扫描说明
逐条检查了 Udemy 页面中的 174 条 Transcript cue，并以每条 cue 对应画面扫描了全长约 9:17 的视频。依据 VIF 创建参数清单中每一次项目揭示、控制台示例、Public VIF 前缀图和 Jumbo Frame 配置示例，共划分为 29 个小节。正式截图均在锁定 Lecture 27896534、Autoplay 关闭、视频播放且控件隐藏后，按完整媒体边界截取并输出为 1364×770，逐张复核了左右与底部边界。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. VIF Parameters 导入
时间范围：00:00–00:27
总结 / Summary
中文
本讲梳理适用于公共、私有和中转虚拟接口（Public, Private, and Transit Virtual Interfaces）的通用创建参数。
English
This lecture introduces the common creation parameters for Public, Private, and Transit Virtual Interfaces.
Transcript
00:00 Hi.
00:01 So in the earlier lecture, we understood different type of the VIFs.
00:04 Now let's understand the VIF parameters.
00:07 Now, in this lecture,
00:08 we are not going to very detail about individual
00:11 VIF that is public or private or Transit.
00:13 But we are talking about general parameters which
00:16 are applicable to most of the VIFs.
00:19 And then while we get into the more detail, we will talk about individual VIFs.
00:24 So let's get started. So the very first thing as you know,
2. 选择底层 Connection
时间范围：00:27–00:58
总结 / Summary
中文
创建 VIF 前必须先选择底层 Direct Connect 连接（DX Connection）或链路聚合组（Link Aggregation Group, LAG）；连接可以是 Dedicated 或 Hosted。
English
A VIF requires an underlying DX Connection or Link Aggregation Group, using either a Dedicated or Hosted connection.
Transcript
00:27 for creating the VIF, you need DirectConnect connection.
00:30 Now that connection can be a Hosted connection or a Dedicated connection
00:34 or it could be a LAG. Now we haven't seen LAG so far, but it is link aggregation.
00:39 That means you can consolidate multiple dedicated
00:42 connections as one logical connection so that you get
00:46 multiplied bandwidth.
00:47 And more about that will cover shortly in the following lectures.
00:52 But then
00:53 you need a connection on top of it, you create a VIF, right? So that's obvious,
3. 选择 VIF Type
时间范围：00:58–01:09
总结 / Summary
中文
VIF 类型（VIF type）决定逻辑用途，可选择 Public、Private 或 Transit。
English
The VIF type determines its logical purpose: Public, Private, or Transit.
Transcript
00:58 then comes the VIF type which is also self-explanatory.
01:03 And then VIF name, you can put any name, essentially it is a tag, a name tag
4. 设置 VIF Name
时间范围：01:09–01:17
总结 / Summary
中文
VIF 名称（VIF name）是用于识别资源的名称标签，可按组织命名规范自由设置。
English
The VIF name is a resource label that can follow the organization's naming convention.
Transcript
01:09 for your VIF like any other AWS resources
01:12 now comes the other important parameters which
01:14 you need to understand why it is required
5. 指定 VIF Owner
时间范围：01:17–01:40
总结 / Summary
中文
VIF 所有者（VIF owner）可以是当前 AWS 账户，也可以是另一个账户；后者形成托管 VIF（Hosted VIF）并需要消费方接受。
English
The VIF owner can be the current AWS account or another account, creating a Hosted VIF that the consumer must accept.
Transcript
01:17 VIF owner. Now, we have been talking about a normal VIF as well as the Hosted VIF.
01:23 Now, if you remember,
01:25 we said like in case of Hosted VIF, the VIF owner is some other AWS account.
01:30 And that's where in this case,
01:32 you have to provide whether it's your own AWS account or
01:36 it's someone else AWS account who will be owning the VIF
6. Private VIF 的 Gateway Type
时间范围：01:40–02:03
总结 / Summary
中文
网关类型（gateway type）只适用于 Private VIF，用于指定该接口如何连接 VPC。
English
Gateway type applies only to a Private VIF and determines how the interface connects to VPCs.
Transcript
01:40 then comes the Gateway type. Now, this is applicable to the private VIF.
01:45 only because
01:47 for public VIF,
01:48 you don't attach it to the VPC but private VIF can be attached to
01:52 the VPC through virtual private Gateway or it can be attached to the direct
01:57 connect gateways. Now, we haven't seen direct connect gateways as of now,
02:00 but this is what the two Gateway types that
7. VGW 或 DX Gateway
时间范围：02:03–02:07
总结 / Summary
中文
Private VIF 可以连接虚拟私有网关（Virtual Private Gateway, VGW）或 Direct Connect 网关（Direct Connect Gateway, DXGW）。
English
A Private VIF can attach to either a Virtual Private Gateway or a Direct Connect Gateway.
Transcript
02:03 you have to select when you create the private VIF
8. 分配 VLAN ID
时间范围：02:07–02:29
总结 / Summary
中文
VLAN ID 使用 IEEE 802.1Q 标记隔离同一物理连接上的 VIF 流量，创建时需要为接口分配 VLAN。
English
A VLAN ID uses IEEE 802.1Q tagging to isolate VIF traffic on the same physical connection.
Transcript
02:07 then comes the VLAN. Now VLAN
02:09 ID is
02:10 something that you want to
02:12 assign it to the VIF.
02:13 And we understood about that in the basics of DirectConnect
02:17 where we say like there is a VLAN trunking happening
02:19 and then you have to tag your VLAN frames so
02:22 that your traffic can be segregated through the same connection.
02:26 And that's where you have to provide this VLAN ID.
9. VLAN 唯一性与范围
时间范围：02:29–02:46
总结 / Summary
中文
同一 DX Connection 上的两个 VIF 不能使用相同 VLAN ID；有效范围为 1–4094，不同连接可以复用同一 ID。
English
VLAN IDs must be unique on one DX connection and range from 1 to 4094, though the same ID can be reused on different connections.
Transcript
02:29 So it should not be duplicated on the same DX connection.
02:32 Of course, two VIFs on the same DX connection cannot have the same
02:36 VLAN ID.
02:37 But across different connections, you can reuse the same VLAN ID
02:42 and the value should be between 1 to 4094.
10. Hosted Connection 的 VLAN
时间范围：02:46–03:08
总结 / Summary
中文
在 Hosted Connection 上，VLAN ID 由连接所有者/Direct Connect Partner 预先配置，客户创建 VIF 时不能修改。
English
For a Hosted Connection, the connection owner or Direct Connect Partner preconfigures the VLAN ID, so the customer cannot edit it.
Transcript
02:46 Now, for Hosted connection, as you know, the Hosted connection is not owned by you,
02:51 right? In that case, VLAN tag is provided by the Hosted connection owner.
02:56 In that case,
02:57 you don't get that option to select the VLAN tag or put the VLAN tag on the VIF.
03:01 It is inherited from your Hosted connection. So it's configured by your partner.
11. BGP Address Family
时间范围：03:08–03:26
总结 / Summary
中文
Direct Connect 需要端到端边界网关协议（Border Gateway Protocol, BGP）路由；地址族（address family）可选 IPv4 或 IPv6。
English
Direct Connect requires end-to-end BGP routing, with an address family of either IPv4 or IPv6.
Transcript
03:08 Now about the BGP, as you know, for DirectConnect,
03:12 it is required to have the end to end BGP
03:15 routing configured. Now, all these parameters will be related to the BGP.
03:20 So first of all, the BGP Peering happens over the
03:23 IPv4 addresses or IPv6 addresses
12. BGP Peer IP Addresses
时间范围：03:26–03:33
总结 / Summary
中文
BGP 对等体 IP 地址（BGP peer IP addresses）的分配规则取决于 VIF 类型和所选地址族。
English
BGP peer IP address allocation depends on the VIF type and selected address family.
Transcript
03:26 then BGP peer IP addresses.
03:28 Now, this would depend on whether you are using a public VIF or a private VIF.
13. Public VIF 的 IPv4 Peer
时间范围：03:33–03:57
总结 / Summary
中文
Public VIF 的 IPv4 BGP 对等需要公共 /30 CIDR；若客户没有合适地址，可请求 AWS 分配。
English
A Public VIF needs a public /30 CIDR for IPv4 BGP peering; AWS can allocate one when the customer does not have it.
Transcript
03:33 Now, if you're using the public VIF, in that case,
03:36 you need to give the public IP ranges for BGP peering in the range of
03:42 /30 CIDR block.
03:43 And
03:44 if you don't have public IP ranges in this CIDR block,
03:48 then you can ask AWS to provide you those public IP ranges
03:52 and those IPs will be used as a BGP peer.
03:55 In that case,
14. Private VIF 的 IPv4 Peer
时间范围：03:57–04:14
总结 / Summary
中文
Private VIF 可从 169.254.0.0/16 范围指定链路本地地址（link-local addresses）；留空时 AWS 会自动选择。
English
A Private VIF can use link-local addresses from 169.254.0.0/16, or AWS can select them automatically.
Transcript
03:57 in case of private VIF,
03:58 you can provide any IP range from the given range that is 169.254.0.0/16.
04:04 And if you skip it, AWS will automatically pick some range from that
04:09 CIDR block and we assign it to your BGP session.
15. IPv6 Peer 自动分配
时间范围：04:14–05:22
总结 / Summary
中文
使用 IPv6 时不能手动选择 BGP peer IP；AWS 会自动分配 /125 IPv6 CIDR。
English
For IPv6, BGP peer addresses cannot be selected manually; AWS automatically allocates a /125 IPv6 CIDR.
Transcript
04:14 Now, one thing to understand is that in case of IPv4
04:17 addresses,
04:19 you can't choose the BGP peer IP addresses.
04:22 It is allocated automatically by AWS in the range of /125 IPv6
04:26 CIDR block.
04:28 So these are
04:29 the things about BGP peer IPs and we'll understand
04:32 more about those when we talk about a specific public VIF and
04:36 private VIF than how these BGP peer IPs can be
04:40 allocated.
04:41 So just to summarize what we saw so far for creating VIF,
04:45 you need to have the connection, the type of the VIF,
04:48 the name of the VIF who is the owner of the VIF.
04:50 Now, in case of private VIF,
04:52 whether it is going to be connected to
04:54 a virtual private Gateway or a DirectConnect Gateway,
04:57 then you need to provide a VLAN tag in case of Hosted connection,
05:00 VLAN tag is already provided by the Hosted connection owner that is your partner.
05:05 And otherwise you will provide a unique VLAN
05:08 ID on that particular connection.
05:10 Then for BGP Routing, you need to
05:12 choose the address family and then based on
05:16 whether it's a public VIF or a private VIF,
05:18 you have to give the BGP Peer IP addresses.
16. Additional VIF Parameters
时间范围：05:22–05:33
总结 / Summary
中文
接下来进入 VIF 的附加 BGP、安全、路由通告和 MTU 参数。
English
The lecture next covers additional BGP, security, route-advertisement, and MTU parameters.
Transcript
05:22 Ok. Moving on, let's understand additional VIF parameters.
05:26 So as you know, there is a BGP peering,
05:28 that means there should be BGP peers and their ASN numbers,
17. BGP ASN
时间范围：05:33–05:46
总结 / Summary
中文
每个 BGP 对等体都需要自治系统号（Autonomous System Number, ASN），此处填写客户侧路由器的 ASN。
English
Each BGP peer needs an Autonomous System Number; this field represents the customer-side router ASN.
Transcript
05:33 autonomous system numbers.
05:34 And in the previous lecture, we learned that
05:37 in a provides a range of numbers for public and private ASNs.
05:42 And in that case, AWS also have some ranges. So
18. Public 或 Private ASN
时间范围：05:46–06:13
总结 / Summary
中文
客户侧 VIF 可以使用公有 ASN（public ASN）或私有 ASN（private ASN）；这与 AWS 侧 VGW、DXGW 或 TGW 的 ASN 参数不同。
English
The customer-side VIF can use a public or private ASN, distinct from ASN settings on AWS-side VGW, DXGW, or TGW components.
Transcript
05:46 for VIF creation,
05:48 you could either have the public or private ASN assigned to your side of the router.
05:52 Now,
05:53 here we are specifically talking about the VIFs and we are not talking about the
05:57 ASNs for other components like DirectConnect Gateway or
06:00 a Transit Gateway or virtual private Gateway.
06:03 Those are all private
06:04 ASNs that AWS side of the components, right?
06:08 But here we are talking about the VIF on your side of the router connection.
19. Public ASN 所有权
时间范围：06:13–06:24
总结 / Summary
中文
若使用 Public ASN，该号码必须由客户拥有并在互联网号码分配机构（Internet Assigned Numbers Authority, IANA）体系下正式注册。
English
A Public ASN must be owned by the customer and formally registered through the IANA system.
Transcript
06:13 So if you own the public ASN
06:16 which you have registered with IANA,
06:18 then of course you can use your public ASN and
06:20 that number will be the same that you are already having,
06:24 right?
20. Private ASN 范围
时间范围：06:24–06:59
总结 / Summary
中文
Private ASN 可使用 16 位或 32 位范围；课程列出 64512–65534 以及 AWS 支持的 32 位范围，并提醒无需死记具体上限。
English
Private ASNs can use 16-bit or 32-bit ranges; the lecture lists 64512–65534 and the AWS-supported 32-bit range without requiring memorization.
Transcript
06:24 But if it's a private ASN,
06:25 then you can have either 16 bit or 32 bit number. For 16 bit,
06:30 It is from 64512 to 65534 and default is 64512.
06:37 And if it is 32 bit, then this range differs a little because
06:42 IANA
06:42 provides much longer range because its full 32 bit number,
06:46 but AWS supports only 31 bit and that's where this number could be between 1 to 2147..,
06:52 whatever that number is.
06:53 So again,
06:55 you don't need to remember all these numbers, but just for your information.
21. 控制台 ASN 校验
时间范围：06:59–07:20
总结 / Summary
中文
AWS 控制台会显示并校验可用 BGP ASN 范围；不被 Direct Connect 支持的号码即使属于更广的 IANA 私有范围也会被拒绝。
English
The AWS console displays and validates the supported BGP ASN range, rejecting values outside Direct Connect's accepted subset.
Transcript
06:59 So if you go to the AWS console and try to create a VIF,
06:59 you will see the BGP ASN number at the bottom
07:05 and the range is specified here.
07:08 So I just tried putting the IANA provided range which
07:10 starts with 4200 for the private ASN 32 bit number,
07:16 but it doesn't accept that.
07:18 Ok. Moving on,
22. BGP MD5 Authentication
时间范围：07:20–07:35
总结 / Summary
中文
可提供 BGP MD5 认证密钥（BGP MD5 authentication key）；若留空，AWS 会自动生成，也可按安全策略使用自定义明文密钥。
English
A BGP MD5 authentication key can be supplied; AWS generates one when omitted, or a custom plaintext key can follow security policy.
Transcript
07:20 you also need to provide the BGP MD5 authentication key.
07:23 Now, if you don't provide this key,
07:26 AWS will automatically generate it for you.
07:28 But if you have a security policy to have your own keys,
07:31 then you can use any plain text kind of keys as well there.
23. Public VIF Prefixes
时间范围：07:35–08:05
总结 / Summary
中文
Public VIF 必须在创建时声明从本地网络通告的前缀（prefixes to advertise）；Private/Transit VIF 则在 BGP 会话建立后动态交换路由。
English
A Public VIF must declare on-premises prefixes during creation, while Private and Transit VIFs exchange routes after BGP comes up.
Transcript
07:35 Moving on for public VIF,
07:37 you also need to specify the prefixes to be advertised from the
07:41 on-premises side.
07:42 Now this isn't true for private VIF or a Transit
07:46 VIF because once the BGP session is established,
07:48 then the BGP peer will exchange those routes.
07:52 But for public VIF, you would have to advertise these routes
07:56 and as AWS router learns those routes,
07:59 so any traffic going to those routes from AWS end it will use the direct
08:03 connection for that
24. 通告 IPv4 或 IPv6 路由
时间范围：08:05–08:11
总结 / Summary
中文
Public VIF 可通过 BGP 通告 IPv4 或 IPv6 路由，AWS 学到这些前缀后会将对应返回流量送入 Direct Connect。
English
A Public VIF can advertise IPv4 or IPv6 routes over BGP so AWS sends matching return traffic through Direct Connect.
Transcript
08:05 and you can advertise both uh IPv4
08:07 routes or IPv6
08:09 routes
25. Public VIF Prefix Diagram
时间范围：08:11–08:16
总结 / Summary
中文
架构图展示多个区域的 Public VIF 汇聚到 Direct Connect，并连接企业数据中心。
English
The diagram shows Public VIFs from multiple Regions converging on Direct Connect and the corporate data center.
Transcript
08:11 how it looks like.
08:12 So this is kind of DirectConnect connection and there are multiple public VIFs.
26. 向 AWS 通告 Prefixes
时间范围：08:16–08:20
总结 / Summary
中文
企业侧通过 Public VIF 向 AWS 通告自身前缀，图中箭头表示路由通告方向。
English
The corporate side advertises its prefixes to AWS over the Public VIF, with the arrow showing the route-advertisement direction.
Transcript
08:16 So you need to advertise the prefixes while you set the VIF.
27. Jumbo Frames 支持
时间范围：08:20–08:45
总结 / Summary
中文
巨型帧（Jumbo Frames）只支持 Private 和 Transit VIF；Private VIF 最大 MTU 为 9001 字节，Transit VIF 最大为 8500 字节，默认 MTU 为 1500。
English
Jumbo Frames are supported only on Private and Transit VIFs: up to 9001-byte MTU for Private and 8500 for Transit, with 1500 as default.
Transcript
08:20 OK, moving on about the Jumbo frames.
08:23 So AWS DirectConnect also supports Jumbo frames,
08:27 but this can only be enabled for Transit VIF or a private VIF.
08:31 So if it is a private VIF, then you can have Jumbo frame up to 9001 byte
08:38 default is 1500 byte.
08:40 And if it's a Transit VIF, it can be up to 8500 bytes.
28. Private VIF Jumbo MTU
时间范围：08:45–08:54
总结 / Summary
中文
创建 Private VIF 时，可在附加设置（additional settings）中启用 9001 MTU 的 Jumbo Frame。
English
When creating a Private VIF, the additional settings can enable a 9001-byte Jumbo Frame MTU.
Transcript
08:45 So if you go to VIF creation page again, in additional settings,
08:49 you can enable the Jumbo frame.
08:51 Now this is for private VIF. Similarly, if you
29. Transit VIF Jumbo MTU
时间范围：08:54–09:17
总结 / Summary
中文
Transit VIF 的创建页同样提供 Jumbo Frame 选项，但其最大 MTU 为 8500；Public VIF 不支持 Jumbo Frames。
English
Transit VIF creation also offers Jumbo Frames, with an 8500-byte maximum MTU; Public VIF does not support Jumbo Frames.
Transcript
08:54 create a Transit VIF, then you could also enable the Jumbo frames.
08:59 So just remember that Jumbo frames are supported in DirectConnect but
09:03 not for the public VIF but for Transit or private VIF.
09:08 So that's it about this lecture.
09:10 Now, let's get into the individual VIF creation process.
09:14 Thanks for watching and stay tuned.
整讲总结 / Overall Summary
中文
创建 VIF 时需要指定底层 Connection/LAG、VIF 类型、名称、所有者、Private VIF 的网关类型、VLAN、BGP 地址族和 Peer IP。附加参数包括客户侧 BGP ASN、MD5 认证、公有 VIF 的前缀通告以及 Private/Transit VIF 的 Jumbo Frame MTU。Hosted Connection 的 VLAN 由 Partner 预配置，Public VIF 的前缀必须在创建时声明。
English
VIF creation requires an underlying Connection or LAG, VIF type, name, owner, Private VIF gateway type, VLAN, BGP address family, and peer IPs. Additional settings include the customer-side BGP ASN, MD5 authentication, Public VIF prefix advertisements, and Jumbo Frame MTU for Private and Transit VIFs. Hosted Connection VLANs are partner-assigned, and Public VIF prefixes must be declared during creation.
返回顶部 ↑