Huawei Reference Verification:
Huawei's carrier IP gateway design requires sufficient policy-processing scale, forwarding resources, routing-information transport capacity, and security controls. An Internet Gateway can receive large external BGP route sets, process prefix and community policies, and advertise selected reachable destinations into other parts of the backbone. Its interface bandwidth, routing-table resources, CPU and memory, and forwarding ASIC capacity must match expected demand. As a boundary between autonomous networks, it also requires routing filtering and defenses against harmful or unauthorized traffic. These are complementary responsibilities: a high packet throughput specification does not compensate for poor BGP scalability or insufficient security. All four proposed factors must be considered.
Technical Deep Dive:
A, B, C, and D are correct. Routing-policy scale covers BGP prefixes, filters, route preference, community and AS-path attributes, and traffic-engineering decisions. Hardware capacity includes interface rates, route and ACL table sizes, packet processing, control CPU, memory, and line-card traffic-management capability. Route transport capability covers BGP session scale, route propagation, policy operations, and convergence under network changes. Security requires route filtering, ingress antispoofing, management-plane access control, control-plane policing, and appropriate DDoS mitigation. On Huawei NetEngine platforms, NP/ASIC forwarding hardware performs FIB lookups, ACL matching, classification, and QoS handling, whereas the control-plane subsystem maintains BGP route state. Designers must size these subsystems independently. `display bgp peer`, `display bgp routing-table`, `display cpu-usage`, `display memory-usage`, and routing statistics can provide operational evidence. A good IGW design satisfies all four domains simultaneously rather than optimizing only raw bandwidth.
───────────────────────────────────────────────────────