Vlan Translations, 6500

Looking to verify if the version IOS on the 6500 will work. This is the document for 12.2SX
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vlans.html#wp1044990
The version running is 12.2(33)SXI2a. It has the appropriate cards, so just need to verify this version has the commands. I dont have direct access to ty them myself, nor attempt to walk someone through on a production switch.
Thanks in advance.

Hi,
From the IOS master commands link
http://www.cisco.com/en/US/docs/ios-xml/ios/interface/command/ir-s7.html#wp3252950350
switchport vlan mapping
To map the traffic arriving on the VLAN original-vlan-id to the VLAN translated-vlan-id and the traffic that is internally tagged with the VLAN translated-vlan-id with the VLAN original-vlan-id before leaving the port, use the switchportvlanmapping command in interface configuration mode. To clear the mapping between a pair of VLANs or clear all the mappings that are configured on the switch port, use the no form of this command.
switchport vlan mapping original-vlan-id translated-vlan-id
no switchport vlan mapping { original-vlan-id translated-vlan-id | all }
Syntax Description
original-vlan-id
Original VLAN number; valid values are from 1 to 4094.
translated-vlan-id
Translated VLAN number; valid values are from 1 to 4094.
all
Clears all the mappings that are configured on the switch port.
Command Default
No mappings are configured on any switch port.
Command Modes
Interface configuration
Command History
Release
Modification
12.2(17b)SXA
Support for this command was introduced on the Supervisor Engine 720.
12.2(18)SXE
This command is not supported on GE Layer 2 WAN ports.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
So 12.2.33SX is supported
Regards,
Alex.
Please rate useful posts.

Similar Messages

Vlan translation on SCE8000 version 3.8.5

i have the version on sce 3.8.5, in the version 3.1 exist a command vlan translation decrement value, but i cant find in the version 3.8.5. how i can configure vlan translation on the sce new version. thanks
regards

If you have to work with it, I would simply import through the finder to a folder on your hard disk and then import from there. You might have to set up the USB communication mode on your camera to Mass storage isntead of PtP (should be somewhere buried in the menus). Changing that setting might help with the direct Lightroom import too. You might also get better results going through a card reader (you can get them at many places for <$10) instead of connecting directly to the camera which is always a recipe for problems and slow imports. A card reader is a good investment as they usually are MUCH faster than going through the camera's USB connection.
A Lightroom upgrade to v5 is $79 dollars. It might be worth it to think about. I understand tight money though and sometimes even $80 is a big deal but you might not have been aware you can get upgrade pricing if you have LR 3. ANother option is getting the creative cloud photographer deal which is $10/month and includes both the full version of Photoshop and Lightroom. I don't like the idea of rental software but that is quite the deal.

SCE vlan translation with connection-mode inline on-failure bypass

Hi guys,
Can anyone tell me the behaviour of the SCE (1010 or 2020) in a failure scenario when configured with the following commands?
connection-mode inline on-failure bypass
VLAN translation increment value 5
While the SCE is in failure mode, will the VLAN increment between the SUB and NET ports still be applied (ie. applied in hardware while the control engine is being bypassed), or will all frames be passed from the SUB to the NET ports unaltered?
Regards,
Brett.

Reading through the CLI :
int LineCard 0
connection-mode inline on-failure bypass
VLAN translation ?
decrement Vlan will be decremented on network port and incremented on subscriber port
increment Vlan will be incremented on network port and decremented on subscriber port
So on traffic that is either coming in on either the network side or sub side will get either incremeneted or decremented for vlan translation.
Is there a need to do this ? what scenario are you considering using it in ? if the traffic is bypassed as is shown why you need to further massage it ?

VLAN translation, Cisco 3750G 12S-E

