VTP Server placement, "router-on-a-stick" vs switch

Is there a benefit to having a switch act as a VTP server, and not a "router-on-a-stick"? What are the drawbacks to having the router act as the VTP server?

Shanky,
There are new IOS in which you can configure your router for VLANS and also VTP parameters. I have a 3745 router with Version 12.3(5b) and I have tried configuring vlans on this and also setting up the VTP parameters. However I have tried connecting a switch to it and setting up the "router-on-stick" to see how it behaves, I will try that out and let you guys know. Please see :
PJB-UPW-PRI#show ver
Cisco Internetwork Operating System Software
IOS (tm) 3700 Software (C3745-IK9S-M), Version 12.3(5b), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Thu 15-Jan-04 23:39 by kellythw
Image text-base: 0x60008AF4, data-base: 0x61D6A000
ROM: System Bootstrap, Version 12.2(8r)T2, RELEASE SOFTWARE (fc1)
PJB-UPW-PRI uptime is 12 weeks, 2 days, 14 hours, 56 minutes
System returned to ROM by power-on
System image file is "flash:c3745-ik9s-mz.123-5b.bin"
PJB-UPW-PRI#show vlan-switch
VLAN Name Status Ports
1 default active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
PJB-UPW-PRI#vlan database
PJB-UPW-PRI(vlan)#vtp server
Setting device to VTP SERVER mode.
PJB-UPW-PRI(vlan)#vlan 2
VLAN 2 added:
Name: VLAN0002
PJB-UPW-PRI(vlan)#exit
APPLY completed.
Exiting....
PJB-UPW-PRI#show vlan-sw
PJB-UPW-PRI#show vlan-switch
VLAN Name Status Ports
1 default active
2 VLAN0002 active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
I think it should make any difference if you are configuring router as a VTP server. It should behave the same way as a L2 switch does but it will definately consume some memory and also CPU of the router. We have to set up router-on-stick for intervlan routing.
regards,
-amit singh

Similar Messages

Secondary VTP server configuration

Hi,
1.We are having a 6513 switch currently acting as VTP server.We are having a secondary 6513 switch which we want to configure as secondary vtp server.I wanted to know whether we require any downtime for configuring the secondary vtp server.Will there be any flapping in the network..?
Rgds./Sachin

