Transform the format of multi-level hybrid hierarchical forwarding information base

Abstract

Embodiments of the present disclosure relate to transforming a multi-level hybrid hierarchical forwarding information base format. A network device may receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device. The network device may process the forwarding data to generate a first set of transformed forwarding next hop entries. The network device may process the first set of transformed forwarding next hop entries associated with a default forwarding class to generate a second set of transformed forwarding next hop entries. The network device may process the first set of transformed forwarding next hop entries associated with all service classes to generate a third set of transformed forwarding next hop entries. The network device may aggregate multiple sets of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries. The network device may transform the final set of transformed forwarding next hop entries into a specific format.

Description

[0001] This application is a divisional application of the invention patent application with Chinese national application number 202010849397.7, application date August 21, 2020, and invention name “Transforming the Format of Multi-level Hybrid Hierarchical Forwarding Information Base”. Background Art

[0002] A forwarding information base (FIB) may be a data structure that includes forwarding data, such as information identifying a destination, information identifying the next hop in a route to the destination, etc. A network device may perform a lookup in the FIB to identify the forwarding data and use the forwarding data to forward a packet to the destination. Summary of the Invention

[0003] According to some implementations, a method may include: receiving, by a network device, forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; processing, by the network device, the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing, by the network device, the first set of transformed group next hop entries and transformed forwarding next hop entries associated with a default forwarding category to generate a second set of transformed forwarding next hop entries; processing, by the network device, the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all service categories to generate a third set of transformed forwarding next hop entries; aggregating, by the network device, the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; converting, by the network device, the final set of transformed forwarding next hop entries into a specific format; and storing, by the network device, the final set of transformed forwarding next hop entries in the specific format in the forwarding information base.

[0004] According to some implementations, a network device may include one or more memories and one or more processors. In some implementations, the one or more processors are communicatively coupled to the one or more memories. The one or more processors may be configured to: receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; process the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with a default forwarding class to generate a second set of transformed forwarding next hop entries; process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries; aggregate the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; transform the final set of transformed forwarding next hop entries into a specific format; receive traffic associated with the network; and forward the traffic based on the final set of transformed forwarding next hop entries in the specific format.

[0005] According to some implementations, a non-transitory computer-readable medium may store one or more instructions. The one or more instructions, when executed by one or more processors of a network device, may cause the one or more processors to: receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; process the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with a default forwarding class to generate a second set of transformed forwarding next hop entries; process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all service classes to generate a third set of transformed forwarding next hop entries; aggregate the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; transform the final set of transformed forwarding next hop entries into a specific format; store the final set of transformed forwarding next hop entries in the specific format in a forwarding information base; receive services associated with a network; and forward the services based on the final set of transformed forwarding next hop entries in the specific format. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figures 1A to 1L is a schematic diagram of one or more example implementations described herein.

[0007] Figure 2 is a schematic diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0008] Figure 3 yes Figure 2 A schematic diagram of example components of one or more devices.

[0009] Figure 4 yes Figure 2 A schematic diagram of example components of one or more devices.

[0010] Figures 5 to 7 is a flow chart of an example process associated with converting a multi-level hybrid hierarchical forwarding information base (FIB) format. DETAILED DESCRIPTION

[0011] The following detailed description of example implementations refers to the accompanying drawings, in which the same reference numbers in different drawings may identify the same or similar elements.

[0012] The FIB on a network device can store forwarding data associated with a large number of destinations (e.g., approximately millions). The FIB can be a hierarchical FIB comprising multiple levels. Incoming traffic received by the network device can be classified into different forwarding classes. Incoming traffic can be routed to different outbound interfaces at different levels in the hierarchy. The network device can distribute traffic (e.g., make load sharing decisions) at different levels in the hierarchy.

[0013] In some hierarchical FIBs (such as multi-level hybrid hierarchical FIBs), one or more sub-hierarchies may exist. A particular sub-hierarchy may be configured to handle a particular forwarding class of incoming traffic (e.g., different sub-hierarchies may be configured to handle different forwarding classes), a particular sub-hierarchy may be configured without a forwarding class configuration, and so on. As a result, because a particular sub-hierarchy of the FIB may not be able to identify traffic distribution for all forwarding classes for traffic to be forwarded via routing, the network device may not be able to determine traffic distribution across outbound interfaces of the network device for routing. This may waste computing resources (e.g., processing resources, memory resources, etc.), networking resources, etc. associated with determining traffic distribution across outbound interfaces of the network device when using such a multi-level hybrid hierarchical FIB.

[0014] Some implementations described herein enable network devices to transform multi-level hybrid hierarchical FIB formats. For example, a network device can process forwarding data associated with a multi-level hybrid hierarchical structure FIB of the network device to generate a set of transformed group next hop entries and / or transformed forwarding next hop entries. The network device can process the set of transformed group next hop entries and / or transformed forwarding next hop entries to generate one or more additional sets of transformed forwarding next hop entries (e.g., including one or more missing transformed next hop entries from the set of transformed forwarding next hop entries, one or more new transformed next hop entries in the set of transformed forwarding next hop entries, etc.). The set of transformed forwarding next hop entries can be aggregated based on the transformed group next hop entries (e.g., based on the forwarding class associated with the transformed forwarding next hop entries) to form a final set of transformed forwarding next hop entries. The network device can transform the final set of transformed forwarding next hop entries into a specific format (e.g., the specific format is configured to represent all business distributions for all forwarding classes).

[0015] The network device can receive traffic and can forward the traffic based on the final set of transformed forwarding next hop entries in a specific format. As a result, the network device can be enabled to determine traffic distribution across outbound interfaces for all traffic forwarding classes associated with the network. This can save computing resources and / or network resources that would otherwise be used to determine traffic distribution for a given destination and a specific forwarding class using a multi-level hybrid hierarchical FIB format (e.g., which may not include complete traffic distribution for all forwarding classes of the destination).

[0016] Figures 1A to 1L FIG. 1 is a diagram of one or more examples 100 associated with determining traffic distribution in a hybrid hierarchical forwarding information base (FIB). Figures 1A to 1L As shown in , example 100 includes one or more endpoint devices and one or more network devices communicating via a network.

[0017] like Figure 1A As shown in , a network device in one or more network devices may include a FIB for storing forwarding data for multiple destinations (such as an endpoint device, another network device, etc.). The FIB may be a data structure that stores forwarding data associated with one or more destinations in a network, in another network, etc. The forwarding data associated with a destination may include information identifying an address of the destination (e.g., an Internet Protocol (IP) address, a port address, etc.), information identifying a next hop in a route to the destination, information identifying an interface associated with the destination (e.g., a Media Access Control (MAC) identifier), etc. The destination may be an endpoint device, another network device, etc.

