WLC5508 connected two switches
Dear All,
I have a WLC 5508 and a brief connected like below.
Internet->Router->2960G A-> (Port0) WLC5508 (Port1) -> 2960G B-> Access Points <-> wireless clients
My Question : Is the above topology work? The access points register to the controller via 2960B, and the data traffic ffrom wireless clients go through from 2960G B to WLC port 1, and WLC pass it to port 0 itself and then go to internet?
Thanks.
Mic
As long as you don't have LAG enabled that will work. You do need to specify a dynamic interface in which the Internet traffic will egress. Your management will be primary port 1 and the your dynamic interface will be primary port 2. Of course port 1 and port 2 would have to be on a different subnet.
If you have both on the same subnet, that will not work. You would trunk the ports and only allow the vlans for that port. Port 1 connected to the switch would only allow the vlan for the management. Port 2 connected on the switch will only allow the vlan for that dynamic interface.
Sent from Cisco Technical Support iPhone App
Similar Messages
-
Networking Best Practices - Connecting Two Switches
Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
For more details on the difference between Access, General, and Trunk modes, follow this link.
http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
http://support.dell.com/support/edocs/network/
Layer 2
Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
We will use 3 VLANs for the following scenario.
VLAN 1=Management
VLAN 2=Client
VLAN 3=Server
To create these VLANs we do the following commands (VLAN 1 is already created by default)
console(config)# vlan database
console(config-vlan)# VLAN 2
console(config-vlan)# VLAN 3
console(config-vlan)# exit
We can then name the VLANs to help keep things organized.
console(config)# interface vlan 2
console(config-vlan)# name Client
console(config-vlan)# exit
console(config)# interface vlan 3
console(config-vlan)# name Server
console(config-vlan)# exit
Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
For the port e1 that connect the two switches to each other would be configured like this.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3. Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
Layer 3 + Layer 2
Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches. Then we will add to the configuration.
We can assign an IP address to each switch with the following command.
Switch A
console(config)#ip address 172.16.1.1 255.255.255.0
Switch B
console(config)#ip address 172.16.2.1 255.255.255.0
Then we will enable routing only on Switch A
console(config)# ip routing
Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
console(config)# interface vlan 2
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
console(config-if-vlan2)# exit
Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
console(config)# interface vlan 3
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.11
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.11
Default Gateway:172.16.30.1
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.12
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.12
Default Gateway:172.16.30.1
External Connection
At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
console(config)# vlan database
console(config-vlan)# VLAN 7
console(config-vlan)# exit
console(config)# interface vlan 7
console(config-vlan)# name WAN
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
console(config-if-vlan2)# exit
On our router we will assign an IP address of 10.10.10.1
Then place the port connecting the switch and router into access mode for VLAN 7. In this case we use port e4.
console(config)# interface ethernet 1/e4
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 7
console(config-if)# exit
We will then need to put in a default route with the next hop as the router IP address. This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A. Generally adding a static route on most routers is done with the following command:
ip route {Network} {Wildcard Mask} {Next Hop-IP}
In our case here are the 2 static routes we could use.
Ip route 172.16.20.0 0.0.0.255 10.10.10.2
Ip route 172.16.30.0 0.0.0.255 10.10.10.2
The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
Layer 3 + Layer 3
In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
To create this VLAN we will run the following commands on both switch A and B
console(config)# vlan database
console(config-vlan)# vlan 6
console(config-vlan)# exit
console(config)# interface vlan 6
console(config-vlan)# name Connection
console(config-vlan)# exit
On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
console(config-if-vlan2)# exit
On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and B we place the connecting ports into Access mode for VLAN 6.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 6
console(config-if)# exit
We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
We will enable routing on Switch B
console(config)# ip routing
What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
console(config)# interface vlan 4
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
console(config-if-vlan2)# exit
Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
console(config)# interface vlan 5
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
console(config-if-vlan2)# exit
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 4.
IP Address:172.16.40.11
Default Gateway:172.16.40.1
Client connected to access port for VLAN 5.
IP Address:172.16.50.11
Default Gateway:172.16.50.1
The end result should look like this.
Troubleshooting
If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
The external router will also need a path defined back to all networks/VLANs.
To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
console# show interfaces detail ethernet 1/g48
To check routing paths:
console# show ip route
The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
-Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
-Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
-Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
-ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
-ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
-ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
-ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow. -
Cisco 2950 MT-RJ ports - Connect two switches?
Hi Everyone,
I'm wondering if I can connect two cisco 2950s together via the two MT-RJ ports they have?
Basically, I'd like the fibre ports to be the trunk between the two switches if possible
I have two of these:
Thanks!Hi,
Yes, that is possible. As long as your fiber patch cable is good there should be no issues.
HTH -
Can I connect two switches to a server?
We share an office with another company but we currently have separate servers and networks.
I'm looking into the possibility of us sharing their server.
The thing is we both have our own switches and and I want to avoid any rewiring of the network. Will I be able to use two switches?
It's a 2x 2.8 GHz quad core intel xeon (with dual ethernet). So is it just a matter of connecting both switches to the server and configuring them in some way?Hi Christiaan,
I end up doing this quite often. You have a few options, the simplest is below...
How many users and devices that require network connections does each company have? If it's under 254 which it sounds like it is and your happy to have the users on the same network, sharing the same ISP. Then the easiest option is going to be your company sharing their network. You'd save a bit of money on your internet connection which could be used to increase the bandwidth on the other companies line if needed.
You would do following. Make sure all devices that need a fixed IP address such as printers/mfds'/switches/WiFI/phone system (if applicable) are changed to a fixed IP address with the relevant subnet mask, dns and gateway from the other companies network. You'd obviously need to get the relevant numbers from their IT guy.
Then you could use your switch as extra capacity on their network by linking it with their switch. Obviously you'd want to use the fastest possible connection between the switches or look to buying something new with more ports. If you both have something like the HP 1810G ProCurve or a compatible switch you can buy two fibre transceivers and connect them with a fibre cable, this will free up more ports for users on the switch or simply connect them via an ethernet cable. On the 1800 series you can use LACP which allows you to use up to 4 ethernet ports to improve the bandwidth thus giving you a 4gigabit connection to their network. Depending on how much traffic there is going to be you might want to skip that as there might be no need.
Then it's just a case of creating your users on their server and creating an area for your company that only you have the access rights to and creating a shared area inter-company area if you want to easily ping them over files.
What do you both use for email? Are you going to look to share a server for it?
Hope that helps
Beatle -
Connecting Two Power Supplies in one PC
Hello there :hypecrite:
Will someone help me on how to connect two Switching P/S in one PC (If it's possible)?
I tried using two P/S in my old PC and it's working just fine. However, the problem is that I cannot switch them on simultaneously because the one is connected directly to the motherboard and the other, I just used a simple switch to turn it on.
Also, please check my P/S for this PC if it's OK.
Thank you and more POWER!!!
:hypecrite:Hello again :hypecrite:
Thank you for your support guyz. I would like to tell you that you are all correct.
I think it's time for me to stop fooling aroung, experimenting things, too. And to trust the verdors instead. I looked for the psu brands that you all mentioned and it turned out my pockets could still handle such a cost, eventhough it costs twice as much as the psu that I have right now, but as long as it's dependable.
And about the problem with my CPU's temperature that I posted last November 12, 2004 (MSI KT4A-V with S/PDIF out and Core center), AMD support center finally replied to me and told me that my temp is OK but not to go above 70C.
Below is my inquiry to AMD and their reply:
My inquiry:
Dear Sir:
I would like to ask what is the NORMAL operating temperature of Athlon XP 2400+ FSB 266 model 8?
When my PC is at idle, my CPU temp reading is 60C and during full load, it reaches to about 66C. It doesn't have any problems though (such as random reboot) but I'm a bit concerned of the temperature reading. Some people say that it's a bit TOO HOT for comfort. Still others say that it is OK. What do you think?
I have read your post on MAXIMUM operating temperatures of Athlon XPs but not the recommended NORMAL operating temperatures.
And also when I turn the BIOS CPU core voltage to AUTO mode the default is 1.575V. My friends said the minimal operating voltage of 2400+ is 1.650V. Is it OK to just leave it to default?
Thank you very much
Sincerely,
Mark E. Guillem
Philippines
My PC Specifications:
AMD Athlon XP 2400+ (Family 6, Model 8, Stepping 1), FSB266 256L2
GlobalWin TAK68 CPU fan (dual fan, ball bearing 5200RPM max each)
MSI KT4A-V (VIA KT400 chipset) BIOS ver. 2.3 date: 09092004 (with MSI Core Center)
512MB DDR333 mem (2x256MB)
Inno3D GeForce FX 5200 128MB with AGP8x w/ TV out
80GB Maxtor 7200RPM 1x133
40GB Seagate 5400RPM 1x100
LiteON LDW 411S DVDRW 40x12x40
LITE-ON XJ-HD166S DVDROM 16x
Pinnacle PCI PCTV Rave TV tuner/capture card
OS: Windows XP SP2
The Reply:
Dear Guillem,
Thank you for contacting Asian and Pacific AMD Technical Support Centre.
I can confirm that the temperatures ranges from 40° - 55° C in moderate usage and with a higher workload around 65° C, but never over 70° C.
What the correct voltage is concerned there are three models of the Athlon XP 2400+. If you have the CPU with the OPN AXDA2400DUV3C the
voltage should be 1.60V otherwise it is 1.65V.
It seems your system would overheat dangerously when set to the right voltage. I would suggest, you do check if the heatsink /fan is installed
properly.
You may find a different reading after upgrading your BIOS.
* Please make sure to download the right BIOS version for your motherboard.
Then, please, make sure that your processor Athlon XP 2400+ is configured in BIOS as follows:
- FSB speed to 133MHz (It is a bidirecctional bus, the full speed would be 266)
- CPU multiplier of 15x
- CPU voltage of 1.65V (1.60V if OPN = AXDA2400DUV3C)
With these settings the clock frequency of the processor should be 2000 MHz.
And finally you can test the CPU on another system to establish if the processor or the motherboard is responsible for the problem . If no other system is
available to you then ask your retailer/reseller to test it for you.
Given the case that the processor is faulty, we inform you that the PIB processors (box processors) have 3 years warranty, whilst OEM processors (tray processors) have only one year. In both cases the first year is given by the reseller and the PIB processors second and third years are served directly by AMD.
If you have any further questions, please, do not hesitate to contact us again.
Kind regards,
Roberto Erler
Technical Support Engineer
Spain: 900 99 71 21 (Número Gratuito)
France: 0800 908 621 (Numéro Vert)
Germany: +49 89 450 53199
Italy: 800 877 224
United Kingdom: +44 1276 803 299
Yesterday, I increased the CPU voltage to 1.60V (from the default of 1.575) and my temp reading was reduced to 50C at idle (from an idle of 60C) and at full load to 60C (from a full load of 66C). I was not expecting this though. I was expecting that my CPU's temp will increase further. But this is what happened. I guess the RIGHT THING should be the RIGHT THING.
Tomorrow, I will buy a new psu with the brands that you mentioned and I hope that my PC's stability and performance will increase further.
Again thank you very much for your support and all.
:hypecrite: -
Enable port security between Two switches
Hi Everyone,
I connected two switches together via below config
Switch A
int gi0/1
switch mode access
switchport access vlan 10
Switch B
int gi0/1
switch mode access
switchport access vlan 10
They work fine with above config.
I did the Test below
However when i changed Config of Switch B as below
int gi0/1
switch mode access
switchport access vlan 10
switchport port-security
Switch B is unable to ping its default gateway.
Also Switch B is not reachable via SSH.
Port is up up and in STP forwarding state.
Switch B can see Switch A as a neighbour.
Also Switch B is not reachable via SSH.
I know that switchport port-security we use only when connecting to PC.
S does this mean that on above scenario layer 1 and layer 2 are up but layers beyond 3 and above are not reachable like ping,ssh etc??
Regards
MAheshI was just trying to see how the switches behave with this config.Nothing much just exploring the options in the network world
Ideally if you want to connect two switches together in Layer 2, Dot1Q trunking is the way to go. You do not want to put port security because it is useless. -
Fiber connection between two switches
Hi All,
Here is the situation, I have two switches which are SF200 and SG300 and trying to link them up using sfp module ( fiber).
They are both in trunk mode and the connection is up but nothing or no ip traffic goes through it .
I have ensured allowed vlans are correct, native vlan do match but still nothing .
Then i did a port monitor on it ( replicate it to another port) but all I could see was bunch of stp,arp , mdsn and llc traffic. nothing to do with do1q extension.
I used wireshark , would I be able to monitor trunk traffic at all? would the protocol be dot1q ?
However the fiber link works if I plug one of the connection which goes to the sg300 to a fiber convertor and then connect a rj45 cable from the convertor to the sg300 rj45 port. that is the only way which it works. This suggest to me a possible issue with the fiber module on the sg300 however I have tried few differnet modules and still nothing , I did even try the one which is on the sf200 ( working ) and still nothing .
What boggles me is the fact that the link is seen as up and all good by both switches but nothing does go through them.
Any one know what the cause could be ?
ThanksWrong forum, post in "Small Business switches". You can move your posting with the Actions panel on the right.
-
Connecting two Nexus switches with link
Hi,
I would like to connect two nexus switches with a link. Like one c5020 and one c5548p. How do i need to configure the ports at both the switches which will be joined with a fiber cable.
For MDS switches such links becomes E-port and fabric is merged. Not sure what happenes at the Nexus swictches. Any input will be appreciated.
Thanks,Do you have fc modules in each nexus? If so, they act much like the MDS 9148. All ports should be default auto speed and auto switchport mode. Insert fc-sfp's and a regular multimode fc cable between them. Default mode is fc switch.
If that doesn't work, configure the mode on each port as E.
Once done, the fc switch portion of each nexus will merge.
Dave -
Connecting two linksys gigabit switches
Hi,
I just bought a slm2024 (24 port managed Gigbabit switch) to replace an older 100Mbit switch. The old switch had PCs and other switches connected to it. The other switches are EG005W ver. 3. (linksys workgroup 5 port gigabit switches)
With the new slm2024 switch, the PCs have no problems connecting. The problem is the EG005W switches. The port on the slm2024 which connects both switches is dark (the LED is dark - no lights at all). Any thoughts on what is the problem? Do I need to configure something special on the slm2024?
I do have an older 100Mbit switch and if I connect it to the new slm2024 switch, the lights are on and traffic is flowing. It is just the EG005W that does not seem to like being plugged in the gigabit switch. It used to work when plugged in the older 100Mbit switch.
Oh and if I try to plug in two EG005W together, I get the same problem. PCs connected to the 2nd switch cannot communicate out either.
I understand that in the past cross-over cables where needed to connect switches but I thought that new switches no longer require this (even my old 100Mbit switch did not require this for the EG005W to work through it).
Any thoughts on how to fix or debug this?
Thanks for any suggestions.there shouldn't be any configuration needed on the ports of the SLM2024 because they are already "smart ports"
this could be a possible problem between these 2 devices -- have heard of similar problem before bet. a switch and hub but i have forgotten their model numbers -- you would think that since they came from the same manufacturer you will have an easier set-up but sometimes that's just not the case -
Two switches connected with fiber in mode trunk - Problem
Hi to all.
Iam new in the forum, and my english is bad.
I want to post a problem. I have two switches connected with fiber in mode trunk, in the switch C3550 i have this configuration:
interface FastEthernet0/1
description Enlace LAB Medicion
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
duplex full
spanning-tree portfast
In the switch C2960 this configuration, on interfaces Fa0/48, Giga0/1:
interface FastEthernet0/48
switchport trunk allowed vlan 1,20,229
switchport mode trunk
spanning-tree portfast
interface GigabitEthernet0/1
switchport trunk allowed vlan 1,20,229
switchport mode trunk
media-type sfp
duplex full
spanning-tree portfast
The problem:
The ip phones with Voice vlan (vlan 20), not find the DHCP server located in the data vlan (vlan 229)
However, using the command:
#switchport trunk native vlan 229
The result is the voice vlan works, but the data vlan not and viceversa depending if the native vlan 229 is present.
I will appreciate any suggestion.leolaohoo.
The configuration on ports switch C2960, have the mode access with voice vlan 20:
interface FastEthernet0/1
switchport access vlan 229
switchport mode access
switchport voice vlan 20
spanning-tree portfast
interface FastEthernet0/2
switchport access vlan 229
switchport mode access
switchport voice vlan 20
spanning-tree portfast
I will remove from trunk links:
spanning-tree portfast
Thanks alot. -
Connecting two cisco ESW 500 series switches.
Hi Experts,
I have a basic knowledge of network and need some help.
I have two cisco ESW 500 series switches and i want to connect them together.
Q1 # Which type of cable i should use to connect these two switches CrossOver or fiber...What is the advantage of using Fiber over CrossOver. ?
Q2 # What are the marked ports in the image used for...???tech spec,
Traditionally you would use crossover to connect switches. Most modern network devices have Auto-MDIX which allows the device to connect using either crossover or straight through.
The ports on the right can be used for uplink or as regular network ports. On the 10/100 versions the ports on the right are usually Gigabit, thus making them more suitable for uplink to another switch, etc.
Please mark this thread as answered or reply if you have any additional questions.
- Marty -
Connecting two san switch in cascade
I am planning to connect two San switch in cascade because the 2/16 san switch that I am using now only have one unused port and I am planning add four server more. So my less expensive solution is using a second 4/16 switch that I have.
- My questions
How I do that ?
Do I need a special license?
Do I need some other change in the ports configuration for this purpose?
Some care I must take?
Thank you
EhabThe answers to your questions are really going to depend on the make and model of your switches.
Some switch types require a license to configure E_Port (switch-to-switch) functionality, but most do not. Whichever port(s) you use to make the connection will need to either be configured as an E_Port or configured in a mode that will allow it to auto-negotiate itself to E (this could be a GL_Port, Gx_Port, or U_Port depending on switch vendor) after the switches establish communication.
If the switch that you are adding has some zoning defined on it that is different than the existing switch then you may run into some conflicts so it is often best to just clear the zoning config on the switch that is being added. Finally, you would want to make sure that each switch has a unique Domain ID otherwise the two switches will segment and not merge. By default, most switches are set to Domain ID 1 so just make sure they are both not set to 1.
hth.
-j -
How do I uninstall an itunes account from an iphone? By accident we connected two phones to the same itunes account and now whenever we download both phones receive the download.
Settings > iTunes & App Store > Automatic Downloads > switch off what you don't want here
-
Using Trunking 1.3 to create a trunk accross two switches
Hi:
I have installed Solaris Trunking 1.3 on my SF 880 which is running Solaris 10. It has two CE interfaces which i have configured in one trunk. Failover works fine when I connect them to a single Nortel 8000 switch. The problem is that I can't get failover working properly when I connect one CE interface to a Nortel 8000 switch and the other CE interface to another Nortel 8000 switch. Should this work? I have seen many references, eg in the Solaris Trunking 1.3 documentation, that actually says you can't create a trunk accross switches but i also found BUG ID 5079123 which says you can.
By the way I can't use the version of trunking software that is bundled with Solaris 10 because it doesn't support the CE interfaces.
Cheers
SteveThanks for your reply. I should have mentioned that i don't need load balencing over the trunk to work. I just need failover to work. In fact that is just what the bug id says i should be able to do across two switches. Here's a copy of the bug id:
Bug ID: 5079123
Synopsis: Trunking 1.3 to support L2 failover across switches
Category: enet_trunking
Subcategory: softwareState: 10-Fix Delivered
Description: Due to overwhelming requests to support L2 failover solution for Sun NIC across two switches. This is not trunking or Link aggregation feature as it breaks the standard of all trunk members connect to one switch.
Requirements are :
1. provide Layer 2 failover similar to IPMP(layer 3) and yet be simple enough to configure.
2. No loadbalancing.
3. Connect across two switches. and when one switch/nic fails, the traffic moves seemlessly and instantly.
4. Failback: When the failed link is back online, traffic moves back to original link. Date Modified: 2004-09-08 06:13:32 GMT+00:00
Cheers
Steve -
Can I create a port channel to two switches that are not stacked?
Two switches, not stacked, but connected together via 802.1q trunk.
Server with four NICs, capable of trunking and LACP.
Can the switches be setup to have an etherchannel between the two switches and the server?Hi,
In short NO
You would need to connect your server to only ONE switch if you want all 4 nics in the same TEAM.
You could use 2 TEAMS and put 2 nics in each forming a 2 port etherchannel to each switch
Regards,
Alex.
Please rate useful posts.
Maybe you are looking for
-
How to connect my wireless printer (HP 1102w) to my ipad2
How to connect my printer (HP 1102w) to my iPad 2?
-
I've downloaded Photpshop elements 13 : how can I open the application ?
I've downloaded Photpshop elements 13 : how can I open the application ?
-
Hi All, I have a scenario where my sender is a SAP system and receiver is a HTTP url. I need to post IDOC from SAP system to the URL .No mapping is required, but i need to send a mail with the status of HTTP POST (e.g. 200 for success, 401
-
We are sending our PO's to ARIBA. Now we want to use XI to do the job of transmitting our PO's from our R/3 systems to ARIBA supplier network. (IDOC ---> XI ---> Ariba) I have been asked to use the CIDX - CXML data structure. But I am confused here.
-
I am looking for Demo Voltage Read VI
I have just begun with labview and according to a tutorial I am looking for Demo Voltage Read VI . where can I find this? Solved! Go to Solution.