Recent Commits to NES-Open-Switch:master

Showing posts with label level. Show all posts
Showing posts with label level. Show all posts

Sunday, June 28, 2015

Bridge MAC learning & forwarding update - 2: adding HAL support

Added #HAL support in #bridge #transparent #port update handler in ethernet module. The new HAL calls will #enable #port #level #MAC #learning & #forwarding separately in #hardware #data-plane.

#Ethernet update 107 ...
[commit 7b5b4358d42edc7c132afd6a2334ca2a196a06ef]

Saturday, June 27, 2015

Bridge MAC learning & forwarding update - 1: correcting port level configuration handler

Correcting #bridge #port level #MAC #learning & #forwarding operations. Added changes in the #transparent #port #configuration #handler to keep HAL in sync with MAC learning & forwarding changes on the base port.

#Ethernet update 106 ...
[commit 156c280a83fb65145f9cc54317cc102e4e28abd0]

Sunday, June 21, 2015

System systemGroup update - 1: added generic system information


Added #generic #system #level #information ( #systemGroup ) in system module. The systemGroup information provides information as description about the system, contact information for the maintainer, system name, location, the services provided by system, list of system modules, etc... This includes systemGroup #parameters like #sysDescr, #sysObjectID, #sysUpTime, #sysContact, #sysName, #sysLocation, #sysServices, #sysORLastChange, #sysORID, #sysORUpTime and #sysORDescr.

#System update 31 ...
[commit 9148b8334c511b54b936eab5689ae7987bbba812]

Thursday, May 14, 2015

Bridge port update - 8

Added #bridge #port #level #admin #flags #handler in ethernet module. These flags control parameters like #CoS, #TC and #PCP #mapping, #service #UNI, #ENNI, #VUNI and #spanning-tree operations on the respective port.

#Ethernet update 98 ...
[commit ee6173e7810d74df24ad7c9916c7f9e81bf330f2]

Sunday, May 10, 2015

Bridge CoS update - 15

Added changes in ethernet module for traversing #port #level #priority #code #point ( #PCP ) #encoding configuration on provider bridges. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 96 ...
[commit 31263afc3940867eeefa3770f9b4dfe2ae855fd0]

Thursday, May 7, 2015

Bridge CoS update - 14

Added optimizations for #port #level #priority #code #point ( #PCP ) #encoding configuration on provider bridges. This will enable to access the optimized encoding configuration entries from the agent framework. These will be used for #GET, #GETNEXT and #SET operations from the agent.

#Ethernet update 95 ...
[commit c0ca95073029d941effab715ff3cf476976ef3b8]

Wednesday, May 6, 2015

Bridge CoS update - 13

Added changes in ethernet module for initializing #port #level #priority #code #point ( #PCP ) #encoding configuration entries and #decoding configuration entries on provider bridges. These changes will initialize the configuration entries with default #CoS and #DEI values as per the translation tables defined in #802-1Q-2011. By default the ingress frame CoS is used unaltered.

#Ethernet update 94 ...
[commit 252dcb6d8f6c9b3c2a3e3393cc78dfd898305b97]

Tuesday, April 28, 2015

Bridge CoS update - 12

Created default tables in ethernet module for #port #level #priority #code #point ( #PCP ) #encoding / #decoding configuration on #provider #bridges ( #PB ). These tables will help to fill PCP encoding / decoding configuration with their initial values. The default table will ensure that ingress CoS is used unaltered and egress CoS is also conveyed unaltered.

#Ethernet update 87 ...
[commit b6c38d7c64f29ecadec9743a092946f773566f9d]

Monday, April 27, 2015

Bridge CoS update - 11

Added changes in ethernet module for traversing #port #level #priority #code #point ( #PCP ) #decoding configuration on provider bridges. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 86 ...
[commit 4e61fd0cd564328a3fbdaa7dfd0fc02f9d5a11af]

Tuesday, April 21, 2015

Bridge CoS update - 10

Added changes in ethernet module for traversing #port #level #access #priority #remapping configuration. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 82 ...
[commit ef219b5ee6c0ebdb066c920e1b11fc02a5197154]

Monday, April 20, 2015

Bridge CoS update - 9