[0018] A network device may receive, process, and / or transmit packets. The packets may be data plane packets (e.g., packets that travel through the network device and do not originate or terminate at the network device), control plane packets (e.g., packets that originate in the control plane of the network device (e.g., generated by the network device) or terminate in the control plane of the network device (e.g., the network device is the destination of the packet), etc. The network device may receive the packet, perform a lookup in a FIB on the network device to identify forwarding data associated with the packet (e.g., information identifying the destination of the packet, information identifying the next hop in a route to the destination, etc.), and transmit the packet to the next hop based on the forwarding data.

[0019] The network device may populate and maintain forwarding data in the FIB based on various techniques. For example, the network device may learn routes and / or updates to routes in the network based on one or more routing protocols (such as Routing Information Protocol (RIP), Open Shortest Path First (OSPF) protocol, Border Gateway Protocol (BGP), Interior Gateway Routing Protocol (IGRP), Enhanced IGRP (EIGRP), Distance-Vector routing protocol, Intermediate System to Intermediate System Protocol (IS-IS) protocol, etc.), and may store information identifying the routes and / or updates to the routes as forwarding data in the FIB. In some implementations, the FIB may be populated with static forwarding data, which may be forwarding data configured and / or maintained by a user (such as a network administrator).

[0020] A network device and / or FIB may include one or more classifier tables for determining a forwarding class for packets received by the network device. A forwarding class may be a group and / or identifier assigned to an incoming packet based on one or more parameters of the incoming packet (e.g., packet code point value, etc.). A forwarding class may enable the network device to aggregate packets into different classifications, which may then be used to define per-hop behaviors (PHBs), assign packets to output queues for transmission, and the like. A forwarding class may enable the network device to aggregate packets for transmission and assign packets to one or more output queues. A forwarding class may identify a priority for the packet, a delivery protocol for the packet (e.g., best effort delivery, etc.), and the like. The network device may determine the forwarding class of a packet by identifying an entry in the packet's header (e.g., a Differentiated Services Code Point (DSCP) entry, a Type of Service (ToS) entry, etc.). The network device may (e.g., using a lookup operation) identify an entry in the classifier table (corresponding to an entry in the packet's header) that identifies the forwarding class (e.g., the classifier table may associate an entry in the packet's header with a forwarding class). The network device and / or the FIB may include a classifier table associated with a particular incoming interface, a particular destination, etc. As described above, upon receiving a packet, the network device may determine a forwarding class associated with the packet. The network device may generate forwarding class information (e.g., indicating the forwarding class) and may include the forwarding class information within the packet (e.g., within a header of the packet).

[0021] Incoming packets for a network device may be segmented into multiple paths for routing at different levels of the FIB hierarchy. For example, the network device may determine, based on forwarding data stored in the FIB, to isolate outgoing paths based on the packet's forwarding class. In some implementations, a particular hierarchy of the FIB may be configured to handle a subset of all forwarding classes, or a particular hierarchy of the FIB may be configured without a forwarding class-based forwarding protocol. For example, the FIB may have a hybrid hierarchical FIB format (e.g., including a hybrid class-based forwarding hierarchy).

[0022] like Figure 1BAs shown in , an example hybrid hierarchical FIB format may include forwarding data associated with a route to a destination. For example, the FIB may store forwarding data associated with a destination prefix (e.g., an IP route such as 1.1.11.4 / 32) associated with a route (e.g., route R1). The forwarding data may identify a top-level next hop (e.g., unilist1) associated with the route prefix, which is the first next hop associated with the route. The forwarding data may identify one or more types of forwarding next hops (e.g., for other network devices or network entities) for the route. The one or more types of forwarding next hops may include an aggregate next hop, an indirect next hop, an indexed next hop, a forwarding next hop, etc.

[0023] The aggregate next hop may be an equal cost multi-path (ECMP) next hop. The aggregate next hop may identify one or more next hops (e.g., the next hop after the aggregate next hop). The paths to one or more next hops from the aggregate next hop may be associated with one or more parameters (e.g., weight, balance, etc.). The weight parameter may identify the priority of the path (e.g., the lowest weight value may identify the primary path, a higher weight value may identify a backup or inactive path, etc.). The balance parameter may identify the load balancing to be applied to traffic between paths with the same weight (e.g., a balance value of 30 associated with a path may indicate that 30% of the traffic from the aggregate next hop should be transmitted via the path). The sum of the balance parameters of all paths from the aggregate next hop may be equal to the total traffic balance entering the aggregate next hop (e.g., if the traffic balance entering the aggregate next hop is 100, then the sum of the balance parameters of all paths from the aggregate next hop may be 100).

[0024] An indirect next hop may identify an indirect next hop for forwarding data (e.g., from an indirect next hop to an aggregate next hop, an indexed next hop, etc.). An indirect next hop may be common to multiple routes. An indexed next hop may identify one or more paths from the indexed next hop to the forwarding next hop. A path in the one or more paths may be associated with a forwarding class. For example, forwarding data may identify three paths from the indexed next hop to three forwarding next hops. A first path may be associated with a first forwarding class, a second path may be associated with a second forwarding class, and a third path may be associated with the remaining forwarding classes (e.g., all other forwarding classes other than the first and second forwarding classes). A forwarding next hop may be associated with an outbound interface of a network device (e.g., associated with a destination of a service). For example, a forwarding next hop may be associated with a unicast transmission (e.g., a one-to-one transmission) to a destination. A forwarding next hop may be associated with an outbound calculation weight. The outbound calculation weight may indicate a traffic balance associated with the forwarding next hop and / or the corresponding outbound interface (e.g., may indicate a percentage or ratio of traffic to be distributed to the forwarding next hop).

[0025] For example, Figure 1B As shown in , an example multi-level hybrid hierarchical FIB format may include forwarding data for a primary path of route R1 that identifies a top-level next hop (e.g., unilist1). The forwarding data may identify three indirect next hops (e.g., indirect1, indirect2, and indirect3) after the top-level next hop. The forwarding data may identify that the path from unilist1 to indirect1 has a balance of 30 (e.g., indicating that 30% of the traffic from unilist1 is associated with the path), the path from unilist1 to indirect2 has a balance of 30 (e.g., indicating that 30% of the traffic from unilist1 is associated with the path), and the path from unilist1 to indirect3 has a balance of 40 (e.g., indicating that 40% of the traffic from unilist1 is associated with the path).

[0026] The forwarding data may identify that traffic from indirect1 should be forwarded to unilist2. Since unilist2 may be an aggregate next hop, unilist2 may split the traffic equally into different paths from unilist2 to the forwarding next hop (e.g., unicast1 and unicast2) (e.g., a balance of 50 for each path). In some implementations, the split of traffic between unicast1 and unicast2 may not be equal (e.g., where a different balance is indicated by the forwarding data). Since the balance of traffic entering unilist2 is 30, the outgoing calculated weight of the path from unilist2 to unicast1 may be 15 (e.g., 50% of 30), and the outgoing calculated weight of the path from unilist2 to unicast2 may be 15 (e.g., a total of 30 between the two paths). Paths from unilist2 may not be eligible for class-based forwarding. That is, paths from unilist2 may not be associated with any particular forwarding class (e.g., paths may be used for all forwarding classes).

[0027] The forwarding data may identify that traffic from indirect2 should be sent to indexed1. The forwarding data may identify that paths from indexed1 to forwarding next hops (e.g., unicast3, unicast4, and unicast5) are associated with particular forwarding classes. For example, the path from indexed1 to unicast3 may be associated with a first forwarding class (e.g., FC 0), the path from indexed1 to unicast4 may be associated with a second forwarding class (e.g., FC 1), and the path from indexed1 to unicast5 may be associated with a default forwarding class (e.g., all forwarding classes not specifically identified by indexed1). Paths from indexed1 may be associated with the same balance as traffic entering indexed1 (e.g., each of the three paths from indexed1 may be associated with an outgoing computation weight of 30).

[0028] Forwarding data may identify that traffic from indirect3 should be sent to indexed3. Forwarding data may identify that paths from indexed3 to forwarding next hops (e.g., unicast6, unicast7, and unicast8) are associated with particular forwarding classes. For example, the path from indexed2 to unicast6 may be associated with a first forwarding class (e.g., FC 0), the path from indexed2 to unicast7 may be associated with a third forwarding class (e.g., FC 2), and the path from indexed1 to unicast5 may be associated with a default forwarding class (e.g., all forwarding classes not specifically identified by indexed2). Paths from indexed2 may be associated with the same balance as traffic entering indexed2 (e.g., each of the three paths from indexed2 may be associated with an outgoing computation weight of 40).

[0029] In some implementations, forwarded data may be identified in Figure 1B One or more additional paths not shown in the . Additional paths may be associated with backup or inactive paths (e.g., forwarding data may identify additional paths with weights greater than 10). An example multi-level hybrid hierarchical FIB format may be hybrid because the FIB includes class-based forwarding (e.g., from an indexed next hop) and non-class-based forwarding (e.g., from an aggregate next hop, such as unilist2). The multi-level hybrid hierarchical FIB format may include four levels (e.g., unilist1 at the first level; indirect1, indirect2, and indirect3 at the second level; unilist2, indexed1, and indexed2 at the third level; and unicast1 through unicast8 at the fourth level). In some implementations, the multi-level hybrid hierarchical FIB format may include more or less than four levels.

[0030] like Figure 1C As shown by reference numeral 105, the network device can receive and store information related to the multi-level hybrid hierarchical structure FIB (such as the above with respect to Figure 1B The network device may process the forwarding data associated with the multi-level hybrid hierarchy FIB described above. As shown by reference numeral 110, the network device may process the forwarding data to identify a top-level next hop entry, create a conditionally transitioned group next hop (CTGNH) entry, and generate a transitioned group next hop entry (TGs) and a transitioned forwarding next hop entry (Ts). As described above, the forwarding data for route R1 may identify that the top-level next hop entry is unilist1. The conditionally transitioned group next hop entry may be based on the identified top-level next hop entry (e.g., the conditionally transitioned group next hop entry may be the identified top-level next hop entry).

[0031] The transformed group next hop entry may identify one or more transformed forwarding next hop entries. The transformed group next hop entry may include one or more transformed forwarding next hop entries associated with the same forwarding class. For example, a first transformed group next hop entry may include one or more transformed forwarding next hop entries associated with a first forwarding class (e.g., FC 0), a second transformed group next hop entry may include one or more transformed forwarding next hop entries associated with a second forwarding class (e.g., FC 1), and so on.

[0032] The transformed forwarding next hop entry may identify an outgoing calculation weight, forwarding class, outbound interface, and / or other forwarding information (eg, one or more next hops from the top-level next hop to the forwarding next hop). For example, the transformed forwarding next hop entry may be a path associated with route R1.

[0033] The network device can process the forwarding data based on the type of the forwarding next hop identified in the forwarding data. For example, if the type of the forwarding next hop is an indirect next hop, the network device can process the forwarding data to identify the next entry after the indirect next hop in the forwarding data. If the type of the forwarding next hop is an indexed next hop, the network device can determine one or more sub-next hops (e.g., the next hop after the indexed next hop). The network device can determine the forwarding class associated with the path from the indexed next hop to (multiple) sub-next hops. The network device can determine one or more forwarding classes associated with the default forwarding class of the indexed next hop (e.g., the network device can determine one or more forwarding classes that the indexed next hop is not explicitly configured to process). If the type of the forwarding next hop is a forwarding next hop, the network device can create a transformed forwarding next hop associated with the forwarding next hop.

[0034] For example, the network device may process forwarding data associated with a first type of next hop (e.g., an aggregate next hop) to generate a first subset of transformed forwarding next hop entries. The network device may process forwarding data associated with a second type of next hop (e.g., an indirect next hop) to generate a second subset of transformed forwarding next hop entries. The network device may process forwarding data associated with a third type of next hop (e.g., an indexed next hop) to generate a third subset of transformed forwarding next hop entries. The network device may process forwarding data associated with a fourth type of next hop (e.g., a forwarding next hop) to generate a fourth subset of transformed forwarding next hop entries. The network device may combine the first subset of transformed forwarding next hop entries, the second subset of transformed forwarding next hop entries, the third subset of transformed forwarding next hop entries, and the fourth subset of transformed forwarding next hop entries to generate a first set of transformed forwarding next hop entries. The first set of transformed forwarding next hop entries may identify a next hop that is associated with an outbound interface (e.g., an interface that is not an outbound interface). Figure 1B As shown in , for each next hop associated with the path of the forwarding next hop or unicast, the transformed forwarding next hop entry can be associated with the corresponding outbound interface of the network device.

[0035] like Figure 1D As shown in , the first set of transformed forwarding next hop entries may include: T4 (e.g., associated with unicast1), T8 (e.g., associated with unicast2), T9 (e.g., associated with unicast3), T10 (e.g., associated with unicast4), T12 (e.g., associated with unicast5), T13 (e.g., associated with unicast6), T14 (e.g., associated with unicast7), and T16 (e.g., associated with unicast8). The transformed forwarding next hop entries may identify associated paths. For example, T4 may identify a path from unilist1 to indirect1 to unilist2 to unicast1, T10 may identify a path from unilist1 to indirect2 to indexed1 to unicast4, and so on. The transformed forwarding next hop entries may identify associated outgoing calculation weights. For example, T4 may identify an outgoing calculation weight of 15, T10 may identify an outgoing calculation weight of 30, T14 may identify an outgoing calculation weight of 40, and so on. The transformed forwarding next hop entries may identify associated forwarding classes. For example, T4 may identify all forwarding classes associated with T4, T9 may identify the associated forwarding class of FC 0, T10 may identify the associated forwarding class of FC 1, T14 may identify the associated forwarding class of FC 2, and so on.

[0036] The converted group next hop entries may include a first converted group next hop entry associated with a first forwarding class (e.g., FC 0), a second converted group next hop entry associated with a second forwarding class (e.g., FC 1), a third converted group next hop entry associated with a third forwarding class (e.g., FC 2), a fourth converted group next hop entry associated with a default forwarding class (e.g., FCD), and so on. The first converted group next hop entry may include one or more converted forwarding next hop entries associated with the first forwarding class (e.g., T9 and T13). The second converted group next hop entry may include one or more converted forwarding next hop entries associated with the second forwarding class (e.g., T10). The third converted group next hop entry may include one or more converted forwarding next hop entries associated with the third forwarding class (e.g., T14). The fourth converted group next hop entry may include one or more converted forwarding next hop entries associated with the default forwarding class (e.g., T12 and T16). T4 and T8 may not be included in the converted group next hop entries because they may not be associated with a specific forwarding class.

[0037] like Figure 1EAs shown by reference numeral 115, the network device may process the transformed group next hop entry and the transformed forwarding next hop entry associated with the default forwarding class to generate the missing transformed forwarding next hop entry. For example, the network device may determine the forwarding class associated with the default forwarding class. The network device may compare the transformed forwarding next hop entries associated with the indexed next hop entries to determine the missing forwarding class. For example, the network device may identify T9 and T10 associated with indexed1. The network device may determine that T9 is associated with the first forwarding class (e.g., FC0) and T10 is associated with the second forwarding class (e.g., FC1). The network device may determine that the transformed forwarding next hop entry associated with indexed1 and the third forwarding class (e.g., FC2) is missing. As a result, the network device may generate a transformed forwarding next hop entry associated with indexed1 and the third forwarding class, the transformed forwarding next hop entry associated with indexed1 and the third forwarding class having the same forwarding information as the transformed forwarding next hop entry associated with indexed1 and the default forwarding class (e.g., T12). Similarly, the network device may determine that a transitioned forwarding next hop entry associated with indexed2 and a second forwarding class (e.g., FC 1) is missing. As a result, the network device may generate a transitioned forwarding next hop entry associated with indexed2 and a second forwarding class, the transitioned forwarding next hop entry associated with indexed2 and a second forwarding class having the same forwarding information as a transitioned forwarding next hop entry associated with indexed2 and a default forwarding class (e.g., T16).

[0038] like Figure 1F As shown in , the network device can determine a second set of transformed forwarding next hop entries. The second set of transformed forwarding next hop entries can include missing transformed forwarding next hop entries (e.g., T11 and T15). The network device can update the transformed group next hop entries based on the second set of transformed forwarding next hop entries. For example, the network device can add T11 to a third transformed group next hop entry (e.g., associated with a third forwarding class) and can add T15 to a second transformed group next hop entry (e.g., associated with a second forwarding class).

[0039] like Figure 1GAs shown by reference numeral 120, the network device can process the transformed group next hop entries and the transformed forwarding next hop entries associated with all business classes to generate new transformed forwarding next hop entries. For example, the network device can process the transformed forwarding next hop entries associated with the aggregate next hop (e.g., unilist2, etc.). The network device can generate a new transformed forwarding next hop entry for each forwarding class, and the new transformed forwarding next hop entry has the same forwarding information as the transformed forwarding next hop entry associated with all business classes. For example, the network device can generate a new transformed forwarding next hop entry by transforming T4 into four new transformed forwarding next hop entries, and the four new transformed forwarding next hop entries have the same forwarding information as T4, but are associated with a specific forwarding class. Similarly, the network device can generate a new transformed forwarding next hop entry by transforming T8 into four new transformed forwarding next hop entries. The number of new transformed forwarding next hop entries can be based on the number of forwarding classes.

[0040] like Figure 1H As shown in , the network device can determine a third set of transformed forwarding next hop entries. The third set of transformed forwarding next hop entries can include new transformed forwarding next hop entries. For example, the new transformed forwarding next hop entries can include T1 (e.g., associated with unicast1 and the first forwarding class), T2 (e.g., associated with unicast1 and the second forwarding class), T3 (e.g., associated with unicast1 and the second forwarding class), T4 (e.g., associated with unicast1 and the default forwarding class), T5 (e.g., associated with unicast2 and the first forwarding class), T6 (e.g., associated with unicast2 and the second forwarding class), T7 (e.g., associated with unicast2 and the third forwarding class), and T8 (e.g., associated with unicast2 and the default forwarding class). The network device can create a final set of transformed forwarding next hop entries, the final set of transformed forwarding next hop entries including all transformed forwarding next hop entries (e.g., T1 to T16) from the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries.

[0041] The network device may update the transitioned group next hop entries based on the third set of transitioned forwarding next hop entries. For example, the network device may add T1 and T5 to a first transitioned group next hop entry (e.g., associated with a first forwarding class), add T2 and T6 to a second transitioned group next hop entry (e.g., associated with a second forwarding class), add T3 and T7 to a third transitioned group next hop entry (e.g., associated with a third forwarding class), and add T4 and T8 to a fourth transitioned group next hop entry (e.g., associated with a default forwarding class).

[0042] As a result, the final set of transformed forwarding next hop entries may include a first subset of transformed forwarding next hop entries associated with a first forwarding category (e.g., FC 0) and a first entry in the transformed group next hop entries (e.g., a first transformed group next hop entry); a second subset of transformed forwarding next hop entries associated with a second forwarding category (e.g., FC 1) and a second entry in the transformed group next hop entries (e.g., a second transformed group next hop entry); a third subset of transformed forwarding next hop entries associated with a third forwarding category (e.g., FC 2) and a third entry in the transformed group next hop entries (e.g., a third transformed group next hop entry); and a fourth subset of transformed forwarding next hop entries associated with a fourth forwarding category (e.g., a default forwarding category) and a fourth entry in the transformed group next hop entries (e.g., a fourth transformed group next hop entry).

[0043] like Figure 1I As shown by reference numeral 125, the network device may aggregate the converted forwarding next hop entries (e.g., the first set of converted forwarding next hop entries), the missing converted forwarding next hop entries (e.g., the second set of converted forwarding next hop entries), and the new converted forwarding next hop entries (e.g., the third set of converted forwarding next hop entries) based on the converted group next hop entries. For example, the network device may aggregate the converted forwarding next hop entries included in the final set of converted forwarding next hop entries based on the converted group next hop entries (e.g., based on the forwarding class of each converted group next hop entry).

[0044] like Figure 1J As shown in Figures 1A to 1HThe multi-level hybrid hierarchical structure FIB format (e.g., a multi-level hybrid hierarchical structure FIB format with four levels (or more)) is converted into a three-level hierarchical structure FIB format. The three levels may include a group next hop level after the conditional transition (e.g., a group next hop entry indicating the conditional transition), a group next hop level after the transition (e.g., a group next hop entry indicating the transition), and a forwarding next hop level after the transition (e.g., a forwarding next hop entry indicating the transition). The forwarding next hop entry after the transition may be aggregated by the associated group next hop entry after the transition and / or the associated forwarding class. For example, the three-level hierarchical structure FIB format may indicate a path from the group next hop after the conditional transition to the first group next hop after the transition (e.g., TG1) and a path to each of the forwarding next hop entries after the transition associated with the first group next hop after the transition (e.g., T1, T5, T9, and T13). The three-level hierarchical structure FIB format may indicate an outgoing calculation weight associated with the path from the group next hop after the first transition to the associated forwarding next hop after the transition. For example, the egress calculation weight of the path from the first post-transition group next hop to the transitioned forwarding next hop T1 may be 15, the egress calculation weight of the path from the first post-transition group next hop to the transitioned forwarding next hop T5 may be 15, the egress calculation weight of the path from the first post-transition group next hop to the transitioned forwarding next hop T9 may be 30, and the egress calculation weight of the path from the first post-transition group next hop to the transitioned forwarding next hop T13 may be 40. The sum of the egress calculation weights of the paths from the first post-transition group next hop may be 100 (e.g., indicating that the paths from the first post-transition group next hop include all potential paths for traffic associated with the first forwarding class (e.g., F0)).

[0045] As a result, the network device can arrange the three-level hierarchical FIB format so that the distribution of traffic through the network to the corresponding outbound interface can be determined for all forwarding classes. For example, for the second forwarding class (e.g., FC 1), the three-level hierarchical FIB format can indicate that 15% of the traffic associated with the second forwarding class (e.g., indicated by an outgoing calculation weight of 15) can be distributed via the transformed forwarding next hop T2, 15% of the traffic associated with the second forwarding class (e.g., indicated by an outgoing calculation weight of 15) can be distributed via the transformed forwarding next hop T6, 30% of the traffic associated with the second forwarding class (e.g., indicated by an outgoing calculation weight of 30) can be distributed via the transformed forwarding next hop T10, and 40% of the traffic associated with the second forwarding class (e.g., indicated by an outgoing calculation weight of 40) can be distributed via the transformed forwarding next hop T15. Similarly, incoming traffic associated with a third forwarding class (e.g., FC2) can be distributed across the outbound interfaces corresponding to the converted forwarding next hop T3, the converted forwarding next hop T7, the converted forwarding next hop T11, and the converted forwarding next hop T14, respectively, with ratios of 15, 15, 30, and 40. The network device can determine traffic distribution for other forwarding classes in a similar manner.

[0046] like Figure 1K As shown by reference numeral 130 in the figure, the network device may transform the aggregated transformed forwarding next hop entries into a specific format. The specific format may be a three-level hierarchical address forwarding table format, an openconfig address forwarding table format (OC-AFT), etc. The specific format may include a conditional identifier that defines an ingress classification criterion to be applied to a packet received by the network device. For example, when a packet is received by a network device, the network device may include a conditional identifier with the packet (e.g., in a header of the packet). The network device may determine the conditional identifier based on forwarding data, information received from another network device, information contained in a packet received by the network device, information stored in a FIB, etc. The conditional identifier may be used by the network device and / or other network devices to determine a distribution (e.g., a path) for the packet.

[0047] like Figure 1LAs shown in , the network device can associate a path from the conditionally transitioned group next hop to one or more (or all) transitioned group next hops with one or more condition identifiers. For example, condition identifiers 44, 45, and 46 can be associated with the first transitioned group next hop (e.g., TG1), condition identifiers 47, 48, and 49 can be associated with the second transitioned group next hop (e.g., TG2), condition identifiers 50, 51, and 52 can be associated with the third transitioned group next hop (e.g., TG3), and condition identifier 53 can be associated with the fourth transitioned group next hop (e.g., TG4).

[0048] The network device may perform the processing of the forwarding data as described above based on a configuration (e.g., settings, etc.) of the network device. For example, the configuration may indicate that the network device is to convert forwarding data associated with the multi-level hybrid hierarchy FIB format. In some implementations, the network device may selectively perform the processing of the forwarding data based on an indication in the forwarding data, based on a configuration, based on user input (e.g., from a network administrator), etc.

[0049] The network device can send data in a specific format (e.g. Figure 1L The transformed forwarding next hop entry (shown in ) is stored in the FIB of the network device. The network device can receive traffic (e.g., packets) associated with the network. The network device can forward traffic based on the transformed forwarding next hop entry in a specific format. For example, the network device can determine a forwarding class and / or condition identifier associated with the traffic. The network device may include a forwarding class and / or a condition identifier (e.g., in a header of a packet) with the traffic. The network device can forward traffic according to the distribution indicated by the transformed forwarding next hop entry in a specific format. The network device can expose the transformed forwarding next hop entry in a specific format to one or more other devices (e.g., one or more other network devices, etc.) for use consumption purposes (e.g., for monitoring via telemetry).

[0050] As a result, a network device can be enabled to determine traffic distribution across outbound interfaces for all traffic forwarding classes associated with the network. A network device can be enabled to track traffic distribution for a given destination and a specific forwarding class of traffic. This can save computing resources and / or network resources that would otherwise be used to determine traffic distribution for a given destination and a specific forwarding class using a multi-level hybrid hierarchical FIB format (e.g., which may not include a complete traffic distribution for all forwarding classes of a destination).

[0051] As indicated above, Figures 1A to 1L are provided as examples. Other examples may be related to Figures 1A to 1L The examples described are different. Figures 1A to 1L The number and arrangement of the devices shown in are provided as examples. Figures 1A to 1L There may be additional devices, fewer devices, different devices, or devices arranged differently than those shown in FIG. Figures 1A to 1L Two or more of the devices shown in FIG may be implemented in a single device, or Figures 1A to 1L The single device shown in can be implemented as multiple distributed devices. Additionally or alternatively, Figures 1A to 1L A set of devices (e.g., one or more devices) shown in FIG. 1 may perform the operations described as being performed by Figures 1A to 1L One or more functions performed by another group of devices shown in .

[0052] Figure 2 FIG is a diagram of an example environment 200 in which the systems and / or methods described herein may be implemented. Figure 2 As shown in , environment 200 may include one or more endpoint devices 210, a set of network devices 220 (shown as network device 220-1 through network device 220-N), and a network 230. The devices of environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0053] Endpoint device 210 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as the information described herein). For example, endpoint device 210 may include a mobile phone (e.g., a smartphone, a wireless phone, etc.), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smartwatch, a pair of smart glasses, a heart rate monitor, a fitness tracker, smart clothing, smart jewelry, a head-mounted display, etc.), a network device, or a similar type of device. In some implementations, endpoint device 210 may receive network traffic from other endpoint devices 210 via network 230 and / or may provide network traffic to other endpoint devices 210 via network 230 (e.g., by using network device 220 as an intermediary to route packets).