Sachin,
Just make sure the VTP configuration revision # on the new switch is lower than that of the existing VTP server switch, enter the VTP configuration - VTP mode as server, domain name, password etc - set up the trunk and the new switch would dynamically learn all the VLANs from the existing VTP server. If you do it this way no downtime would be required and there should be no disruption to production traffic.
Have a look at this document to learn more about VTP configuration revision.
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_35_se/configuration/guide/swvtp.html
HTH
Sundar

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: Can Ping a device in another VLAN, that device cannot ping back

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: From the Switch I can Ping a device in another VLAN, that device cannot ping back. Some devices can ping devices in other VLANs and the device in the other VLAN can successfully return the Ping. Have a look at the attached diagram.
Router Config:
show run
Building configuration...
Current configuration : 7224 bytes
! Last configuration change at 09:05:48 EDT Wed Aug 6 2014
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname ROUTER
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -8 0
ip cef
ip name-server 8.8.8.8
no ipv6 cef
multilink bundle-name authenticated
license udi pid CISCO1941/K9
object-group network Net_Obj_Group1
description This network group allows all 10.0.0.0 and Email Forwarder server through to the Plt PCs
205.191.0.0 255.255.0.0
10.0.0.0 255.0.0.0
object-group network Net_Obj_Group2
description This Network Group includes the Host IPs allowed through the Plant Router
host 10.194.28.23
host 10.194.28.25
host 10.194.28.26
host 10.194.28.27
host 10.194.28.28
host 10.194.28.29
host 10.194.28.37
host 10.194.28.39
host 10.194.28.40
host 10.194.28.70
host 10.194.28.130
host 10.194.28.131
host 10.194.28.132
host 10.194.28.133
host 10.194.28.134
host 10.194.28.135
host 10.194.28.136
host 10.194.28.137
host 10.194.28.138
host 10.194.28.139
host 10.194.28.140
host 10.194.28.141
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description Port Ge0/0 to IT Enterprise network Switch GE1/0/38
ip address 10.194.28.111 255.255.255.0
ip access-group 105 in
ip access-group 106 out
ip nat outside
ip virtual-reassembly in
shutdown
duplex full
speed auto
no mop enabled
interface GigabitEthernet0/1
description Port to Plant PCN-K/L24 Sw1 Port 0/24
no ip address
duplex auto
speed auto
no mop enabled
interface GigabitEthernet0/1.102
description Port to VLAN 102
encapsulation dot1Q 102
ip address 192.168.102.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.104
description Port to VLAN 104
encapsulation dot1Q 104
ip address 192.168.104.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.105
description Port to VLAN 105
encapsulation dot1Q 105
ip address 192.168.105.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.106
description Port to VLAN 106
encapsulation dot1Q 106
ip address 192.168.106.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.107
description Port to VLAN 107
encapsulation dot1Q 107
ip address 192.168.107.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.111
description Port to VLAN 111
encapsulation dot1Q 111
ip address 192.168.111.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.117
description Port to VLAN 117
encapsulation dot1Q 117
ip address 192.168.117.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.121
description Port to VLAN 121
encapsulation dot1Q 121
ip address 192.168.121.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.125
description Port to VLAN 125
encapsulation dot1Q 125
ip address 192.168.125.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.150
description Port to to VLAN 150
encapsulation dot1Q 150
ip address 192.168.150.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.999
description Port to VLAN 999
encapsulation dot1Q 999
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
no ip http secure-server
ip nat inside source static 192.168.102.201 10.194.28.23
ip nat inside source static 192.168.121.201 10.194.28.25
ip nat inside source static 192.168.106.251 10.194.28.26
ip nat inside source static 192.168.107.245 10.194.28.27
ip nat inside source static 192.168.102.251 10.194.28.28
ip nat inside source static 192.168.150.201 10.194.28.29
ip nat inside source static 192.168.107.179 10.194.28.37
ip nat inside source static 192.168.111.201 10.194.28.39
ip nat inside source static 192.168.105.201 10.194.28.40
ip nat inside source static 192.168.106.21 10.194.28.70
ip nat inside source static 192.168.107.146 10.194.28.130
ip nat inside source static 192.168.107.156 10.194.28.131
ip nat inside source static 192.168.107.161 10.194.28.132
ip nat inside source static 192.168.107.181 10.194.28.133
ip nat inside source static 192.168.107.191 10.194.28.134
ip nat inside source static 192.168.106.202 10.194.28.135
ip nat inside source static 192.168.106.212 10.194.28.136
ip nat inside source static 192.168.117.190 10.194.28.137
ip nat inside source static 192.168.117.100 10.194.28.138
ip nat inside source static 192.168.106.242 10.194.28.139
ip nat inside source static 192.168.125.100 10.194.28.140
ip nat inside source static 192.168.125.99 10.194.28.141
ip nat outside source static 10.194.28.23 10.194.28.23
ip nat outside source static 10.194.28.25 10.194.28.25
ip nat outside source static 10.194.28.26 10.194.28.26
ip nat outside source static 10.194.28.27 10.194.28.27
ip nat outside source static 10.194.28.28 10.194.28.28
ip nat outside source static 10.194.28.29 10.194.28.29
ip nat outside source static 10.194.28.37 10.194.28.37
ip nat outside source static 10.194.28.39 10.194.28.39
ip nat outside source static 10.194.28.40 10.194.28.40
ip nat outside source static 10.194.28.70 10.194.28.70
ip nat outside source static 10.194.28.130 10.194.28.130
ip nat outside source static 10.194.28.131 10.194.28.131
ip nat outside source static 10.194.28.132 10.194.28.132
ip nat outside source static 10.194.28.133 10.194.28.133
ip nat outside source static 10.194.28.134 10.194.28.134
ip nat outside source static 10.194.28.135 10.194.28.135
ip nat outside source static 10.194.28.136 10.194.28.136
ip nat outside source static 10.194.28.137 10.194.28.137
ip nat outside source static 10.194.28.138 10.194.28.138
ip nat outside source static 10.194.28.139 10.194.28.139
ip nat outside source static 10.194.28.140 10.194.28.140
ip nat outside source static 10.194.28.141 10.194.28.141
ip route 0.0.0.0 0.0.0.0 10.194.28.1
access-list 105 permit ip object-group Net_Obj_Group1 object-group Net_Obj_Group2
access-list 106 permit ip object-group Net_Obj_Group2 object-group Net_Obj_Group1
dialer-list 1 protocol ip permit
control-plane
banner login ^CC
Login banner for Plant Router #01^C
banner motd ^CC
MOTD Banner for Plant Router^C
line con 0
password XXXXXXXXX
logging synchronous
login
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password XXXXXXXXX
logging synchronous
login
transport input all
scheduler allocate 20000 1000
ntp server 10.199.100.92
end
Switch Config:
sh ru
Building configuration...
Current configuration : 6513 bytes
version 12.2
no service pad
service timestamps debug uptime
service timestamps log datetime localtime show-timezone
service password-encryption
hostname K24Sw01
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -5
clock summer-time EDT recurring
udld aggressive
crypto pki trustpoint TP-self-signed-593746944
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-593746944
revocation-check none
rsakeypair TP-self-signed-593746944
4B58BCE9 44
quit
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
interface FastEthernet0
no ip address
interface GigabitEthernet0/1
description Trunk port for vlans 105, 111, 125 and 999 from K24Sw01 port Ge0/1 to P22Sw01 port Ge0/24
switchport trunk allowed vlan 105,111,125,999
switchport mode trunk
interface GigabitEthernet0/2
description Trunk port for vlans 150 and 999 from K24Sw01 port Ge0/2 to N25Sw01 port Ge0/26
switchport trunk allowed vlan 150,999
switchport mode trunk
interface GigabitEthernet0/3
description Trunk port for vlans 102, 104, 106, 107, 117 and 999 from K24Sw01 port Ge0/3 to K28Sw01 port Ge0/26
switchport trunk allowed vlan 102,104,106,107,117,999
switchport mode trunk
interface GigabitEthernet0/4
description Trunk port for vlans 102, 106, 107 and 999 from K24Sw01 port Ge0/4 to H23Sw01 port Ge0/26
switchport trunk allowed vlan 102,106,107,999
switchport mode trunk
interface GigabitEthernet0/5
description Trunk port for vlans 121, 125 and 999 from K24Sw01 port Ge0/5 to M21Sw01 port Ge0/24
switchport trunk allowed vlan 121,125,999
switchport mode trunk
interface GigabitEthernet0/6
description OPEN
spanning-tree portfast
interface GigabitEthernet0/7
description OPEN
spanning-tree portfast
interface GigabitEthernet0/8
description OPEN
spanning-tree portfast
interface GigabitEthernet0/9
description OPEN
spanning-tree portfast
interface GigabitEthernet0/10
description VLan 102 access port
switchport access vlan 102
spanning-tree portfast
interface GigabitEthernet0/11
description - VLan 104 access port
switchport access vlan 104
spanning-tree portfast
interface GigabitEthernet0/12
description - VLan 105 access port
switchport access vlan 105
spanning-tree portfast
interface GigabitEthernet0/13
description - VLan 106 access port
switchport access vlan 106
spanning-tree portfast
interface GigabitEthernet0/14
description - VLan 107 access port
switchport access vlan 107
spanning-tree portfast
interface GigabitEthernet0/15
description - VLan 111 access port
switchport access vlan 111
spanning-tree portfast
interface GigabitEthernet0/16
description - VLan 117 access port
switchport access vlan 117
spanning-tree portfast
interface GigabitEthernet0/17
description - VLan 121 access port
switchport access vlan 121
spanning-tree portfast
interface GigabitEthernet0/18
description - VLan 125 access port
switchport access vlan 125
spanning-tree portfast
interface GigabitEthernet0/19
description - VLan 150 access port
switchport access vlan 150
spanning-tree portfast
interface GigabitEthernet0/20
description - VLan 999 access port
switchport access vlan 999
spanning-tree portfast
interface GigabitEthernet0/21
description OPEN
spanning-tree portfast
interface GigabitEthernet0/22
description OPEN
spanning-tree portfast
interface GigabitEthernet0/23
description OPEN
spanning-tree portfast
interface GigabitEthernet0/24
description From ROUTER Gw ge0/1
switchport trunk allowed vlan 102,104-107,111,117,121,125,150,999
switchport mode trunk
interface GigabitEthernet0/25
interface GigabitEthernet0/26
interface Vlan1
no ip address
no ip route-cache
shutdown
interface Vlan102
ip address 192.168.102.253 255.255.255.0
interface Vlan104
no ip address
no ip route-cache
interface Vlan105
no ip address
no ip route-cache
interface Vlan106
no ip address
no ip route-cache
interface Vlan107
no ip address
no ip route-cache
interface Vlan111
no ip address
no ip route-cache
interface Vlan117
no ip address
no ip route-cache
interface Vlan121
no ip address
no ip route-cache
interface Vlan125
no ip address
no ip route-cache
interface Vlan150
no ip address
no ip route-cache
interface Vlan999
no ip address
no ip route-cache
ip default-gateway 192.168.102.1
ip http server
ip http secure-server
snmp-server engineID local 00000009020000019634C2C0
snmp-server community public RO
snmp-server location
snmp-server contact
banner motd ^CCC ADMIN USE ONLY! ^C
line con 0
session-timeout 10
password xxxxxx
logging synchronous
login
stopbits 1
line vty 0 4
session-timeout 10
password xxxxxxx
login
line vty 5 15
session-timeout 10
password xxxxxxxx
login
ntp server 10.199.100.92
end
K24Sw01#

