...
- All the ONOS instances should have session with every PCC.
- Devices' links' cost/bandwidth should not be modified after initial config.
Usage
1. To setup a MPLS tunnels between routers using ONOS, ONOS should know about the topology.
BGP should provide this information to ONOS.
{
"apps": {
"org.onosproject.provider.bgp.cfg": {
"bgpapp": {
"routerId": "172.16.0.22",
"localAs": 100,
"maxSession": 20,
"lsCapability": true,
"holdTime": 180,
"largeAsCapability": false,
"flowSpecCapability": "IPV4",
"bgpPeer":[ {"peerIp": "172.16.3.15", "remoteAs": 100, "peerHoldTime": 120, "connectMode":"active"}
]
}
}
}
}
This can be checked using devices and links commands respectively.
2. Configuration at router should be made to establish PCEP session with ONOS.
3. Next CLI/web/REST can be used to configure tunnels.
onos> pce-setup-path l3::routinguniverse=0:asn=100:domainid=-1408236785:isoid=5555.5555.0055 l3::routinguniverse=0:asn=100:domainid=-1408236785:isoid=6666.6666.0066 0 rsvp
Please note that 0 stands for RSVP signaled LSPs.
You can find further help for CLI using pce-setup-path --help.
onos> pce-query-path
path-id : 0
source : IpTunnelEndPoint{ip=5.5.5.5}
destination : IpTunnelEndPoint{ip=6.6.6.6}
path-type : MPLS
symbolic-path-name : rsvp
constraints:
cost : TE_COST
bandwidth : 0.0
onos>
onos> pce-update-path -b 10 0
onos> pce-query-path
path-id : 1
source : IpTunnelEndPoint{ip=5.5.5.5}
destination : IpTunnelEndPoint{ip=6.6.6.6}
path-type : MPLS
symbolic-path-name : rsvp
constraints:
cost : null
bandwidth : 10.0
path-id : 0
source : IpTunnelEndPoint{ip=5.5.5.5}
destination : IpTunnelEndPoint{ip=6.6.6.6}
path-type : MPLS
symbolic-path-name : rsvp
constraints:
cost : TE_COST
bandwidth : 0.0
onos>