[0054] The network device 220 includes one or more devices capable of receiving, processing, storing, routing, and / or providing services (e.g., packets, other information, or metadata, etc.) in the manner described herein. For example, the network device 220 may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router, a provider core router, etc.), a virtual router, etc. Additionally or alternatively, the network device 220 may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, a data center server, etc.), a load balancer, and / or the like. In some implementations, the network device 220 may be a physical device implemented within a housing (such as a rack). In some implementations, the network device 220 may be a virtual device implemented by one or more computer devices in a cloud computing environment or a data center. In some implementations, a group of network devices 220 may be a group of data center nodes for routing traffic flows through the network 230.

[0055] The network 230 includes one or more wired and / or wireless networks. For example, the network 230 may include a packet-switched network, a cellular network (e.g., a fifth-generation (5G) network, a fourth-generation (4G) network (such as a Long Term Evolution (LTE) network), a third-generation (3G) network, a code division multiple access (CDMA) network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber-optic-based network, a cloud computing network, etc., and / or combinations of these or other types of networks.

[0056] Figure 2 The number and arrangement of devices and networks shown in are provided as examples. Figure 2 There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently than those shown in FIG. Figure 2 Two or more of the devices shown in FIG may be implemented in a single device, or Figure 2 The single device shown in FIG200 may be implemented as multiple distributed devices. Additionally or alternatively, one or more devices of environment 200 may perform one or more functions described as being performed by another group of devices of environment 200.

[0057] Figure 33 is a diagram of example components of a device 300. The device 300 may correspond to the endpoint device 210, the network device 220, etc. In some implementations, the endpoint device 210, the network device 220, etc. may include one or more devices 300 and / or one or more components of the device 300. Figure 3 As shown in , the device 300 may include one or more input components 310-1 to 310-B (B≥1) (hereinafter collectively referred to as input component 310 and individually referred to as input component 310), a switching component 320, one or more output components 330-1 to 330-C (C≥1) (hereinafter collectively referred to as output component 330 and individually referred to as output component 330) and a controller 340.

[0058] The input component 310 can be one or more attachment points for a physical link and can be one or more entry points for incoming traffic (such as packets). The input component 310 can process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 310 can transmit and / or receive packets. In some implementations, the input component 310 can include an input line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), a packet forwarding component, a line card controller component, an input port, a processor, a memory, and / or an input queue. In some implementations, the device 300 can include one or more input components 310.

