TED update - 8: adding TE-Link reservation database

#Added #TE-Link #reservation parameters agent routines in TED module. On #LSP #reservation on the TE-Link an entry is made to keep #track of the #reservation just made. These entries hold the #bandwidth information related to each LSP reservation. On creating a #in-segment over a #mpls-interface, a reservation is done over the respective TE-Link and #link-reservation entry is created. On events like #protection #switching or an #LSP #tear #down the respective link-reservation entries will be appropriately handled. This stands as a #database of all the #reservations done in the system for various services LSPs. This allows to avoid complex cases as #double #reservations, where #backup or #detour #paths are involved. The #bandwidth consumed by each reservation is marked in the #link-reservation entries and when #make-before-break ( #MBB ) use-cases are involved it helps to get current #reservation and make #changes accordingly.

#TED update 8 ...
[commit 9bea6e0c39a5d80ccab1a8244a677f65955a1ee8] (https://github.com/nes-repo/NES-Open-Switch/commit/9bea6e0c39a5d80ccab1a8244a677f65955a1ee8)

TED update - 6: renaming standard TE node entries

Renamed #standard #TE-node entries in TED module. The TE-node configuration entries has been made straight forward by correcting it's name. The TE-node entries contain #attributes like #node-id, #autonomous-system-number ( #ASN ), #country-code ( #CC ), #itu-t-carrier-code ( #ICC ) and a local node index for unique reference. This enables to refer the nodes in the network using either using the ASN or the ITU-T based ICC addressing scheme. This also serves as a #database of all #known #nodes in the system. When new nodes gets discovered by the TE signaling modules (e.g. OSPF-TE, ISIS-TE) a dedicated entry will be created for each node, so that it can be referenced in remaining parts of the system (e.g. endpoints of TE-Link). The TE-nodes will be referenced as source, destination or the intermediate nodes of an tunnel LSP path.

#TED update 6 ...
[commit dad1472900d98945f8807cd3103518fd8a4e3463] (https://github.com/nes-repo/NES-Open-Switch/commit/dad1472900d98945f8807cd3103518fd8a4e3463)

TED update - 4: adding extended TED parameter framework

Added #extended #custom #TED #parameter s in TED module. The new TED #framework include #node, #link, #link-address and #node-adjacency #databases on the network. The node database include s all TE nodes present in the network. The TE-Links configured on each node is captured in the link database, the addresses by which the links are identified is available in the link-address database. The adjacency information between the nodes and their neighbors are available in node-adjacency database. The #locally #configured #TE-Link information is directly fed to the TED database, also the #TE information #available #from the #external #signaling modules (e.g. #OSPF-TE, #ISIS-TE) is also captured in the TED database. The TED database is used to efficiently #compute #path for #tunnel #LSPs.

#TED update 4 ...
[commit 77ac9c70e846cd31b39d39b67b4b749e437fde8e] (https://github.com/nes-repo/NES-Open-Switch/commit/77ac9c70e846cd31b39d39b67b4b749e437fde8e)

GMPLS update - 1: created new GMPLS and TED modules in the system

Created #Generalized #Multi-Protocol #Label #Switching ( #GMPLS ) and #Traffic #Engineering #Database ( #TED ) modules in the system. The GMPLS module will assist the operator in creating transport paths - #tunnel s - in the network. The TED module will hold the information about the network necessary for planning resource optimized paths - tunnel s - in the network and provides  traffic engineering capability to GMPLS module. With the help of TED the GMPLS module will create transport #Label #Switched #Path s ( #LSP ) in the network with optimum resource ( e.g. #bandwidth ) utilization.

#GMPLS update 1 + #TED update 1 ...
[commit 0cc8969658eaab27d351dfc95a2b4ef658507edd] (https://github.com/nes-repo/NES-Open-Switch/commit/0cc8969658eaab27d351dfc95a2b4ef658507edd)

Bridge VLAN update - 10

Added changes for creation of #bridge #VLAN #runtime #database #hierarchical #entries in ethernet module. This involves the removal of cross references which were created for maintenance of #dynamic #VLAN #state.

#Ethernet update 97 ...
[commit 0a8f3f5924230dfd8b9bb53203b41ee912dd1eb2]

Bridge VLAN update - 9

Added changes for removal of #bridge #VLAN #runtime #database #hierarchical #entries in ethernet module. This involves the removal of cross references which were created for maintenance of #dynamic #VLAN #state.

#Ethernet update 93 ...
[commit 7a37a14752def2a2ddc5b28ecf76778a86290d07]

Bridge VLAN update - 3

Added #bridge #dynamic #VLAN #database #cleanup step in to #bridge #VLAN #component cleanup routine in ethernet module. This will cascade the cleanup from bridge VLAN component to bridge dynamic VLAN database. #Removed #redundant #indexing in bridge VLAN component database, using bridge component instead. This will enable much optimized, #unified component wide #indexing scheme.

#Ethernet update 54 ...
 [commit 3197832ed855f1cc9cfa734750a6486cd648f95c]