HI Mark,
Here is the my config:
Create sub-interfaces, set 802.1Q trunking protocol and ip address on each sub-interface
Router(config)#interface f0/0
Router(config-if)#no shutdown
(Note: The main interface f0/0 doesn’t need an IP address but it must be turned on)
Router(config)#interface f0/0.10
Router(config-subif)#encapsulation dot1q 10
Router(config-subif)#ip address 192.168.10.1 255.255.255.0
Router(config-subif)#interface f0/0.20
Router(config-subif)#encapsulation dot11 20
Router(config-subif)#ip address 192.168.20.1 255.255.255.0
(Note: In the “encapsulation dot1q 10″ command, 10 is the VLAN ID this interface operates in)
Configure VLAN
Switch(config)#vlan 10
Switch(config-vlan)#name SALES
Switch(config-vlan)#vlan 20
Switch(config-vlan)#name TECH
Set ports to access mode & assign ports to VLAN
Switch(config)#interface range fa0/1
Switch(config-if)#no shutdown
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 15
Switch(config-if)#interface range fa0/3
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode access
Switch(config-if)# switchport access vlan 20
Switch(config-if)#interface range fa0/5
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode trunk
1. Please check all your port are up.
2. Check the config once again.
3. Make sure the swicth and router connection port configured as trunk and it should be up.
This config is working for me,
Regards
Dont forget to rate helpful posts.

