I currently have 3 core switches on my campus. They are 6509 catalyst switches. They currently are not interconnected to each other.I want to interconnect them to each other. The IP addresses of each core sit on a interface Loopback500. [code] How can I interconnect each core to each other and what IP scheme could I use. I want them to be straight L3 to each other.
connecting a 5548 pair to our core 6509s. Just want to be sure we don't introduce any issues into the network.The 6509's are connected and perform all the routing. Essentially, we're moving away from a 3750 stack in the data center and the 5548s are the replacement. We'd want to limit the vlans to the specific server network vlans. Our current setup is a port channel between the 3750 and each of the 2 6509s for redundancy. I'd like to use the same functionality when we connect the 5548's but I'm looking for what the config should look like to ensure no spanning tree loops are introduced and that it is configured optimally.
If I have two stackable switches one switch uplinks to one 6509 core switch and the other connection uplinks to another 6509 core switch, and also the other stackable switch does not connect to the core switches. Because I am using hsrp and also we are not using vss then one uplink to the core is not in used only ones is so then how does creating an etherchannel between does two uplinks to both core switches benefit me in anyway such as more bandwith and using both uplinks at the same time or I'm I wrong?
If I have two stackable switches were only one stackable switch has two uplinks one uplink goes to one core 6509 switch and the other uplink goes to the other 6509 core switch can a Layer 3 etherchannel be used if each uplink go to a different core switch, by the way hsrp is running between both switches and also can you give an example how data will be routed from the stackable switch through the ethernetchannel to one of the core switch accross the WAN to another core switch?
I have a 3750X four-switch stack acting as the core of a fairly simple LAN. All I need to achieve (and this seems inordinately hard, but it is entirely likely that I'm just being dense) is to get access to the internet through my core switch, through the firewall and out through my VSAT. I've spoken at some length with the firewall providers (Cyberoam) and they tell me all I need to do when I migrate onto my new system (Cyberoam is currently in place at the entrance to our existing LAN) is change the local IP address of the Firewall, plug in the new switch to the LAN port, and away I go. Tried that, didn't work, so obviously I'm missing something.
we are using cisco 6509 series switches as core switches. and Cisco 4510,4507 series switches as edge switches. all the vlans are created at core switches and propogating to edge switches through VTP. we are using OSPF as routing protocol at core switch for internal routing. till now we are using 4510,4507 switches as layer 2 switches. Since, 4510 & 4507 switches are hign end swithces i want use them as layer 3 switches instead of layer 2.if i change these switches from layer 2 to layer 3 does it make any impact on our network or better to keep them as layer 2 switches.if i change these switches to layer 3 is there any advantage i will have.
we have two 6513 core switches redundant to each other by using HSRP and MST. Currently we have a problem in a CPU as it's high in both cores as appeared in the following logging message:
In my network i have two 6509s connected with L3 etherchannel. i have created saparate vlans in the two 6509s with different switches.now i want to use one vlan in 1st 6509 in the 2nd 6509 how can i use ...
I am working for a customer on an enterprise site containing many 6509's. We have built a test environment and upgraded a chassis from sup720 running 12.2(18)SXF15 to VS-S2T-10Gb running 12.2(50)SY on the management card. I have noticed and so has the customer that there are many commands missing or added and they want an expalnation of these. I can do some of them easily, change syntax etc but for instance it has added a table-map, 50 vlans with a large MTU and large COPP policy.
What are these ?? and also is there a quick way resource etc to find out why the commands have been added/removed, for instance-mls ip cef load-sharing full is missing--
We have a Cisco 3750G Core switch which has physical connections, each configured as trunks to two HP Access switches. The client who uses these access switches would like to put a link between the two, but this would create a loop.
The company I work have finally decided to enter the 21st century and invest in a new telephone system (Interactive Intelligence) to replace the legacy system which has served us well for the past 10 years. The project has only just started and involves upgrading sections of CAT3 cabling to CAT6, replacing Cisco 3550 switches in one area of the building with Cisco 4507 switches and upgrading our Core switches with Cisco Nexus 7010's. The area that concerns me most is enabling the network for qos as I have very little experience with it. At the moment Im trying to read as much documentation as I can on QOS to bring myself up to speed.
The access layer switches will consist of a mixture of Cisco 3750 & 4507 switches connected to Cisco Nexus 7010 switches which will form a collapsed aggregation & core layer.
Basically, how I should approach this daunting task of making sure the network will support VOIP.
We are using CISCO Catalyst 6500 switches as collapsed core/distribution switches (2 layer architecture). I want to connect approximatly 10 application servers to the network. Can I connect the servers directly to the catalyst 6500 switches using WS-X6148E-GE-TX line cards? The other option is to use access switchs and then connect the servers to the catalyst 6500 through access switch(Catalyst 3750).
recommend a cisco core switch and access switches in IPTV network infrastructure?I was ask to implement a network for IPTV system but i don't have idea what will be the model i will use.
I configure 3750 stack switch as core and 2960 stack switches as access layer switches.I connected my laptop to one of my core stack in VLAN 10 and I am pinging to one of my server in VLAN 1. What will be the minimum latency at the time of inter VALN routing
I've been fighting what seems to be an increased number of outqueue drops on our core stack and edge switches for the last 3 or 4 weeks.(The core consists of a stack of 5 3750s in 32-gig stack mode. The wkgrp switches are 3560s. all are at 12.2.52) The wkgrp switches are directly connected to users. We use Nortel IP phones with the phone inline with the user PC. auto-neg to 100/full. [code] However I have tried turning off QOS on a couple of workgroup switches (no mls qos, but left individual port configurations the same) but am still seeing drops.Since I have disabled qos on the switches in question (no mls qos) (not the core tho) I am presuming these commands have no affect on the switch operation and therefore cannot be related to the problem. With QOS turned off one would presume that it is general congestion - especially at the user edge where busy PC issues might contribute. So I wanted to see if I could see any instances of packets in the output queues building up.
I wrote some scripts and macros that essentially did a snapshot of 'show int' every 20 seconds or so, and looked for instances of 'Queue: x/' where x was greater than zero.What I found after several days of watching the core stack, and a few of the workgroup switches that are most often displaying the behavior, was that I NEVER saw ANY packets in output queues. I often saw packets in Input queues for VLAN1, once in a great while I would see packets on input queues for fa or Gi interfaces, but NEVER on output queues. [ code] Additionally, when I look (via snmp) at interface utilization on interfaces showing queue drops (both core and wkgroup), they are occurring at ridiculously low utilization levels (as low as 4 to 8%). I've tried to look for microbursts between the core and a wkgroup switch where the core interface was experiencing drops, but haven't seen any (using observer suite). [code] While the queue-drop counts aren't critically high at this point, they are happening more frequently than in the past and I would like to understand what is going on... In most cases, no error counters are incrementing for these interfaces. Is there some mechanism besides congestion that could cause output queue drops?
We currently have 2 6509s with redundant Sup720-3b's and PFC3B daughter cards which are connected together over dark fibre using the Gb fibre connectivity built into the supervisors.
The requirement is to upgrade this connection to 10Gb as inexpensively as possible.
Do I need to purchase new supervisors in order to do this properly or can I use a separate 10Gbe module (we have a spare slot), i.e. can I get away without using the connectivity built into the supervisors?
The other idea I had was putting a couple of 3750-X switches at each end to sit in front of the 6509s and provide the 10Gb connectivity between sites. I could then use the existing Gb uplinks on the supervisors whilst also providing connectivity for some devices that currently connect to the 6509s but could just as well connect here.
We have a number of 6509s which generally have dhcp relay agents configured on the SVIs. The dhcp servers are centralised. Recently we've had one or two faults with misconfigured or faulty devices (blade server chassis and also printers) generating high volumes of dhcp discover packets and causing high cpu on the relevant 6500. I would like to rate limit these discover packets, which are layer 2 broadcasts. Storm control can't discriminate between different types of broadcasts and on a gig link would need to be set down at about 1% to have much effect on the problem. I've looked at CoPP and also mls hardware rate-limiting but as I understand it, these two features don't control broadcast traffic. I also looked at dhcp snooping but if an interface receives a high level of dhcp discover broadcasts, e.g. over 100pps, I don't want it to go error-disabled (as this would knock down the whole edge switch), just to drop the excess packets.
[code] I would like to config two IP ranges, one for staff, one for guest wireless access. The dlink wap supports multi vlan SSIDs.Reason I'm doing this is to prevent access on the guest wireless to access the win 2003 server.Will the switch inter vlan route the 192.168.2.1 to 192.168.1.1? How will vlan 2 get DHCP, will dhcp relay need to be set on vlan 2 to 192.168.1.20 ? [code]
I have a connection on IP 192.168.1.21, Subnet 255.255.255.0 - this is on the default VLAN1 on the switch. I need to route this to IP 10.0.3.101, Subnet 255.255.252.0 - which is set up on VLAN2 on the switch. I have set the switch to Layer 3 via console.
how I setup this route? I am use the Browser based interface.
I've recently installed an SGE2010 switch, which I have set to 'Layer 3' mode.
I have created 2 VLANs using 192.168.10.x and 192.168.20.x (using .50 for the VLAN IP address in each case) - however, I need to be able to allow certain traffic between the VLANs.Alternatively, to get things started - I'm assuming I need to set up ACLs to allow access between VLANs - how would I configure the switch to allow all traffic from one VLAN to the other?
configure my new SG300-28P. When I have started the switch, I have specified a new password and enabled telnet in order to setup the switch in Layer 3 mode.
After a restart, the switch took its IP address from a DHCP server. When I try to set a static IP address (192.168.2.1), I receive the following error message: Duplicated IP interface on the same subnet.
The IP address 192.168.2.1 is not used by any device within the network. For information, the message doesn't appear when the switch is in Layer 2 mode.
why I can't change the IP address of default vlan in Layer 3 mode ? All I can do is set the IP address to static or dynamic.
For test purpose, I have added 2 vlans. But I wasn't able to route traffic between vlan. how to configure the switch to route traffic between vlan?
find below details informations about my VLANs.
- Default (VLAN ID 1) IP Address : 192.168.2.1 Subnet : 255.255.255.0
I have recently purchased 2 SG 300 switches, 1 x SG 300 52 & 1 x SG 300 10, and I am hoping getting the following set-up working.To assist I have drawn the following simple network diagram (below) which hopefully makes it a little clearer what I am trying to do:I have 2 companies occupying a single office with the requirement to share printers/devices etc... so basically I am looking to set-up 2 VLANS (say VLAN 10 & VLAN 20) with inter-vlan routing. To add a little complexity the main comms area is located in the basement of the building, this houses the 2 DSL routers and 2 Servers, one for each company. I am proposing putting the SG 300 10 port switch in here and then use the 3 uplinks I have been given to connect back to the SG 300 52 which is in a patch cabinent 2 floors up. I want to use 2 uplinks (in a LAG) for Company A and 1 uplink for Company B. FYI. DHCP is being served out by each respective router.
My organization wishes to host a LAN gaming event. The setup I have in mind involves a 24-port switch for connecting all the player computers and having that switch connected to a smaller "core" switch which has the the game server and router connected to it. I'd like to know if I can set things up as follows...
SG200-26 with ports 1-24 on seperate VLANs so they cannot talk to eachother. I'd then like ports 25 and 26 to be an aggregated (for bandwidth and redundancy) trunk port to carry all 24 VLANs plus an additional management VLAN (ex. VLAN 100) that will be used for accessing the switch. I'd like those aggregated trunk ports to connect to an SG300-10 "core" switch which will be connected to the game server and to a router for internet access.
I'd like the ability to have two network connections from the game server to the switch, one on the management VLAN and one on a different VLAN (ex. VLAN 50) that will be accessed by the players (ports 1-24 on the SG200-26). The core switch needs the ability to perform restricted inter-VLAN routing, in that it doesn't allow VLANs 1-24 to talk to eachother but they can talk to the server's VLAN but only through specific service ports (ex. port 12345, 12346). Is this possible?
Furthermore how would I configure the SG300-10 to allow VLANs 1-24 to talk to VLAN 50, but not themselves or VLAN 100. As well, I'll probably have the router on it's own VLAN (ex. VLAN 60) and allow VLANs 1-24 to access it but only through HTTP port 80 for web access.
I have six Cisco 300 Series switches in Layer 2 mode. They are all connected using ports in Trunk mode. These Trunks are tagged members of all VLANS.
I have one 300 series in layer 3 mode with IP address assigned to each VLAN.I would like to use one Internet gateway for multiple VLANS. This gateway has numerous IP ports that forward to internal ip addresses on various machines.
All i9nternal clients use their respective VLAN IP as their default gateway.The Layer 3 switch is connected to one of the Layer 2's using a Trunk that is a tagged member of all of the VLANS.
I understand how traffic routes from a client to its respective VLAN gateway. Where I am confused is how it routes from there to the Internet gateway? Internet gateway is 192.168.1.1.VLAN IP's are 192.168.2.1, 192.168.3.1, etc...
Should the Internet Gateway be patched into the Layer 3 switch or one of the Layer 2's using a separate "Internet" VLAN?
I used two sf-300 switch and create 4 vlans and intervlan routing is working fine.
Port 1 - 10 -------------> Vlan 1 Port 2 -20----------------> Vlan 2 Port 3 - 30------------------> Vlan 3 Port 4 - 40--------------------> Vlan 4
giga1 -----------------> connected to router (This router used for intervlan routing).
SF-300 Port 1 is connected to Internet Modem. This modem worked as dhcp server also for vlan 1, my problem is that when vlan 1 is not communicate to vlan2,3,4 and 2,3,4 are not communicating.
How i can communicate vlan 1 to 2,3,4 vlan.
how i can connect the modem in switch? Access port or Trunk port ( Presently available in vlan 1 Access port)Any route i need to make? sf-300 or modem or router?
Currently, we have a plain network and we are planning to 'upgrade' it a little. We want to implement VLANs to separate wireless clients, workstations + servers and infrastructure devices form each other.As of now, we have no VLANs, and no managed Switches. We only have an RV016 that handles two ISPs and a 3rd party connection service to the office branches ( I belive they're using Frame Relay, but as far as we know, we are not concerned since we cannot touch their devices)
The reason behind the title, pointing towards the famous SGE2000P, is that my workplace is located in Argentina... and we don't have as many choices as some of you guys have ! In fact, I was unsuccessful trying to get a Cisco partner to contact me. We would like to replace the RV016 with a cisco 1941 (and a HWIC switch card).
So, back to business..! Assuming we will be using the SGE2000P switches, I was thinking about setting VLANs using 802.1Q through seven of these switches, along with a 1941 Cisco router. I'm expecting the 1941 to handle load balancing between both ISPs and the 3rd party link. Now, as for Inter VLAN routing, I would like to have gigabit traffic between VLANs.
Is it possible to use one SGE as Layer 3 mode to hande inter VLAN traffic (gigabit speeds) while using the 1941 as a end point device to reach internet (using PAT) ?Would you suggest me to use the 1941 for Inter VLAN routing, despite the 10/100 limitation(*) and use all SGE's in L2 mode? We need two ISPs, a third link for the FR connection, and finally the LAN interface. As far as I know, I'm limited to the gigabit builtin interfaces for WAN purposes, am I right?
CiscoSwitch1(4506) has 3 VLANs(12,13,14) and Switch2(4948) has 3 different VLANs(22,23,24) and IP routing has been enabled in both switches with SVI interfaces for each vlan. intervlan routing is works fine.Now there is a requirement to connect these switches together. Vlan 12 on the Cisco switch 4506 has to be made available from vlan 22 from Switch2(4948). basically Vlan 12 is having a multicast source (225.0.0.0 & 226.0.0.0) which should be accessabile from vlan 22 of cisco switch 4948.I got 2 ideas
1) Create a trunk between these switches and configure L2 vlan(12) in cisco 4948...i know theoritically it should work but what my concern is Ip routing enabled in both switches will it create any issues? is it a gud solution to this requirement?
2) Create a separate IP network on the ports connecting to both switches and set up routes to the networks.ex- console(config)#ip route 192.168.10.10 255.255.255.0 192.168.20.1.
I have two C2960 switches which have the management VLAN for other switches. These two switches are connected with each other via portchannel. Now the mgmt0 of few switches is connected to switch 1 and few other connect to switch 2.I have also connected the mgmt0 of switch 1 to an access port of switch 2 and vice versa.However in this set-up I am unable to reach switch1 via the mgmt0 IP address. However I can reach the mgmt0 Ip address of switch 2.I can also reach switch 1 and 2 via their int vlan IP.Has some one else experienced this and is their any specific reason why mgmt 0 IP address of switch 1 is not reachable.I have tried doing similar set-up on C3750, but have acheived same result i.e. I am unable to reach mgmt0 of switch 1.