[cisco-voip] 9.3.1 , TVS, and IPv6

[Pawlowski, Adam]

Morning list,

     From what I can read, TVS has been a thrill ride for those of us lucky enough to run afoul of SBD. I'm hoping we haven't run into such a situation here but I have a question. We just pushed 9.3.1 out to devices from 9.1.1SR1, with peer firmware sharing enabled. This went miserably and left a lot of devices stranded at 9.1.1 or at an "Upgrading" screen. Working with TAC on that but so far nothing. We began receiving reports from end users that their directories were missing, they can't change ringers, etc. Last time this happened we had phones that had picked up a bum ITL from a partial rollout, and we had to erase them by hand.

     This time that shouldn't have been the case - it was just a firmware upgrade. However, it looks like some of the phones that have gone to 9.3.1 have decided that they want to use IPv6 when talking to the TFTP to verify their initial configurations, when they have no TVS server list built on the device. In looking at the phone console logs, you can see that the device is in "IP mode 1" and tries to connect to TFTP, say "192.168.0.1 :: " which is obviously not a V6 address. We're not running V6 so it has no address bound. No traffic leaves the phone, but, the phone says it timed out (EAGAIN) connecting to the TFTP and won't verify the ITL/CFG/etc.

      What I'm looking at it is setting V6 to off at the cluster, but, I don't see any way to repair this on affected devices (could be a large amount) other than erasing the ITL, or deploying IPv6. Given the leg work that could go into identifying and taking care of these devices, it's arguable as to which one would be harder at this point.

      Any comment on this with this firmware? Anyone else run into this miserable trouble?

Adam Pawlowski
SUNYAB Network and Classroom Services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121105/749fde4f/attachment.html>