Fail to ping from VTP server to a host connected to VTP Client

Hi guys,
I have 2 3560 configured as VTP server and client, did all the trunk setup. A VLAN 102 172.100.4.254/24 created on server side.
Now I can ping the 172.100.4.211 and 172.100.4.254 from vtp client switch
but can't ping 172.100.4.211 from vtp server switch.
routing is handled by a 2811 which can also ping 172.100.4.211 and 172.100.4.254.
Any help is appreciated...

it's like this:
2811 - 3560(vtp server ) - 3560(vtp client) - ESXi
ip route VLAN 102 VLAN 102
172.100.4.254 172.100.4.211
VLAN 101 VLAN 101
172.16.70.254 172.16.70.201
And I just figured out the issue, the address 4.211 belongs to network node in a openstack, should be bind to a bridge instead of interface. thanks anyway!

VTP server and client setup in multiple switches

I understand that we need to setup 1 vtp server and client to exchange trunking messages, to advertise and to updates. But when I have 4 switches connected in square formation, which 1 should I choose to become Server? Another senario, if I have distribution and core layer switches, where I should place my VTP server switch?
Thanks.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Not sure about VTPv3, but with earlier VTP versions, the only major difference between VTP servers and clients is, servers allow you to configure VLAN changes. Both exchange VLAN database information with their immediate neighbors. The real advantage of only having one VTP server configured, it avoids two people configuring two VTP servers at the same time, and creating an update conflict between them. (NB: if you lose your only VTP server, you can promote a client to be a server.)

