Cisco Catalyst 2955 Causes Some Devices to "Die" During Boot

I posted this question in the LAN section of the forums, but I realize this is probably the proper forum for my question.
I have recently purchased a Cisco Catalyst model WS-2955C-12 switch. During POST (boot), the console reports that the switch undergoes what is known as a "FRONT-END LOOPBACK TEST". During this test the 14 port lights on the device light up amber for a moment, connectivity is lost, and after a second or two the lights go off and connectivity returns. We've found that the moment the lights go off at the end of this test, if we have a specific device (with a specific ethernet chip) directly connected to the switch the ethernet chip is adversely affected by this test - the device "goes dark" and is not capable of communicating with anything (including other switches, routers, etc...) until it is power-cycled. What exactly does this FRONT-END LOOPBACK TEST do (I know it's for validating the ports for hardware defects), and what does it send across the wire that could be causing my ethernet chip onboard the device to go bonkers?
Thanks!
-Danny

The ethernet chip on the device (the device is a National Instruments product) is an STMicro STE10/100E, and I'm fairly confident I now know what's happening but I don't know why.
When my ethernet chip is in Autonegotiate mode, the "FRONT-END LOOPBACK TEST" performed by the catalyst does something where, at the conclusion of the test, the ethernet chip goes into an autonegotiation state and never comes back out of it. I'm thinking the "FRONT-END LOOPBACK TEST" is sending something across the wire that's confusing this specific ethernet chip; I've tried 3 Intel parts and also a Broadcom part and they rode it out in autonegotiation mode just fine. If I put the STE chip into a manually-configured mode the "FRONT-END LOOPBACK TEST" doesn't cause it to "go dark".
So, my question is really what does the FRONT-END LOOPBACK TEST do? Does it perform a remote loopback test (the STE10/100E doesn't support loopback tests)?
-Danny

Similar Messages

Front-End Loopback Test on Catalyst 2955 causes connected hardware to "die"

I have recently purchased a Cisco Catalyst model WS-2955C-12 switch. During POST (boot), the console reports that the switch undergoes what is known as a "FRONT-END LOOPBACK TEST". During this test the 14 port lights on the device light up amber for a moment, connectivity is lost, and after a second or two the lights go off and connectivity returns. We've found that the moment the lights go off at the end of this test, if we have a specific device (with a specific ethernet chip) directly connected to the switch the ethernet chip is adversely affected by this test - the device "goes dark" and is not capable of communicating with anything (including other switches, routers, etc...) until it is power-cycled. What exactly does this FRONT-END LOOPBACK TEST do, and what does it send across the wire that could be causing my ethernet chip onboard the device to go bonkers?
Thanks!
-Danny

Cisco IOS Release 12.1(22)EA1 runs on Catalyst 2955, Catalyst 2950, and Catalyst 2940 switches.
Review the new software features, open caveats, and resolved caveats sections for information specific to your switch. The information in this document refers to all the switches, unless otherwise noted.
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
If you are installing a new switch, refer to the Cisco IOS release label on the rear panel of your switch.
If your switch is running, you can use the show version user EXEC command. See the "Finding the Software Version and Feature Set" section.
If you are upgrading to a new release, refer to the software upgrade filename for the Cisco IOS version.
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/12122ea1/ol554602.htm

IMPORTANT!!!! 400wPSU cause some AGP8x shut down during lauch games?

Hi,guys
i think there are many people have the same problem as the topic
i've read some thread regarding to the unstable of play games using agp8x cards
here are some graphic cards that i know
radeon9500 series
radeon9600 series
radeon9700 series
radeon9800 series
nvidia gf4 ti series
can any help us is it true that the problem is from PSU
http://www.msi.com.tw/program/e_service/forum/index.php?sid=&postid=177066#post177066
here is a person who fix the problem with 550w psu

Don´t think so. My friend has a 350W-Ultra-Silent-PSU and it´s working fine with his 865PE-Neo2 LS and a Radeon 9700.
I have a 365W-PSU and a Radeon 9700pro and it´s also working fine.
Of course the detailed specs of the PSU are important. Current on 5V, 3,3V, 12V and so on.
There are other problems, bios/hardware related (PAT, HT, S-ATA on ICH5R) which are still unsolved by MSI.
At many times "change your PSU, it´s too weak!!!11" is just an "easy" answer by some people here in this forum.

Ask the Expert: Layer 2 Security on Cisco Catalyst Platforms

With Wilson Bonilla
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about about issues in designing, planning, and implementing Layer 2 security in your LAN network with expert Wilson Bonilla.
Wilson will cover topics that network engineers face daily such as Spanning Tree Protocol security, private VLANs, IP source guard, protected ports, dynamic ARP inspection, virtual LAN access-control lists (VLAN ACLs), and Dynamic Host Configuration Protocol (DHCP) snooping over Cisco Catalyst platforms. With the fast growth of networks, Layer 2 security is even more critical in the LAN to help your network become more reliable, efficient, and secure. Wilson will answer your questions about LAN networks with Cisco Catalyst switches.
Wilson Bonilla is a technical networking trainer at the Learning and Development Department for Cisco Technical Assistance Center located in Costa Rica. Before joining the Training Department, he worked for the Cisco TAC as a customer support engineer focused on LAN Switching for more than two years. While working on LAN switching, Wilson also had roles such as technical leader and trainer, adding to his area of expertise in Cisco Catalyst Layer 2 switching. He has CCNP routing and switching certification and is currently studying to achieve his CCNA certification in data center.
Remember to use the rating system to let Wilson know if you've received an adequate response.
Because of the volume expected during this event, Wilson might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure community, subcommunity, LAN, Switching and Routing, shortly after the event. This event lasts through November, 2013. Visit this forum often to view responses to your questions and those of other Cisco Support Community members.

Hello NetNavi.
Check the post above about MacSec for more information and let me know if you need further clarification, if so I will do my best,
In regards to best practices there is a Cisco document; it describes deployments and best practices in every scenario; Supplicants, authenticator, authentication services and other configurations. Please check it out:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6586/ps6638/deploy_guide_c17-663760.html
In regards to Private VLANS:
What is a Private Vlan?
A private Vlan is a way to isolate hosts within the same Vlan or broadcast domain. So even when you might have devices sharing the same broadcast domain they can be isolated, this isolated is configured based on sub-domains also most often called primary and secondary Vlans.
What is a primary Vlan?
The primary Vlan is representation of the private Vlan, a primary Vlan has one or more secondary Vlans, a switch uses the primary Vlan to present traffic from the secondary Vlans to its neighboring devices.
What is a secondary Vlan?
A secondary Vlan is a sub-domain of the primary Vlan. We could say that the secondary Vlans belongs to the primary. The must be associated to a primary Vlan. There are two types of secondary vlans: Isolated and Community secondary Vlans.
What does it happen to host within a secondary isolated Vlan?
Host within the isolated vlan; can’t communicate to neither other host in the same isoalted vlan nor host in a community vlan.
What does it happen to host within the secondary community Vlan?
Host within the community Vlan can communicate with other host assigned to the same community vlan, but they can’t talk to host in other community vlans.
What are the benefits of implementing private Vlans?
Scalability: The most common scenario is a service provider. Imagine all customers of a service provider connected through DSL, cable modem… it’s very likely that all customers belong to the same broadcast domain, however if that’s the case why is it that I can’t use my neighbor’s printer, or maybe why is it that I can’t access the files he has store in his computer, (security) we are in the same broadcast shouldn’t I be able to at least ping his ip address?. Well that’s because the ISP must guarantee some type of security for their customers, and because put every single customer that they have in a single Vlan is not scalable they use private Vlans.
Examples:
ISP use private vlans to protect from security bridges, Private vlans and isolated Vlans are used to protect personal information for example from one customer to another.
DMZ; Many implementations utilizes private vlans in a DMZ to limt or minimize that risk of a compromised server.
I would like to share this documentation with you for further information and configuration guidelines
http://www.cisco.com/en/US/tech/tk389/tk814/technologies_configuration_example09186a008017acad.shtml#hw
This document explains what Cisco Catalyst switches support Private Vlans.
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml
Let me know if you have further questions.
Regards
Wilson B.

Cisco Catalyst Supervisor communication issue?

Hey all,
I had a slight issue regarding two supervisor engines on a Cisco Catalyst 4500 device where the keepalives between the two sups lost communication for roughly 50~ seconds. This triggered an SNMP alert but it looks like they regained connectivity before a switchover was initiated. Has anyone ever experienced anything like this before?

You obviously need to configure the ports etc. but the switch should recognise the module as long as you have an IOS that supports it.
There is nothing extra to do, you just slot the module in.
If you are connecting all your distribution switches to the 6500 then if you don't need a vlan/IP subnet in multiple buildings then you should use L3 connections to the 6500.
Note also that you may want to consider at some time in the future a second supervisor or another chassis as this 6500 with one supervisor is a single point of failure ie. if it goes then there is no communication between buildings.
Jon

Cisco Catalyst 2950/2960/3750 Multicast Traffic Preference

Hello all,
we, as a student company act as an ISP for university dormitories. We would like to (if it's possible) deploy QoS to prefer multicast traffic over all other types of traffic.
Devices used in network:
Acces layer: Cisco Catalyst 2950, 12.1(22)EA14
Dristribution layer: Cisco Catalyst 2960G, 12.2(58)SE1
Core layer: Cisco Catalyst 3750G, 12.2(52)SE
Do you see any possibility to solve this with these devices? We have almost no experience with QoS, therefore any help would be greatly appreciated.
Thanks in advance.

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
Hmm, I think it should be doable although the 2950s, if non-E variants, are especially weak in QoS features. I.e. those might create some issues.
With the 2960G and 3750G, you often will create problems when you enable QoS because QoS, by default, allocates its buffers resources for 4 egress queues per port rather than using all for 1 egress queue per port. However, this can be countered by QoS parameter tuning, but that takes some QoS expertize to match to your traffic and your overall QoS policy.

Which one is the console port of a cisco catalyst 500 express ?

i cant find it anywhere ?

jillesmiedema,
I haven't used that type of Cisco switch myself but did some research and it looks like there is no console port on this switch. It appears to be set up via a GUI application.
See this link...
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6545/product_data_sheet0900aecd80322aeb.html
which states this...
The Cisco Catalyst Express 500 Series switches are designed for ease of use. The switch is initialized through the GUI Device Manager; no console cable or terminal emulation application is needed
As far as help setting this switch up please see the following link which should get you started in the right direction...
http://www.cisco.com/en/US/docs/switches/lan/catalystexpress500/release_12.2_25_fy/quick/start/1708402.html
Hope this helps you out. Let us know how it goes.
Ryan

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: Can Ping a device in another VLAN, that device cannot ping back

Cisco 1941 Router-on-a-Stick w/ 11VLANs trunked to a Cisco 2960: From the Switch I can Ping a device in another VLAN, that device cannot ping back. Some devices can ping devices in other VLANs and the device in the other VLAN can successfully return the Ping. Have a look at the attached diagram.
Router Config:
show run
Building configuration...
Current configuration : 7224 bytes
! Last configuration change at 09:05:48 EDT Wed Aug 6 2014
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname ROUTER
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -8 0
ip cef
ip name-server 8.8.8.8
no ipv6 cef
multilink bundle-name authenticated
license udi pid CISCO1941/K9
object-group network Net_Obj_Group1
description This network group allows all 10.0.0.0 and Email Forwarder server through to the Plt PCs
205.191.0.0 255.255.0.0
10.0.0.0 255.0.0.0
object-group network Net_Obj_Group2
description This Network Group includes the Host IPs allowed through the Plant Router
host 10.194.28.23
host 10.194.28.25
host 10.194.28.26
host 10.194.28.27
host 10.194.28.28
host 10.194.28.29
host 10.194.28.37
host 10.194.28.39
host 10.194.28.40
host 10.194.28.70
host 10.194.28.130
host 10.194.28.131
host 10.194.28.132
host 10.194.28.133
host 10.194.28.134
host 10.194.28.135
host 10.194.28.136
host 10.194.28.137
host 10.194.28.138
host 10.194.28.139
host 10.194.28.140
host 10.194.28.141
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description Port Ge0/0 to IT Enterprise network Switch GE1/0/38
ip address 10.194.28.111 255.255.255.0
ip access-group 105 in
ip access-group 106 out
ip nat outside
ip virtual-reassembly in
shutdown
duplex full
speed auto
no mop enabled
interface GigabitEthernet0/1
description Port to Plant PCN-K/L24 Sw1 Port 0/24
no ip address
duplex auto
speed auto
no mop enabled
interface GigabitEthernet0/1.102
description Port to VLAN 102
encapsulation dot1Q 102
ip address 192.168.102.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.104
description Port to VLAN 104
encapsulation dot1Q 104
ip address 192.168.104.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.105
description Port to VLAN 105
encapsulation dot1Q 105
ip address 192.168.105.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.106
description Port to VLAN 106
encapsulation dot1Q 106
ip address 192.168.106.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.107
description Port to VLAN 107
encapsulation dot1Q 107
ip address 192.168.107.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.111
description Port to VLAN 111
encapsulation dot1Q 111
ip address 192.168.111.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.117
description Port to VLAN 117
encapsulation dot1Q 117
ip address 192.168.117.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.121
description Port to VLAN 121
encapsulation dot1Q 121
ip address 192.168.121.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.125
description Port to VLAN 125
encapsulation dot1Q 125
ip address 192.168.125.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.150
description Port to to VLAN 150
encapsulation dot1Q 150
ip address 192.168.150.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.999
description Port to VLAN 999
encapsulation dot1Q 999
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
no ip http secure-server
ip nat inside source static 192.168.102.201 10.194.28.23
ip nat inside source static 192.168.121.201 10.194.28.25
ip nat inside source static 192.168.106.251 10.194.28.26
ip nat inside source static 192.168.107.245 10.194.28.27
ip nat inside source static 192.168.102.251 10.194.28.28
ip nat inside source static 192.168.150.201 10.194.28.29
ip nat inside source static 192.168.107.179 10.194.28.37
ip nat inside source static 192.168.111.201 10.194.28.39
ip nat inside source static 192.168.105.201 10.194.28.40
ip nat inside source static 192.168.106.21 10.194.28.70
ip nat inside source static 192.168.107.146 10.194.28.130
ip nat inside source static 192.168.107.156 10.194.28.131
ip nat inside source static 192.168.107.161 10.194.28.132
ip nat inside source static 192.168.107.181 10.194.28.133
ip nat inside source static 192.168.107.191 10.194.28.134
ip nat inside source static 192.168.106.202 10.194.28.135
ip nat inside source static 192.168.106.212 10.194.28.136
ip nat inside source static 192.168.117.190 10.194.28.137
ip nat inside source static 192.168.117.100 10.194.28.138
ip nat inside source static 192.168.106.242 10.194.28.139
ip nat inside source static 192.168.125.100 10.194.28.140
ip nat inside source static 192.168.125.99 10.194.28.141
ip nat outside source static 10.194.28.23 10.194.28.23
ip nat outside source static 10.194.28.25 10.194.28.25
ip nat outside source static 10.194.28.26 10.194.28.26
ip nat outside source static 10.194.28.27 10.194.28.27
ip nat outside source static 10.194.28.28 10.194.28.28
ip nat outside source static 10.194.28.29 10.194.28.29
ip nat outside source static 10.194.28.37 10.194.28.37
ip nat outside source static 10.194.28.39 10.194.28.39
ip nat outside source static 10.194.28.40 10.194.28.40
ip nat outside source static 10.194.28.70 10.194.28.70
ip nat outside source static 10.194.28.130 10.194.28.130
ip nat outside source static 10.194.28.131 10.194.28.131
ip nat outside source static 10.194.28.132 10.194.28.132
ip nat outside source static 10.194.28.133 10.194.28.133
ip nat outside source static 10.194.28.134 10.194.28.134
ip nat outside source static 10.194.28.135 10.194.28.135
ip nat outside source static 10.194.28.136 10.194.28.136
ip nat outside source static 10.194.28.137 10.194.28.137
ip nat outside source static 10.194.28.138 10.194.28.138
ip nat outside source static 10.194.28.139 10.194.28.139
ip nat outside source static 10.194.28.140 10.194.28.140
ip nat outside source static 10.194.28.141 10.194.28.141
ip route 0.0.0.0 0.0.0.0 10.194.28.1
access-list 105 permit ip object-group Net_Obj_Group1 object-group Net_Obj_Group2
access-list 106 permit ip object-group Net_Obj_Group2 object-group Net_Obj_Group1
dialer-list 1 protocol ip permit
control-plane
banner login ^CC
Login banner for Plant Router #01^C
banner motd ^CC
MOTD Banner for Plant Router^C
line con 0
password XXXXXXXXX
logging synchronous
login
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password XXXXXXXXX
logging synchronous
login
transport input all
scheduler allocate 20000 1000
ntp server 10.199.100.92
end
Switch Config:
sh ru
Building configuration...
Current configuration : 6513 bytes
version 12.2
no service pad
service timestamps debug uptime
service timestamps log datetime localtime show-timezone
service password-encryption
hostname K24Sw01
boot-start-marker
boot-end-marker
no aaa new-model
clock timezone EDT -5
clock summer-time EDT recurring
udld aggressive
crypto pki trustpoint TP-self-signed-593746944
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-593746944
revocation-check none
rsakeypair TP-self-signed-593746944
4B58BCE9 44
quit
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
interface FastEthernet0
no ip address
interface GigabitEthernet0/1
description Trunk port for vlans 105, 111, 125 and 999 from K24Sw01 port Ge0/1 to P22Sw01 port Ge0/24
switchport trunk allowed vlan 105,111,125,999
switchport mode trunk
interface GigabitEthernet0/2
description Trunk port for vlans 150 and 999 from K24Sw01 port Ge0/2 to N25Sw01 port Ge0/26
switchport trunk allowed vlan 150,999
switchport mode trunk
interface GigabitEthernet0/3
description Trunk port for vlans 102, 104, 106, 107, 117 and 999 from K24Sw01 port Ge0/3 to K28Sw01 port Ge0/26
switchport trunk allowed vlan 102,104,106,107,117,999
switchport mode trunk
interface GigabitEthernet0/4
description Trunk port for vlans 102, 106, 107 and 999 from K24Sw01 port Ge0/4 to H23Sw01 port Ge0/26
switchport trunk allowed vlan 102,106,107,999
switchport mode trunk
interface GigabitEthernet0/5
description Trunk port for vlans 121, 125 and 999 from K24Sw01 port Ge0/5 to M21Sw01 port Ge0/24
switchport trunk allowed vlan 121,125,999
switchport mode trunk
interface GigabitEthernet0/6
description OPEN
spanning-tree portfast
interface GigabitEthernet0/7
description OPEN
spanning-tree portfast
interface GigabitEthernet0/8
description OPEN
spanning-tree portfast
interface GigabitEthernet0/9
description OPEN
spanning-tree portfast
interface GigabitEthernet0/10
description VLan 102 access port
switchport access vlan 102
spanning-tree portfast
interface GigabitEthernet0/11
description - VLan 104 access port
switchport access vlan 104
spanning-tree portfast
interface GigabitEthernet0/12
description - VLan 105 access port
switchport access vlan 105
spanning-tree portfast
interface GigabitEthernet0/13
description - VLan 106 access port
switchport access vlan 106
spanning-tree portfast
interface GigabitEthernet0/14
description - VLan 107 access port
switchport access vlan 107
spanning-tree portfast
interface GigabitEthernet0/15
description - VLan 111 access port
switchport access vlan 111
spanning-tree portfast
interface GigabitEthernet0/16
description - VLan 117 access port
switchport access vlan 117
spanning-tree portfast
interface GigabitEthernet0/17
description - VLan 121 access port
switchport access vlan 121
spanning-tree portfast
interface GigabitEthernet0/18
description - VLan 125 access port
switchport access vlan 125
spanning-tree portfast
interface GigabitEthernet0/19
description - VLan 150 access port
switchport access vlan 150
spanning-tree portfast
interface GigabitEthernet0/20
description - VLan 999 access port
switchport access vlan 999
spanning-tree portfast
interface GigabitEthernet0/21
description OPEN
spanning-tree portfast
interface GigabitEthernet0/22
description OPEN
spanning-tree portfast
interface GigabitEthernet0/23
description OPEN
spanning-tree portfast
interface GigabitEthernet0/24
description From ROUTER Gw ge0/1
switchport trunk allowed vlan 102,104-107,111,117,121,125,150,999
switchport mode trunk
interface GigabitEthernet0/25
interface GigabitEthernet0/26
interface Vlan1
no ip address
no ip route-cache
shutdown
interface Vlan102
ip address 192.168.102.253 255.255.255.0
interface Vlan104
no ip address
no ip route-cache
interface Vlan105
no ip address
no ip route-cache
interface Vlan106
no ip address
no ip route-cache
interface Vlan107
no ip address
no ip route-cache
interface Vlan111
no ip address
no ip route-cache
interface Vlan117
no ip address
no ip route-cache
interface Vlan121
no ip address
no ip route-cache
interface Vlan125
no ip address
no ip route-cache
interface Vlan150
no ip address
no ip route-cache
interface Vlan999
no ip address
no ip route-cache
ip default-gateway 192.168.102.1
ip http server
ip http secure-server
snmp-server engineID local 00000009020000019634C2C0
snmp-server community public RO
snmp-server location
snmp-server contact
banner motd ^CCC ADMIN USE ONLY! ^C
line con 0
session-timeout 10
password xxxxxx
logging synchronous
login
stopbits 1
line vty 0 4
session-timeout 10
password xxxxxxx
login
line vty 5 15
session-timeout 10
password xxxxxxxx
login
ntp server 10.199.100.92
end
K24Sw01#

HI Mark,
Here is the my config:
Create sub-interfaces, set 802.1Q trunking protocol and ip address on each sub-interface
Router(config)#interface f0/0
Router(config-if)#no shutdown
(Note: The main interface f0/0 doesn’t need an IP address but it must be turned on)
Router(config)#interface f0/0.10
Router(config-subif)#encapsulation dot1q 10
Router(config-subif)#ip address 192.168.10.1 255.255.255.0
Router(config-subif)#interface f0/0.20
Router(config-subif)#encapsulation dot11 20
Router(config-subif)#ip address 192.168.20.1 255.255.255.0
(Note: In the “encapsulation dot1q 10″ command, 10 is the VLAN ID this interface operates in)
Configure VLAN
Switch(config)#vlan 10
Switch(config-vlan)#name SALES
Switch(config-vlan)#vlan 20
Switch(config-vlan)#name TECH
Set ports to access mode & assign ports to VLAN
Switch(config)#interface range fa0/1
Switch(config-if)#no shutdown
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 15
Switch(config-if)#interface range fa0/3
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode access
Switch(config-if)# switchport access vlan 20
Switch(config-if)#interface range fa0/5
Switch(config-if)#no shutdown
Switch(config-if)#switchport mode trunk
1. Please check all your port are up.
2. Check the config once again.
3. Make sure the swicth and router connection port configured as trunk and it should be up.
This config is working for me,
Regards
Dont forget to rate helpful posts.

LMS 3.2 some devices appear by IP not hostname

dears
i've problem in LMS 3.2 that some devices appear in RME by ip not hostname although they are in HOSTS file !
i tried to use resolver.pl tool and it can fetch the host name when typing the ip but devices still appearing by ip !
i'm using Comon Services 3.3

The device which are already in LMS DCR would stay as it is, if they are added by IP already.
If you are sure all the devices are in hosts file, than you should modify your scheduled discovery job for Update DCR Display Name check box.
Select this checkbox if you want to update the display name of the devices that already exist in DCR, in the next Device Discovery cycle.
For example, consider a device which is discovered by Common Services Device Discovery, exists in DCR with the display name as its hostname.
If you change the Preferred DCR Display Name as IP Address for the next Device Discovery, Common Services Device Discovery will update the display name of the device as its IP Address in DCR after the next Device Discovery.
The display name of devices are not overwritten in the future Device Discovery cycles if you have not selected this option.
For more details check :
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.3/user/guide/dcr.html#wp1469536
-Thanks

Cisco Catalyst 3850 as ntp master

Hi All,
I have 2 x Cisco Catalyst 3850 stacked together. What are your recommendations if I use the C3850 as a ntp master for all edge switches connected in my network? All edge switches must be authenticated if it needs NTP sychronization. But other than that, what are the downsides?
For example,
1. I heard that switches do not have an internal clock so is a poor device to be a centralized NTP master.
2. I have also read that switches also have slow CPU processors that may lack the processing required.
3. Its NTP sychronization will use external NTP servers which are resolved into IP addresses (e.g. pool.ntp.org). IP address can change. What other more reliable NTP sources are there?
4. Any other thoughts and comments are most welcome.

Firstly, DO NOT use the command "ntp master". Cisco do not recommend using this commands because this will confuse the NTP propagation inside the network.
Next, all Cisco devices do not have a dedicated clock. All appliances need to get SNTP/NTP time synch from somewhere. This "somewhere" could either be a dedicated GPS-based NTP server and/or a time synch somewhere out in the internet.
You can also use the command "ntp update-calendar". This new command allows appliances to take regular "snapshot" of the time and save it into the NVRAM. In case there was a reboot or a power failure, the appliance's time is not too far away instead of waiting 5 to 10 minutes for SNTP/NTP to synch.

Equium A60-157: error caused by device driver

Hi all,
I'm trying to write my PhD thesis at the moment and am being hampered by my laptop! It keeps randomly bringing up the blue screen of death and then restarting; when it's all loaded up, I get a 'serious error' message that says 'error caused by device driver'. As far as I know, all the programs I have are compatible... I was advised to restore factory settings, which I did a few months ago. And I've had the BIOS update suitable for my computer. But it's still happening!!
If it helps, the programs I use daily are Microsoft Word, Access and Powerpoint, Internet Explorer and MSN Messenger. I don't run any high spec games (only Minesweeper occasionally!)
What can I do? Does anyone else have this problem? Any advice would be much appreciated, as these crashes are not helping my work!
Thanks...

Hi guys,
I seem to have a similar problem. About a month ago I reinstalled windows using the product recovery cd and three days later I started getting a blue screen. But the error occurs only when shutting down (not always, I can`t see any pattern)- right before the shut down itself, windows has already logged off and settings are saved. The error code is 0x50 and the report says it is caused by an unknown device driver.
The day that stop error started I installed an educational software (Leankey's) for which I used a virtual cd. But at the initial launch the program "freezed" and I had to close it and open it again, there wasn`t a problem. After that I tried to copy some files on a blank cd (without using any burning software) and it said that the device was not accessible.
I tried disabling DMA but that didn`t help. In the event viewer I saw error messages that say the cdrom has a bad block. I`m not sure whether this has something to do with the stop error but they started at the same time. I can still burn cds with other software (nero). I tried to update the device driver but it didn`t help.
Maybe I have to uninstall the driver first but from the device manager when I check the properties of the device (driver details) it uninstalls the device and the driver remains. Should I delete the driver files manually? I have checked all device drivers and they are all compatible. All installed software is digitally signed. (I immediately removed the Learnkey`s software but I think it has changed some dll...
I will appreciate any suggestions.
P.S. When I run the toshiba diagnostic tool it skips testing the cd/dvd but it doesn`t say why.
Details about my system:
Satellite Pro L10
MS Widows XP Pro 5.1.2600 SP2
BIOS: v 2.60 (updated 2 days ago)
Intel Celeron M 1.60 GHz
496 MB Ram
55.890 GB
Video: Intel 82852/82855 GM/GME Graphics Controller ver=6.14.10.3929
Sound: Conexant AC-Link Audio
Network: Realtek RTL8139/810x Family Fast Ethernet NIC
Modem: AC97 SoftV92 Data Fax Modem with SmartCP ver=7.12.13.50
IDE Device 1: Fujitsu MHV2060AT
IDE Device 2: None
IDE Device 3: Mat****a DVD-Ram UJ-831S Firmware=1.90
Internet Explorer:
6.0.2900.2180

XFi-2- Latest firmware (1.20.08) has caused some issues on 32GB model...

HXFi-2- Latest firmware (.20.08) has caused some issues on 32GB model... When I started my PC last night, it notified me that new firmware was avaliable so it downloaded it and installed it on my Xfi-2 32GB
According to the release notes, it was to add support for the 64 GB model as well as some general improvements.
I can't determine what the latest improvements were (anyone have any clues ) and the UI seems the same.....the only things that have changed are that my applications no longer work (when I go into the applications shortcut, it says there is no valid content: I haven't touched these folders etc and they are still populated with the three standard apps as far as I can tell)
The other thing (which may not be related to the firmware upgrade) is that my photos shortcut now pulls up some of my music folders that contain album art. Is this a feature or a bug (I don't want it to happen, I just want it to show photos within the 'photos' folder on the device).... I think it may have been caused by me simply dragging and dropping music folders onto the device using windows explorer rather than going through Centrale (slow!)
Cheers

Hi Timmo.
What release notes are you reading? I have seen no reference to improvements other than adding support for the new 64 GB model on this firmware version. From the description of the problems you have, it seems that your player has some sort of file system corruption on the internal flash. I would suggest reinstalling the firmware on your device after formatting it (formatting the device only should be enough, I think).
The size of the new firmware release, double than the size on the previous one, means that it probably has new features and applications that will be enabled on the future; however I doubt it means it has new features right now and hope it does not means we have two firmwares (on for the 64 GB model and other for the previous ones) as the SRM/AlphaBIOS pair on the Digital Alpha systems (an ugly hack on these superb computers, in my humble opinion) -- by the way, the new firmware does not require more space on the internal flash (I have 5077 MB available on mine with all firmware releases).
The behavior you describe about album art being shown on the photos shortcut happens with older firmware releases too; I prefer album art embedded on the audio files instead of being available as another file. I agree with you, only pictures under the photos directory should be shown as images.
Cheers.

802.1x on Cisco Catalyst 2960

I am trying to enable 802.1x on one of
the switchports of the Cisco Catalyst
2960:
C2960#sh run | i radius
aaa authentication login test group radius local
aaa authentication dot1x default group radius
radius-server host 10.250.97.26 auth-port 1812 acct-port 1813
radius-server source-ports 1645-1646
radius-server key 123456
C2960#sh run | i dot
aaa authentication dot1x default group radius
dot1x system-auth-control
dot1x guest-vlan supplicant
dot1x critical eapol
C2960#conf t
Enter configuration commands, one per line. End with CNTL/Z.
C2960(config)#int g0/14
C2960(config-if)#dot1x ?
% Unrecognized command
C2960(config-if)#dot1x
As you can see, I can not enable 802.1x
at the interface level. The code is am running is 12.2.25SEE4:
Switch Ports Model SW Version SW Image
* 1 24 WS-C2960G-24TC-L 12.2(25)SEE4 C2960-LANBASEK9-M
System image file is "flash:c2960-lanbasek9-mz.122-25.SEE4.bin"
According to Cisco, this image supports
802.1x. Why can't enable it at the
interface level?
Can someone help me out? Thanks.

some additional info:
C2960#sh dot1x all
Sysauthcontrol Enabled
Dot1x Protocol Version 2
Critical Recovery Delay 100
Critical EAPOL Enabled
C2960#

Adding a new subscriber in CUCM 9.1.2 cluster cause all device reset

I am on CUCM version 9.1.2 ,whenever i add the subscriber /upgrade the subscriber to Cluster ,all the registered devices drops .
Not sure why ,In Cisco Documentation ,it never stated this bug in 9.1.2 service release notes.
However , In 9.1.1 mentioned about this in important notes.
CSCub12922: Adding a new subscriber causes device reset
After you install a new node in an existing cluster, all phones that are registered to the cluster are reset.
Anyone experienced ? or aware about this bug?
Is this the case going forward in any version after 8.X? for subscriber addition to cluster will reset the devices?
Thanks
Manoj

Hi Manoj,
As per the following bug
https://tools.cisco.com/bugsearch/bug/CSCub12922/?reffering_site=dumpcr
Symptom:
Add new subscriber to existing 8.x CUCM cluster cause all device reset
Conditions:
Adding a new subscriber to existing 8.x CUCM cluster cause all device reset due to database update. Issue recreated in lab when "Prepare Cluster for Rollback to pre 8.0" set to both true & false. The symptom and logs are the same in each scenario
This is not a bug. The condition is applicable only to CUCM 8.6 and higher releases. Whenever a node is added to CUCM cluster , from CUCM 8.6 onwards , the phones belonging to that Call Manager group will be automatically restarted
Workaround:
None
So, this applies to all 8.6+ releases of cucm.
HTH
Manish

Cisco Catalyst 2960-X and Cisco Prime compatibility

Hello All,
I had review all the compatibility matrix of versions of Cisco Prime 1.2, 1.4 and 2.0, and just can't find the Cisco Catalyst 2960-X series as a listed device, which really surprises me.
Can you clear that out??
Thanks,

The 2960X (and XR) support was added with Device Pack 2 for PI 2.0. It was released on 22 January 2014 and is available here.
(PI 2.1 won't be out until later this year, release date not yet announced.)
Following are the 2960X/XR types added:
Cisco Catalyst 2960-X Series Switches
Device Type
SYSOIDS
S/W Version
Software
Cisco Catalyst 2960X-24TS-L Switch
OID:1.3.6.1.4.1.9.1.1699
>=12.1
IOS
Cisco Catalyst 2960X-48FPD-L Switch
OID:1.3.6.1.4.1.9.1.1690
>=12.1
IOS
Cisco Catalyst 2960X-48LPD-L Switch
OID:1.3.6.1.4.1.9.1.1691
>=12.1
IOS
Cisco Catalyst 2960X-48TD-L Switch
OID:1.3.6.1.4.1.9.1.1692
>=12.1
IOS
Cisco Catalyst 2960X-24PD-L Switch
OID:1.3.6.1.4.1.9.1.1693
>=12.1
IOS
Cisco Catalyst 2960X-24TD-L Switch
OID:1.3.6.1.4.1.9.1.1694
>=12.1
IOS
Cisco Catalyst 2960X-48FPS-L Switch
OID:1.3.6.1.4.1.9.1.1695
>=12.1
IOS
Cisco Catalyst 2960X-48LPS-L Switch
OID:1.3.6.1.4.1.9.1.1696
>=12.1
IOS
Cisco Catalyst 2960X-24PS-L Switch
OID:1.3.6.1.4.1.9.1.1697
>=12.1
IOS
Cisco Catalyst 2960X-48TS-L Switch
OID:1.3.6.1.4.1.9.1.1698
>=12.1
IOS
Cisco Catalyst 2960X-24PSK-L Switch
OID:1.3.6.1.4.1.9.1.1700
>=12.1
IOS
Cisco Catalyst 2960X-48LPS-S Switch
OID:1.3.6.1.4.1.9.1.1701
>=12.1
IOS
Cisco Catalyst 2960X-24PS-S Switch
OID:1.3.6.1.4.1.9.1.1702
>=12.1
IOS
Cisco Catalyst 2960X-48TS-LL Switch
OID:1.3.6.1.4.1.9.1.1703
>=12.1
IOS
Cisco Catalyst 2960X-24TS-LL Switch
OID:1.3.6.1.4.1.9.1.1704
>=12.1
IOS
Cisco Catalyst 2960-XR Series Switches
Device Type
SYSOIDS
S/W Version
Software
Cisco Catalyst 2960XR-48FPD-I Switch
OID:1.3.6.1.4.1.9.1.1797
>=12.1
IOS
Cisco Catalyst 2960XR-48LPD-I Switch
OID:1.3.6.1.4.1.9.1.1798
>=12.1
IOS
Cisco Catalyst 2960XR-48TD-I Switch
OID:1.3.6.1.4.1.9.1.1799
>=12.1
IOS
Cisco Catalyst 2960XR-24PD-I Switch
OID:1.3.6.1.4.1.9.1.1800
>=12.1
IOS
Cisco Catalyst 2960XR-24TD-I Switch
OID:1.3.6.1.4.1.9.1.1801
>=12.1
IOS
Cisco Catalyst 2960XR-48FPS-I Switch
OID:1.3.6.1.4.1.9.1.1802
>=12.1
IOS
Cisco Catalyst 2960XR-48LPS-I Switch
OID:1.3.6.1.4.1.9.1.1803
>=12.1
IOS
Cisco Catalyst 2960XR-48TS-I Switch
OID:1.3.6.1.4.1.9.1.1804
>=12.1
IOS
Cisco Catalyst 2960XR-24PS-I Switch
OID:1.3.6.1.4.1.9.1.1805
>=12.1
IOS
Cisco Catalyst 2960XR-24TS-I Switch
OID:1.3.6.1.4.1.9.1.1806
>=12.1
IOS
Cisco Catalyst 2960XR-48FPD-L Switch
OID:1.3.6.1.4.1.9.1.1807
>=12.1
IOS
Cisco Catalyst 2960XR-48LPD-L Switch
OID:1.3.6.1.4.1.9.1.1808
>=12.1
IOS
Cisco Catalyst 2960XR-48TD-L Switch
OID:1.3.6.1.4.1.9.1.1809
>=12.1
IOS
Cisco Catalyst 2960XR-24PD-L Switch
OID:1.3.6.1.4.1.9.1.1810
>=12.1
IOS
Cisco Catalyst 2960XR-24TD-L Switch
OID:1.3.6.1.4.1.9.1.1811
>=12.1
IOS
Cisco Catalyst 2960XR-48FPS-L Switch
OID:1.3.6.1.4.1.9.1.1812
>=12.1
IOS
Cisco Catalyst 2960XR-48LPS-L Switch
OID:1.3.6.1.4.1.9.1.1813
>=12.1
IOS
Cisco Catalyst 2960XR-48TS-L Switch
OID:1.3.6.1.4.1.9.1.1814
>=12.1
IOS
Cisco Catalyst 2960XR-24PS-L Switch
OID:1.3.6.1.4.1.9.1.1815
>=12.1
IOS
Cisco Catalyst 2960XR-24TS-L Switch
OID:1.3.6.1.4.1.9.1.1816
>=12.1
IOS

Cisco Catalyst 2955 Causes Some Devices to "Die" During Boot

Similar Messages

Maybe you are looking for