National Research and Education Network
Education Cloud Data Center
Multi-Channel HD Telemedicine Solution
Over The Top/Multi-Tenant Data Center (OTT/MTDC)
Internet Exchange Point (IXP)
Internet Access Provider (IAP)
Design & Simulation
Planning & Analytics
Oil & Gas IoT
HPC & Operations Management
Digital Urban Rail
Retail Cloud Platform
Enterprise Data Center
Enterprise Cloud Communications
Network Management System
Buy from Huawei
If you want to get more information about your project, you can submit your information and we will contact you as soon as possible.
If your company has signed an eDeal contract with Huawei, please buy your required product/solution via the link below.
Buy from resellers
Search for a nearby reseller and get direct contact information.
Become a Partner
Resources and Support
Huawei Authorized Learning Partner
Huawei Authorized Information and Network Academy
|ip community-filter 1 permit 6333:6333|
|route-policy EXAMPLE deny node 10 if-match community-filter 1|
|import-route bgp permit-ibgp route-policy EXAMPLE|
|display route-policy EXAMPLE|
|deny : 10 (matched counts: 0)|
|Match clauses: if-match community-filter 1|
When redistribute routes from bgp to OSPF, the community will not take effect.
Actually, while a route is redistributed into OSPF, it is not redistributed from bgp routing table directly, but from IP routing table.
The bgp routes are put into IP routing table first, then redistribute this routes from IP routing table to OSPF table. So it will loss the community attribute while put bgp routes into IP routing table.
Use ip-prefix to filter the routes while redistribute routes from bgp to OSPF. This limitation is not only for NE20E, but just a limitation of the VRP platform. So Huawei router and switch may have the same issue. The redistributed is from IP routing table, not from bgp routing table, so we can’t filter according to communities.