The difference between VTP server and transparent mode on Catalyst Switch.

Hello
I have a question about the difference between VTP server mode and VTP transparent mode on general catalyst switch.
Basically VTP server mode can create and modify VLAN configuration but actually there is not any VLAN configuration through running-config, is it true? When I checked it on Cat3550, certainly there is not VLAN configuration on VTP server mode. But VTP transparent can create VLAN and configuration but does not synchronize with other switch VLAN status. I appreciate any related information and reason of the VTP server mode specification, thank you very much.
[VTP Transparent mode]
3550#sh vtp status
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 1005
Number of existing VLANs : 27
VTP Operating Mode : Transparent
VTP Domain Name :
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
*omit
3550#
3550#sh run
Building configuration...
*omit
vlan 99
name TEST-VLAN
[VTP Server mode]
3550#sh vtp status
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 1005
Number of existing VLANs : 27
VTP Operating Mode : Server
VTP Domain Name :
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
*omit
3550#
3550#sh run
Building configuration...
*no VLAN like above configuration on VTP transparent mode.
Best Regards,
Masanobu Hiyoshi

Hi mhiyoshi,
3550#sh vtp status
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 1005
Number of existing VLANs : 27
VTP Operating Mode : Transparent
VTP Domain Name :
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
*omit
3550#
3550#sh run
Building configuration...
*omit
vlan 99
name TEST-VLAN
The above out put indicates that Vlan is created and then mode changed to transparent. i.e why revision no is 0.
3550#sh vtp status
VTP Version : 2
Configuration Revision : 0
Maximum VLANs supported locally : 1005
Number of existing VLANs : 27
VTP Operating Mode : Server
VTP Domain Name :
VTP Pruning Mode : Disabled
VTP V2 Mode : Disabled
VTP Traps Generation : Disabled
*omit
3550#
3550#sh run
Building configuration...
*no VLAN like above configuration on VTP transparent mode.
This indicates that vlan never created in server mode nor learnt from another switch as revision no is 0

I have a 27" iMac connected to several others pc and to Server via router. Very frequently Lan or internet drops in my iMac

I have a 27" iMac connected to several others pc and to Server via router. Very frequently Lan or internet drops in my iMac. I Have OS 10.6.7 with all updates.

Issues like this are going to be related to the network. Intermittant problems are typically due to network interference, have you checked istumbler.net to get a report of your network?

Server 2003 routing and remote access not passing VPN traffic

I've inherited a network that has two IP scopes that are routed through a Windows 2003 server with Routing and Remote Access. I can ping both sides (we'll call them HQ and Plant) internally. My firewall has an IP from the HQ IP scope and when
I connect via VPN, I can see all the devices on the HQ network including the network card that is in the routing server for that "side". However, if I'm connected via VPN, I cannot get to any of the IPs on the Plant side, not even the card
in the routing server. The buck stops on the server.
I should mention, that the firewall assigns IP addresses that are on the HQ scope, so all VPN connections will have an address from that side.
I'm lost on how to get this set up so my VPN traffic coming in from the HQ side can be routed to the Plant devices.

