[BGPCEP-90] ODL takes a long time to detect interface is down Created: 25/Apr/14  Updated: 03/Mar/19  Resolved: 28/Apr/14

Status: Resolved
Project: bgpcep
Component/s: General
Affects Version/s: Bugzilla Migration
Fix Version/s: Bugzilla Migration

Type: Bug
Reporter: Valentin Mayamsin Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

External issue ID: 850

 Description   

Scenario:

1. Create an LSP
2. Subscribe to LSP change notifications using DataBrokerService.registerDataChangeListener(instanceId, listener) where instanceId:

InstanceIdentifier.builder(NetworkTopology.class)
.child(Topology.class, new TopologyKey(new TopologyId(topologyId)))
.child(Node.class, new NodeKey(new NodeId(nodeId)))
.augmentation(Node1.class)
.child(PathComputationClient.class)
.child(ReportedLsp.class, new ReportedLspKey(lspName));

3. Shut down one of the LSP hop interfaces to make it unroutable
4. Note when ODL sends event about LSP change.

On our setup ODL takes about 6 mins to detect interface is down.

Version:
org.opendaylight.controller.version = 0.1
org.opendaylight.controller.build.scm.version = 832327e85f47db63006e9bd6115ea85104124f4f
org.opendaylight.controller.build.user = jenkins-controller
org.opendaylight.controller.build.workspace = **********
org.opendaylight.controller.build.timestamp = 1398341431797
org.opendaylight.controller.build.machine = **********

 Comments   
Comment by Valentin Mayamsin [ 25/Apr/14 ]

Tested on two setups, in both cases it took 6 mins

Comment by Valentin Mayamsin [ 26/Apr/14 ]

Seems like it is slow in VIRL, it works well on real devices

Comment by Dana Kutenicsova [ 28/Apr/14 ]

Not an ODL problem.

Generated at Wed Feb 07 19:12:00 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.