[0059] The switching component 320 can interconnect the input component 310 with the output component 330. In some implementations, the switching component 320 can be implemented via one or more crossbar switches, via a bus, and / or using shared memory. The shared memory can act as a temporary buffer to store packets from the input component 310 before the packets are ultimately scheduled for delivery to the output component 330. In some implementations, the switching component 320 can enable the input component 310, the output component 330, and / or the controller 340 to communicate with each other.

[0060] The output component 330 can store packets and can schedule packets for transmission on an output physical link. The output component 330 can support data link layer encapsulation or decapsulation and / or various high-level protocols. In some implementations, the output component 330 can transmit packets and / or receive packets. In some implementations, the output component 330 can include an output line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some implementations, the device 300 can include one or more output components 330. In some implementations, the input component 310 and the output component 330 can be implemented by a set of identical components (e.g., and the input / output component can be a combination of the input component 310 and the output component 330).

[0061] The controller 340 includes a processor, for example, in the form of a CPU, GPU, APU, microprocessor, microcontroller, DSP, FPGA, ASIC, and / or another type of processor. The processor can be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the controller 340 can include one or more processors that can be programmed to perform functions.

[0062] In some implementations, the controller 340 may include RAM, ROM, and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory, etc.) that stores information and / or instructions for use by the controller 340.