Hi,
To be honest, your statement confused me a bit.
VPN is used for external client get access to internal resource. When we setup VPN server, we usually have two NICs. We need choose a NIC that will be used when client initiate
a connection request. I prefer to call it external NIC card. The internal one will work as DHCP relay agent. So this is a single way connection. You cannot dial from internal to external.
If I misunderstood you, please elaborate what you are trying to do.
Hope this helps.

Impact of changing vtp server name

Dear Sir,
Please let me know as below:-
1.) How's vtp works?
2.) what's the impact chaging vtp server name?
thanks.

Hostname doesn't have anything to do with the VTP domain name.
VTP runs in 3 modes - Server, Client and Transparent.
In server mode you could add VLANs and it gets propogated to all other servers and clients if the domain name is the same. In client mode the switch only gets VTP updates and uses it but you can't add vlans. In transparent mode the switch that gets the update from the server forwards the VTP update but it doesn't use itself.
When you say VTP server name I assume you must be taking about VTP domain name. If you change the domain of the VTP server and if that's the master server then you could isolate that device from the other switches and it may result in a network outage.
HTH,
Sundar
*Please rate all helpful posts.

Exchange 2010 SP3 DAG Witness/Quorom Server Placement with 3 Datacenters

Hi we have 2 Exchange 2010 SP3 Server in the same Organization in a DAG
First one in Datacenter 1 in Germany
Second one in Datacenter 2 in Austria
There is a Third Datacenter available in Switzerland
Where should we place the Witness Server?
Our major concern is not a WAN Link will go down, most time a Datacenter will loose Power for some hours due
maintenance work or other things.
Is it a good idea to place the Witness Server in the third Datacenter!?
We found a Document which some missconception which talks about placing the witness always in
the primary Datacenter. But the Datacenter Switchover Document for Exchange 2013 says use a third Datacenter.
Is that also okay for Exchange 2010 or are they totally different?
Thank you in advance
Troga

Hi,
It is a new configuration option in Exchange 2013 that we use a third location for hosting the witness server.
Placing FSW in the third location will privide the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
For more details, you can look at the "Witness server placement considerations" section in the following article.
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

Report of switches in VTP Server Mode

I am using CiscoWorks LMS 3.2.
How can I run a report that will tell me the VTP mode of my switches?
I want to ensure that ONLY my VTP server is in server mode, and that all of my other switches are in client mode.
Thankd in advance!

Click here for information.
(43051)

CatOS and removing a vlan from its VTP server..

Hi guys
Question I hope can be cleared up very quickly.
I have a pair of old switches running CatOS, these are also VTP servers for the network running off em..
I need to de-comission a Vlan but cannot figure out the best way to remove the vlan from them?
Obviously,
IOS I would just
conf t
no vlan xx
end
But I cannot for the life of me find the best way to do this on CatOS...
Ive found that it may be a "clear vlan xx" command, but not sure..
Any ideas?
Thanks,
-Graham
Please note: My comments are simply suggestions. I cannot be held liable for any loss of data, life or marbles due to following my instructions.
Technical Design Engineer
IMsupporting.com - Live chat software

Doesnt that just remove the vlan from the port?
Ideally I want to remove the vlan completely from the system? ( Its a VTP server too )
Ie:
conf t
no vlan xx
end
Would do it on cisco IOS..
would
conf t
clear vlan xx
end
do it on catos?
Thanks
Graham

VTP server

I need to deploy on the core switches (2 Catalyst 4500 with supervisor 10GE) a redundant VTP server configuration.
The solution is to configure the same VTP server on both switches, configure the same parameters and the same vlan on both switches: are there any problems or does anyone have other better solutions ?
Thanks in advance.

