CC2530 - zStack 2.3.0. After reset, Coordinator PANID is increase 1.

Your observation is expected when the Coordinator does not save its network information to Non-Volatile memory.

When you reset the Coordinator, the first thing it does is request beacons from existing networks and your Router provides one with PanID = 0x001. Since the Coordinator's basic job is to start a new new network, it cannot reuse 0x0001, so it must choose another PanID -- the default algorithm in Z-Stack is to increment the PanID, hence the value of 0x0002 that you are seeing.

If you want the Coordinator to "remember" the PanID that it uses to start a network, build your project with the NV_RESTORE compile option. That will cause the Coordinator to read the network parameters from Non-Volatile memory after a reset -- it won't start a new network, it will resume operation on the one it previously started.

Setting NV_RESTORE is desirable in  many cases, but I believe it is NV_INIT which causes the PAN ID to be stored in NV memory.