[0063] In some implementations, the controller 340 can communicate with other devices, networks, and / or systems connected to the device 300 to exchange information about the network topology. The controller 340 can create a routing table based on the network topology information, can create a forwarding table based on the routing table, and can forward the forwarding table to the input component 310 and / or the output component 330. The input component 310 and / or the output component 330 can use the forwarding table to perform route lookups for incoming and / or outgoing packets.

[0064] The controller 340 may perform one or more of the processes described herein. The controller 340 may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device may include memory space within a single physical storage device or memory space spread across multiple physical storage devices.

[0065] The software instructions may be read from another computer-readable medium or another device into a memory and / or storage component associated with the controller 340 via a communication interface. The software instructions stored in the memory and / or storage component associated with the controller 340, when executed, may cause the controller 340 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0066] Figure 3 The number and arrangement of components shown in are provided as examples. Figure 3 Device 300 may include additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Additionally or alternatively, one or more components of device 300 (e.g., one or more components) may perform one or more functions described as being performed by another group of components of device 300.

[0067] Figure 4 is a diagram of example components of a device 400. Device 400 may correspond to endpoint device 210, network device 220, etc. In some implementations, endpoint device 210, network device 220, etc. may include one or more devices 400 and / or one or more components of device 400. Figure 4 As shown in , device 400 may include a bus 410 , a processor 420 , a memory 430 , a storage component 440 , an input component 450 , an output component 460 , and a communication interface 470 .

[0068] The bus 410 includes components that allow communication between components of the device 400. The processor 420 is implemented in hardware, firmware, or a combination of hardware and software. The processor 420 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor 420 includes one or more processors that can be programmed to perform functions. The memory 430 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor 420.

[0069] The storage component 440 stores information and / or software related to the operation and use of the device 400. For example, the storage component 440 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a magnetic cassette, a magnetic tape, and / or another type of non-transitory computer-readable medium and a corresponding drive.

[0070] Input components 450 include components that allow device 400 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 450 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 460 include components that provide output information from device 400 (e.g., a display, a speaker, and / or one or more LEDs).

[0071] The communication interface 470 includes transceiver-type components (e.g., a transceiver and / or a separate receiver and transmitter, etc.) that enable the device 400 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. The communication interface 470 can allow the device 400 to receive information from another device and / or provide information to another device. For example, the communication interface 470 can include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, an RF interface, a universal serial bus (USB) interface, a wireless local area interface, a cellular network interface, etc.

[0072] Device 400 can perform one or more processes described herein. Device 400 can perform these processes based on processor 420 executing software instructions stored by non-transitory computer-readable media (such as memory 430 and / or storage component 440). Computer-readable media is defined herein as non-transitory memory devices. Memory devices include memory space within a single physical storage device or memory space spread across multiple physical storage devices.

[0073] The software instructions may be read from another computer-readable medium or from another device into the memory 430 and / or storage component 440 via the communication interface 470. The software instructions stored in the memory 430 and / or storage component 440, when executed, may cause the processor 420 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0074] Figure 4The number and arrangement of components shown in are provided as examples. Figure 4 Device 400 may include additional components, fewer components, different components, or components arranged in a different manner than those shown in . Additionally or alternatively, one or more components of device 400 may perform one or more functions described as being performed by another group of components of device 400.

