<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51863/queries-regarding-iv-update-procedure-in-mesh-sdk</link><description>Hi, 
 I am using nrf mesh sdk 3.1.0. with nrf52832. 
 For iv update one condition is iv_timeout_limit_passed(m_net_state.iv_update.timeout_counter). The timeout_counter value is not stored in flash. so on every power cycle it starts from zero. Please</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 May 2020 07:12:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51863/queries-regarding-iv-update-procedure-in-mesh-sdk" /><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/252304?ContentTypeID=1</link><pubDate>Fri, 29 May 2020 07:12:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5a26466-eccb-4aca-87b1-bdb696509efe</guid><dc:creator>Igor</dc:creator><description>&lt;p&gt;Related thread:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/60144/access_model_publish-returns-nrf_error_forbidden-in-lpn-and-all-friendships-time-out/248638#248638"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/60144/access_model_publish-returns-nrf_error_forbidden-in-lpn-and-all-friendships-time-out/248638#248638&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/209984?ContentTypeID=1</link><pubDate>Tue, 17 Sep 2019 06:54:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d99393fd-4999-44a3-8d2a-28873187ecc2</guid><dc:creator>Aniket_Shet</dc:creator><description>&lt;p&gt;Thanks Simonr. will test it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/209973?ContentTypeID=1</link><pubDate>Tue, 17 Sep 2019 05:54:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d9b1109a-7fc3-43b4-b999-a13775d195d8</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Aniket&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Here are the possible workarounds provided by one of our developers:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;1. Decrease NETWORK_SEQNUM_FLASH_BLOCK_SIZE from 8192 to e.g. 512. This will prevent the application from running out of sequence numbers very quickly. Try this first to see if it helps.&lt;/p&gt;
&lt;p&gt;I&lt;span style="text-decoration:underline;"&gt;f you know how long the devices are awake, option 2 or 3 can be used as well:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;2. Set the initial value of timeout_counter close to 96 hours (depending on how long the devices are awake).&lt;/p&gt;
&lt;p&gt;3. Reduce NETWORK_MIN_IV_UPDATE_INTERVAL_MINUTES value so that the IV update procedure could be triggered earlier.&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;We do not recommend using option 4 unless all of the above fails:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;4. Enable the test mode (like you suggest). This will allow you to change the IV update state as soon as the device has run out of sequence numbers.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/209841?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2019 13:02:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:04feaf50-55f5-4e37-975a-80e3726803a8</guid><dc:creator>Aniket_Shet</dc:creator><description>&lt;p&gt;Hi Simonr,&lt;/p&gt;
&lt;p&gt;Thanks for the update.&lt;/p&gt;
&lt;p&gt;Till fix is implemented can I get a workaround for this? will setting&amp;nbsp;m_test_mode to true be helpful?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/209825?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2019 12:36:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf983c31-bb07-45d4-b942-e95663c10c26</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Aniket&lt;/p&gt;
&lt;p&gt;I heard back from the devs, and it seems like this can happen. This has been confirmed by the development team, and a fix will most likely be implemented in a future release.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Queries regarding iv update procedure in mesh sdk</title><link>https://devzone.nordicsemi.com/thread/208689?ContentTypeID=1</link><pubDate>Mon, 09 Sep 2019 12:36:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a8b2306-0149-496c-aaa6-fe66df62c3b1</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Aniket&lt;/p&gt;
&lt;p&gt;Good question, I&amp;#39;ve asked the Mesh team internally for a verified answer on this, as I&amp;#39;m not completely sure myself. This might take some days though, so please be patient. I&amp;#39;ll update you as soon as I know something!&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>