How to monitor the Enterprise Router (ER) in Huawei Cloud
Site24x7 continuously monitors your Enterprise Router (ER) metrics, giving your team real-time visibility into instance-level traffic throughput, packet delivery rates, and drop events across both router instances and individual attachments.
Use cases
Routing resilience: Spikes in Drops indicate that traffic is being discarded due to missing or misconfigured routes. Alerting on these counters helps your team resolve routing gaps before entire application segments lose connectivity.
Attachment-level visibility: Tracking Attachment Traffic lets your team pinpoint which VPC, VPN, or direct link is overloaded. Rebalancing or resizing attachments helps prevent the router from becoming a bottleneck.
Capacity assurance: Inbound and Outbound Bit Rates give a continuous view of router utilization against provisioned capacity. Setting thresholds helps trigger proactive scaling before throughput limits degrade inter-VPC latency.
Setup and configuration
Enterprise Router resources are auto-discovered and monitored during the Huawei Cloud integration. To enable monitoring, follow the steps below:
- Navigate to Cloud > Huawei > Add Huawei Monitor. Follow these steps to add a Huawei Cloud monitor.
- While adding or editing a Huawei Cloud monitor, select ER from the Service/Resource Types drop-down and click Save.
- Navigate to Cloud > Huawei, select the created Huawei monitor, and then click Enterprise Router.
Supported metrics
Traffic
Metric name | Description | Units |
| Instance Inbound Bytes | Total bytes received by the Enterprise Router (ER) instance across all attachments in the monitoring period. | Byte |
| Instance Outbound Bytes | Total bytes transmitted by the ER instance across all attachments in the monitoring period. | Byte |
| Attachment Inbound Bytes | Total bytes received through a specific attachment connected to the ER. | Byte |
| Attachment Outbound Bytes | Total bytes transmitted through a specific attachment connected to the ER. | Byte |
Network
Metric name | Description | Units |
| Instance Inbound Bits Rate | Rate of bits received by the ER instance per second, reflecting overall ingress throughput. | Bit/second |
| Instance Outbound Bits Rate | Rate of bits transmitted by the ER instance per second, reflecting overall egress throughput. | Bit/second |
| Instance Inbound Packets | Total number of packets received by the ER instance in the monitoring period. | Count |
| Instance Outbound Packets | Total number of packets transmitted by the ER instance in the monitoring period. | Count |
| Attachment Inbound Bits Rate | Rate of bits received through a specific attachment per second. | Bit/second |
| Attachment Outbound Bits Rate | Rate of bits transmitted through a specific attachment per second. | Bit/second |
| Attachment Inbound Packets | Total packets received through a specific attachment in the monitoring period. | Packet/second |
| Attachment Outbound Packets | Total packets transmitted through a specific attachment in the monitoring period. | Packet/second |
Drops
Metric name | Description | Units |
| Instance Blackhole Dropped Packets | Number of packets dropped at the instance level because they matched a blackhole route entry. | Count |
| Instance No-Route Dropped Packets | Number of packets dropped at the instance level because no matching route was found in the routing table. | Count |
Attachment Traffic
Metric name | Description | Units |
| Attachment Inbound Bytes | Total bytes received through a specific attachment in the monitoring interval, providing per-attachment ingress volume. | Byte |
| Attachment Outbound Bytes | Total bytes transmitted through a specific attachment in the monitoring interval, providing per-attachment egress volume. | Byte |
Attachment Network
Metric name | Description | Units |
| Attachment Inbound Bits Rate | Rate of bits per second received through a specific attachment, reflecting real-time ingress load on that connection. | Bit/second |
| Attachment Outbound Bits Rate | Rate of bits per second transmitted through a specific attachment, reflecting real-time egress load on that connection. | Bit/second |
| Attachment Inbound Packets | Total packets received through a specific attachment, useful for comparing packet counts against byte volumes. | Count |
| Attachment Outbound Packets | Total packets transmitted through a specific attachment in the monitoring period. | Count |
Attachment Drops
Metric name | Description | Units |
| Attachment Blackhole Dropped Packets | Number of packets dropped on a specific attachment because they matched a blackhole route. | Count |
| Attachment No-Route Dropped Packets | Number of packets dropped on a specific attachment because no route was available to forward them. | Count |
Threshold configuration
You can configure thresholds and alerts for all ER metrics to proactively detect performance degradation and connection issues.
Go to Admin > Configuration Profiles > Threshold and Availability to create or modify your alert profiles.
IT Automation
Use Site24x7's IT Automation to resolve common issues with ER performance automatically:
- Go to Admin > IT Automation Templates. Then, click Add Automation Templates.
- Create an automation rule by selecting the automation Type (e.g., Server reboot, clear queue).
- Map the created rules to the ER monitor for automatic execution during alerts.
Configuration rules
Use Configuration Rules to simplify bulk setup across ER instances. Automatically assign Threshold Profiles, Notification Profiles, Tags, and Monitor Groups when new monitors are discovered.