-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: SEBA 2.0
-
Component/s: ONOS & Apps
-
Labels:None
-
Environment:
SiaB "make latest"
-
Story Points:3
-
Epic Link:
In a SiaB with multiple OLTs / ONUs / RGs, I've seen all the RGs authenticate successfully but then DHCP fails on some of them. My concern is that this is a bug in the ONOS apps that could also manifest on a physical pod.
When this happens, I see that the subscribers have all been programmed:
onos> volt-programmed-subscribers location=of:00000da7f2c143c7/129 subscriber=[id:PSMO00010001,cTag:112,sTag:223,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:00000da7f2c143c7/130 subscriber=[id:PSMO00010003,cTag:114,sTag:223,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:00000da7f2c143c7/131 subscriber=[id:PSMO00010002,cTag:113,sTag:223,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:0000d0d3e158fede/129 subscriber=[id:PSMO00000003,cTag:114,sTag:222,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:0000d0d3e158fede/128 subscriber=[id:PSMO00000001,cTag:112,sTag:222,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:0000d0d3e158fede/131 subscriber=[id:PSMO00000000,cTag:111,sTag:222,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:0000d0d3e158fede/130 subscriber=[id:PSMO00000002,cTag:113,sTag:222,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze] location=of:00000da7f2c143c7/128 subscriber=[id:PSMO00010000,cTag:111,sTag:223,nasPortId:,uplinkPort:-1,slot:-1,hardwareIdentifier:null,ipaddress:null,nasId:null,circuitId:,remoteId:,technologyProfileId:64,upstreamBandwidthProfile:Bronze,downstreamBandwidthProfile:Bronze]
However the subscriber flows are not created for some. For example:
onos> flows -s -f "IN_PORT:130"
deviceId=of:0000000000000001, flowRuleCount=0
deviceId=of:00000da7f2c143c7, flowRuleCount=1
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:130, ETH_TYPE:eapol, VLAN_VID:4091], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:1, metadata=METADATA:ffb004000000000/0]
deviceId=of:0000d0d3e158fede, flowRuleCount=1
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:130, ETH_TYPE:eapol, VLAN_VID:4091], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:1, metadata=METADATA:ffb004000000000/0]
onos> flows -s -f "IN_PORT:129"
deviceId=of:0000000000000001, flowRuleCount=0
deviceId=of:00000da7f2c143c7, flowRuleCount=5
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:ipv4, IP_PROTO:17, UDP_SRC:68, UDP_DST:67], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:4000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:eapol, VLAN_VID:112], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:70004000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:ipv6, IP_PROTO:17, UDP_SRC:547, UDP_DST:546], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:4000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=1000, selector=[IN_PORT:129, VLAN_VID:None], treatment=[immediate=[VLAN_PUSH:vlan, VLAN_ID:112], transition=TABLE:1, meter=METER:2, metadata=METADATA:df004000000002/0]
ADDED, bytes=0, packets=0, table=1, priority=1000, selector=[IN_PORT:129, VLAN_VID:112], treatment=[immediate=[VLAN_PUSH:vlan, VLAN_ID:223, OUTPUT:2], meter=METER:2, metadata=METADATA:4000000000/0]
deviceId=of:0000d0d3e158fede, flowRuleCount=5
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:eapol, VLAN_VID:114], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:72004000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:ipv4, IP_PROTO:17, UDP_SRC:68, UDP_DST:67], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:4000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=10000, selector=[IN_PORT:129, ETH_TYPE:ipv6, IP_PROTO:17, UDP_SRC:547, UDP_DST:546], treatment=[immediate=[OUTPUT:CONTROLLER], meter=METER:2, metadata=METADATA:4000000000/0]
ADDED, bytes=0, packets=0, table=0, priority=1000, selector=[IN_PORT:129, VLAN_VID:None], treatment=[immediate=[VLAN_PUSH:vlan, VLAN_ID:114], transition=TABLE:1, meter=METER:2, metadata=METADATA:de004000000002/0]
ADDED, bytes=0, packets=0, table=1, priority=1000, selector=[IN_PORT:129, VLAN_VID:114], treatment=[immediate=[VLAN_PUSH:vlan, VLAN_ID:222, OUTPUT:2], meter=METER:2, metadata=METADATA:4000000000/0]
Above, the subscribers on UNI port 130 don't get set up.