Customer Stories
Blog
How to Buy
Contact Us
About Digi
Leadership
Locations
Awards
Export Policy
Environment
Careers
Investor Relations
IoT Products and Services
Embedded Systems
Digi XBee Ecosystem
Digi XBee RF Modules
Digi XBee Cellular Modems
Digi XBee Gateways
Digi XBee Tools
System-on-Modules
Single Board Computers
IoT Development Kits
Networking
Cellular Routers
Gateways
Infrastructure Management
Console Servers
Serial Connectivity
USB Connectivity
IoT Software and Services
Digi Remote Manager
Wireless Design Services
Professional Services
TrustFence Security Framework
Featured
5G
FirstNet
Private LTE/CBRS
Zigbee
USB Over IP/AnywhereUSB
XCTU
Digi TrustFence
/
Built-in security framework for the IoT
SmartSense
Solutions
Solutions by Application
Public Transit
Traffic Management
Remote Worker
Kiosks and Digital Signage
Branch Networking
Positive Train Control (PTC)
More Applications
Solutions by Technology
The Journey to 5G
Cellular Failover
FirstNet
Private LTE Based on CBRS
SD-WAN
Smart Out-of-Band Management
Zigbee Wireless Mesh Networking
More Technologies
Solutions by Industry
Energy
Smart Cities
Medical
Industrial
Retail
Transportation
Resources
Resource Library
Events
Webinars
Videos
Examples and Guides
Project Gallery
More Resources
Recent News
Press Releases
News Coverage
Security Center
Certifications
Support
Support Services
Support Forum
Product Returns (RMA)
Warranty Registration
Expert Support Login
Knowledge Base
Drivers
Firmware Updates
Documentation
Diagnostics, Utilities & MIBS
Embedded Patches
Sample Applications
Search
Remember
Register
Home
/
Support
/
Support Forum
/
How long is the update routing table time? Or update mechanism?
Digi Forum
All Activity
Q&A
Questions
Hot!
Unanswered
Tags
Categories
Users
Ask a Question
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.
All categories
Digi Remote Manager
(353)
Python
(964)
RF Solutions and XBee
(8,001)
Device Cloud-enabled RF Gateways
(92)
XBee3
(320)
IEEE 802.11 (Wi-Fi)
(264)
IEEE 802.15.4
(1,629)
ZigBee PRO Featureset (and legacy ZNet 2.5)
(1,476)
ZigBee Smart Energy Profile 1.1
(109)
DigiMesh Proprietary Mesh Networking
(749)
Multipoint Proprietary
(195)
XLR PRO
(14)
XStream
(40)
XTend
(127)
XCite
(4)
XPress
(8)
Miscellaneous Hardware and Software
(497)
XBee Programmable Development
(756)
XBee Cellular
(101)
MicroPython
(54)
Digi TransPort
(730)
Digi Connect Cellular
(410)
DAL
(2)
Embedded Devices
(4,056)
Rabbit
(3,144)
Console Servers
(340)
Modbus and Industrial Automation
(235)
Realport
(580)
Serial Servers
(807)
Satellite Modules
(24)
USB
(1,216)
Serial Cards
(712)
ConnectPort Display
(54)
Feedback/Wish List
(86)
Other/Legacy
(331)
How long is the update routing table time? Or update mechanism?
0
votes
I have this configuration as below.
C-R1-E.
I added new router R2 between C and R1. Actually R2 is near R1.
So I thought R1's routing table would show the route path R1-R2-C.
But it didn't show it when I read the route table of R1 by ZDO command.The route table wasn't updated...
I don't know the routing table update period or the update mechanism for routing table...
Let me know how to get the latest route table in the xbee module.
update
routing
table
time
asked
Dec 27, 2016
in
RF Solutions and XBee
by
hwjang11
(
-1
points)
Please
log in
or
register
to add a comment.
Please
log in
or
register
to answer this question.
1 Answer
0
votes
A routing table is only updated if the current rout is broken.
And No, it would not be C - R1 - R2 -E unless the Router 1 was only in range of the Coordinator, router 2 was only in range of both the end device and router 1.
answered
Dec 27, 2016
by
mvut
Veteran of the Digi Community
(
13,680
points)
Thanks for your reply..
But I said that I added R2 between C and R1.
So, I thought that your routing table would add also new path R1-R2-C, besides old path(R1-C).
But it didn't that..
If your policy is that a routing table is only updated if the current route is broken,
it is correct.
But your X-CTU shows new path...
It really does not matter where you placed R2. The point being that as long as your R1 and the Coordinator and End device are in range, it will never send data via R2. The reason for that is that it is always going to take the least amount of hops to get the data from Point A to point Z.
E's parent is R1..But R1 has new path to C.
You mean that R1's routing table isn't updated unless R1 is disassociated.
The LQI among R1-R2-C maybe better than the LQI between R1 and C.
But you mean that it doesn't matter in your routing policy.....
No that is not what I am saying. As long as the router 1 is in range of the the coordinator, it is going to send the data direct. That is, it is not going to use another router to forward the data to the coordinator. No when it can get it to the coordinator all on its own.
1) If then, there is no way that routing table of a router is updated periodically?
2) Why X-CTU can show new path?
The routing tables are updated automatically if the existing table is incorrect.
XCTU is doing a neighbor table lookup. That is how it determines the paths that are available.
What do you mean that the existing table is incorrect?
1)
If I added R2 between C and R1, neighbor information of R1 is updated.
But the routing table of R1 is not updated unless the R1 is disconnected.
2)
Can R1 do neighbor table lookup?
if then, how?
Yes you just need to issue a ZDO command to read the neighbor table.
1. You mean that X-CTU shows new the map by using neighbor tables not routing tables?
But it shows LQI information between the path..
2. Actually I think that the neighbor table's LQI by using ZDO (0x8031) seems not proper.
XCTU uses different options for different radios. For the Zigbee enabled devices, I believe it uses the neighbor table. As for LQI, there are ways to test that and obtain it.
Please
log in
or
register
to add a comment.
...