802.1q support on 2610 router built-in eth interface

I read in an official Cisco document that support for 802.1q on built-in ethernet interfaces on routers was enabled for recent IOS versions. I installed an recent IOS version and still giving me a hard time. Any ideas?
I attached the document.

the ping is responding ok but the network services are pretty slow, here is the show version output:
CusSanJoseRou1#sh version
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IS-M), Version 12.2(34a), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Tue 02-May-06 11:58 by pwade
Image text-base: 0x8000808C, data-base: 0x8111CF0C
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
CusSanJoseRou1 uptime is 1 week, 5 days, 5 hours, 29 minutes
System returned to ROM by reload
System image file is "flash:c2600-is-mz.122-34a.bin"
cisco 2610 (MPC860) processor (revision 0x202) with 45056K/4096K bytes of memory.
Processor board ID JAB0331000W (4147343804)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
1 Ethernet/IEEE 802.3 interface(s)
2 Serial(sync/async) network interface(s)
1 ISDN Basic Rate interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102

Similar Messages

  • How fast can Broadcom 802.11n support for maximum?

    hey everybody,i got U160 yesterday that the WLAN adapter is  Broadcom 802.11n but i just got a connection speed of 65Mbps but i can get 150 Mbps with my G230 with intel 5100 bgn ,connecting to the same N-Router,so i am wondering how fast can Broadcom 802.11n support for maximum.......

    if readycomm installed, remove it.
    check your firewall is active and using high performance.
    by the way, which model of broadcom are you using?

  • Can't connect to Time Capsule + no 802.11n support

    I just got my new 13" MacBook (late 2008). Originally, I thought I couldn't connect to my wireless N router which happens to be Apple Time Machine. According to network utility program, my MacBook only supports a/b/g - this is not right! Now, I discover that in addition to the N problem I can't even connect to my Time Capsule wirelessly! Good thing I have 2 separate wireless routers (linksys).
    My other Macs (white MacBook and 20" iMac) have no problem connecting to Time Capsule over 802.11n. Both machine indicates 802.11n support under network utility program.
    Compound this problem with stuck 'a' key on my keyboard.
    I really, don't get this problem. I spent an hour with Apple tech with no avail. I am thinking about returning this new MacBook.

    I have the exact same problem you have described. Unable to find a solution. Odd because I have a 2007 MacBook Pro and it works fine wirelessly. Wireless-N on the MacBook works fine and it can connect to other wireless networks, just not it's home one.
    If anybody is interested, here's a dump from the console log when airport attempts to connect. Our wireless station doesn't broadcast.
    Macintosh-6 airportd[6001]: Could not find any preferred networks; trying broadcast requests..
    Macintosh-6 airportd[6001]: Broadcast requests also failed..
    Macintosh-6 airportd[6001]: Probing highest ranked networks via directed scan..
    Macintosh-6 kernel[0]: AirPort: Link Up on en1
    Macintosh-6 kernel[0]: AirPort: Link Down on en1
    Macintosh-6 airportd[6001]: Error: Apple80211Associate() failed -25
    Macintosh-6 mDNSResponder[20]: setsockopt - IPMULTICASTIF error 169.254.141.134 -1 errno 49 (Can't assign requested address)
    Macintosh-6 configd[14]: rtmsg: error writing to routing socket

  • 2610 router - determining type of device [XM vs. non-XM]

    [New to the community, not sure where to start first, so I picked here!]
    I have an old 2610 router that has been mothballed for quite a while now, that I'd like to reuse for a different purpose. To do so, I'm going to need an additional module, which I have found, but I'm not sure if the IOS is up-to-date enough to support it. The problem for me, is figuring out what I should be looking at. The specs for the device [NM-4E 4-port Ethernet network module] with regards to supported IOS versions are as such:
    2600XM Series  - 12.1(14) or 12.2(8)T1
    2600 series  - 11.3(4)T
    The problem I have is, how do I tell if I am using an XM or non-XM series device? As stated above, I know it's a 2610, but I don't know where it falls in the rest of the product line. 'show version' returns this information...
    IOS (tm) C2600 Software (C2600-I-M), Version 12.0(9), RELEASE SOFTWARE (fc1)
    ...which seems to fall right between the XM and non-XM device versions. I'm just not sure where to look for the information I need.
    Any suggestions would be appreciated.
    Thanks,

    facsniagara wrote:[New to the community, not sure where to start first, so I picked here!]I have an old 2610 router that has been mothballed for quite a while now, that I'd like to reuse for a different purpose. To do so, I'm going to need an additional module, which I have found, but I'm not sure if the IOS is up-to-date enough to support it. The problem for me, is figuring out what I should be looking at. The specs for the device [NM-4E 4-port Ethernet network module] with regards to supported IOS versions are as such:2600XM Series  - 12.1(14) or 12.2(8)T1
    2600 series  - 11.3(4)T The problem I have is, how do I tell if I am using an XM or non-XM series device? As stated above, I know it's a 2610, but I don't know where it falls in the rest of the product line. 'show version' returns this information...IOS (tm) C2600 Software (C2600-I-M), Version 12.0(9), RELEASE SOFTWARE (fc1)...which seems to fall right between the XM and non-XM device versions. I'm just not sure where to look for the information I need.Any suggestions would be appreciated.Thanks,
    Norm
    The 2610 has one 10Mbps interface.
    The 2610-XM has one 100Mbps interface.
    So either see what it reports on bootup or do a "sh ip int brief". If the ethernet interface is labelled fa... then that is fast ethernet ie. 100Mbps.
    Jon

  • I have a new Linksys router.  When I load the accompanying CD it informs me that it supports OS 10.5.8 or later, OS 10.6.1 or later, and OS 10.7 or later.  I am running 10.9.2, which apparently isn't supported by this Router.  Any suggestions?

    I have a new Linksys router.  When I load the accompanying CD it informs me that it supports OS 10.5.8 or later, OS 10.6.1 or later, and OS 10.7 or later.  I am running 10.9.2, which apparently isn't supported by this Router.  Any suggestions?

    No they should be agnostic about what is behind them, but as to support for IP6, or whether any computers or tablets can use AC... and hasn't Apple's own units sometimes stop being supported with new Mac and new versions of OS X? seems so.
    I said above, why would anyone install any kind of software to use a router? although Netgear's GEnie is or was installed on my systems that adds a nice way to log in and manage the router, so I have to take that back a notch.
    Support for modems and ISPs is a concern, my modem is not certified fully with DOCSIS 3.0 or  FIOS.
    Look around and you can find routers having trouble with some network services like Airplay, printing and scanning, the software bundled with router.
    However, ethernet chips, and the driver, can be a factor. Problems with Intel networking chip and high bandwidth streaming and not being able to handle the load when used by wifi euipment like notebooks and other devices.
    I have only seen the LARGE number of complaints on MacBook forums about wifi issues to suspect something is wrong but not sure what. And those are people that depend on wifi I assume, though some could use their Thunderbolt equipped Mac to use ethernet to get around the problems. And I am seeing the same thing with some Windows users and maybe they all have common Intel chips???
    MacBook Pro constantly losing wireless connectivity
    I use Windows 8.1 primarily. I also don't know enough or as much to know "Why is the sky blue" either.
    Just pass along this example:
    If you're setting up a new PC for the first time, check if your router is fully compatible with Windows. Because of the new networking features in Windows (8.1), some older network routers aren't fully compatible and can cause problems. For a list of routers that are compatible with Windows 8.1 and Windows RT 8.1, go to the Windows Compatibility Center.
    Anyone remember when 10.4.0 had so many issues with LAN that it could not be used, work on fix was going on and wasn't complete until 10.4.2/4.3 (and first time we got a new full 10.4.3 DVD because customers needed a reliable system.

  • Does ACE-30 support multicast in routed mode?

    We currently have ACE20's, which only support multicast in bridge mode.
    Was wondering if it's the same on ACE30's, or if Cisco finally implemented support for mcast in routed mode.
    thx
    Kevin

    Could you please confirm if this applies to both ACE20 & ACE30, or just ACE20?
    If both, when does Cisco plan on supporting mcast in routed mode?
    thx
    Kevin

  • WinPE 5 802.1x Support with SCCM 2012 R2

    Please see updated information a few posts down.
    I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012.  I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties.  I am trying to follow the guide on the deploymentguys.
     I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line.  doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2"
    does work.  I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2"  All i get is error setting
    user data for interface ethernet2, the operation is not supported.
    How does one get 802.1x working in WinPE 4.0?
    Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:
    So here's the current situation and hopefully someone has seen it before.
    My boot image has the prestart command set to x:\8021x\configure8021x.cmd.  If i make a USB boot media this command will run and work with an 8021x wire plugged in.  If I PXE boot with a non8021x
    wire plugged in this command will run.  If I PXE Boot with an 8021x
    wire plugged in it does not run the command.  If the boot image gets staged from the windows software center it
    also will not run my command.
    Does anyone know why the staged boot image and booting from PXE are not running my prestart command?  It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

    Well progress on this issue has been made.  So why I was getting the operation not supported is because I was exporting our corporate 8021x LAN profile which gets put in place by group policy, which i assumed would work.  So i unjoined the windows
    7 machine from the domain and was then able to modify the LAN profile to be what is exactly in the documentation with images.  
    Then the above command works and I no longer get the operation is not supported and I am able to move on to the next steps which is to create a script file which contains the net start and the netsh commands i was using above to test it. Great!
    Now my next issue comes up when the instructions tell me to modify the winpeshl.ini file which it says is located at X:\windows\System32\Winpeshl.ini.  So I mount the boot.wim file that I did earlier and I browse to the location in question however
    the first thing I notice is that when I open the winpeshl.ini file to go to modify it I expect to see:
    [LAUNCHAPPS]
    “%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
    Instead what I find is it says:
    [LAUNCHAPPS]
    %Windir%\system32\netstart.exe, -prompt%SYSTEMDRIVE%\sources\recovery\recenv.exe
    So I thought ok I will create a copy of this file and rename it to winpeshl.ini.bak and then modify it to say what It says it should be in the instructions which is:
    [LAUNCHAPPS]
    winpeinit.exe
    %SYSTEMDRIVE%\Windows\System32\wscript.exe, %SYSTEMDRIVE%\8021x\Configure8021xUser.wsf
    “%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
    Next I unmount the boot.wim file and overwrite the copy I had.  Next I update the distribution points and PXE boot a test machine. What I see next is
    what I dont understand.  Upon booting and hiting F8 to get to a command line I cd into x:\windows\system32\ and notice that I do indeed still have my winpeshl.ini.bak file so I open the winpeshl.ini file I had thought I modified earlier and low and behold
    it contains this which is different when I look at it when I mounted the wim file:
    [LAUNCHAPPS]
    “%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
    So something is modifying this file and setting it this way effectively overwriting what I put in so that my script can run and configure the 8021x user settings.
    Is there some updated documentation somewhere, how do I proceed from here??  
    The next steps after this would be to modify the unattend.xml file at a certain location to run the Configure8021xUserWindows.wsf script which does the winpe script just instead
    of running from X: it runs from C: as it says in the documentation.   But I can't move on to test this yet without getting the winpe part working.

  • No 802.11n support in macbook pro leopard install

    I upgraded my MacBook Pro to Leopard last week (and then updated to 1.5.1 yesterday)
    Other users here have claimed that they see 802.11n support in the Network utility (choosing en1 as the Network Interface). However, I do not. I only see a/b/g.
    I also went ahead and purchased the 802.11n enabler (for $2.16). I got an error message that the software is incompatible with my hardware. My guess is that the enabler is probably incompatible with Leopard - although the Apple Store says nothing about this.
    Why did others get 802.11n installed automatically via their Leopard upgrade but in my case it did not?
    How do I upgrade my MacBook Pro (10.5.1) to 802.11n?
    Thanks,
    Bill

    I just realized that I don't have the right mbpro for 802.11n as I don't have core 2 duo.
    ***** to be me I guess.
    I'll look for an after market solution to upgrade to 802.11n.
    Thanks.

  • Help Enabling 802.11b Support

    Can anyone help? All I want to do is enable 802.11b support on my Cisco 877W. My 802.11g clients can see and attach to it no problems. My 802.11b clients cannot see it at all. I have tried all sorts but nothing has helped. My config looks like this:
    interface Dot11Radio0
    no ip address
    encryption key 1 size 128bit 7 BC48CE99C4E9B683819990D3C1A5 transmit-key
    encryption mode wep mandatory
    ssid *****
    authentication open
    speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0
    48.0 54.0
    station-role root
    no dot11 extension aironet
    bridge-group 1
    bridge-group 1 spanning-disabled
    What do I need to add to make it visible and available to 802.11b clients?
    Many Thanks,
    Matt

    I'd start by defaulting the AP back to factory default, no WEP, no authentication.
    Check to see if the 802.11b clients can connect.
    If all the 802.11b clients are running the same software, check to see that they are up-to-date drivers & client software. If you're using the MS client software (Zero Wireless Config) try a client using the vendor's client software instead.
    If the clients are not eve associating, look at the basic parameters: things like preamble length (legacy default is "long" which is a one meg data rate)
    If you can get the 802.11b client to connect whith all open parameters, then add WEP. Be advised that some clients need the WEP entered as HEX, not ASCII.
    For example ASCII "ABCD" would be "41 42 43 44" in hex ... make sure you're using the same system. IF youre using something like "12345abcde" that can be a valid (but incorrect) hex string when ou really intend for it to be ASCII.
    Also note that leading or training spaces (ASCII 20) are valid characters. Make sure you do not have leading or training spaces in your WEP (unless you really want them there, in whch case, make sure they're there)
    Make sure the Ethernet format is correct: use the Web GUI to set up. Check the parameters on the "Interfaces" page and do not (at least initially) use the "Best throughput" or "Best Range" settings, leave it at "Default Settings"
    If your 802.11b clients are PDAs, bar-code scanners, or other hand-held devices, check that they are at default settings for the standard 802.11b protocols; some use proprietary protocols for better performance or security.
    That's about it for me ... let us know if any of that changes (works / doesn't work, but acting differently / doesn't work, looks the same).
    Good Luck
    Scott

  • Clarification on 802.1x support for 3560

    Hi all: have a question on support of 802.1x support in 3560.
    This (http://www.cisco.com/en/US/products/hw/switches/ps5528/products_configuration_guide_chapter09186a00801e85c4.html) one talks about 802.1x configuration on a 3560 with 12.1(19)EA1
    But this tool http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp tells me that IEEE 802.1x-VLAN Assignment is supported only on ED Releases 12.2(25)SEE1, 12.2(25)SED1, 12.2(25)SEC2, 12.2(25)SEB4, 12.2(25)SEA, 12.2(25)SE for 3560.
    Does this mean Cisco is recommending using 12.2.(25) for 802.1x for these switches eventhough 12.1(19) supports it?
    Thanks
    Ravi

    Only the following 3560 are supported in 12.1.19EA1:
    Catalyst 3560-24PS
    Catalyst 3560-48PS
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12119ea1/ol510401.htm#84866
    The rest of 3560 have different minimum IOS requirements:
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/125see1/ol9586.htm#wp84866
    So, wht I am trying to say is, the feature, 802.1x-Vlan Assignment is supported in 12.1(19)EA1 but depending on what kind of 3560, it will require a minimum IOS. If your 3560 is either Catalyst 3560-24PS or Catalyst 3560-48PS, you can run 802.1x-Vlan Assignment on it.
    Please rate all posts.

  • Tacacs per vrf no supported on my router, does a gre tunnel would work?

    Hi,
    Basically the problem is that I am working with old routers, checked already on feature navigator an the following commands are not supported on the router to communicate to a TACACS server that resides on a vrf:
    Configuring Per VRF for TACACS+ Servers: Example
    The following output example shows that the group server tacacs1 has been configured for per VRF AAA services:
    aaa group server tacacs+ tacacs1
    server-private 10.1.1.1 port 19 key cisco
    ip vrf forwarding cisco
    ip tacacs source-interface Loopback0
    ip vrf cisco
    rd 100:1
    interface Loopback0
    ip address 10.0.0.2 255.0.0.0
    ip vrf forwarding cisco
    Basically I can not support all the above, however I was thinking of bypassing the command creating a GRE tunnel, I just need a confirmation if the following would work, if not I would appreciated that someone can point me into a better direction:
    ON BRANCH ROUTER:
    int l0
    ip add 1.1.1.1 255.255.255.0
    no shut
    int tun10
    ip add 2.2.2.1 255.255.255.0
    ip vrf forwarding cisco
    tun so l0
    tun dest [ip add of router directly connected to tacacs server]
    ip tacacs source-interface l0
    tacacs-server host 10.10.10.1
    tacacs-server key 7 cisco
    ON REMOTE ROUTER:
    int l0
    ip add 3.3.3.3 255.255.255.0
    no shut
    int tun10
    ip add 2.2.2.2 255.255.255.0
    ip vrf forwarding cisco
    tunn so l0
    tunn dest [ip add of branch router]
    Attached is some real information, the ip address of the real tacacs server is 10.20.30.61.

    Thanks for the response but I post the question after knowing that, I already checked on Feature Navigator that THIS IS NOT SUPPORTED for my router, at the end of my configuration I am purposing a workaround using a tunnel to bybass the nonsupported configuration.
    My question to you is, does a configuration with gre with vrf can work instead of the nonsupported configuration?
    I know that the alternative is to run Radius but it is more paperwork to do than trying to implement a solution with the current IOS.
    Thanks and sorry if I didn't make self clear at the beginning of my first post.

  • SUP720 MPLS support only 700 routes per VRF?

    In following document i found that SUP720 supporting only 700 router per 1 VRF. Am i right?
    http://www.cisco.com/en/US/partner/products/hw/modules/ps4835/products_data_sheet09186a0080159856.html

    There is no such thing as a limit of 700 routes per VRF. What is described in this URL is that scalability testing has been performed with 1024 VRFs with 700 routes each (1024*700=716800 routes total).
    You could go way beyond 700 routes per VRF if you don't plan to provision that many VRFs.
    Let me know if I answered your question,

  • Extreme 802.11n support for POE 802.3af?

    Can anyone confirm if the new (current) generation Airport Extreme 802.11n supports PoE installation? There was a special -- also called education -- version of the previous generation Extreme based station for POE installation.
    thanks.
    * Nevermind, found previous posts!

    jheiliger, Welcome to the discussion area!
    The new square 802.11b/g/n AirPort Extreme base station (AEBS) apparently does NOT support POE (Power over Ethernet).

  • 802.1x support Preboot Execution Environment (PXE)

    Hi,
    I'd like to know if 802.1x support Preboot Execution Environment (PXE) and how its configured?
    Anyone have implemented that?
    Thanks
    BR

    Some info in an FAQ will help:
    <http://www.cisco.com/application/pdf/en/us/guest/netsol/ns75/c685/ccmigration_09186a0080259020.pdf>
    The Guest-VLAN is an alternative for dealing with this if your machines are not capable of supporting the new EFI from Intel (hence lack of 802.1x for PXE).

  • Cad ver 8 NIC test for 802.1q support

    Hi Pros,
    UCCX SRND ver 8 mentions that "appendix C on Cisco CAD Installation Guide" describes a way to test whether a computer NIC supports 802.1q for monitoring and recording services.
    Couldnt find appendix C on the guide 
    Anyone knows about where I can find this info or way to test the 802.1q support?
    Regards,
    Pratik

    Hi Pratik,
    IP Communicator (in SCCP) is indeed supported as one of the monitoring devices, this is listed in the Hardware/Software compatiblity matrix for UCCX. (http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf)
    As your CIPC will be installed on the same PC as the CAD, the RTP packets will be received on this PC and CAD will be able to access them.
    Regards,
    Angelique

Maybe you are looking for