MPLS support GEC on 7600 with SUP-720-3BXL ?

Hi all
Could someone let me know does 7600 with SUP-720-3BXL support full MPLS, MPLS-TE, QoS, ... on Gigabit Ethernet channel interface ?
Which port interface (LAN/WAN, ...) does 7600/SUP-720-3BXL support full MPLS features ?
And does 10GBASE XENPAR Modules support full MPLS features ?
thanks you

The Cisco 7200 Series offers numerous LAN and WAN interfaces for diverse connectivity requirements. Modular processors for the Cisco 7200 Series provide flexibility as their need grows. The three onboard Gigabit Ethernet interfaces,in the Cisco 7301 VAM2+ security router bundle provides the same high performance.For further information verify the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps341/prod_bulletin0900aecd80205255.html

Similar Messages

  • 6506, 6509 Chassis Exchange along with SUP 720-3B and SUP 2T-10G

    Hi friends,
    I have a situation which looks straight forward but since I have not done this before, I thought I should put this here to have some ideas and gottchas related suggestions to look for.
    Situation 1:
    Basically I have a situation where there is an existing 6506 chassis with SUP32-GE-3B. for some business reasons we have to replace that with a 6509 chassis with SUP720-3B keeping the configuration intact.
    Situation 2:
    In another situation, we need to replace an existing standalone chassis 6509 with SUP-2T-10G with a pair of 6506 with SUP-2T-10G on each running VSS. Is there any gottachas around this work?
    Also, while I was trying to boot the spare 6506 with SUP-2T card, it constantly went to monitor mode with the following error messages
    System Bootstrap, Version 12.2(50r)SYS3, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 2012 by cisco Systems, Inc.
    PYRAMID platform with 2097152 Kbytes of main memory
    rommon 1 >
    rommon 1 > boot
    PCMCIA bootdisk: device is not initialized
    open: read error...requested 0x4 bytes, got 0x0
    trouble reading device magic number
    boot: cannot open "bootdisk:"
    boot: cannot determine first file name on device "bootdisk:"
    rommon 2 >
    Any suggestions for this? It looks like the bootflash memory is missing from the SUP. I am not sure if this flash is usually onboard on this SUP or it should be like an external PCMCIA card. 
    Look forward for your help and suggestions.
    Thanks in advance.
    Regards,
    Mohit

    Hi SJ
    The 16-port 10 Gigabit Ethernet module is interoperable with all models of the Cisco Catalyst 6500 Series Virtual Switching Supervisor Engine 720 with 10 Gigabit Ethernet uplinks or Cisco Catalyst 6500 Series Supervisor Engine 720, including VS-S720-10G-3C, VS-S720-10G-3CXL, WS-Sup720, WS-Sup720-3B, and WS-Sup720-3BXL. When mixing DFCs in the same chassis, the chassis will operate in the mode of the lowest common denominator.
    see link below
    http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/product_bulletin_cisco_catalyst_6500_series_16port_10gigabit_ethernet_module.html 
    Regards,
    Yaseen

  • Cisco 6500 with SUP 720 - Invalid boot Image

    Diagnostic sanity check on the 6500 reports Invalid boot image "bootdisk:<output omitted>
    The boot statement on the 6500 is :-
    boot system bootdisk:<filename.bin> and the 6500 boots fine.
    Please advise.
    Thank You.

    Hi ,
    I have found bug which is internally found by cisco.The bug is CSCsc98471 and following are details of bug .
    The command "show diagnostic sanity" checks amongst other things, if the current bootstring is matching pointing to an existing file.
    Since ION bootstring format has been extended (assuming an installed image) this check fails although the bootstring is correct.
    Can be easily reproduced by entering the "show diagnostic sanity" command.
    6500-6#show diagnostic sanity
    Pinging default gateway 172.26.197.33
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 172.26.197.33, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
    Could not verify boot image "sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm," specified in the boot string.
    6500-6#show bootvar
    BOOT variable = sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm,12;
    6500-6#dir sup-bootflash:/newsys/s72033/base/
    Directory of sup-bootdisk:/newsys/s72033/base/
    84 -rwx 1375696 Jan 5 2006 20:51:24 -08:00 imf.tar
    85 -rwx 12873200 Jan 5 2006 20:51:22 -08:00 s72033-adventerprisek9_wan_dbg-vm
    It is found in 12.2(18.09.20)SX3.39.
    *** open a TAC case so that the same bug is fixed in 12.2(18)SXF4.
    Hope it helps you.Plz rate it.
    Thanks,
    satish

  • 6500 sup 720 with MPLS, GRE and FWSM problem

    We have 6500 sup 720 with MPLS configured and FWSM in transparent  mode. We also terminate GRE tunnels on the same 6500.
    After implementing the command “mls mpls tunnel-recir” GRE tunnels are hardware switched (which we want them to be), but we don’t have any more connection from locations thru GRE tunnels to servers behind FWSM.
    Does anybody have idea how to solve this problem?

    Hi,
    not sure what you mean exactly.
    the command “mls mpls tunnel-recir” is needed to avoid packets corruption in cases where the Supervisor engine is handling both the GRE header encapsulation and the MPLS label stack imposition. Since it cannot do it in one single shot (without causing random corruption) recirculation is needed. Nevertheless its presence does not influence whether the GRE traffic is handled in hardware or in software. Even without it, IF THE GRE TUNNELS ARE CORRECTLY CONFIGURED (meaning that each GRE tunnels has its unique source address etc.), the traffic is handled in hardware.
    However since you say that after you enabled it you don't have connectivty anymore I suppose that some issue related to recirculation is happening (i.e. traffic ends up in the wrong internal vlan after recirculation).
    Unfortunately the support forum is not meant to help in this case as in-depth troubleshooting is required. For that you need a TAC case.
    regards,
    Riccardo

  • How many VRF-Lite Routing Instances can a 6509-E with a 720-Sup module run?

    I know that in a 4500 style switch it supports a maximum of 64 VRF-lite routing instances. However what is the maximum amount of VRF-Lite routing instances can a 6509-E switch support with a Sup-720 sup module?

    Sup 720  supports 1024 VRF Lites
    see table-1 in this link:
    http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/product_data_sheet09186a0080159856.html
    HTH

  • Difference between RSP-720 and SUP-720 on 7600

    Hi all,
    I wonder what's the big difference between RSP-720 and SUP-720. both have almost the same feature set, performance and also same price. Anyone can explain in detail?
    This can also be applied to difference between 6500 and 7600 and narrow difference between routers and switches these days.

    There are tons of differences between the RSP and the SUP 720.
    http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0900aecd8057f3b6.html
    Look @ the " Hardware Enhancements over Supervisor Engine 720" section
    The 6500 and 7600 are diverging in terms of software release support on 12.2(33)SX* for 6500 and 12.2(33)SR* for 7600 which means the feature sets will be diametrically opposite.
    E.g. VSS on Cat6k's is not available on 7600's

  • Sup 720 & Sup 32 with WS-X6408-GBIC

    I have an old 6509 with sup 1 and some WS-X6408-GBIC. Now i will upgarde to Sup 720 or Sup 32.
    I need to confirm if WS-X6408-GBIC ( no A) is compatible with the new sups? specially with the shared Bus limitation on the module.

    Ran your configuration through dynamic config tool (www.cisco.com/dprg) and it doesnt show support for that gbic blade. The closest i can find is 6408A.
    HTH
    PS: please remember to rate helpful posts!

  • Cisco 4500 Chessis Switch with sup 7l-e supports VSS for long distance upto 40 Km

    Hello Team,
    hope you will find this massage in good health and spirit.
    As per my understanding, Cisco 4507R+E with Sup-7L-E will supports VSS for long distance upto 40 Km, i have a scenario that there are two Data Centre of a Company at different graphical location (distance is 2 Km), both have separate network devices but distributed servers connectivity and all servers accessed from both location (some servers are placed in location 1 and some servers are at location 2), both location has separate ISPs link with segregation of internet connectivity (some users using internet from ISP-1 and other are using ISP-2), Core Switches of both location connected to each other via fiber (company fiber not ISP), at this moment Core Switches are configured with multi-group HSRP and next upgrade to VSS.
    My concern is if Virtual Switch link (VSL) goes down (which will configure on company fiber link) what is the behavior of Switches, both are in Master mode and working standalone or behavior are different, please confirm and suggest for better.
    Regards,
    Ammar Ud-Din

    does anyone reply me on this......

  • 6509E VSS w/Quad-Sup 720 - Traffic Forwarding Issue

    Hello all,
    I ran into an interesting problem yesterday evening while performing a quad-sup upgrade to an existing dual-sup 6509E VSS architecture. Unfortunately, the expiration of my maintenance window forced me to roll back the changes before I had the opportunity to truly discover the root issue, however, I wanted to post my experience on Support Forums with the hope that someone else has run into it before.
    The customer I was working with has an existing dual-sup (720) environment operating in VSS mode. Both sup's were installed an operational in slot 5 of each chassis. The switch ID's had been assigned as 1 and 2, and the VSL was comprised of the two 10GE interfaces connected between each of the sup modules (1/5/4-2/5/4 and 1/5/5-2/5/5). The customer wanted to increase their intra-chassis redundancy by installing two additional sup 720 modules in slot 6 of each chassis, and adding these 10GE interfaces to the VSL.
    The overall upgrade went very well. I began by physically installing an additional sup 720 in slot 6 of the VSS standby chassis, and the sup module came up into RPR-Warm status (which is the desired state). I then physically installed an additional sup 720 in the VSS active chassis, and it too came up into RPR-Warm status. After reviewing the VSS redundancy state, I determined that everything looked good, and proceeded to add the additional 10GE links (1/6/4-2/6/4 and 1/6/5-2/6/5) into the VSL configuration. I then physically connected the additional VSL links (but shifted them around as to achieve diversity between the chassis (1/5/4-2/5/4, 1/5/5-2/6/5, 1/6/4-2/6/4, 1/6/5-2/5/5). I then reviewed the VSL link state and EtherChannel state, and everything looked great.
    At that point, we were pretty much done with the switch configuration, and proceeded to verify that server/network resources were not affected. I found that there seemed to be an issue sending traffic across the VSL. For example, some physical servers connected to switch ID 1 were having a difficult time communicating to physical servers connected to switch ID 2 (this customer is still working on dual-homing hosts). I looked at all of the obvious things - physical VSL interfaces, EtherChannel status, etc., and everything looked good. I then proceeded to remove physical VSL interfaces from the configuration, eliminating those that were added that evening (e.g., all interfaces except the original 1/5/4-2/5/4 were removed) - nothing. At this point, I was 10 minutes from the expiration of the maintenance window and was forced to roll back. It wasn't until the newly added sup's were physically removed from the chassis that the issue subsided. That said, I was able to conclude that the VSL wasn't the problem at all, but perhaps the installation of the sup's was??
    All of the sup 720's were running 12.2(33)SXI6 code, which I had verified to be a safe harbor version (although there are known bugs, none appear to be related to this issue).
    Has anyone run into this issue before? Any thoughts would be appreciated!

    You bring up VSS outside of the current environemnt. Create all vlans with a spanning tree priority higher than the existing.
    Create all the vlan interfaces and leave them shutdown.
    Connect the existing core to the new VSS core. Make sure that all vlans are properly crossing the trunk between old and new cores. Depending on how you're routing is set up, you might need to create a vlan to use for routing updates only.
    At this point, you can start changing spanning tree priorities to move the root of the vlans to the vss. Once these have been moved, you can start to manipulate hsrp.
    Whichever switch has the backup interface, shut those interfaces down. After this is done, shut the vlan inteface on the old core and no shut on the vss. Since vss doesn't use hsrp, it's hard to manipulate the vss since you want the vlan interface to be the previous standby ip.
    Flipping the vlan intefaces shouldn't cause any issues. I've done this method several times in large hospitals with no issues.
    Once you have the vss running, you can move the access switches 1 link at a time. Make sure you're running rapid pvst.
    The method I've used for this is to create a port channel on both the access switch and the vss. On the vss, you can assign the interfaces into the port channel immediately. On the access switch, disconnect one of the interfaces that goes to the old core. Add the disconnected inteface into the port channel then plug it back in. It should come up as the only member of the etherchannel. After you verify this link is up properly, perform the same with the second uplink on the access switch. When you plug it in, it should join the channel and you should be fine. With rapid pvst, nothing should be noticeable when the links block and unblock.

  • Does BT IP Clear MPLS support multicast?

    Hi
    Requirement is to multicast music on hold RTP stream from a Data Center to a remote site over BT IP Clear MPLS network. Catalyst 3750 switches (both running IP Services Image) will BGP peer with BT PE equipment. The Catalyst 3750 switches will also be configured with PIM-SM.
    Does BT MPLS support IP Multicast? I could not find any info on the web so I am hoping people have tried it and (hopefully) it worked for them!
    Are there any restictictions/limitations using Catalyst 3750 for BGP peering?
    Thanks

    sidhu
    If you are looking for multicast support on mpls link then you need to ask your SP to provide you the mVPN services. Because they need to configure the default and data mdt under the vrf.
    regards
    shivlu jain

  • Sup 720 unlabelled Red LED

    I have a pair of 6513s with a pair of Supervisors in each and on one of the standby (Sup 720) front panel is a RED LED. This LED has no label and is just to the left of the Console port. I have checked reference documents and this LED is not mentioned? Any idea? Thanks

    Hi
    I feel the sup mite have got stuck up in rommon prompt and requires manual boot command to boot it up..
    once it gets booted up check out the valid ios file in the disk0 or disk1 and configure the boot system command accordingly.
    once you are thru with that save the config and check with show bootvar to verify whether the changes got replicated or not..
    regds

  • Sup 720 Fabric questions

    Hi,
    If you use a 6509-E with a Sup 720 this gives you a 720 Aggregate switch fabric which is broken down across all of teh 9 slots. However each slot only has 2 x 20 Gbps interfaces, so if you plugged in a 48 10/100/1000 you will not be able to get the full 48 Gbps throughput.
    I know it is probably impossible to generate so much traffic but i am curious as the modules are marketed as non-blocking?
    does anybody have some infor on this
    Thanks

    Fabric channels run at 20 Gbps Full Duplex, so 20 Gbps in / 20 Gbps out, so the claim is 40 Gbps in full duplex and 80 Gbps/slot with dual fabric channels
    Search for 80 Gbps:
    http://www.cisco.com/en/US/products/hw/modules/ps4835/products_data_sheet09186a00801dce34.html

  • Configure VSS on cisco 4506-E With sup ws-x45-sup8-e

    Hi There,
    I want to configure VSS on 4506-E with sup card 8 (ws-x45-sup8-e). Currently 4506-E is having 3.3.0.x0 with ROM as 15.1(1r)sg1.
    I am unable to configure VSS on this, i believe it is not support. Anyone help me on that.
    Many Thanks

    I believe VSS is not yet supported with IOS 3.3.X.  
    There's a new IOS scheduled for release by the end of June 2014.  Not sure if VSS will be supported by then.

  • Mvpn support on 6500/7600

    Hi,
    Does anyone know what the current status is for support of mvpn on the Catalyst 6500/7600 with OSM modules.
    The multicast engineering webpage says it is in EFT but I don't know how old that info is.
    Thanks.

    Assuming that you are running with the sup720-3bxl then MVPN should be released September this year.

  • MPLS MTU on FE interfaces with fixed interface MTU

    What is the recommendation for setting MPLS MTU when the hardware does not permit the setting of the interface MTU:
    PE-Edge-2(config)#int fastEthernet 0/0
    PE-Edge-2(config-if)#mtu 1524
    % Interface FastEthernet0/0 does not support user settable mtu.
    The MPLS MTU could be changed with "mpls mtu 1524", but this gives the error:
    PE-Edge-2(config-if)#mpls mtu 1524
    *Dec 24 20:54:43.467: %TFIB-3-MPLS_MTU_SET: Setting mpls mtu to 1524 on FastEthernet0/0 which is higher than the interface mtu 1500 . This could lead to packet forwarding problems including packet drops.
    Is it permissible to set the MPLS MTU greater than the interface MTU, as I thought that MPLS packets cannot not be fragmented, but rather simply dropped?
    In this scenario, is the only solution to limit the size of inbound packets with something like "ip tcp adjust-mss 1476" to avoid any potential packet drops?

    if your doing AToM then you have to change the mpls mtu in order to transport full frames over your backbone. I have the same issue with the mtu and setting the mpls mtu to 9196 while leaving the mtu at 1500 did not impact regular traffic at all but it did allow our l2vpn's to function correctly.

Maybe you are looking for

  • Error with Custom Idoc

    Hi All, I have created a custom idoc for creation of master data in the system. This custom idoc is using a custom function module to process the idocs. In the FM i have used Call transaction method to upload the master data in the sap system. Everyt

  • How do I get my item when its been shipped to a different address?

    So I ordered an iPod touch 16gb blue for myself, I got everything down: my shipping address and billing address. And right when I got the shipment notification, the address they have sent the item to is wrong. I don't live in Texas, I live in America

  • The tempory password sent to my account will not r...

    i am trying to get skype on my new tv and do you think it will let me sign in i've tried using my facebook details which signs in automatically on lap top and desk top with out a problem and I have tried changing the password on laptop and now it is

  • Issues with screensaver after playing video in iTunes

    I've recently started having an issue with my screensaver not turining itself on if i pause videos played in iTunes (fullscreen), and after escaping fullscreen view and pausing video the screensaver won't turn itself on. At all, not until I restart m

  • Are Gigabit speeds achievable, am I using the right RJ45 plugs?

    I recently purchased a AEBS, and am so pleased with it. Wireless printing work flawless and I have not be prone to any problems yet. However, I thought I would try out the Gigabit Ethernet today. I bought a Cat 6 Patch cable with the ends already fit