Hi
I need to do some VLAN translation where I achieve the following:
On port 1 translate VLAN 101 -> 1001. VLAN 102 -> 1002. VLAN 103 -> 1003.
On port 2 translate VLAN 104 -> 1001. VLAN 105 -> 1002. VLAN 106 -> 1003.
On port 3 translate VLAN 107 -> 1001. VLAN 108 -> 1002. VLAN 109 -> 1003.
In example VLAN 1002 in on port 2 is translated to VLAN 105 internally on the Cisco.
How do I do this? :)

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
You might be able to cross link VLAN ports, e.g. port 1, VLAN 101, connects to port 2, VLAN 1001, to effect a "translation", but on a switch with only 12 ports, you can only do 5 such connections (I'm assuming you want 1 or 2 ports for connections to other devices to move the VLAN traffic in or out).

VLAN translation for VoIP config.

I have an Cisco 1751-v4 as the core router. Also a Cisco Cat 1900 switch with ports 17-24 configured for VLAN membership VLAN 2 (VLAN 1 is data).
My goal is to configure VoIP, but I want the VLAN to be on a 172.x.x.x subnet.
Can I create a second dhcp pool I can include "option 150" for VoIP only?
my next question is I have a fast ethernet interface (LAN) and an ethernet interface (WAN, which interface do I configure the VLAN encapsulation on?
I have included my current config below.
thanks for the help.

Ankur,
I am still having issues configuring VLAN's.
During some reading, I understand I should not have to create a trunk as I am only using a single cisco 1900 switch.I should not have to configure VTP on the switch as well for the same purpose.
Here is what I am looking at:
Router#>int fasteth0/0
ip address 192.168.2.1 255.255.255.0
ip helper-address 192.168.2.0
ip nat inside
From what I have read, I need to configure the DHCP DATA pool (192.168.2.0) as vlan1 native. But when I attempt to configure the IP address for the native VLAN1 on fastethernet0/0.1 (subinterface) I recieve IP address overlap with int fasteth0/0 interface error.
Question, can I configure interface fastethernet0/0 without an IP address,but configure the subinterfaces 0/0.1 and 0/0.2 with ip address?
ip dhcp pool Data
network 192.168.2.0 255.255.255.0
domain-name 5thborocs.com
default-router 192.168.2.1
dns-server 63.162.197.69 208.33.149.39
ip dhcp pool VoIP
network 192.168.3.0 255.255.255.0
domain-name 5thborocs.com
default-router 192.168.2.1
option 150 ip 192.168.2.1
interface FastEthernet0/0
description Cisco 1900sw
ip helper-address 192.168.2.0 (or without a helper address)
ip nat inside
ip virtual-reassembly
speed auto
full-duplex
interface FastEthernet0/0.1
description Data
encapsulation dot1Q 1 native
ip address 192.168.2.1 255.255.255.0
ip helper-address 192.168.2.0
interface FastEthernet0/0.2
description VoIP
encapsulation dot1Q 2
ip address 192.168.3.1 255.255.255.0
ip helper-address 192.168.3.0
no snmp trap link-status

RSPAN limitations with vtp domain on 6500- 12.2.3(33)SXH5 ERROR DUPLICATED MAC ADDRESS ON TWO VLANS

Hello everyone,
i have a network with a
L3(core) 6500 12.2.3(33)SXH5 with vtp (server) and pruning on, rstp
L2(distribution, ) with 3750 fiber connected
L2(access) with mixed hardware 2950-3750
when i go to setup a rspan:
6500(config)#vlan 400
6500(config-vlan)#remote-span
access(config)#monitor session1 source remote vlan400
access(config)#monitor session1 destination fa2/0/1
access(config)#monitor session1 source int gi1/0/37, gi1/0/44, tx
access(config)#monitor session1 destination remote vlan 400
my problem is on a periferic access switches 2950 not redundant:
i relevated a
duplicate mac-address table, i found a every mac on 2 vlan, the 200 and 400(of remote span) with related problem of loss of packets and random connection problem
My question is:
is compatibile the rspan with 6500 vtp, how i can fixed this problems?
thank you

Other users from the forums with a similar problem came to a conflict occurring here
Oct 18 11:52:41 MacBook-Pro opendirectoryd[123]: 2595.39 - ODNodeCreateWithNameAndOptions failed with error 'Unknown node name' (2000)
They say it's some sort of conflict with the language of the installation or is it language keyboard input, then what is meant and how it can be solved I do not understand if this is certainly so.
(sorry for my bad english)

VRF-Lite with 6500 w/ Sup720

I am working with a customer who would like to utilize path isolation in their network using VRF-Lite. I am currently debating between the use of GRE tunnels vs. VLANs between 3 core switches they currently have in place today. This is going to be overlay network on top of what they currently have. The core is all L2 today with 802.1q trunks between each of 3 cores in a ring topology. Closets are single homed into the core throughout.
My question is regarding GRE vs. VLANs. Currently, we are looking at having to deploy 12 VRFs to support 12 seperate network types they would like to isolate. The Access layer switches will trunk to the cores where the core will apply VRFs to specific VLANs based on their role.
Which is going to be a more scalable solution from a performance and adminstration standpoint. GRE, VLANs, or MPLS?
Currently the GRE implementation is going to require that we configure many loopbacks and tunnels on each core in order to get the VRFs talking to each other in each core. The VLAN approach will require 24 VLANs per core (assuming we would go with PTP vs Multipoint for routing inside the VRF).
Any thoughts on which way to proceed? From what i have read GRE is more appropriate when you have multiple hops between VRF tables, which in this case we do not. I am just concerned with loopbacks,tunnels, and then routing on top of that the GRE solution will lack scalability as they add more VRFs. A PTP VLAN will pose a similar problem without the need for loopbacks which should simplify the solution.
Can we use MPLS here and just do PE to PE MPLS and still get the VRF segmentation we need between cores?
I would like eventually migrate the entire core to L3 completely but today we are stuck with having to support legacy networks (DEC/LAT/SNA) and have to keep some L2 in place.
Whats the best approach here?

Shine,
I actually ended up with basically the same design you are talking about here except that I ended up adding a couple 6500 +FWSM and NAC L3/L2 CAM/CAS into the mix.
Here is the high level overview
1. Every Closet had a minimum of 6 VLANs - unique to the stack or closet switch - Subnets were created for each VLAN as well - no spanning of L2 VLANs across switch stacks.
2. VLANs were assigned for - Voice, Data, LWAPP VLAN, Guest/Unauthorized, Switch/Device Management, and at least 1 special purpose VLAN - (Lab, Building Controls, Security, etc).
3. Then we trunked all the VLANs back to 1 of 3 cores - 6509s with Sup-720s
4. Each Core 6509 was configured for each L2 VLAN with a L3 SVI (The VLANs configured here were not configured on any other cores - we didn't have available fiber runs to do any type of redundant pathing across multiple cores so it wasn't valid in this design to configure VLAN SVIs on more than one core).
5. Each L3 SVI was assigned to the appropriate VRF based on use - Voice, Data, LWAPP, etc
6. Spanning-Tree Roots for all VLANs trunked to a core were specific to that core - they did not trunk between Cores - no loops
7. Each Core was connected via a L2 Trunk that carried Point to Point VLANs for VRFs traffic - We had an EIGRP AS assigned to each VRF on the link - so we had 6 VRFs and 6 EIGRP AS per trunk.
8. This design occurred on each core x2 as it connected to the other cores in a triangle core fashion.
9. Each of the Cores had a trunk to to 6500 with a FWSM configured - VRF/L3 PTP VLAN design continued here as well
10. The 6500+FWSM was configured with multiple SVIs and VRFs - we had to issue mult-vlan mode on the FWSM to get it to work.
11. Layer 2 NAC was configured with VLAN translation coming into the Core 6500/FWSM for Wireless in L2 InBand Mode - the L3 SVIs were configured on the clean side of the NAC CAM so traffic was pulled through the CAM from from the dirty side - where the controller mapped host SSIDs to appropriate VLANs. We only had to configure a couple host VLANs here - Guest and Private so this was not much of an issue - Private was NAC enabled, Guest VLAN/SVI was mapped to a DMZ on the firewall
12. For Layer 3 NAC we justed used an out of band CAM configurations with ACLs on the Unauthorized VLAN
It worked like a charm.
If I had to do it all over again I would go with MPLS/BGP for more scalability. Configuring trunks between the cores and then having the mulitple EIGRP AS/PTP VLANs works well in networks this small but it doesn't scale indefinately. It sounds like your network is quite large. I would look into MPLS between a set of at least 3-4 Core PE/CE devices. Do you plan on building a pure MPLS core for tagged switched traffic only? Is your campus and link make up significant enough to benefit from such a flexible design?

CSM 3.3.1 and 6500

Hello,
We are facing a problem with CSM 3.3.1 and 6500 switch with FWSM. We have 2x 6500 switches with 2 supervisors in each + 2 FWSM cards one in each chassis. The problem is that we have CSM 3.3.1 that manages the switch and FWSM. The problem is that when we try to delete a VLAN in 6500 we get a deployment failure because the switch outputs this message:
% Applying VLAN changes may take few minutes. Please wait..
We are using the following IOS version.
CSR-CORE#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 02-Sep-09 01:00 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX6, RELEASE SOFTWARE (fc1)
CSR-CORE uptime is 22 weeks, 6 days, 23 hours, 59 minutes
Uptime for this control processor is 22 weeks, 6 days, 23 hours, 55 minutes
Time since CSR-CORE switched to active is 22 weeks, 6 days, 23 hours, 55 minutes
System returned to ROM by power cycle at 06:42:16 UTC Fri Feb 12 2010 (SP by power on)
System restarted at 11:10:39 EEST Mon Jun 14 2010
System image file is "sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin"
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C6509-E (R7000) processor (revision 1.5) with 983008K/65536K bytes of memory.
Processor board ID SMC1401000U
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
30 Virtual Ethernet interfaces
116 Gigabit Ethernet interfaces
12 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
CSR-CORE#
Note that we are NOT using VSS.
TIA,
Nicos

Hi all,
Sorry for not replying earlier. We found a workaround, as quoted below:
Changing How Security Manager Responds to Device Messages
Security Manager has built-in responses to many of the response messages that can be encountered when configuring a device. You might find that messages Security Manager treats as errors are messages that you want to ignore or treat as informational. Although you can configure your deployment jobs to ignore errors, you might instead want to update Security Manager to treat specific messages differently. To change how Security Manager treats a message, you need to update the DCS.properties file in \CSCOpx\MDC\athena\config folder in the installation directory (usually c:\Program Files).
Use a text editor such as NotePad to update the file. It is easiest to determine the message you want to ignore by looking at the transcript of a deployment job that encountered the error using these steps:
Step 1 Select the job with the error message from the Deployment Manager window.
Step 2 Click the Transcript button in the Deployment Details tab to open the transcript.
Step 3 Identify the error text that you want to ignore.
Step 4 Locate the appropriate warning expressions property in the DCS.properties file. For example, for PIX devices the property is called dev.pix.warningExpressions, whereas for IOS devices the property is called dev.ios.warningExpressions.Conversely, you can make device responses that are not tagged with the Error prefix to appear as error messages. To do this, add the message to the Error Expressions list (for example, dev.pix.ErrorExpressions).
Step 5 Add the error text to the warning expressions list. The warning message should be a generic regular expression string. Except for the last expression, you must delimit all expressions with “$\”. For example, if the message you want to ignore is “Enter a public key as a hexadecimal number,” enter the following string: .*Enter a public key as a hexidecimal number .*$
Step 6 Restart the CiscoWorks Daemon Manager
This has resolved the issue successfully

Concerning OTV and VLAN Assignments

I've been looking around but can't find any specific information...
When configuring OTV between data centers, is it required/advisable/best practice to have the VLANs that you need to extend from one DC to another have the same VLAN ID? Does that matter?
For example, VLAN 10 in New York DC is the 172.31.12.0/23 network. I want to extend the 172.31.12.0/23 network to the Los Angeles DC. Does the VLAN ID in the LA DC need to be VLAN 10 or can I use any VLAN ID in this case?
Thanks!

Hi Clay,
In my opinion it would be best practice to have the same VLAN numbering across the data centres you're extending VLANs, purely to keep things simple. Obviously if you translate from one VLAN number to another it will add some complexity and so complicate troubleshooting to some extent.
As far as whether having the same IP subnet assigned to different VLAN numbers is possible, I'm afraid you can't do this today. As of November 2012 Cisco were saying support for OTV VLAN translation would be available in the Nexus 7000 NX-OS 6.2 release. If you have Cisco Partner level access you can see the Nexus 7000 Roadmap Update presentation where this is discussed (see slide 11).
Regards

Managed subnet and dynamic vlans

Hi all,
I have confusion with managed subnet, we have 3 untrusted vlans, 9 trusted vlans and 3 separate vlans for vlan mapping. all vlans have different ip subnets, but untrusted vlans don’t have ip subnet, it will another vlan’s ip subnet so which vlan and which subnet ip should I use for managed subnet?
Here is the detail of vlan and ip
Untrusted vlan
101      for floor 1
102     for floor 2
103 for floor    3
We have separate vlan for vlan mapping
101 <-> 901          (172.30.1.0/24)
102 <-> 902         (172.30.2.0/24)
103 <-> 903         (172.30.3.0/24)
In the initial phase untrusted client should get 172. 30.X.X range ip address from dhcp and for trusted clients they should get the ip address as per the trusted vlans as follows
Trusted Vlan                              (ip subnet)
501     for floor 1 sales dept     (192.168.1.0/24)
502     for floor 2 sale dept           (192.168.2.0/24)
503    for floor 3 sales dept        (192.168.3.0/24)
601 for floor 1 mkt dept          (192.168.4.0/24)
602 for floor 2 mkt dept        (192.168.5.0/24)
603 for floor 3 mkt dept        (192.168.6.0/24)
701 for floor 1 admin dept      (192.168.7.0/24)
702 for floor 2 admin dept      (192.168.8.0/24)
703 for floor 3 admin dept     (192.168.9.0/24)
And I need to configure dynamic vlan for all users. E.g. if user is from sales department and login from floor 1 trusted vlan should be 501 and if this user login from floor 2 then trusted vlan should be 502. Can anyone give me the configuration sample or ideas for this scenario?
Thank you

Laxman,
Your managed subnets should be the IP range of 172.30.x.y (where y is a valid number and NOT the network number, i.e.0 or 255) with a VLAN tag of 101, 102 or 103.
For ensuring that the VLANs translate properly according to where your users are, you can assing named VLANs in the role-based VLAN config screens. Make sure the case matches as you define them on the switch and CAM. So this way if a user is on first floor and his role-based assigned VLAN is Sales, it will translate to 501, etc
HTH,
Faisal

QinQ vs. Vlan mapping

Hi guys, for me it is new, so i would like to ask that what is different between QinQ and vlan mapping. I hope all guy let could explain me. Thank

To my knowledge vlan-mapping is another word for vlan translation, meaning you translate (modify) the vlan ID in the frame when entering / exiting a specific interface.
QinQ is sometimes also called vlan stacking, meaning a frame is altered with a outer vlan tag (ID) and keeping the inner tag of the original frame. This technique is mostly used by service providers to designate a vlan ID per customer in a VPLS network.

Unknown interface vlan on fwsm

ive done the ff. on the msfc
firewall module 2 vlan-group 1
firewall vlan-group 1 100,200,300
interface Vlan100
no ip address
interface Vlan200
no ip address
shutdown
interface Vlan300
no ip address
shutdown
BUT WHEN I DO THE FF ON THE FWSM
int vlan 300
i get the foloowing
FWSM# conf t
FWSM(config)# int vlan 300
Unknown interface vlan.
the fwsm is not recognizing my vlan. what is missing?
thanks

Hi
Have you created the vlans at Layer 2 ie. if you do a "sh vlan" on the 6500 do you see your vlans ?
You do not create layer 2 vlans by entering
int vlan300
no ip address
shutdown.
If you want vlan 300 to be firewalled then please
1) remove the "interface vlan 300" from the 6500 ie.
6500(config)# no interface vlan 300
2) Add the vlan at layer 2 on the 6500 ie.
6500(config)# vlan 300
6500(config-vlan)# name vlan300
Do this for all vlans you want to firewall.
Jon