Added changes in ethernet module for traversing #port #level #CoS #remapping configuration. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 81 ...
[commit 59c6924795664ff8cdda4a2b4c0cec202a1ce2a7]

Saturday, April 18, 2015

Bridge CoS update - 8

Added changes in ethernet module for traversing #port #level #effective ( #remapped ) #CoS to #traffic-class #mapping configuration. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 80 ...
[commit dfbd4317ba1dc11718a32227cd76925e799a200a]

Tuesday, April 14, 2015

Bridge CoS update - 7

Added optimizations for #port #level #priority #code #point ( #PCP ) #decoding configuration on provider bridges. This will reduce the memory requirement for supporting PCP decoding configuration. The configuration will decide the effective #CoS and #drop #eligibility ( #DEI ) of the incoming frame based on ingress CoS. Based on the priority code point row selected in the PCP table on the port, the CoS and DEI decoded on the frames will change. By default, for a frame the ingress CoS is used unaltered.

#Ethernet update 77 ...
[commit 1232c133519a37001035c506fb9f9984f9b86234]

Friday, April 10, 2015

Bridge CoS update - 6

Added changes in ethernet module for traversing #port #level #service #access #priority #remapping configuration entries on provider bridges. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 74 ...
[commit da62efad1123bdbf472ceff31c9529ff49d28250]

Thursday, April 2, 2015

Bridge CoS update - 5

Added optimizations for #port #level #priority #code #point ( #PCP ) #encoding configuration on provider bridges. This will reduce the memory requirement for supporting PCP encoding configuration. The configuration will decide the CoS encoded on the outgoing frames, based on the #customer #CoS and #drop #eligibility ( #DEI ) of the frame. Based on the priority code point row selected in the PCP table on the port, the CoS encoded on the frames will change. By default, for a frame the egress CoS is used unaltered.

#Ethernet update 70 ...
[commit fb4bcfd54d7dd6e5eb271db8419f0580f248a6a1]

Tuesday, March 31, 2015

Bridge CoS update - 4

Added optimizations for #port #level #service #access #priority #remapping configuration on provider bridges. This will reduce the memory requirement for supporting service access priority remapping configuration. The service access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the provider network border - either on a customer edge port ( #CEP ) or a customer network port ( #CNP ) -, while receiving data from the customer network. This is useful to request priority handling of customer frames in the provider network. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is used unaltered.

#Ethernet update 68 ...
[commit 416f683112105b43bdca799b83e8ed23f748a54e]

Monday, March 30, 2015

Bridge CoS update - 3

Added optimizations for #port #level #access #priority #remapping configuration on customer bridges. This will reduce the memory requirement for supporting access priority remapping configuration. The access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the customer domain border, while sending data to the provider network. This is useful when the #SLA with the #provider #network requires specific kind of CoS mapping for required QoS treatment. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the egress CoS is send unaltered.

#Ethernet update 67 ...
[commit 927d1b2c75c52888f6a251138ed93a9e58c914a6]

Tuesday, March 24, 2015

Bridge CoS update - 2

Added optimizations for  #port #level #effective ( #remapped ) #CoS to #traffic-class #mapping in ethernet module. The optimization reduces memory used for maintaining this configuration in ethernet module. The traffic-class decides the #QoS treatment for ethernet frames. The remapped CoS which was deduced from the ingress CoS is used for deciding the traffic-class to be applied. By default - without any configuration present, all CoS values are mapped to same default traffic-class 0.

#Ethernet update 63 ...
[commit e21c37a8db62c1e13e5ae10c0074fe68585bc654]

Thursday, March 19, 2015

Bridge CoS update

Added corrections for #general #bridge #port #CoS #configuration in ethernet module. The general configuration controls the default CoS applied on frames, number of traffic classes supported, PCP row to be used for remarking of frames, etc ...

Added optimizations for #port #level #CoS #remapping configuration. This will reduce the memory requirement for supporting CoS remapping configuration. The CoS remapping will enable to map CoS on frames to a different CoS value. The remapped CoS will be used for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is considered as the #effective #CoS for QoS handling.

#Ethernet update 61 ...
[commit 45523fe6405229f8f91f0bd77771646acbb9ce85]