Cisco Cisco IOS Software Release 12.0(13)S7

16:56:27.099: mpdm: p-data updated

16:56:27.099: mpdm: pdata write completion transaction

16:56:27.099: mpdm: mpls_pblocks_avail(aggrset 0, modulo 32)

16:56:27.099: mpdm: region 0 new submaps/pblocks: [0] [1] [2] [3]

16:56:29.623: mpdm: pblock alloc transaction

16:56:29.623: mpdm: need to update pdata file

16:56:29.623: mpdm: encode in-mem pblock db

16:56:29.623: mpdm: aggr set 0: U U U U U U U U U U U U U U U U U U U U U U U U F F F F F 

F F F

16:56:29.631: mpdm: p-data updated

16:56:29.631: mpdm: pdata write completion transaction

16:56:29.631: mpdm: mpls_pblocks_avail(aggrset 0, modulo 32)

16:56:29.631: mpdm: region 0 new submaps/pblocks: [4] [5] [22] [23]

.

.

.

This sample output provides the following information about MPLS safe label reuse and label allocation:

What happens when the safe-to-reuse timer expires (time 16:55:14.699: the pdata file is updated 
with the new state: FFFFFFUUU. . .FFF (F represents pblocks in the free state, U represents pblocks 
in the in-use state)

A periodic (1 minute) timer expires and notices that the process (mpdm process) used to write to the 
persistent data file is no longer needed (time 16:55:49.015)

The following two processes are repeated when the label allocator needs more new pblocks (times 
16:56:29.623 and 16:56:29.631):

The label allocator needs new pblocks; the allocation of pblocks requires an update to the persistent 
data file; the update requires the mpdm process that is created (time 16:56:27.059)

The mpdm process updates the persistent data file; the label manager is notified that the new pblocks 
it requested are available (time 16:56:27.099)

Use this command to exit to user EXEC mode. For example:

Router# exit

Router>

This section contains the following configuration examples for safe MPLS label reuse:

The following configuration example shows how to disable and reenable safe MPLS label reuse. 

To disable the MPLS Safe Label Reuse After Router Restart feature: