接口

采集于 2026-07-28，来自本部署中的一台 CE。sitecli/capture-manifest.json 记录了具体是哪个节点，scripts/capture-sitecli.sh --check 会针对实时 CE 重新校验命令 面。

这些命令报告的是内核的视角。Argo 数据平面维护着自己的视角，可通过 vif 查看，两者可能并不一致。

ip

接受一个 ip 子命令。addr 是最常用的；route、link 和 neigh 也 可用。

{"command":["ip","addr"]}

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: a-i-eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 60:45:bd:eb:38:ea brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.4/26 brd 10.0.2.63 scope global noprefixroute eth1
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 60:45:bd:eb:3d:f3 brd ff:ff:ff:ff:ff:ff
    inet 10.0.3.4/26 brd 10.0.3.63 scope global noprefixroute eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::55af:2cd4:23a1:7e06/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 62:61:2b:33:cd:42 brd ff:ff:ff:ff:ff:ff
    inet 100.64.255.1/29 brd 100.64.255.7 scope global docker0
       valid_lft forever preferred_lft forever
10: tap_eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc multiq state UNKNOWN group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
11: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.4/26 brd 10.0.1.63 scope global noprefixroute vhost0
       valid_lft forever preferred_lft forever
13: vethfrr0@if12: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:01:02:03:04:05 brd ff:ff:ff:ff:ff:ff link-netns frrns
15: argo-envoy-0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1520 qdisc noqueue state UP group default qlen 1000
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
17: host-envoy-0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ee:95:ea:b5:8c:2a brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
    inet 169.254.100.1/30 scope global host-envoy-0
       valid_lft forever preferred_lft forever
18: xc-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
19: argo-end@xc-br0-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 76:e0:23:f6:48:8b brd ff:ff:ff:ff:ff:ff
20: xc-br0-end@argo-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master xc-br0 state UP group default qlen 1000
    link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
22: linkquality0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 590 qdisc noqueue state UP group default
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns ns-link-quality
24: vethbfd0@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns bfdns
25: keepalived-tap: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 32:1d:e4:ae:46:0e brd ff:ff:ff:ff:ff:ff
    inet 169.254.10.13/30 brd 169.254.10.15 scope global keepalived-tap
       valid_lft forever preferred_lft forever
27: vethdnsmasq0@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:01:02:03:04:07 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet 169.254.254.103/32 brd 169.254.255.255 scope global vethdnsmasq0
       valid_lft forever preferred_lft forever

按设计，CE 拥有三块 Azure 网卡——管理/SLO、外部、内部/SLI——但 guest 并不会按照该顺序所暗示的方式呈现它们，而误读这些 输出正是浪费时间的地方。

在 guest 中	承载
a-i-eth0	完全没有地址——这是被重命名的物理 eth0，由 Argo 数据平面接管
vhost0	管理/SLO 地址，即 BGP 建立对等的地址，也是站点对象上报的地址
eth1 和 eth2	外部与内部/SLI 地址——但顺序并不固定

eth1 和 eth2 中哪一个是内部接口，在不同节点上并不相同

从本次部署中三台 CE 上实时读取的结果：在 f5-xc-ce-vm-01 和 f5-xc-ce-vm-03 上，内部/SLI 地址位于 eth2；而在 f5-xc-ce-vm-02 上它位于 eth1。配置中没有任何内容决定这一点。

因此，永远不要从接口名推断子网，也永远不要把某个节点上的映射关系照搬到 另一个节点。改为按地址匹配——CE 地址所属的子网是稳定的，即使承载该地址的 接口并不稳定。

a-i-eth0 不承载地址，也正是无法通过管理地址访问 sshd 的全部原因： 那里根本没有监听程序，而不是端口被阻断。参见 SSH。

ip-link-show

仅限链路层：状态、MTU、排队规则、MAC。

{"command":["ip-link-show"]}

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: a-i-eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 60:45:bd:eb:38:ea brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 60:45:bd:eb:3d:f3 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether 62:61:2b:33:cd:42 brd ff:ff:ff:ff:ff:ff
10: tap_eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc multiq state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
11: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 60:45:bd:eb:3f:f2 brd ff:ff:ff:ff:ff:ff
13: vethfrr0@if12: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 02:01:02:03:04:05 brd ff:ff:ff:ff:ff:ff link-netns frrns
15: argo-envoy-0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1520 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
17: host-envoy-0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ee:95:ea:b5:8c:2a brd ff:ff:ff:ff:ff:ff link-netns envoy-ns
18: xc-br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
19: argo-end@xc-br0-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 76:e0:23:f6:48:8b brd ff:ff:ff:ff:ff:ff
20: xc-br0-end@argo-end: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master xc-br0 state UP mode DEFAULT group default qlen 1000
    link/ether aa:db:2f:e1:15:2c brd ff:ff:ff:ff:ff:ff
22: linkquality0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 590 qdisc noqueue state UP mode DEFAULT group default
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns ns-link-quality
24: vethbfd0@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 00:00:5e:00:01:00 brd ff:ff:ff:ff:ff:ff link-netns bfdns
25: keepalived-tap: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 32:1d:e4:ae:46:0e brd ff:ff:ff:ff:ff:ff
27: vethdnsmasq0@if26: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 02:01:02:03:04:07 brd ff:ff:ff:ff:ff:ff link-netnsid 4

当问题是“链路是否已启用，以及它的 MTU 是多少”时，这比 ip addr 更快。 MTU 不匹配是隧道能够建立但无法通过流量的常见原因。

ip-link-set Exec 层级 —— 会产生变更

将某个接口或组置为 up 或 down。

ip-link-set (<device>||<group>) (up||down)

此处未执行，且无法通过常规方式访问

这是本版本中唯一的 Exec 层级命令。它发往 exec 端点 而非 exec-user，并且会改变节点状态：在远端 CE 上将 eth0 置为 down 会 移除你用于管理它的路径，包括调试 API 本身。

本页有意不包含任何采集到的输出。采集工具会拒绝整个 Exec 层级，并且是从实时目录而非硬编码列表读取层级信息，因此即使未来 版本将其他命令提升到该层级，这一点仍然成立。