Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
Automatically at ONOS start up, adding the application name “"vpls” " in the list of apps to be started automatically, in the own cell file, on the management machine, before pushing the ONOS bits;
Manually, through the ONOS Command LIne (CLI), typing “"app activate org.onosproject.vpls”".
Configuring VPLS is fairly simple. The application exploit a quite small part of the general ONOS network configuration (interfaces).
...
Please, consider the example below:
| Wiki Markup |
|---|
{
"ports" : {
"of:0000000000000001/1" : {
"interfaces" : [
{
"name" : "vlan100H1",
“vlan”"vlan": “100”
"100"
}
]
},
"of:0000000000000002/1" : {
"interfaces" : [
{
"name" : "vlan100H2",
"vlan" : "100"
}
]
},
"of:0000000000000002/2" : {
"interfaces" : [
{
"name" : "vlan200H1",
"vlan" : "200"
}
]
},
"of:0000000000000003/1" : {
"interfaces" : [
{
"name" : “vlan100H3"vlan100H3",
"vlan" : "100"
}
]
},
"of:0000000000000004/1" : {
"interfaces" : [
{
"name" : "vlan200H2",
"vlan" : "200"
}
]
}
}
} |
As soon as two or more interfaces will be configured to receive packets tagged using the same VLAN Id, intents for broadcast will be installed by VPLS.
...
Hosts are not communicating? Do you have at least two interfaces configured and two hosts attached - using the same VLAN Id?
Is your configuration correct? Has it been correctly parsed? The first step is to checked if the configuration has been parsed and correct running at the ONOS CLI the command “"interfaces”". This should give you a list of interfaces configured in the system
Any exception? Type log:exeption-display in the ONOS CLI to discover it.
Are hosts connected to your OpenFlow data plane? I a host start to send out packets into the OpenFlow network you should be able to see it, even if VPLS is not installed yet or no configuration is provided. Go in the ONOS CLI and type
“"hosts
”". As result, you should see something similar to this (100, 2000, 300 in this case are the VLAN Ids used):
...
id=02:2D:BD:5B:9E:43/100, mac=02:2D:BD:5B:9E:43, location=of:0000000000000003/3, vlan=3500, ip(s)=10.2.7.1, 10.1.7.1
id=1E:7B:8C:0E:67:6E/2000, mac=1E:7B:8C:0E:67:6E, location=of:0000000000000004/3, vlan=3500, ip(s)=10.1.4.2, 10.1.5.2, 10.1.7.2
id=86:C0:D9:41:D5:46/100, mac=86:C0:D9:41:D5:46, location=of:0000000000000001/4, vlan=3500, ip(s)=10.2.5.1, 10.1.5.1
...
id=92:1D:B3:D3:BE:2A/300, mac=92:1D:B3:D3:BE:2A, location=of:0000000000000002/3, vlan=3500, ip(s)=10.2.4.1, 10.1.4.1
...
Are intents installed? (type in the ONOS CLI “intent "intent -s” s" - which stays for intents summary, type only “intents” "intents" to see the detailed list of intents)
Yes! (we’re happy!).
No! Ops….let’s check flows, since 1 intent is composed by one or more flows!
Type “flows "flows pending-add” add" to see if there’s any flow for which ONOS still not received an installation confirmation
Type “flows” "flows" to see the detailed list of flows - installed or not by the system
...