today i enable ip v6 tunnel when i enable esxiting working configration i am getting this error and tunnel is going on and off and cpu usage jump to above 50 from 4-5 percent
Connecting to and IPv6 tunnel provider is, like in every case where you are bringing up an interface (for example when using PPPoE to connect via DSL), kind of CPU-expensive. There are many things that have to be done in this process, like setting routes and firewall rules, reconfiguring and restarting services, etc.
If this 'connecting to the internet' fails, then the ASG tries it again and again and again. In your case, the connection to your tunnel broker fails. So the ASG tries to connect again and again and ...
I don't think that you can expect a cpu load from 0% during such a period, so i don't see a problem (besides you not being able to connect to your tunnel broker) here.
Connecting to and IPv6 tunnel provider is, like in every case where you are bringing up an interface (for example when using PPPoE to connect via DSL), kind of CPU-expensive. There are many things that have to be done in this process, like setting routes and firewall rules, reconfiguring and restarting services, etc.
If this 'connecting to the internet' fails, then the ASG tries it again and again and again. In your case, the connection to your tunnel broker fails. So the ASG tries to connect again and again and ...
I don't think that you can expect a cpu load from 0% during such a period, so i don't see a problem (besides you not being able to connect to your tunnel broker) here.