> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cn/elastic-compute/instance-monitoring/03-network-drops.md).

# 网络层是否丢弃了我的数据包？

当请求无声无息地消失时，这些面板能在几秒内告诉您网络是否是责任方——如果是，是哪一层出了问题。

## IP 面板与 vNIC 面板

ZEC 为实例的网络流量提供两种不同的视角：

* **IP 面板**测量**南北向流量**——经由绑定到您实例的公网 IP 进出的字节数和数据包数。它们只统计通过该 IP 进出 ZEC 网络的流量，执行 IP 带宽配额的速率限制策略器也位于此层。
* **vNIC 面板**测量**虚拟网卡所能看到的全部流量**，以网卡视角为准。这包括南北向流量*以及*与 ZEC 内部其他实例、服务和私有端点之间的**东西向流量**——例如 VPC 流量、同区域内的服务调用等。IP 面板看不到此类流量。

一条实用规则：

* **仅 IP 面板出现丢包** → 几乎可以确定是您的 IP 带宽配额限制导致的。请提升 IP 带宽或平滑突发流量。
* **仅 vNIC 面板出现丢包** → 受影响的流量是内部流量，从未经过 IP 策略器。请与相关私有网络面板交叉核验，若丢包持续存在，请联系支持。
* **IP 面板和 vNIC 面板均出现丢包** → 流量为南北向，并触达了 IP 限制；vNIC 面板反映的是同一批丢包。

## IP Bandwidth — Inbound / Outbound drop bandwidth

## IP Packet Transmission — Inbound / Outbound packet loss

命中 IP 层并被数据平面丢弃的流量。此处的丢包几乎总是**带宽限制丢包**：您的流量超出了该 IP 的合约速率，策略器丢弃了突发部分。

当您在突发性工作负载（TCP 慢启动、突发扇入、批处理作业）上观察到请求丢失时，请首先检查此面板。如果这些面板显示有丢包，请提升 IP 带宽或平滑流量。如果这些面板显示正常，则问题在其他地方。

## IP Bandwidth — Inbound / Outbound

## IP Packet Transmission — Inbound / Outbound

该 IP 上的南北向总吞吐量。可用作上述丢包比率的分母，以及实例跨公网边界传输流量的总体视图。

## vNIC Bandwidth — Inbound / Outbound

## vNIC Packet Transmission — Inbound / Outbound

虚拟网卡处理的全部流量——南北向与东西向合并统计。方向以 Guest 视角为基准：**Inbound** 指 VM 接收到的流量。

如果 vNIC 带宽或数据包数量明显高于对应的 IP 数量，差值即为东西向流量。对于与同一 VPC 内其他实例通信的实例，这属于正常现象。

## vNIC Packet Transmission — Inbound / Outbound packet loss

## vNIC Packet Transmission — Inbound error

虚拟网卡层面的丢包或错误。正常运行时这些值应为零。若您发现非零值，请联系支持——这是基础设施侧的红色警报。

## API 参考

IP 指标使用 `DescribeEipMonitorData`；vNIC 指标使用 `DescribeInstanceMonitorData`。EIP API 在单次响应中同时返回吞吐量和丢包值（`in`、`out`、`loseIn`、`loseOut`）。

| Console 面板                                         | API                         | metricType   | 备注                                 |
| -------------------------------------------------- | --------------------------- | ------------ | ---------------------------------- |
| IP Bandwidth（Inbound / Outbound / Drops）           | DescribeEipMonitorData      | `BANDWIDTH`  | 响应包含 `in`、`out`、`loseIn`、`loseOut` |
| IP Packet Transmission（Inbound / Outbound / Drops） | DescribeEipMonitorData      | `PACKETS`    | 响应包含 `in`、`out`、`loseIn`、`loseOut` |
| vNIC Bandwidth — Inbound / Outbound                | —                           | —            | 仅 Console 可用                       |
| vNIC Packet Transmission — Inbound                 | DescribeInstanceMonitorData | `RX_PACKETS` |                                    |
| vNIC Packet Transmission — Outbound                | DescribeInstanceMonitorData | `TX_PACKETS` |                                    |
| vNIC Packet Transmission — Inbound packet loss     | DescribeInstanceMonitorData | `RX_DROPPED` |                                    |
| vNIC Packet Transmission — Outbound packet loss    | DescribeInstanceMonitorData | `TX_DROPPED` |                                    |
| vNIC Packet Transmission — Inbound error           | DescribeInstanceMonitorData | `RX_ERRORS`  |                                    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.console.zenlayer.com/welcome/cn/elastic-compute/instance-monitoring/03-network-drops.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.