<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>As long as the VLAN interface has a different IP subnet, you're fine doing this. Regardless if the VLAN is routing or not. Trust me....it's worked when we didn't want it to work. ;) <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: "Dane" <dane@pktloss.net><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "Wes Sisk" <wsisk@cisco.com>, cisco-voip@puck.nether.net<br>Sent: Wednesday, September 30, 2009 2:14:54 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] Restoring 4.1(3)sr5d Publisher?<br><br>I don't think changing the vlan alone would always be the best way.<br>Correct me if I am wrong but if you have routed vlans (is that the<br>right term?) your IP to IP communication between pub and sub could<br>still work. Unless the method for the sub checking to see if the pub<br>is back online is broadcast based then changing the vlan isn't enough.<br> The point I believe is to ensure that the sub see the pub is back<br>online before the pub is completely restored with all the correct data<br>right. If it does and the pub isn't 100% restored then data from the<br>pub could get pushed to the sub?<br><br>I might be way off.<br><br><br><br>On Wed, Sep 30, 2009 at 1:08 PM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>> so, changing the VLAN on the switch is good enough?<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: "Wes Sisk" <wsisk@cisco.com><br>> To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>> Cc: "Dane" <dane@pktloss.net>, cisco-voip@puck.nether.net<br>> Sent: Wednesday, September 30, 2009 1:35:00 PM GMT -05:00 US/Canada Eastern<br>> Subject: Re: [cisco-voip] Restoring 4.1(3)sr5d Publisher?<br>><br>> If TAC engineer is not familiar then yes, please do escalate. It is still<br>> supported and this knowledge is still available to help you.<br>><br>> Otherwise -<br>> it is good to install and upgrade the publisher offline. It is not good to<br>> take the publisher offline by simply unplugging the network cable. That<br>> takes down the IP interface and causes numerous problems with installs and<br>> upgrades.<br>><br>> /Wes<br>><br>> On Wednesday, September 30, 2009 11:40:55 AM, Lelio Fulgenzi<br>> <lelio@uoguelph.ca> wrote:<br>><br>> Your process is what I would do. Get it running to the version you have now<br>> offline and then once you have restored everything from backup shut down the<br>> publisher, plug it in and then restart it. once it is restarted, you will<br>> have to restart the TFTP server and other subscribers.<br>><br>> Hopefully you don't have to republish the databases. But if you do, you can<br>> use the dbhelper tool to do that.<br>><br>> Hopefully others will help.<br>><br>> P.S. If your TAC engineer is not familiar with 4.1, then I would ask to have<br>> the case escalated to someone who has 4.1 experience.<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: "Dane" <dane@pktloss.net><br>> To: cisco-voip@puck.nether.net<br>> Sent: Wednesday, September 30, 2009 11:21:46 AM GMT -05:00 US/Canada Eastern<br>> Subject: [cisco-voip] Restoring 4.1(3)sr5d Publisher?<br>><br>> We had a drive fail on our publisher and had someone swap it out last<br>> night. Well it seems they made a couple of mistakes and left me no<br>> option but having to rebuild and restore now.<br>><br>> Were running 4.1(3)sr5d and have a current BARS backup.<br>><br>> Problem is all the media we have is some what old so I am having to<br>> install and upgrade and upgrade and upgrade to get back to where we<br>> were.<br>><br>> My concern centers around the fact that this is the publisher that is<br>> down and having to be rebuilt using older media and then upgrading to<br>> get back to the point we were. Is there a risk in corrupting or<br>> interrupting the subscriber that is currently operational and running<br>> everything? I am afraid of the publisher coming back online too early<br>> during the process and somehow overwriting information on the<br>> subscriber before the publisher is fully built.<br>><br>> My TAC engineer isn't familiar with the 4.1 release and windows side<br>> of things. Currently the plan he suggests based on the media we have<br>> available is to install 4.0.2 (from media) offline (unplug cable),<br>> then upgrade it to 4.1(3), then upgrade to 4.1(3)sr5d, then install<br>> BARS from that version of CM and do the restore of the BARS backup<br>> data.<br>><br>> Does this sound right to others?<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></div></body></html>