[0075] Figure 5 is a flow chart of an example process 500 associated with converting a multi-level hybrid hierarchical forwarding information base (FIB) format. In some implementations, Figure 5 One or more process blocks of may be performed by a network device (e.g., network device 220). In some implementations, Figure 5 One or more process blocks of may be performed by another device or group of devices that are separate from or include the network device, such as an endpoint device (e.g., endpoint device 210). Additionally or alternatively, Figure 5 One or more process blocks may be executed by one or more components of the device 300 (e.g., input component 310, switching component 320, output component 330, controller 340, etc.), the device 400 (e.g., processor 420, memory 430, storage component 440, input component 450, output component 460, communication interface 470, etc.), and the like.

[0076] like Figure 5 As shown in , process 500 may include receiving forwarding data associated with a multi-level hybrid hierarchical forwarding information base of a network device (block 510). For example, as described above, the network device may receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device.

[0077] like Figure 5 As further shown in FIG5 , process 500 may include processing the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries (block 520). For example, as described above, the network device may process the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries.

[0078] like Figure 5 As further shown in FIG5 , process 500 may include processing a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries (block 530). For example, as described above, the network device may process a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries.

[0079] like Figure 5 As further shown in FIG5 , process 500 may include processing the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries (block 540). For example, as described above, the network device may process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries.

[0080] like Figure 5 As further shown in FIG5 , process 500 may include aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate a final set of transformed forwarding next hop entries (block 550). For example, as described above, the network device may aggregate the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate the final set of transformed forwarding next hop entries.

[0081] like Figure 5 As further shown in FIG, process 500 may include converting the final set of converted forwarding next hop entries into a specific format (block 560). For example, as described above, the network device may convert the final set of converted forwarding next hop entries into a specific format.

[0082] like Figure 5 As further shown in FIG5 , process 500 may include storing the final set of transformed forwarding next hop entries in a specific format in a forwarding information base (Block 570). For example, as described above, the network device may store the final set of transformed forwarding next hop entries in a specific format in a forwarding information base.

[0083] Process 500 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0084] In a first implementation, process 500 includes processing forwarding data to identify a top-level next hop entry in the forwarding data and creating a conditionally transitioned group next hop entry.

[0085] In a second implementation, alone or in combination with the first implementation, process 500 includes receiving traffic associated with a network and forwarding the traffic based on a final set of transformed forwarding next hop entries in a particular format.

[0086] In a third implementation, alone or in combination with one or more of the first and second implementations, the specific format includes a three-level hierarchical address forwarding table format.

[0087] In a fourth implementation, processing forwarding data to generate a transformed group next hop entry and a first set of transformed forwarding next hop entries, alone or in combination with one or more of the first to third implementations, includes: processing forwarding data associated with a first type of next hop to generate a first subset of transformed forwarding next hop entries; processing forwarding data associated with a second type of next hop to generate a second subset of transformed forwarding next hop entries; processing forwarding data associated with a third type of next hop to generate a third subset of transformed forwarding next hop entries; processing forwarding data associated with a fourth type of next hop to generate a fourth subset of transformed forwarding next hop entries; and combining the first subset of transformed forwarding next hop entries, the second subset of transformed forwarding next hop entries, the third subset of transformed forwarding next hop entries, and the fourth subset of transformed forwarding next hop entries to generate the first set of transformed forwarding next hop entries.

[0088] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the first type of next hop corresponds to an aggregate next hop, the second type of next hop corresponds to an indirect next hop, the third type of next hop corresponds to an indexed next hop, and the fourth type of next hop corresponds to a forwarding next hop.

[0089] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, the final set of transformed forwarding next hop entries includes next hop entries that are each associated with a corresponding egress interface of the network device.

[0090] although Figure 5 Example blocks of process 500 are shown, but in some implementations, Figure 5 Process 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in . Additionally or alternatively, two or more of the blocks in process 500 may be executed in parallel.

[0091] Figure 6 is a flow chart of an example process 600 associated with converting a multi-level hybrid hierarchical FIB format. In some implementations, Figure 6 One or more process blocks of may be performed by a network device (e.g., network device 220). In some implementations, Figure 6One or more process blocks of may be performed by another device or group of devices that are separate from or include the network device, such as an endpoint device (e.g., endpoint device 210). Additionally or alternatively, Figure 6 One or more process blocks may be executed by one or more components of the device 300 (e.g., input component 310, switching component 320, output component 330, controller 340, etc.), the device 400 (e.g., processor 420, memory 430, storage component 440, input component 450, output component 460, communication interface 470, etc.), and the like.

[0092] like Figure 6 As shown in , process 600 may include receiving forwarding data associated with a multi-level hybrid hierarchical forwarding information base of a network device (block 610). For example, as described above, the network device may receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device.

[0093] like Figure 6 As further shown in FIG6 , process 600 may include processing the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries (block 620). For example, as described above, the network device may process the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries.

[0094] like Figure 6 As further shown in FIG6 , process 600 may include processing a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries (block 630). For example, as described above, the network device may process a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries.

[0095] like Figure 6 As further shown in FIG6 , process 600 may include processing the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries (block 640). For example, as described above, the network device may process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries.

[0096] like Figure 6As further shown in FIG6 , process 600 may include aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate a final set of transformed forwarding next hop entries (block 650). For example, as described above, the network device may aggregate the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate the final set of transformed forwarding next hop entries.

[0097] like Figure 6 As further shown in FIG, process 600 may include converting the final set of converted forwarding next hop entries into a specific format (block 660). For example, as described above, the network device may convert the final set of converted forwarding next hop entries into a specific format.

[0098] like Figure 6 As further shown in FIG6 , process 600 may include receiving traffic associated with the network (block 670). For example, as described above, the network device may receive traffic associated with the network.

[0099] like Figure 6 As further shown in FIG, process 600 may include forwarding traffic based on the final set of forwarding next hop entries after transformation in a specific format (block 680). For example, as described above, the network device may forward traffic based on the final set of forwarding next hop entries after transformation in a specific format.

[0100] Process 600 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0101] In a first implementation, the second set of transformed forwarding next hop entries includes a transformed forwarding next hop entry that is missing from the first set of transformed forwarding next hop entries.

[0102] In a second implementation, alone or in combination with the first implementation, the third set of transformed forwarding next hop entries includes a new transformed forwarding next hop entry associated with a forwarding class included in the first set of transformed forwarding next hop entries.

[0103] In a third implementation, alone or in combination with one or more of the first and second implementations, the final set of transformed forwarding next hop entries includes: a first subset of transformed forwarding next hop entries associated with the first forwarding class and the first entry in the transformed group next hop entries, a second subset of transformed forwarding next hop entries associated with the second forwarding class and the second entry in the transformed group next hop entries, a third subset of transformed forwarding next hop entries associated with the third forwarding class and the third entry in the transformed group next hop entries, and a fourth subset of transformed forwarding next hop entries associated with the fourth forwarding class and the fourth entry in the transformed group next hop entries.

[0104] In a fourth implementation, alone or in combination with one or more of the first to third implementations, the specific format includes an openconfig address forwarding table format.

[0105] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the final set of transformed forwarding next hop entries in the specific format includes a conditional identifier that defines ingress classification criteria applied to the packet.

[0106] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, the multi-level hybrid hierarchical forwarding information base includes four or more levels.

[0107] although Figure 6 Example blocks of process 600 are shown, but in some implementations, Figure 6 Process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in . Additionally or alternatively, two or more of the blocks in process 600 may be executed in parallel.

[0108] Figure 7 is a flow chart of an example process 700 associated with converting a multi-level hybrid hierarchical FIB format. In some implementations, Figure 7 One or more process blocks of may be performed by a network device (e.g., network device 220). In some implementations, Figure 7 One or more process blocks of may be performed by another device or group of devices that are separate from or include the network device, such as an endpoint device (e.g., endpoint device 210). Additionally or alternatively, Figure 7 One or more process blocks may be executed by one or more components of the device 300 (e.g., input component 310, switching component 320, output component 330, controller 340, etc.), the device 400 (e.g., processor 420, memory 430, storage component 440, input component 450, output component 460, communication interface 470, etc.), and the like.

