Unfortunately, ASRs don't support RJ45 10GE interfaces. Also, there are no SFP+ interfaces supporting 10GBaseT.
If You need to have the 10GBaseT interface, you can try to use 6500E/6800 linecards or Nexus 3000/5000 series - they have routing capabilities, but YMMV - depends on what you need this router for.
... View more
PFC stands for "Policy Feature Card" and it's present on the Supervisor, and can be present on the line cards. DFCs, or "Distributed Feature Card" are present only on the line cards, and on some devices (like Cat6500 or 7600 router) can be added at later time to upgrade the capabilities of device. For the Supervisor, PFC is always there - it can be offloaded by decisions taken by DFCs at line cards, but it's there to hold both forwarding information & features - like ACLs, QoS policies and so on. On the line cards (for Catalyst 6500 and 7600 router) there's no PFC installed, they're using central PFC on the Supervisor to provide services/forward traffic.
... View more
There is no recommended limit on ISR G2s, there's limit to the number of packets/second that can be switched through the router or some specific recommendations for advanced features - like firewall sessions/second, VPN sessions and things like that. There are thus bandwidth recommendations not user recommendations. Small ASA (5505) was limited to the number of users (10/50/unlimited) using license.
... View more
OK, it seems the 1941W config is quite complicated at start. The reality is, it's quite simple: interface Wlan-GigabitEthernet0/0 description Internal switch interface connecting to the embedded AP This is internal switch that connects all internal components together. In theory it would be able to reconnect the integrated WLAN ISM to any other port, but it seems it is hardcoded to be connected to GE0/0: edge#sh platform mgf module Registered Module Information Code: NR - Not Registered, TM - Trust Mode, SP - Scheduling Profile BL - Buffer Level, TR - Traffic Rate, PT - Pause Threshold slot vlan type/ID TM SP BL TR PT ---- ---- ---------- ------- --- ------ ----- ---- ISM/WLA 1 Switch/4 UP 1 low 1000 high EHWIC-0 NR EHWIC-1 NR While it is not obvious from this printout, it becomes apparent when you check for CDP neighbors: edge#sh cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater Device ID Local Intrfce Holdtme Capability Platform Port ID edge wlan-ap0 144 R S I CISCO1941 wlan-ap0 edge-ap Gig 0/0 127 T I AP801AGN- Gig 0 tor-core Gig 0/1 130 R S I WS-C4948 Gig 1/34 tor-core Gig 0/0 129 R S I WS-C4948 Gig 1/1 Note that Gig0/0 of 'edge' (which is a router 1941W) seems to be connected both to switch (Catalyst 4948) AND the wlan-ap0 device which is a Aironet 801AGN AP (actually, an ISM module acting as AP). For integrated WLAN AP to work in autonomous mode, where it uses two radios - dot11radio 0 which is 2.4GHz B/G/N capable, and dot11radio1 which is 5GHz A capable, it's elegant to create two bridge-groups, that are bridged over the Wlan-GigabitEthernet0/0 to GE0/0 to subinterfaces 'terminating' them in layer 3, providing IP via DHCP, etc. Here's complete config of interesting parts: router config ! this is DHCP part - the server will reside on router service dhcp ip dhcp excluded-address 192.168.20.0 192.168.20.9 ip dhcp excluded-address 192.168.21.0 192.168.21.9 ! ip dhcp pool WLAN_BGN_USERS network 192.168.20.0 255.255.255.0 default-router 192.168.20.1 dns-server 192.168.10.254 ! ip dhcp pool WLAN_A_USERS network 192.168.21.0 255.255.255.0 default-router 192.168.21.1 dns-server 192.168.10.254 ! ! if you wish to transport traffic from both radios separately, ! you will need trunk on the internal intraface - we're using ! VLAN20 (bridge-group 20) and VLAN21 (bridge-group21) ! ! note that by default, all traffic is going over VLAN1 ! (bridge-group 1) interface interface Wlan-GigabitEthernet0/0 description Internal switch interface connecting to the embedded AP switchport mode trunk ! this is the essential command ! if you wish to transport two VLANs ! this is internal interface - we choose GE0/0 as internal ! to not mess up WLAN traffic with external interface traffic interface GigabitEthernet0/0 description LAN interface ip address 192.168.10.1 255.255.255.0 ip nat inside interface GigabitEthernet0/1 description INTERNET interface ip address x.x.x.2 255.255.255.252 ! this is interface for managing integrated AP - think about it as console ! connection that needs IP layer to function properly - the IP itself may come ! from any location interface wlan-ap0 description Service module interface to manage the embedded AP ip unnumbered gigabitethernet0/0 ! those are interfaces terminating at L3 the bridge-groups from integrated AP interface Vlan20 ip address 192.168.20.1 255.255.255.0 ip nat inside ip virtual-reassembly ! interface Vlan21 ip address 192.168.21.1 255.255.255.0 ip nat inside ! note, that you need to create them also in local switch ! database to function correctly ! and the config is not visible in running configuration: ! ! edge(config)# vlan 20 ! edge(config-vlan)# name WLAN_BGN ! edge(config)# vlan 21 ! edge(config-vlan)# name WLAN_A ! ! this will end up in the output of following command: ! edge#sh vlan-switch ! ! VLAN Name Status Ports ! ---- -------------------------------- --------- ------------------------------- ! 1 default active ! 20 WLAN_BGN active ! 21 WLAN_A active ! ! ...and on the flash0: filesystem when you save the config after changes: ! ! edge#dir flash0: ! Directory of flash0:/ ! 1 -rw- 44907852 Jun 29 2010 17:09:56 +01:00 c1900-universalk9-mz.SPA.150-1.M2.bin ! 2 -rw- 720 Jun 29 2010 20:14:16 +01:00 vlan.dat ! ip route 0.0.0.0 0.0.0.0 x.x.x.1 integrated AP config in autonomous mode After connecting to the AP by doing ' service-module wlan-ap 0 session ': ! note that we will use two SSIDs, one per each radio, both using ! WPA2 PSK mode - CHANGE THE PRESHARED KEYS! dot11 ssid WLANA authentication open authentication key-management wpa guest-mode wpa-psk ascii testkeyA ! dot11 ssid WLANBGN authentication open authentication key-management wpa guest-mode wpa-psk ascii Bkeytest ! we're doing integrated routing & bridging - where we can we route, else we bridge: bridge irb ! now for the dot11radio 0, the one working in 2.4GHz frequency (802.11b/g/n) ! it will broadcast SSID 'WLANBGN' interface Dot11Radio0 description 802.11bgn radio no ip address no ip route-cache ! encryption mode ciphers aes-ccm ! broadcast-key change 3600 ! ! ssid WLANBGN ! antenna gain 0 station-role root no cdp enable bridge-group 21 bridge-group 21 subscriber-loop-control bridge-group 21 block-unknown-source no bridge-group 21 source-learning no bridge-group 21 unicast-flooding bridge-group 21 spanning-disabled ! now for the dot11radio 1, the one working in 5GHz frequency (802.11a) ! it will broadcast SSID 'WLANA' interface Dot11Radio1 description 802.11a radio no ip address no ip route-cache ! encryption mode ciphers aes-ccm ! ssid WLANA ! antenna gain 0 no dfs band block channel dfs station-role root no cdp enable bridge-group 20 bridge-group 20 subscriber-loop-control bridge-group 20 block-unknown-source no bridge-group 20 source-learning no bridge-group 20 unicast-flooding bridge-group 20 spanning-disabled ! internal GE interface bridging traffic from/to 802.11a radio - we tag it with 802.1Q 20 interface GigabitEthernet0.20 description 802.11a bridge encapsulation dot1Q 20 no ip route-cache bridge-group 20 bridge-group 20 subscriber-loop-control bridge-group 20 block-unknown-source no bridge-group 20 source-learning no bridge-group 20 unicast-flooding bridge-group 20 spanning-disabled ! internal GE interface bridging traffic from/to 802.11b/g/n radio - we tag it with 802.1Q 21 interface GigabitEthernet0.21 description 802.11bgn bridge encapsulation dot1Q 21 no ip route-cache bridge-group 21 bridge-group 21 subscriber-loop-control bridge-group 21 block-unknown-source no bridge-group 21 source-learning no bridge-group 21 unicast-flooding bridge-group 21 spanning-disabled !
... View more