|
|
| jkoh_tt 2002-08-14, 10:40 pm |
| Hi guys,
need some technical help. I intend to "rename" our existing VTP domain name. We have about 30 + switches acting as VTP client. Upon the renaming, will all the clients recognise the renamed VTP domain name?
Jeff | |
|
|
| jkoh_tt 2002-08-15, 7:24 pm |
| thanks javed, well, it all because of our company name changing. Now we have to rename everything, Exchange, DNS, domain name....
jeff | |
| whytokayok 2002-08-19, 5:27 am |
| I believe when you change the domain name you will also reset the revision number back to zero.. | |
| jeff_j_black 2002-08-19, 11:50 am |
| VLAN Domain does not have to reflect Active Directory Domain name, they are not related. | |
| whytokayok 2002-08-20, 1:45 am |
| Good point JB.....There is really no need to change your VLAN domain name unless there are some legal issues your company is dealing with. I ran in to a problem where the corporate lawyers informed us that nothing could have the old company's name on it. | |
| jeff_j_black 2002-08-20, 6:39 am |
| I guess in reading it again that may be the case. Maybe use more generic names for VLANs? | |
| whytokayok 2002-08-20, 7:20 am |
| Yeah, as long as all the clients in the VTP domain have the same name is really what matters........ | |
| whytokayok 2002-08-20, 8:00 am |
| It seems to me that if you change the VTP domain name in the server switch then the client switches would not recognize the new VTP domain name. I would check with Cisco TAC, but I think you would have to manually change the name in all the client switches..... | |
| jkoh_tt 2002-08-28, 2:29 am |
| thanks guys, yup, i understand that VTP Domain does not have any relationship with MS product. It's just that this name change involve the whole corporation, from infastructure to business aspect. anyway..i agreed with whytokayok, by changing the domain name on the server, it means by creating ANOTHER vtp domain...i will have to manually configure on all the edge as well...sucks!! | |
| darthfeces 2002-08-28, 8:29 am |
| yes,
the biggest thing you have to watch out for is
a loss of sync in your revision #'s
that IS bad.
that is why when bringing a new core on to the network it is recommend to bring it on as a client
let it learn vtp info then change to server mode.
in this case you would have brought it in as a server and it would have started propagating it's own revision #
if you have access to equipment you could simulate this and see how the transition acts and formulate a best approach. | |
| jkoh_tt 2002-08-28, 8:02 pm |
| humm...that's right darth, so when are you planning for your CCIE written? | |
| jeff_j_black 2002-08-28, 8:15 pm |
| darth, that is so profound I had to save it to my hard drive. |
|
|
|