[0109] like Figure 7 As shown in , process 700 may include receiving forwarding data associated with a multi-level hybrid hierarchical forwarding information base of a network device (block 710). For example, as described above, the network device may receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device.

[0110] like Figure 7 As further shown in FIG, process 700 may include processing the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries (block 720). For example, as described above, the network device may process the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries.

[0111] like Figure 7 As further shown in FIG, process 700 may include processing a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries (block 730). For example, as described above, the network device may process a first set of translated group next hop entries and translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries.

[0112] like Figure 7 As further shown in FIG, process 700 may include processing the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries (block 740). For example, as described above, the network device may process the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries.

[0113] like Figure 7 As further shown in FIG, process 700 may include aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate a final set of transformed forwarding next hop entries (block 750). For example, as described above, the network device may aggregate the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entry to generate the final set of transformed forwarding next hop entries.

[0114] like Figure 7As further shown in FIG, process 700 may include converting the final set of converted forwarding next hop entries into a specific format (block 760). For example, as described above, the network device may convert the final set of converted forwarding next hop entries into a specific format.

[0115] like Figure 7 As further shown in FIG, process 700 may include storing the final set of transformed forwarding next hop entries in a specific format in a forwarding information base (Block 770). For example, as described above, the network device may store the final set of transformed forwarding next hop entries in a specific format in a forwarding information base.

[0116] like Figure 7 As further shown in FIG. 7 , process 700 may include receiving traffic associated with the network (block 780). For example, as described above, the network device may receive traffic associated with the network.

[0117] like Figure 7 As further shown in FIG, process 700 may include forwarding traffic based on the final set of forwarding next hop entries after transformation in a specific format (block 790). For example, as described above, the network device may forward traffic based on the final set of forwarding next hop entries after transformation in a specific format.

[0118] Process 700 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0119] In a first implementation, process 700 includes processing forwarding data to identify a top-level next hop entry in the forwarding data and creating a conditionally transitioned group next hop entry.

[0120] In a second implementation, alone or in combination with the first implementation, processing forwarding data to generate a transformed group next hop entries and a first set of transformed forwarding next hop entries includes: processing forwarding data associated with a first type of next hop to generate a first subset of transformed forwarding next hop entries; processing forwarding data associated with a second type of next hop to generate a second subset of transformed forwarding next hop entries; processing forwarding data associated with a third type of next hop to generate a third subset of transformed forwarding next hop entries; processing forwarding data associated with a fourth type of next hop to generate a fourth subset of transformed forwarding next hop entries; and combining the first subset of transformed forwarding next hop entries, the second subset of transformed forwarding next hop entries, the third subset of transformed forwarding next hop entries, and the fourth subset of transformed forwarding next hop entries to generate the first set of transformed forwarding next hop entries.

[0121] In a third implementation, alone or in combination with one or more of the first and second implementations, the final set of transformed forwarding next hop entries includes next hop entries that are respectively associated with corresponding outbound interfaces of the network device.

[0122] In a fourth implementation, alone or in combination with one or more of the first to third implementations, the second set of transformed forwarding next hop entries includes a transformed forwarding next hop entry that is missing from the first set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries includes a new transformed forwarding next hop entry that is associated with a forwarding class included in the first set of transformed forwarding next hop entries.

[0123] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the multi-level hybrid hierarchical forwarding information base includes four or more levels.

[0124] although Figure 7 Example blocks of process 700 are shown, but in some implementations, Figure 7 Process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in . Additionally or alternatively, two or more of the blocks in process 700 may be executed in parallel.

[0125] According to various implementations of the present disclosure, the following examples are provided.

[0126] Example 1. A method comprising: receiving, by a network device, forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; processing, by the network device, the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing, by the network device, the first set of transformed group next hop entries and transformed forwarding next hop entries associated with a default forwarding category to generate a second set of transformed forwarding next hop entries; processing, by the network device, the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all service categories to generate a third set of transformed forwarding next hop entries; aggregating, by the network device, the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; converting, by the network device, the final set of transformed forwarding next hop entries into a specific format; and storing, by the network device, the final set of transformed forwarding next hop entries in the specific format in the forwarding information base.

[0127] Example 2. The method of Example 1, further comprising: processing the forwarding data to identify a top-level next hop entry in the forwarding data and creating a conditionally transitioned group next hop entry.

[0128] Example 3. The method of Example 1, further comprising: receiving traffic associated with the network; and forwarding the traffic based on the final set of transformed forwarding next hop entries in the specific format.

[0129] Example 4. The method of Example 1, wherein the specific format comprises a three-level hierarchical address forwarding table format.

[0130] Example 5. A method according to Example 1, wherein processing forwarding data to generate a transformed group next hop entry and a first set of transformed forwarding next hop entries includes: processing forwarding data associated with a first type of next hop to generate a first subset of transformed forwarding next hop entries; processing forwarding data associated with a second type of next hop to generate a second subset of transformed forwarding next hop entries; processing forwarding data associated with a third type of next hop to generate a third subset of transformed forwarding next hop entries; processing forwarding data associated with a fourth type of next hop to generate a fourth subset of transformed forwarding next hop entries; and combining the first subset of transformed forwarding next hop entries, the second subset of transformed forwarding next hop entries, the third subset of transformed forwarding next hop entries, and the fourth subset of transformed forwarding next hop entries to generate the first set of transformed forwarding next hop entries.

[0131] Example 6. The method of Example 5, wherein: the first type of next hop corresponds to an aggregate next hop, the second type of next hop corresponds to an indirect next hop, the third type of next hop corresponds to an indexed next hop, and the fourth type of next hop corresponds to a forwarding next hop.

[0132] Example 7. The method of example 1, wherein the final set of transformed forwarding next hop entries includes next hop entries each associated with a corresponding egress interface of the network device.

[0133] Example 8. A network device comprising: one or more memories; and one or more processors for: receiving forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; processing the forwarding data to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing the first set of transformed group next hop entries and transformed forwarding next hop entries associated with a default forwarding category to generate a second set of transformed forwarding next hop entries; processing the first set of transformed group next hop entries and transformed forwarding next hop entries associated with all service categories to generate a third set of transformed forwarding next hop entries; aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; converting the final set of transformed forwarding next hop entries into a specific format; receiving services associated with a network; and forwarding services based on the final set of transformed forwarding next hop entries in the specific format.

[0134] Example 9. The network device of Example 8, wherein the second set of translated forwarding next hop entries includes a translated forwarding next hop entry that is missing from the first set of translated forwarding next hop entries.

[0135] Example 10. The network device of Example 8, wherein the third set of transitioned forwarding next hop entries includes a new transitioned forwarding next hop entry associated with a forwarding class included in the first set of transitioned forwarding next hop entries.

[0136] Example 11. The network device of Example 8, wherein the final set of transformed forwarding next hop entries includes: a first subset of transformed forwarding next hop entries, the first subset of transformed forwarding next hop entries being associated with a first forwarding class and a first entry in the transformed group next hop entries, a second subset of transformed forwarding next hop entries being associated with a second forwarding class and a second entry in the transformed group next hop entries, a third subset of transformed forwarding next hop entries being associated with a third forwarding class and a third entry in the transformed group next hop entries, and a fourth subset of transformed forwarding next hop entries being associated with a fourth forwarding class and a fourth entry in the transformed group next hop entries.

[0137] Example 12. The network device of Example 8, wherein the specific format comprises an openconfig address forwarding table format.

[0138] Example 13. The network device of example 8, wherein the final set of transformed forwarding next hop entries in the specific format includes a conditional identifier that defines an ingress classification criterion to apply to the packet.

[0139] Example 14. The network device of Example 8, wherein the multi-level hybrid hierarchical forwarding information base comprises four or more levels.

