Cisco Switching/Routing :: IP Routing On 6500 Series Vs 3750?
Oct 30, 2011
For intervlan routing, Is 'IP routing' command enabled by default on a 6500 series switches based on the IOS?hes, do we need to enable the "ip routing" command manually for intervlan routing?
For intervlan routing, Is 'IP routing' command enabled by default on a 6500 series switches based on the IOS?and on 3750 switches, do we need to enable the "ip routing" command manually for intervlan routing?
I have a routed interface on a Cisco 6500 Series switch. I am trying to find a way to adjust the tcp mss.To date I have not yet been able to find a way to accomplish this. Is this just not supported?
My task is to upgrade a couple of 6500 series switches, 6513 with SUP720/MSFC3 (WS-SUP720) and Policy Feature Card 3 (WS-F6K-PFC3B) installed. How to upgrade those switches if in SSO redundancy mode with two SUPs installed?
I understand that it is good to connect to the MSFC3 via console and upgrade this first, is this correct?
I also have to upgrade some 6509 but I only can test it on one 6509-E, how to get everything up to date. [code]
some of the features of 6500 are enabled by default and woudn't appear in the "Show run". See the command below and how do I make sure whether these featues are enabled by default or not. Would it appear in the config if enabled?
ip verify unicast source reachable-via rx ip verify unicast source reachable-via any
storm-control broadcast level 70
what are the difference between the commands below and can they be enabled together.
spanning-tree guard root vs spanning-tree loopguard default vs spanning-tree guard loop
I am getting the below messages on my Cisco 6500 series switches every 1min. The IOS version is 12.2(33)SXI6 & with SUP32-GE-3B
%ILPOWER-7-DETECT: Interface Fa1/1: Power Device detected: Cisco PD %ILPOWER-7-DETECT: Interface Fa1/1: Power Device detected: Cisco PD %ILPOWER-7-DETECT: Interface Fa1/1: Power Device detected: Cisco PD
These messages are I am recieving on few ports only not on all port having IP Phone connected. I tried changing the phone to some other model but that also did not resolved my problem. Also I tried powering on the phone using power adapter but the issue still persist.
Client are not facing any issues due to this error, but still I would like know what can be the issue which is generating these logs.
I am little confused about the location of FIB table and adjacency table in both cisco 6500 series and fixed ports switches .In case of 6500 series switches
"Central CEF mode:The CEF FIB and adjacency tables reside on the route processor,and the route processor performs the express forwarding. Use this CEF mode when line cards are not available for CEF switching, or when features are not compatible with distributed CEF."
If line cards do no support CEF, then FIB and adjacency tables are built and are located on route processor( control plane ). Data plane operations are implemented in software and route processor performs those operations.
Some Cisco switches actually use different hardware to control the different planes. For example, the Cisco Catalyst 6500 is a modular switch that uses the Multilayer Switch.Feature Card (MSFC) for control-plane operations, and the supervisor Policy Feature Card (PFC) for the data-plane operations.
Supervisor module has has MSFC and PFC. MSFC implements control plane operation where as PFC implements data plane operation.But the first paragraph says in Central cef mode, both data plane and control plane operations are implemented by route processor. [code]
Do these switches implement the Central mode cef in same way as mentioned above. i.e
"Central CEF mode:The CEF FIB and adjacency tables reside on the route processor and the route processor performs the express forwarding. Use this CEF mode whenline cards are not available for CEF switching, or when features are not compatible with distributed CEF."Or fixed ports switches such as 3750 implement data plane operation in hardware where FIB tabe and adjacency table are maintained on Data plane.
I am connecting power cable (series power cables) on 3750 stacks. i have connected them the same way the stack cables are connected i.e. fo rexample on a stack with 3 3750s:
1- fitst slot on fist switch connected the second slot last switch in the stack.
2- second slot/ port on the first switch to the first on second and seoncd on teh second switch to first on the third switch.
this how they are alway been stacked.Now, I need to connect power cables and I have followed the same method for stacks up to 4 switches. it seems that if a stack has more tham 4 switches, then the cabling will be dofferent!?I was wondering what will be on the cabling scheme for stacks more than 4 switches.
I am planning to migrate the core switch from cisco 3750 to Cisco catalysts 6513 switch. What could be the best approach to minimize the downtime or avoid disrupting the production. I have couple of thoughts, one method is to build the core and then replace the existing core, another option is to build the new switch as the second VTP server and once it recieves all the VTP information then disconnect the old server.
We need to implement VLANs on my company's network. I have 3750 L3 swtich, ive setup 3 vlans for testing. ive setup SVI everything.now how do I connect it to 3com that will also use VLANs. should I set trunk port of cisco and 3com? or no need?
I'm thinking about using a 3750 stacking around 4 or 5 switches intead of using one 4500 series switch.
1-My first argument was concerning the budget (one 4500 instead of four or five 3750 in stack mode) ---- Here i think 4 or 5 stacked 3750 is cheap than one 4500 2- My second argument was about harware redundancing that i don't have with one 4500 and that i have with stack mode ----Here i have more hardware redundancing with 3750 3- The bug that we notice today in 2960 and 3750 and not in 4500 4- Simple to manage a 4500 compare to 3750 stack design 5- I was looking also for the one with best backplane ----Here i didn't have any infos concerning the best backplane between 4 or 5 stack 3750 and a 4500. 6- I'm also looking for power redundancing.
I want to limit the bandwidth of my Catalyst 3750 series switch, I read the cisco documentation and I applied the commands but I didn't get the wanted results.
For the outbound traffic it's ok, but for the inbound traffic I used policing but I get an unstable traffic. I used, an access list and a class-map to classify the traffic and then a policy-map.(I followed the steps mentioned in this site: [URL]
Is there any challenge to upgrade core switch 6500 series from Nexus 7009 which runs NxOS, because i have 3750X series switches connected at distribution and access layer in my network topology??
Is there any challenge if we place NxOS in core and IOS in distribution and Access layer??? how we are able to match sh run config in existing 6500 switch to Nexus 7009 NXOS?
I have 2 6504's running HSRP as my core. They are each etherchannel'd to my Datacenter switch (3750 Stack) -- see image below.The problem i a having is with the etherchannel status:
Core1 PO11 status w (waiting) Core2 PO11 status P(bundled)
DC11 PO48 status P -- but only to Core2 - the interfaces to Core1 are suspended. (See attached configuration documents) None of the devices have any information in the logs. I run this same configuration in my central location, but we are running Nexus 7000's. With the 6500's, do I need to split the port channels on the 3750 to allow them to negotiate the etherchannel? If I split the portchannels, are there any concerns? Should I expect to see the etherchannel status as P (Bundled) or H (Hot-Standby)?
we are using 3750 and 2950 switches both of them do not support vlan up to 4000 .we need vlan about 3000 .Whic cisco series switch do support vlan up to 4000.
2950 S-SW1.3(config-vlan)#exi
Proposed configuration has too many VLANs for this platform. Reduce the number of VLANs proposed.
S-SW1.3(config)#end 3750 SW1(config-vlan)#exi
proposed configuration exceeds the limit of 1005 VLANs that can be supported on this platform. Reduce the number of VLANs proposed to be within this limit.
I have a new Cisco 2960 S series switch with a basic configuration that needs to be uplinked or daisy chained to a Cisco 3750 switch. I am not getting any connectivity to the network with either a straight through or crossover cable. the port remains in amber but a 'show interface' indicates that the interface is up. I can manage the switch with a PC patched into any port on the switch with a static IP address. Must be something very simple that I am missing. Outlined below is the configuration.
I'm looking to restrict Inter-VLAN routing through L3 switch (cisco 6500) and wanted to know best possible way to do it. I used VACL and achieved success to some extent, but my config is making clients take up to 5-6 mins to authenticate IP address from the DNS (bootps).My VACL config was as follows:
Subnet to restrict is 10.100.15.0 (VLAN 15) STEP 1: Created extended ACL to allow bootpc/bootps through DNS ip access-list extended EACL_DNS permit udp any eq bootps any permit udp any eq bootpc any
STEP 2: Created standard ACLs to allow only relevant subnet, server VLANs & some IPs from other subnets for printers/scanners etc.
ip access-list standard SACL_VLAN_15 permit 10.100.15.0 0.0.0.255 (the subnet I'm restricting) permit 10.100.50.0 0.0.0.255 (server VLANs) permit 10.100.25.45 0.0.0.0 (printer in another VLAN which has to have access in VLAN 15)
STEP 3: Created VLAN access list
vlan access-map VACL_15 10 match ip address EACL_DNS action forward vlan access-map VACL_15 20 match ip address SACL_15 action forward
STEP 4: Applying VLAN Access list on VLAN 15 vlan filter VACL_15 vlan-list 15 Though the above works, below is noted:
1. I'm still able to PING 10.100.15.2 (the switch virtual interface) from outside the subnet, which I don't intend to do so. Howeve all cients in the subnet have no connectivity from outside the VLAN 15.
2. As mentioned its taking quiet some time to negotiate with the DNS server at system boot time.
I used to "ip routing" command in order to enable inter-vlan routing, for example with 3750 cisco. I have a 6503 cisco with SUP720 MSFC3. I was able to create some vlans but I can not configure inter-vlan routing.
sw#conf t Enter configuration commands, one per line. End with CNTL/Z. swsur(config)#ip routing
I have a network with a Catalyst 3750 as the main switch and then some Catalyst 2960 switches that are plugged in to that. I have a server running windows server 2008 with a couple of virtual machines running in Hyper-V. I created 4 VLANS listed below and gave the 3750 the following IP Address.I would like the 3750 to only be configurable from VLAN 40 but currently every VLAN can connect to it, I noticed in the standard web page settings there was a setting for "Management VLAN" but it was set to 1 and would not let me change it, I kinda assumed that was for the management port in the back.-Now the tricky part, I was trying to set up routing between the VLANs and so far I have only been able to get a sort of "all or nothing" routing to work. I can turn IP routing on and add two or more VLANs to the routing and it works fine. But what I was hoping to do is create a couple of "junction vlans" that would only route to one or two other vlans. For instance, I wanted to create a VLAN 100 that routed to VLAN 20 and 30 but nothing else. I also want to route VLAN 1 just to VLAN 30, and so on. I am able to do each one of the cases but only one, it seems like the switch only supports one "routing table" am I missing something or is this just a limitation of the switch?
Is a 3750 sw capable of handling full routing tables and what can you recommend in a small mutihomed BGP router or switch capable of handling full routing tables?
I have a network with several catalyst 2960 switches and one catalyst 3750. I have created two VLAN and set up the proper routing and everything is working fine there. I have a client/server application that used multicast in the initial start up for the client to determine available servers, the issue is one of my clients is on a different VLAN then the server. I am able to route the multicast using MVR as long as both the server and the client are plugged into the 3750 by creating a static route, making the server a source port and the client a receive port. Unfortunately I need the client and the server plugged in to different 2960s. My question is how do I establish multicast routing between the two and perferably do it dynamically (always route multicast traffic from one VLAN to another).
I have been looking into this for a while and I can't seem to figure out why my 2nd vlan is not able to connect properly to the net.
My switch has 12 ports where my devices connects directly, they are all on Vlan 1 and they all work perfectly. on Port 12 I have a dlink router that is connected to a cable modem. the dlink router has an Ip address of 192.168.0.20
I created a second vlan (vlan2) and enabled dhcp relay on it. then I assigned port 9 on the switch to (vlan2)my laptop which is connected to port 9 seems to get an ip address fine and able to ping only some devices on my network (vlan1) and is not able to go out to the internet. I think it has to do with the routes. [code]
I have the task of replicating the router config on a 3825 router on a 3750 switch. Reason is we are taking out the router and replacing it with the switch to make use of the router for other functions.
Below is main part of the router config:
! ip source-route ip cef ! ! multilink bundle-name authenticated ! license udi pid CISCO3825 sn FCZxxxxxxx ! vlan internal allocation policy ascending
[code].....
The 3750 switch I have runs C3750E-UNIVERSALK9-M, Version 12.2(55)SE3 on a LAN BASE license.
The first thing I have done is to order for a license upgrade to IP BASE which would give the support for OSPF routing.I do not see much of an issue with the Interface configs, however, I am not too sure about replicating the routing config on the switch.
My question is can I run the commands as shown for the OSPF routing on the switch? If not, can I get suggestions on how best to set this up on the switch?
In 3750 switch,I have configured intervlan routing.I have three vlans Vlan 10,vlan 20,Vlan 30 and I have assigned IP address for that Vlan.In vlan 10,I have connected one systen gigabitethernet 0/1 interface.From my system I am able to ping vlan 10 ip address but I can't able to ping other vlan ip address (vlan 20,vlan 30).Is it possible to up the protocol for all that time.
I am using a 3750 as a default gateway for multiple Vlans on a few 2960 switches. The trunk lines are configured and working and I have assigned ip addresses to each of the Vlan interfaces on the 3750. My issue is that I can only ping the ip address on the Vlan interface of the 3750 if I have a working computer plugged directly into the Vlan on the 3750. I only have 3 vlans on the 3750 that have hosts directly connected (vlans 2, 10 and 40) the other vlans ( 20 and 70) don't have any clients plugged into them on the 3750 but the hosts reside on 2 different 2960s that connect via trunk ports. How do I keep the vlan interface on the 3750 switch pingable when I don't have hosts directly connected in that vlan on the 3750? (yes, I have enabled ip routing on the 3750)
I have a simple design with 3750. I configured a route-map which define a next hop. I defined this route-map on a policy on a vlan interface.When I test some ping and a debug ip policy and it seems that my policy never match.Is there any mechanism that prevent the switch from using PBR? I think of CEF .