Hi R,
It is always good to have 2 VTP servers just incase something happens to the main VTp server you still have second to hold the network and vlan information.
No need to manually create the same vlan on both the servers. Just let it be in VTP server mode and it will sync the vlan information from the first VTP server like all VTP clients do. Just manually create vlan on first VTPservers.
Make sure VTP version , domain name and password if you configure exactly matches in all your switches which you want to take part in same VTP domain.
HTH
Ankur

Router on a Stick with Cisco/Linksys SRW2024 Switch

Does anybody have experience with configuring a router on a stick type configuration with a non-Catalyst switch? I have a SRW2024 switch and a 2611 router. I would like to configure the switch with a trunk port and use dot1q encapsulation on subinterfaces on the router to route between the subnets. Configuring the router is simple, but the switch is very confusing and I just can't seem to get it to work. Any ideas? Is this even doable with this combonation of hardware?
Thanks in advance.
-Dan

The "Encapsulation dot1q 1 native" command is not a valid command on my router. Specifically, the native command is not an option. Perhaps that isn't in my IOS version?
IOS (tm) C2600 Software (C2600-JS56I-M), Version 12.0(7)T, RELEASE SOFTWARE (fc2)
IOS image: c2600-js56i-mz.120-7.T
However I did a whole lot of messing around with it today and I think I finally got it. The trouble is, IMHO, the switch menus are too messy and hard to understand. It seems to allow me to do impossible things which adds to the confusion.
Here's what worked for me:
My router config was correct to begin with.
Router-A (Cisco 2611):
interface Ethernet0/0
ip address 192.168.1.10 255.255.255.0
interface Ethernet0/0.2
encapsulation dot1Q 2
ip address 10.0.0.1 255.0.0.0
Switch (Linksys SRW20204):
Menu: Switch > VLAN Interface Settings
Select the port number of the port to be the trunk.
Set Port VLAN Mode to Trunk. Submit.
Menu: Switch > VLAN
Create a second VLAN with the ID of 2.
Add the ports to be "Included" on this VLAN.
Leave the workstation ports "Untagged".
(This is where I was screwing up)...
"Include" the Trunk port AND select "Tagged".
So basically, I was tagging the workstation ports and not the trunk port. But the correct way is the Trunk port must be Included on all VLANs and have Tagging turned on for all VLANs. All the workstation ports should be included on whatever VLAN they should be on but NOT Tagged. It makes sense now because a workstation would have no idea what to do with a tagged frame.
Why I can enable tagging on non-trunk ports is a mystery. They really should explain that better in the manual. Perhaps add some examples. I find the manual for this switch to be extremely vague overall.
Thakns for the help guys!
-Dan

Router-on-a-stick swap to L3-switches

Hi Gents,
My very first post to any forum that relates my work... I was not able to find any discussions about this, so sorry if this is answered somewhere.
Question goes, is there any best practices or things that should be taken in to an account when one is going to swap ROAST devices to L3 capable switches.
So, my task is to update redundant CE devices (2 x 1800 series router and 2 x 2960 switches, Router on a stick) to some L3 -switches. I think that this is quite straight forward to do. You just swap one side at time. But, if you try to minimise or even avoid network connectivity lost, what to do? We use naturally HSRP and spanning tree. Is there anything to pay a special attention?
I think that HSRP timers are default. We use RSTP. Behind the switches there are some servers with dual NICs, but its only fault tolerance, not load balancing.
Thanks!

Hello!
Well best practice - do not hurry and do everything not at once, but by little iteration steps. Begin by adding new L3 switches to existing network without connecting to them any production servers. Then move IP interfaces one by one from ROAST to L3 switches. Plan everything on a paper or any documenting solution up to the exact commands you going to execute on each peace of your network. Take advantage from peer review tradiotion with your co-workers. If you are not very confident with what you are going to do, simulate it all in Packet Tracer/GNS/IOU/etc.
Your network is not large as it seems from your description, so I think you will do everything within two or three weeks without any impact on production.

VTP Server placement, "router-on-a-stick" vs switch

Similar Messages

Maybe you are looking for