[0140] Example 15. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a network device, cause the one or more processors to: receive forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device; process the forwarding data to generate a first set of transitioned group next hop entries and transitioned forwarding next hop entries; process the first set of transitioned group next hop entries and transitioned forwarding next hop entries associated with a default forwarding class to generate a second set of transitioned forwarding next hop entries; process the transitioned group next hop entries and transitioned forwarding next hop entries associated with all traffic classes to generate a second set of transitioned forwarding next hop entries; aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; transforming the final set of transformed forwarding next hop entries into a specific format; storing the final set of transformed forwarding next hop entries in the specific format in a forwarding information base; receiving business associated with a network; and forwarding the business based on the final set of transformed forwarding next hop entries in the specific format.

[0141] Example 16. The non-transitory computer-readable medium of example 15, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: process the forwarding data to identify a top-level next hop entry in the forwarding data and create a conditionally transitioned group next hop entry.

[0142] Example 17. A non-transitory computer-readable medium according to Example 15, wherein one or more instructions that cause one or more processors to process forwarding data to generate a transformed group next hop entries and a first set of transformed forwarding next hop entries cause the one or more processors to: process forwarding data associated with a first type of next hop to generate a first subset of transformed forwarding next hop entries; process forwarding data associated with a second type of next hop to generate a second subset of transformed forwarding next hop entries; process forwarding data associated with a third type of next hop to generate a third subset of transformed forwarding next hop entries; process forwarding data associated with a fourth type of next hop to generate a fourth subset of transformed forwarding next hop entries; and combine the first subset of transformed forwarding next hop entries, the second subset of transformed forwarding next hop entries, the third subset of transformed forwarding next hop entries, and the fourth subset of transformed forwarding next hop entries to generate the first set of transformed forwarding next hop entries.

[0143] Example 18. The non-transitory computer-readable medium of example 15, wherein the final set of transformed forwarding next hop entries includes next hop entries each associated with a corresponding egress interface of the network device.

[0144] Example 19. A non-transitory computer-readable medium according to Example 15, wherein: the second set of transformed forwarding next hop entries includes transformed forwarding next hop entries that are missing from the first set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries includes new transformed forwarding next hop entries that are associated with forwarding classes included in the first set of transformed forwarding next hop entries.

[0145] Example 20. The non-transitory computer-readable medium of example 15, wherein the multi-level hybrid hierarchy forwarding information base comprises four or more levels.

[0146] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and changes may be made in light of the above disclosure and may be acquired from practice of the implementations.

[0147] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software.

[0148] As used herein, a service or content may include a collection of packets. A packet may refer to a communication structure for conveying information, such as a protocol data unit (PDU), a service data unit (SDU), a network packet, a datagram, a fragment, a message, a box, a frame (e.g., an Ethernet frame), a portion of any of the foregoing, and / or another type of formatted or unformatted data unit capable of transmission over a network.

[0149] It is apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation of implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code—it is understood that software and hardware can be used to implement the systems and / or methods based on the description herein.

[0150] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various implementations includes each dependent claim and every other claim in the claim set.

[0151] Likewise, unless otherwise clearly described, the elements, actions or instructions used herein should not be interpreted as being critical or essential. In addition, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". Further, as used herein, the article "the" is intended to include one or more items quoted in conjunction with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more items (such as related items, irrelevant items, the combination of related items and irrelevant items, etc.), and can be used interchangeably with "one or more". In the case of only being intended to represent an item, phrase "only one" or similar language is used. In addition, as used herein, the terms "have (has)", "have (have)", "have (having)" etc. are intended to be open terms. In addition, unless otherwise clearly stated, phrase "based on" is intended to represent "at least partially based on". Furthermore, as used herein, the term "or" is intended to be inclusive when used in series and may be used interchangeably with "and / or" (e.g., when used in conjunction with "either" or "only one of") unless expressly stated otherwise.

Claims

1. A method for communication, comprising: processing, by a network device, forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing, by the network device, the converted group next hop entries and the first set of converted forwarding next hop entries associated with the default forwarding class based on a default forwarding class to generate a second set of converted forwarding next hop entries; processing, by the network device, the first set of the transformed group next hop entries and the transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries; aggregating, by the network device, the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; as well as The network device converts the final set of converted forwarding next hop entries into a specific format.

2. The method of claim 1 , wherein the first set of converted forwarding next hop entries identifies one or more of the following: Outgoing calculation weight; Forwarding Class; or Outbound interface.

3. The method of claim 1 , wherein processing the forwarded data comprises: The forwarding data is processed based on a type of the forwarding next hop identified in the forwarding data.

4. The method of claim 1 , wherein processing the first set of the converted group next hop entries and the converted forwarding next hop entries comprises: The translated group next hop entry and the translated forwarding next hop entry are processed to generate missing translated next hop entries. 5 . The method of claim 4 , wherein the second set of translated forwarding next hop entries includes the missing translated next hop entry.

6. The method of claim 1 , wherein converting the final set of converted forwarding next hop entries into the specific format comprises: Convert a forwarding information base format with a multi-level mixed hierarchical structure of four or more levels into a forwarding information base format with a three-level hierarchical structure.

7. The method according to claim 1, wherein the specific format comprises: The next jump level of the group after the condition changes; The next jump level of the transformed group; as well as The next hop to forward after the transformation.

8. A network device comprising: one or more memories; as well as One or more processors to: processing forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing, based on a default forwarding class, the translated group next hop entries and the first set of translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries; processing the first set of the transformed group next hop entries and the transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries; aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; as well as The final set of transformed forwarding next hop entries is transformed into a specific format.

9. The network device of claim 8, wherein the first set of converted forwarding next hop entries identifies one or more of the following: Outgoing calculation weight; Forwarding Class; or Outbound interface.

10. The network device according to claim 8, wherein, to process the forwarded data, the one or more processors are configured to: The forwarding data is processed based on a type of the forwarding next hop identified in the forwarding data.

11. The network device of claim 8, wherein to process the first set of the converted group next hop entries and the converted forwarding next hop entries, the one or more processors are configured to: The translated group next hop entry and the translated forwarding next hop entry are processed to generate missing translated next hop entries.

12. The network device of claim 11, wherein the second set of transitioned forwarding next hop entries includes the missing transitioned next hop entry.

13. The network device of claim 8, wherein in order to convert the final set of the converted forwarding next hop entries into the specific format, the one or more processors are configured to: Convert a forwarding information base format with a multi-level mixed hierarchical structure of four or more levels into a forwarding information base format with a three-level hierarchical structure.

14. The network device according to claim 8, wherein the specific format comprises: The next jump level of the group after the condition changes; The next jump level of the transformed group; as well as The next hop to forward after the transformation.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a network device, cause the network device to: processing forwarding data associated with a multi-level hybrid hierarchical forwarding information base of the network device to generate a first set of transformed group next hop entries and transformed forwarding next hop entries; processing, based on a default forwarding class, the translated group next hop entries and the first set of translated forwarding next hop entries associated with the default forwarding class to generate a second set of translated forwarding next hop entries; processing the first set of the transformed group next hop entries and the transformed forwarding next hop entries associated with all traffic classes to generate a third set of transformed forwarding next hop entries; aggregating the first set of transformed forwarding next hop entries, the second set of transformed forwarding next hop entries, and the third set of transformed forwarding next hop entries based on the transformed group next hop entries to generate a final set of transformed forwarding next hop entries; as well as The final set of transformed forwarding next hop entries is transformed into a specific format.

16. The non-transitory computer-readable medium of claim 15, wherein the first set of converted forwarding next hop entries identifies one or more of: Outgoing calculation weight; Forwarding Class; or Outbound interface.

17. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the network device to process the forwarded data cause the network device to: The forwarding data is processed based on a type of the forwarding next hop identified in the forwarding data.

18. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the network device to process the first set of the transitioned group next hop entries and the transitioned forwarding next hop entries cause the network device to: The translated group next hop entry and the translated forwarding next hop entry are processed to generate missing translated next hop entries.

19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the network device to transform the final set of transformed forwarding next hop entries into the specific format cause the network device to: Convert a forwarding information base format with a multi-level mixed hierarchical structure of four or more levels into a forwarding information base format with a three-level hierarchical structure.

20. The non-transitory computer-readable medium of claim 15, wherein the specific format comprises: The next jump level of the group after the condition changes; The next jump level of the transformed group; as well as The next hop to forward after the transformation.

Images