We had a change in the environment which was planned off hours. After the change the router was rebooted and did not come back online. We had a tech drive into the site to reboot the router, this was all done within the change window and outside production (no operational impact) hours. The client insists for a priority 2, does it qualify for a priority 2 if issue is rectified without production impact?
Priority 2 seems pretty high. But I don't know your SLY with the client. Change, as well as incident/problem, priorities should be described in the SLA in order to avoid such situation. If it is not done yet (from your question I assume - it's not) then I would suggest you do it. One of the purposes of the SLA is to clarify "rules of the game".