3750 Metro ethernet switch

Folks,
I have 6500's at the core and want to use the 3750 at the PE. My question is the following:
1) 3750 would do Q-IN-Q.
2) Once the packet reaches the 6500(sup 720) running MPLS. What happens to the frame. Do i use xconnect to transfer the frame to the appropriate PE?
Just confussed about how does the PE use the Q-IN-Q information to direct it to the appropriate PE?
Sample config would be highly appreciated.
Thanks

Well.. its about product features .. you gotta compare products with your requirments at various layer of your network and to come out with justification of your requirments . Any ways below is snippet for you to have some justification between two products
===============================================
What is the difference between the Cisco Catalyst 3750 Metro Series and the Cisco Catalyst 3750 Series?
The Cisco Catalyst 3750 Metro Series is built for Metro Ethernet access in a customer location, enabling the delivery of more differentiated Metro Ethernet services. These switches feature bidirectional hierarchical QoS and Traffic Shaping; intelligent 802.1Q tunneling with class-of-service (CoS) mutation; VLAN translation; MPLS, EoMPLS, and Hierarchical Virtual Private LAN Service (H-VPLS) support; and redundant AC or DC power. They are ideal for service providers seeking to deliver profitable business services, such as Layer 2, Layer 3, and MPLS VPNs, in a variety of bandwidths and with different SLAs. With flexible software options, the Cisco Catalyst 3750 Metro Series offers a cost-effective path for meeting current and future service requirements from service providers.
The standard Cisco Catalyst 3750 Series is an innovative product line for midsize organizations and enterprise branch offices. Featuring Cisco Systems® StackWise technology, Cisco Catalyst 3750 Series products improve LAN operating efficiency by combining industry-leading ease of use and high resiliency for stackable switches.
What is the Metro Ethernet positioning of the Cisco Catalyst 3750 Metro Series, the Cisco Catalyst 3550 Series, and the Cisco Catalyst 2950 Series?
Cisco Catalyst 3750 Metro Series Switches
=========================================
Cisco Catalyst 3750 Metro Series switches are a new line of premier, customer-located switches that bring greater intelligence for Metro Ethernet access, enabling the delivery of more differentiated Metro Ethernet services. These fixed configuration switches feature bidirectional hierarchical QoS and Traffic Shaping; intelligent 802.1Q tunneling; VLAN translation; MPLS, EoMPLS, and H-VPLS support; and redundant AC or DC power. They are ideal for service providers seeking to deliver profitable business services, such as Layer 2, Layer 3, and MPLS VPNs, in a variety of bandwidths and with different SLAs. With flexible software options, the Cisco Catalyst 3750 Metro Series offers a cost-effective path for meeting current and future service requirements from service providers.
Cisco Catalyst 3550 Series Switches
==================================
With a range of Fast Ethernet, Gigabit Ethernet, DC power, and fiber configurations, the Cisco Catalyst 3550 Series is an intelligent metro access switch for service providers serving the enterprise and small and medium-sized business markets. Featuring 802.1Q tunneling, high-performance IP routing, and subsecond Spanning Tree Protocol convergence, this line of powerful, cost-effective, fixed-configuration switches enables Metro Ethernet services such as Transparent LAN services and business-class Internet access.
Cisco Catalyst 2950 Series Switches
===================================
Ideal for Metro Ethernet access in residential markets, the Cisco Catalyst 2950 Series is an affordable line of fixed-configuration Fast Ethernet and Gigabit Ethernet switches. Featuring advanced rate limiting, voice VLAN support, and multicast management, these switches enable residential Metro Ethernet services such as Internet access, voice over IP (VoIP), and broadcast video.
Hope it helps
Ps rate this post if it helps u ..
Thanks and Regards
Raj

