Question Re: connecting 2960C switch to 3750 stack, max number of VLANS limit...
Hypothetical question: Let's suppose for example I've got a 3750 switch stack in a data center with over 300 VLANs defined on the 3750 stack, and that stack is also my VTP domain server. I wish to connect a small compact 2960C switch (which has a max limit of 255 VLIDs) as a VTP client to the 3750 stack's VTP domain and have the port at each end of this uplink connection set up to be an 802.1q trunk, but limit the VLIDs trunked to the 2960 to just a small handful (let's say just 3 or 4 vlans) via for example something like "switchport trunk allowed vlan 1,2,11,18" on the uplink port of the 2960C switch. Will the mere fact that there are hundreds of VLIDs present in the vlan configs on the 3750 stack confuse the little 2960C switch's max 255 vlans limits? Or will the 2960C with its "Lan Base" software happily show all 300+ vlans present in the parent switch stack in a "show vlan" command but simply only let you activate up to the 255 limit locally on that switch?
Normally I'd just use a 3560C switch with IP Base software for this purpose and not worry about any vlan max limit, but we're having to penny-pinch the project and save a few hundred dollars on this compact switch purchase and I've never used the 2960 family before. The small compact switch will be used to host a non-Cisco, 3rd party wireless LAN controller with several APs that will have a handful of different SSIDS, each on a separate vlan, and will not be located in the data center, but in another building connected by a fiberoptic link that will carry the "trunk".
EDIT: I found an old discussion thread where someone else was faced with a similar scenario, and he discovered that even with using "switchport trunk allowed..." and "switchport trunk pruning..." commands on the interfaces at both ends of the link, that the 2960 switch would still fall out of VTP client mode into transparent mode, which make you lose the benefit of having centralized management of a VTP domain. Seems the VTP protocol will always publish the full list of vlans from the server and this blows the mind of the small switches which drop into VTP transparent mode because they cannot handle all that many spanning tree sessions. Looks like the 2960 simply cannot be used in a high-vlan-density network if you wish to preserve central VTP domain management features. Rats.
The house network machine can browse and playback/stream video fine, however at the same time the machine on the wireless shows significant slowdown when browsing the web.
The issue is defiantly on the wireless side, If i plug a machine directly into the switch and assign it a static ip, i do not get slowdown, so this is happening before it reaches the poe switch.
So many factors affect the way to stream data up and down wireless. Sure, I have seen >40 clients on 802.11a AND 802.11b radio of a single 1140 AP. But this is not good. Why? Because wireless is a very "noisy" environment. When one talks, everyone else has to stop, listen and waits for their turn. The > 80 wireless clients connected to the 1140 AP had a detected maximum speed of 11 Mbps and they couldn't get any higher than that. They couldn't get any lower than 11 Mbps because I've disabled lower data rates.
You said you hard-code the channels to 1, 6 and 11 but what is the co-channel interferrence like in your wireless environment?
Similar Messages
-
Switch on 3750 stack lost connectivity
Hello
Users on switch 6 were unable to connect to the network for a while and we saw the switch change status to 'READY' for no apparent reason in the logs (it was working fine before.) Please see attached file for the switch logs. Any ideas on what might have caused this?
Thanks
Amy
3750x, 6 switches in stack. Software version 12.2(58)SE2Hi,
It appears that some one has disconnected and reconnected the stacking cables and that is was causing the logs.
does "sh switch details" show all the stacking cable are connected properly?
HTH -
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. -
Hello,
I have an Spanning tree problem when i conect 2 links from Switch DELL M6220 (there are blades to virtual machines too) to 2 links towards 2 switches CISCO 3750 connected with an stack (behavior like one switch for redundancy, with one IP of management)
In dell virtual machine is Spanning tree rapid stp, and in 3750 is Spanning tree mode pvst, cisco says that this is not important, only is longer time to create the tree.
I dont know but do you like this solutions i want to try on sunday?:
Could Spanning tree needs to work to send one native vlan to negociate the bdpus? switchport trunk native vlan 250
Is it better to put spanning-tree guard root in both 3750 in the ports to mitigate DELL to be root in Spanning Tree?
Is it better to put spanning- tree port-priority in the ports of Swicht Dell?
¿could you help me to control the root? ¿Do you think its better another solution? thanks!
CONFIG WITH PROBLEM
======================
3750: (the 2 ports are of 2 switches 3750s conected with a stack cable, in a show run you can see this)
interface GigabitEthernet2/0/28
description VIRTUAL SNMP2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4,13,88,250
switchport mode trunk
switchport nonegotiate
logging event trunk-status
shutdown
interface GigabitEthernet1/0/43
description VIRTUAL SNMP1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4,13,88,250
switchport mode trunk
switchport nonegotiate
shutdown
DELL M6220: (its only one swith)
interface Gi3/0/19
switchport mode trunk
switchport trunk allowed vlan 4,13,88,250
exit
interface Gi4/0/19
switchport mode trunk
switchport trunk allowed vlan 4,13,88,250
exitF.Y.I for catylyst heroes - here is the equivalent config for SG-300 - Vlan1 is required on the allowed list on the catylyst side (3xxx/4xxx/6xxx)
In this example:
VLANS - Voice on 188, data on 57, management on 56.
conf t
hostname XXX-VOICE-SWXX
no passwords complexity enable
username xxxx priv 15 password XXXXX
enable password xxxxxx
ip ssh server
ip telnet server
crypto key generate rsa
macro auto disabled
voice vlan state auto-enabled !(otherwise one switch controls your voice vlan….)
vlan 56,57,188
voice vlan id 188
int vlan 56
ip address 10.230.56.12 255.255.255.0
int vlan1
no ip add dhcp
ip default-gateway 10.230.56.1
interface range GE1 - 2
switchport mode trunk
channel-group 1 mode auto
int range fa1 - 24
switchport mode trunk
switchport trunk allowed vlan add 188
switchport trunk native vlan 57
qos advanced
qos advanced ports-trusted
exit
int Po1
switchport trunk allowed vlan add 56,57,188
switchport trunk native vlan 1
do sh interfaces switchport po1
!CATYLYST SIDE
!Must Explicitly allow VLan1, this is not normal for catalysts - or spanning tree will not work ! Even though it’s the native vlan on both sides.
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,56,57,189
switchport mode trunk -
Hi,
I have 3 3750 switches: WS-C3750G-12S-S, WS-C3750G-16TD, WS-C3750G-16TD.
They are connected via Stack Cable in half-duplex mode.
I have a 10GE module(X2-10GB-LR=) on WS-C3750G-16TD.
the bandwidth of the logical switch should be 32Gbps. My question is about oversubscribe. totally there are 44 Giga ports. how these 44 Giga ports and 1 10Giga port share this 32Gbps? And what's mean half-duplex for stack mode?
Thank you very much.
Regards,
ShaHello Sha,
this might not directly answer your question, but the way I understand the StackWise technology is that the switches in the stack form a logical ring, with a maximum backplane throughput of 32Gbps, as you already said. Each packet on each switch is load-balanced across the ring. The ring/backplane supports 32Gbps max, if you have more ingress bandwidth than that, the 32Gbps will still be the limit.
I found this article, which explains some of the issues, you might want to have a look at it:
Cisco Catalyst 3750 stackable switches
http://www.networkworld.com/reviews/2003/0811revcisco.html
HTH,
GP -
My first questin has to do with the Console port in a stack. It has been observed that the console port on the master switch is designated "Con 0". So my question is how do I access the other con ports on member switches to configure them?
The second question is what is the mechanism for statically numbering all of the switches in a stack so they are always numbered the way I configure them to be ie in case of some disaster or power outage I need to know that switch 5 will come back as switch 5 even if switches 1-4 do not come back to life.
Thanks1. When you connect via a console cable to any of the switches in a stack you always access the stack master. The stack master is the only switch that can be used to configure the stack and its members. Assuming you have a stack of two 48 port (10/100/1000) switches; switch 1 is the master and switch 2 is a stack member. If you want to configure ports on switch2 you just use the appropriate port numbers (int gig 2/0/1 to 2/0/52). If for some reason you need console access to a stack member you can use the 'session ' command; however, do keep in mind that this access will be limited to only show and debug commands. All configuration is done via the stack master.
2. You can renumber a switch to ensure that it always retains the same number by using the 'stack renumber ' command. For example to renumber switch 2 in a stack to 3 you will use 'switch 2 renumber 3' global configuration command.
The following URL has great information on how to manage switch stacks.
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_guide_chapter09186a008050245f.html#wp1170757 -
Hi
I have Stack of 7 3750 Switches. In that Switch 1 is master with 15 Priority and other switches are Member but because of some reason switch 1 rebooted and then Switch 2 becomes Master because it’s having 14 Priority.
We have 2 uplinks which connected on switch 1 (1/1/1) and switch 6 (6/1/1) Tengig port. Also we have 4 AP connected on switch 6.
So we observed that the Switch 1 came up and after that 3 AP is disconnected from WLC. if we disconnect the uplink port on Switch 1 (1/1/1) AP will connect the WLC and using uplink 6/1/1 but if we connect uplink port 1/1/1 and disconnect the uplink port 6/1/1 all 4 AP will disconnect from Network.
We try to connect the Uplink 1/1/1 to Switch 1 other port 1/1/2 but face the same issue. So we reconnect the port 6/1/1 and used the same link which connect on 1/1/1 to switch 7 (7/1/1) and AP will connect on WLC. So as per this troubleshooting we thought some issue with Network Module or Switch of Switch1.
So we Swap the Network module between Switch1 and Switch7 and connect the uplink on 1/1/1 but face the same issue and if we connect the same uplink on Switch 7 Ap connect to WLC.
So we thought that Switch is having issue. But before raising an RMA for Switch we observer 1 more thing that. Earlier that when the Switch 1 is Master all 4 AP's connected to WLC and working fine but when the Switch1 became rebooted and Switch2 became Master issue started. So we rebooted the Switch 2 and make switch master and found that while connecting on port 1/1/1 of Switch port AP's are able to connect to WLC and Issue resolved.
So I wants to know that is there any requirement that If the high priority switch rebooted and after came up it should not be Master then connected uplink will not work.
Also let us know what’s happen if the high priority switch came up in network. Means it’s will became Master or Menber.Just now i Found one bug which is matching on our issue.
3750x stack fails to update ARP table after reboot causing traffic loss
BUG ID:-CSCtz98066
Symptoms: When the master switch (Switch A) is reloaded or loses power and
rejoins the stack as a member switch, any traffic stream being sent through
Switch A is unable to be received by the destination because the newly joined
member is not able to establish an ARP entry for the next hop router/switch.
Debugs confirm that Switch A does not send a GARP/ARP for the next hop, though
traffic continues to be sent to the switch.
Conditions: The symptom is observed when only Switch A has a physical
connection between the source and destination router/L3 switch. The newly
elected master (Switch B) does not.
Workaround: Ping destination from Switch A, forcing ARP request/response.
Also affected version is 12.2(58)SE and15.0(1)SE2 and we are using IOS 12.2(58)SE.
So we are going to upgrade the devices by this weekend with IOS 15.0(2)SE5.
Will update you once we upgraded the switches. -
Power Redundancy problem for cisco 3750 stack switches
Hi Team,
I have installed and configured cisco 3750X series switches in stackwise. Those are having dual power supply.
Power redundancy test performed:
1. Removed one of the power supply and inserted it back.
2. once the first power supply is ready, removed another power supply and switch got rebooted.
please find the below stack-power output:
JP2-RDC-DIS-02#sh stack-power detail
Power Stack Stack Stack Total Rsvd Alloc Unused Num Num
Name Mode Topolgy Pwr(W) Pwr(W) Pwr(W) Pwr(W) SW PS
Powerstack-2 SP-PS Stndaln 700 477 223 0 1 2
Powerstack-1 SP-PS Stndaln 700 477 223 0 1 2
Power stack name: Powerstack-2
Stack mode: Power sharing
Stack topology: Standalone
Switch 2:
Power budget: 223
Power allocated: 223
Low port priority value: 22
High port priority value: 13
Switch priority value: 4
Port 1 status: Not connected
Port 2 status: Not connected
Neighbor on port 1: 0000.0000.0000
Neighbor on port 2: 0000.0000.0000
Power stack name: Powerstack-1
Stack mode: Power sharing
Stack topology: Standalone
Switch 1:
Power budget: 223
Power allocated: 223
Low port priority value: 22
High port priority value: 13
Switch priority value: 4
Port 1 status: Not connected
Port 2 status: Not connected
Neighbor on port 1: 0000.0000.0000
Neighbor on port 2: 0000.0000.0000
Can anyone help what went wrong here?
Thanks
ManishCosmetic bug
CSCui21029 3750X Stack no standalone stays in running configureation as standalone
Symptom:
When you are configuring a 3750x stack and initially putting it into a stack ring topology by configuring the following.
Switch(config)#stack-power switch 1
Switch(config-switch-stackpower)#sta
Switch(config-switch-stackpower)#no stan
Switch(config-switch-stackpower)#no standalone
You will see that in the running configuration it shows up as standalone mode
stack-power switch 1
switch mode: standalone
stack-power switch 2
switch mode: standalone
Conditions:
3750X stacks with any license level
Workaround:
none -
Visibility of 3750 Stack Switches on SCH Portal
We have implemented Smart Call Home in one of our customer network. Customer has 34 3750 switches configured in stack. We have done SCH configuration for all 34 devices, problem over here is on SCH portal under “Global Summary Report” only 17 switches are reflecting however in “Device Report” all 34 devices are reflecting.
Can you please confirm/suggest to whom we can coordinate to resolve “Global Summary Report” discrepancy issue.When a stack boots, each stack of switches determines a master switch. The master switch is the switch handling coordination for all of the other switches in the stack and outside communication.
It looks like the global summary report is reporting only the master switch for the stack. This makes sense to me. All of the other switches in the stack are suppose to be invisible to the outside world and the stack is supposed to operate as a single virtual switch. Since it is a virtual switch, each virtual switch should be counted once as a single entity.
All of the devices in the stack are available for view if you drill down, but from a Smart Call Home view, only the stack master is communicating with Smart Call Home.
But the bottom line is this is only software and can be written differently if it is too confusing to the customer. -
Magic number mismatch: bad mzip file in 3750 stack switch
Hi All can anybody help me in this error msg
"magic number mismatch: bad mzip file"
I am trying to upgrade the switch with"c3750e-ipbasek9-tar.122-55.SE5.tar" in 3750 stack switch it is showing this error msg while booting
thanks in advanceHi,
The reason you are getting this error message on the switch is a corrupt or wrong IOS image "c3750e-ipbasek9-tar.122-55.SE5.tar".
If the switch is in rommon mode, and you have any other image in the switch, boot it using that image. Once the switch is up, download and copy the correct IOS image once again on the switch and try to upgrade.
If you need help in finding the correct IOS image, give me the exact switch model number, i will help you with that.
But forsure the image is wrong or corrupt and that is why you are getting this error.
Thanks
Ankur
"Please rate the post if found useful" -
2960x - stack cables connected while switches power on. SFP ports - status unknown
Connected 2960x uplink using SFP ports both stacks and all 4 ports worked good.
Remote tech connected last stack cable between first and last switch, in 2 different 2960x stacks of switches, while switches were powered on. A longer stack cable was needed. 3 of 4 SFP ports did stopped communicating.
One stack SFP stayed up in switch 2, not master. Completed reload - other SPF connected in switch 4/0/52
Second stack no connection on either SFP, remote tech power cycled switches.
After power cycle one SFP worked in Master 1/0/52, other switches SFP ports show "unknown" when inserting SFP.
Configured port 48 on stack with issue and connected second uplink just fine.
Has anyone experienced this with the SFP's?
- GLC-T P/N 30-1410-03
Looking for documentation on reccommending procedure for connecting stack cables while switches should be powered off or not.
Thanks,Opened Cisco TAC case. the following bug was found.
the two different HBRN's below require 2 different IOS and they cannot be in same stack.
https://tools.cisco.com/bugsearch/bug/CSCur56395
switch#sh ver | s Hardware Board
Hardware Board Revision Number : 0x05
switch#remote command 2 sh ver | s Hardware Board
Switch : 2 :------------ Hardware Board Revision Number : 0x05
switch#remote command 3 sh ver | s Hardware Board
Switch : 3 : ------------ Hardware Board Revision Number : 0x12
switch#remote command 4 sh ver | s Hardware Board
Switch : 4 :------------Hardware Board Revision Number : 0x12
From Cisco.
Developers have recommended to upgrade the IOS version of switches with a Hardware Board revision Number below 0x10 to the release 15.0(2.0).EX5ES. this is the one attached to this email and should be applied to switch 1 and 2.
For switches with a Hardware Board revision Number above 0x10 to the release 152-2.4.E1ES, which I will send you right away. This should be done on switch 3 and 4.
Now, If you load the engineering special, you will need to do a full power-cycle (physically unplug the power and plug it back in for every single switch). A simple ‘reload’ will not resolve this.
The same must be done on Switch-0. For this stack you will only need to load the image attached to this email since all the Hardware Board revision Numbers are lower than 0x10.
done. -
3750 Cross-stack equal cost routes across different switches in the stack
Hello,
If I configure a cross stack ethernet channel does it support link aggregation to increase bandwidth or is it just support for link failover?Answer is support for link failover.
The EtherChannel on multiple switches in the Cisco Catalyst 3750 stack is called cross-stack EtherChannel.
If a link within an EtherChannel fails, traffic previously carried over that failed link changes to the remaining links
within the EtherChannel. A trap is sent for a failure, which identifies the switch, the EtherChannel, and the failed link.
Inbound broadcast and multicast packets on one link in an EtherChannel are blocked, and cannot return on any other link of the EtherChannel.
HTH
Regards
inayath -
4900 M Switch with 3750 FiBer connectivity
Hi,
We need to connect following switch over DarK Finber
4900M with this fiber
<TR style="HEIGHT: 15pt" mcestyle="height: 15pt;">
<TD style="WIDTH: 88pt; HEIGHT: 15pt" height=20 width=117 mcestyle="width: 88pt; height: 15pt;">10GBase-LX4
or
10GBase-LR
Other end we are having 3750-48 TS with this module :1000BaseSX SFP
Will the above fiber module are compatible ?
Br/Subhojiton 4900M side: we have any one of them : 10GBase-LX4,10GBase-LR ( Which end physical termination SC)On 3750 Side: we have 1000BaseSX SFP ( switch end physical termination LC)
Not remotely compatible for two reasons:
1. One end is LR and the other end is SX. Both has to be the same, either LR-LR or SX-SX. Not both.
2. One end is 10 Gbps and the other is 1 Gbps. Both end has to be same, either 10 Gbps or 1 Gbps.
In case the same is not compatible, what is the possbile workaround
The 4900M can support CVR-X2 module. So if you have WS-X4908 line card, you just get one CVR-X2 module and you should be able to use the following 1Gbps SFP modules:
GLC-T (1000BASE-T)
GLC-SX-MM
GLC-LH-SM
GLC-ZX-SM
GLC-SX-MMD
GLC-LH-SMD
GLC-BX-D
GLC-BX-U
CWDM SFP
DWDM SFP
DWDM SFP (add.)
GLC-EX-SMD
(CPN 10-2624-01
or later only)
GLC-ZX-SMD -
I'm new to Cisco switches.
I need to connect two 3750G stacks. One stack consists of 3 x 3750G-48PS and 2nd stack is 3 x 3750G-24TS. Since all switches have 4 SFP ports I would like to use them to create 3 3Gb etherchannels in a full mesh and redundancy.
stack1 Gi1/0/49 - stack2 Gi1/0/25
stack1 Gi1/0/50 - stack2 Gi2/0/25
stack1 Gi1/0/51 - stack2 Gi3/0/25
stack1 Gi2/0/49 - stack2 Gi1/0/26
stack1 Gi2/0/50 - stack2 Gi2/0/26
stack1 Gi2/0/51 - stack2 Gi3/0/26
stack1 Gi3/0/49 - stack2 Gi1/0/27
stack1 Gi3/0/50 - stack2 Gi2/0/27
stack1 Gi3/0/51 - stack2 Gi3/0/27
Is this overkill or am I headed in a right direction? I have only the default VLAN so I understand that only one etherchannel is used for cross stack connection. Will this achieve auto failover?
FredNot sure what you mean by "if we brought down the switch hosting it" , if you mean one switch in the stack then you would not lose your connection . The etherchannel would consist of one connection out of each switch in the stack on one etherchannel , the data would continue to flow over the other 2 links in the etherchannel. If you have one etherchannel consisting of one connection out out of each switch in the stack then you have 3 redundant gigbit connections , highly unlikely you would lose all 3 and this simplifies the config by only having one ehterchannel and saves money by not having to buy so many sfp gbics.
-
Hi,
We have a set of users on the cisco 3750 switch. This needs to be connected to an asa where the gateway resides.
I am bit confused on the connection configuration between asa & 3750.
Should i just configure a port on 3750 to vlan 100 & physically connect it to an interface on the asa , while the asa interface gets the layer 3 ip address.
3750:-
int gig1/0/1
des Connection to ASA
switch mode access
switch access vlan 100
ASA:-
interface GigabitEthernet0/1
nameif LINK1
security-level 100
ip address 172.30.10.1 255.255.255.0
Is the above correct? What else would i need to do if the users connected to 3750 need access via the ASA.
Thanks in advance.Hi,
Are you saying that you only have Vlan 100 on the 3750 and no other Vlans? In that case it would seem fine presuming you have the free ports on the ASA to support this setup.
In the long term its not a good idea since you are going to run out of ASA ports pretty soon (if you do this for many Vlans on multiple switches perhaps). If you have several Vlans which L3 gateway should be on the ASA you would need to have a Trunk to the ASA to conserver ports on the ASA (unless ofcourse some Vlan alone requires a Gigabit link to the ASA with no other Vlans on that link)
The most common problem I see here on the forums related to a setup where there might be a L3 configured 3750 on the internal network and ASA in front of it at the edge of the network is the fact that users have activated routing on the L3 switch and configure Vlan interface (SVI) for their Vlans on the 3750 which are used as gateways for some of the networks and then start expiriencing problems with asymmetric routing with the ASA.
I guess you can avoid such problems by setting up the network in one of these ways
A L2 Switch network with different user Vlans which all have their L3 gateway on the ASA. Provided that the ASA models throughput will not be a problems.
A L3 Switch or router in the LAN acting as the L3 gateway for all the user traffic. This would naturally mean ASA could not control traffic between the networks like in the first setup.
A L3 Switch or router in the LAN acting as the L3 gateway for all the user traffic. Furthermore different LAN/DMZ networks are divided in their own VRFs (own Routing Tables instead of the global routing table). This would enable you to attach each Vlan interface (host gateway) to a specific VRF (routing table) on a single L3 device and therefore separate their traffic and bring it through the ASA (as each VRF could have their own default route and link to the ASA)
There are other options naturally that mix these up with eachother but I would say that the above are the most common ones that I have seen.
But to shortly answer your question again, the configuration you suggest seems to be fine (but perhaps not optimal in the long run)
Hope this helps
- Jouni
Maybe you are looking for
-
I have recently started using iCloud on my laptop syncing it with my iPad. When the syncing process starts it stops and gives me a message something like: You do not have permission to sync this folder. Then it wants me to unlock and gives other s
-
I had a nifty note taking program with a launch line in the Tools Tab of the browser ... I offered six separate pages to take notes ... I cannot remember the name of the program and when I updated the Mozilla Firefox Browser to the latest version abo
-
Hello All, So I am finishing up my video project and for some reason I am unable to hear the audio for my project... The mute buttons are not checked so I am not sure what the issue is, when I open another one of my projects the auido plays but for t
-
Airport Extreme no longer see's Epson R320 Printer
All of a sudden i cannot print through Airport, i have to plug into USB port on my Mac Pro. If I try to print over the network its shows my printer offline. Any ideas.
-
I have a situation where using an attachment will not work - because of the sensitivity of the item being stored. It has to be made available to a subset of participants within the process instance. I can use ScreenFlow mapped to a JSP to upload the