<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Thanks. I'm thinking I'll just stick with recreating it all over. It's likely not going to happen that many times.<br><br>I'm just hoping they have this fixed by 6 or 7.<br><br><br>----- Original Message -----<br>From: "Erick Bergquist" <erickbee@gmail.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "Ryan Ratliff" <rratliff@cisco.com>, "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Tuesday, March 31, 2009 8:53:31 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Replacing VG224 Script Error<br><br>Under the interface, the mac-address command. Then you need to save<br>the config and reboot for SCCP functions to pick it up. You can use<br>the 'show stcapp device summary' command to make sure your device<br>names are using right MAC Address for the beginning. The device name<br>in that output has to match whatever is in CUCM.<br><br>YMMV on this workaround, it worked for me 2-3 times I've done it but<br>gave me trouble once and I had to add it as new to CCM with the ports,<br>etc.<br><br>Router(config-if)#mac-address ?<br> H.H.H MAC address<br><br><br>On Tue, Mar 31, 2009 at 9:46 AM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>> Erick,<br>><br>> what command did you use to change the MAC address of the interface?<br>><br>> Cisco TAC is dropping the ball on my case and I want to consider going<br>> forward with any new installations with private MAC addresses.<br>><br>><br>><br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> "Bad grammar makes me [sic]" - Tshirt<br>><br>><br>> ----- Original Message -----<br>> From: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>> To: "Erick Bergquist" <erickbee@gmail.com><br>> Cc: "Ryan Ratliff" <rratliff@cisco.com>, "cisco-voip voyp list"<br>> <cisco-voip@puck.nether.net><br>> Sent: Friday, March 27, 2009 2:39:12 PM GMT -05:00 US/Canada Eastern<br>> Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>><br>> Too late. Damage was done.<br>><br>> ----- Original Message -----<br>> From: "Erick Bergquist" <erickbee@gmail.com><br>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>> Cc: "Ryan Ratliff" <rratliff@cisco.com>, "cisco-voip voyp list"<br>> <cisco-voip@puck.nether.net><br>> Sent: Friday, March 27, 2009 11:50:46 AM GMT -05:00 US/Canada Eastern<br>> Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>><br>> Is changing the MAC Address on the VG224 LAN interface to match and<br>> rebooting the 224 not working as a workaround? After rebooting the<br>> VG224 with changed MAC address you can do a 'show stcapp device<br>> summary' to see if the device name matches that on CCM side.<br>><br>> On Fri, Mar 27, 2009 at 10:37 AM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>>> Thanks for following up. I'm hoping the TAC comes up with something.<br>>> Otherwise, I'm gonna have to revert to installing the gateway, devices and<br>>> DNs all from scratch. Yuck.<br>>><br>>> ----- Original Message -----<br>>> From: "Ryan Ratliff" <rratliff@cisco.com><br>>> To: "Ryan Ratliff" <rratliff@cisco.com><br>>> Cc: "Lelio Fulgenzi" <lelio@uoguelph.ca>, "cisco-voip voyp list"<br>>> <cisco-voip@puck.nether.net><br>>> Sent: Friday, March 27, 2009 11:24:32 AM GMT -05:00 US/Canada Eastern<br>>> Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>>><br>>> Sorry I just noticed my 4.1 server did give me the same popup error.<br>>> It happened to appear behind my main IE window and I didn't notice it<br>>> until just now.<br>>><br>>> -Ryan<br>>><br>>> On Mar 27, 2009, at 10:30 AM, Ryan Ratliff wrote:<br>>><br>>> Just tested with 4.1(3), 4.2(3), and 7.0(2). All three let me change<br>>> the mac address of the gateway but the 4.1(3) server did not update<br>>> the endpoint devicenames. New ports did take the new mac address<br>>> though. Both 4.2 and 7.0 did update the endpoint devicenames.<br>>><br>>> Starting to think the error you are getting is better than it making<br>>> it look like everything works ok when it actually doesn't.<br>>><br>>> Haven't found a bug yet unfortunately.<br>>><br>>> -Ryan<br>>><br>>> On Mar 27, 2009, at 10:04 AM, Lelio Fulgenzi wrote:<br>>><br>>> 4.1(3) no havey bulk loady. :(<br>>><br>>> The process updated some of them, but not all of them.<br>>><br>>> the vg248 replacement worked fine. i'm wondering if it's a bug<br>>> introduced with some recent SR since i haven't replaced a vg248 in a<br>>> while.<br>>><br>>> ----- Original Message -----<br>>> From: "Ryan Ratliff" <rratliff@cisco.com><br>>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>> Cc: "Erick Bergquist" <erickbee@gmail.com>, "cisco-voip voyp list"<br>>> <cisco-voip@puck.nether.net><br>>> Sent: Friday, March 27, 2009 9:22:02 AM GMT -05:00 US/Canada Eastern<br>>> Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>>><br>>> Never run into it personally before but I can understand where the<br>>> CCMAdmin may not be able to go and update the hostname for all the<br>>> dependent devices. Heck in this case it may be trying to do just<br>>> that and getting a db error returned.<br>>><br>>> As a workaround you should be able to do a BAT export - all details<br>>> of the gateway. Take the file and edit the mac-address field and<br>>> then do an import-all details.<br>>><br>>> For a sccp vg224 you will want to watch out for CSCsw43113 but there<br>>> is a pretty easy workaround for it.<br>>><br>>> -Ryan<br>>><br>>> On Mar 27, 2009, at 7:52 AM, Lelio Fulgenzi wrote:<br>>><br>>> Interesting. We'll have to see what TAC says about this.<br>>><br>>> As for SCCP/STCAPP, I simply grabbed the config from the other unit,<br>>> copied it to the new unit to startupconfig and it worked fine.<br>>><br>>> Oh well.<br>>><br>>> ----- Original Message -----<br>>> From: "Erick Bergquist" <erickbee@gmail.com><br>>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>> Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>>> Sent: Friday, March 27, 2009 12:27:18 AM GMT -05:00 US/Canada Eastern<br>>> Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>>><br>>> I now remember getting some error when I replaced a clients VG224 on<br>>> CCM 4.x and when I went to try to change MAC address on existing<br>>> gateway in CCM it displayed some error message and thats why I did the<br>>> MAC address change on the gateway and found out I had to reboot the<br>>> gateway for SCCP to see the change. There was one time that method<br>>> didn't work somewhere else and I had to delete the old ports from CCM<br>>> and add the whole gateway and all ports back from scratch. That took<br>>> some time to do. Had 2 Web windows open and copied the old port config<br>>> to the new port then deleted the old one. I haven't had to do this<br>>> with 5.x or higher yet so don't know if they behave the same.<br>>><br>>> The other thing with replacing VG224 with SCCP set up, is you can't<br>>> paste in the old running config with it working right away. For all<br>>> the stcapp commands to take the sccp commands need to be in the<br>>> running config, but the stcapp commands come before sccp so after you<br>>> paste in the old config you need to enter the missing stcapp commands.<br>>><br>>><br>>> On Thu, Mar 26, 2009 at 12:26 PM, Lelio Fulgenzi <lelio@uoguelph.ca><br>>> wrote:<br>>> > Yes, SCCP.<br>>> ><br>>> > It should be simple enough to change it on the gateway config and<br>>> it should<br>>> > change all the phones. The MAC address on the phones is greyed out<br>>> anyway -<br>>> > you can't change them.<br>>> ><br>>> > I never knew you could change the MAC address on the switch. Not<br>>> sure if I<br>>> > like that though. :(<br>>> ><br>>> > ----- Original Message -----<br>>> > From: "Erick Bergquist" <erickbee@gmail.com><br>>> > To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>>> > Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>>> > Sent: Thursday, March 26, 2009 1:09:17 PM GMT -05:00 US/Canada<br>>> Eastern<br>>> > Subject: Re: [cisco-voip] Replacing VG224 Script Error<br>>> ><br>>> > SCCP?<br>>> ><br>>> > I haven't changed the MAC address on the CCM side before due to the<br>>> > fact I didn't want to go into changing all the ports.<br>>> ><br>>> > What I've done is to change the mac-address on the VG224 ethernet<br>>> > interface configuration to match the old one. You do need to wri mem<br>>> > the config and reboot the VG224 (router) for the SCCP function on<br>>> the<br>>> > IOS to pick up that change. After the reboot then the gateway<br>>> > registers with the CCM with the old mac like before and all is<br>>> > good..... YMMV, this worked for me a few times so far.<br>>> ><br>>> > On Thu, Mar 26, 2009 at 11:48 AM, Lelio Fulgenzi<br>>> <lelio@uoguelph.ca> wrote:<br>>> >> I'm replacing a VG224 and when I went to change the MAC address<br>>> on the<br>>> >> gateway configuration I got a script error back saying the device<br>>> needed a<br>>> >> device pool (See below). I could also swear that another dialog<br>>> box comes<br>>> >> up<br>>> >> quickly that has something about duplicates not allowed, but it<br>>> >> disappears.<br>>> >><br>>> >> Please don't tell me that to replace a VG224 I have to<br>>> reconfigure all the<br>>> >> ports!<br>>> >><br>>> >> Error Information<br>>> >><br>>> >> The specified device requires a Device Pool. (53)<br>>> >><br>>> >> Details:<br>>> >><br>>> >> Error No. -2147219915 (0x80040635):<br>>> >> CDBLException Dump: [The specified device requires a device pool.]<br>>> >><br>>> >> ---<br>>> >> Lelio Fulgenzi, B.A.<br>>> >> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G<br>>> 2W1<br>>> >> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>> >><br>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>>> >> "Bad grammar makes me [sic]" - Tshirt<br>>> >><br>>> >><br>>> >> _______________________________________________<br>>> >> cisco-voip mailing list<br>>> >> cisco-voip@puck.nether.net<br>>> >> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>> >><br>>> >><br>>> ><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> cisco-voip@puck.nether.net<br>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>><br>>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> cisco-voip@puck.nether.net<br>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>><br>>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> cisco-voip@puck.nether.net<br>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>><br>>><br>><br></div></body></html>