Using M1 and F1 ports in OTV set up

I am building a typical OTV architecture (on a stick, not inline) on Nexus 7000s; the join and internal interfaces in my OTV VDC are using M1 card ports. Can the other end of those links -- i.e. the interfaces in my Agg VDC -- use ports on my F1 card? Or do both ends of the internal and join links (all 4 ports) need to be on my M1 card? Asking because my M1 card is full at present.

Hi,
What is your nexus version ?? , below version 6.0 don't support on F1 module . 6.2 version supports on F1 module .
Version 6.2
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/release/notes/62_nx-os_release_note.html#31296
OTV
The following Overlay Transport Virtualization (OTV) features are available in Release 6.2(2):
The VLAN translation feature allows you to connect applications that reside in separate Layer 2 domains between data centers.
Selective unknown Unicast flooding is a per MAC address configuration that allows OTV to flood across the DCI for the specified MAC address. This feature is particularly helpful for applications that go silent and timeout from the ARP tables.
Dedicated broadcast group allows you to configure a separate multicast address for broadcast traffic. This feature is useful for organizations that need separate QoS policies for broadcast traffic.
OTV has built-in BFD support that does not require any additional configuration on the OTV side, which helps with any reconvergence that OTV might have to handle.
The scale of OTV and how fast it converges are improved in this release.
F1 Series and F2e Series modules can be used as internal interfaces with the OTV VDC.
Version 6.0
Q. What modules of the Cisco Nexus 7000 Series will support OTV?
A. OTV is supported on all M-series modules. OTV is not supported on F1-series modules. Deployments using F1 series can leverage VDC separation to achieve the desired combination of line cards and functionality.
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-series-switches/qa_c67-574969.html
OTV Hardware Support and Licensing Information
The only Cisco platform supporting OTV functionality at this time is the Nexus 7000. Figure 1-37 shows all existing M1 linecards OTV fully supports.
Figure 1-37 M1 Linecards Supporting OTV
Full support essentially means that both Join and internal interfaces can be configured on one of the M1 modules mentioned. OTV on F1 modules is not supported on NX-OS releases shipping at the time of writing of this document (5.2 and 6.0 releases) and will be introduced in a future software release but restricted only to internal interfaces (an M1 linecard will always be required on the OTV edge device to source the OTV encapsulated traffic out of the Join interface).
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro/DCI_1.html#wp1186106
HTH
Sandy.

Problem with Syncing configuration to our CSM

Recently we have had problems syncing between our pair of redundant CSM's.
Here is the behavior we observe when we run the command on one of our 6500.
! config 6500-2
module ContentSwitchingModule 2
ft group 1 vlan 4
priority 10 alt 20
! config 6500-1
module ContentSwitchingModule 2
ft group 1 vlan 4
6500-2#hw-module csm 2 standby config-sync
After we run this command on 6500-2 the log shows that the sync happens and the CSM config is deleted on 6500-1 and then nothing happens.
Here is the exact logout on each of the 6500.
6500-2(ACTIVE)
May 28 17:45:11.353 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Bulk sync started
May 28 17:45:11.369 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configurations to Standby CSM, this may take several minutes!
May 28 17:45:12.749 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
May 28 17:45:14.869 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
May 28 17:45:24.345 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Manual bulk sync completed
May 28 17:45:24.349 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Config Sync does not save Standby running-config to startup-config
6500-1(STANDBY)
May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Started clearing configuration
May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Completed clearing configuration
May 28 17:45:17.096 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Standby: Config Sync does not save running-config to startup-config
May 28 17:45:17.100 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration are being deleted from supervisor
May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration being deleted on Standby CSM
May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: New configuration are being configured
As you can see the configuration ends up being deleted from the STANDBY and the new configuration never gets configured to 6500-1(STANDBY).
We have tried replacing the SUP engine however this did not help. We will try to replace the CSM next. If anyone can shed some light on why this would happen I would apreciate it.

Hi
pls check for IOS bug CSCtd09117 and CSCsx64648

Vlan Translations, 6500

Similar Messages

Maybe you are looking for