cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5875
Views
0
Helpful
37
Replies

2950 - Power cycle issue

Jeff Harned
Level 1
Level 1

Hi All,

I am new to networking but have been working with a small LAN setup with success.

This is my issue:

I am using one 2950 switch along with data converison devices converting incoming serial data to multicast data back to serial data.
For the switch configuration I have chosen to use MVR (Multicast VLAN Registration) assigning ports in a VLAN (Virtual LAN) configuration.

I save the configuration steps using the "copy running-config startup-congfig" command.  So far everthing is working great!

However, when I do a power cycle on the switch the ports become inactive (although the port status LEDs are green).  I know no multicast data is getting through to the devices because there are no data activity LEDs lit up on them.

Performing a "show running-config' on the switch shows that the configuration entries are intact.  To get the LAN setup to work again I have to retype the configuration steps again into the switch.  Can someone help me with this issue?

Thanks.

Regards,

Jeff

Cisco 2950 Switch
IOS Version 12.1(22)EA9
Running Standard Image

24 FastEthernet Ports

37 Replies 37

Hi Eugen,

Thanks.

I was able to correct the private-config file to "flash:private-config.text".  I still though have the same situation after a power cycle.

I have another switch which the boot path was not configured correctly so I went ahead and corrected the mistakes. The document attached shows the directories after a power cycle.  I reloaded like before but still have the same situation with this switch.  Looking at the document I see no evidence of a problem.

Looking at the startup-config file indicates that all is there.  So close on getting this to work......there has to be an answer!!!  Is there any other thing I can look at?  Is there something missing in my configuration that needs to be addded to pass the data through?

Thanks.

Regards,

Jeff

Hi Jeff,

Good to hear that almost everything is working.

I would try to erase nvram once more, now that all the paths have been configured, and reconfigure the switch again from scratch, save and reload to see if those 2 lines of configuration you mentioned will be there on reload. If not, you may have to enter them everytime you reload the switch which shouldn't be too often I hope.

I don't know what else to suggest. Have a read thru this document, it may help you

http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/software/release/12.1_6_ea2c/configuration/guide/swgigmp.html#wp1050897

All the best!

Regards

Eugen

Hi Eugen,

Took your suggestion and reloaded with the same results. Even viewing the switch through the console port during a cold start up after a power cycle the switch indicates that the fastethernet ports changed state to up, yet those destination ports just will not fire!!

Anyway, I will continue looking into this.  I would like to thank you for all help and since I am pretty new to this you have provided me with a good foundation to learn and work with!!

Thanks.

With Regards,

Jeff

Hi Jeff,

If you run "show ip interface brief" and shows that your interfaces are up and up under the headings Status and Protocol

and you have mac addresses associated with those ports that you configured, use "show mac-address-table" to see if the right end device mac address is in the table, then I will also suggest looking at the streaming server or end devices configuration as well.

Thanks for you kind words, I am glad to hear that my advice didn't confuse you

All the best

Eugen

Hi Eugen,

Got a little deeper with this issue........where I am right now.

Summary:

I configured another switch using IGMP, configuring it with VLANS (but did not use MVR this time).  This did not work before or after a power cycle.  What I ended up doing was removing all VLANS from the configuration and sure enough the destination devices recieved data, even after a power cycle!!

I still want to use VLANS and it bothers me why it is not working.  There is a number of configuration possibilities associated with VLANS.  There must be something missing in my configuration using the first switch.  Do have any suggestions?

Thanks.

Regards,

Jeff

Hi Eugen,

I have some more info for you from your last reply.

The attached files are for the units running with data getting to the three desination units.

Under the "show ip interface brief" I do not understand what I am reading. For one thing it only lists VLAN 20 which is set for one of the destination units.  It does not list VLAN's 25 and 30 which are being used for the other two destination units.  It also does not list VLAN 10 which is the MVR VLAN.

What I also do not understand is what does it mean by saying VLAN 20 is administratively down when that assigned VLAN to port is receiving data?

I also notice that the ports that I am using in my setup all indicate they are up.

Under the "show mac-address-table"

I am not using mac addresses from the units in my cofiguration. It states VLAN 10 with the assigned ports 24 and 7 which is correct.  Those two ports are from the "source" units.  Below is how I have Vlan 10 configured:

cisco1(config)#mvr

cisco1(config)#mvr group 239.1.1.3

cisco1(config)#mvr group 239.1.1.4

cisco1(config)#mvr querytime 10

cisco1(config)#mvr vlan 10

cisco1(config)#mvr mode dynamic

Again, I am using multicast data coming out of these units.  I am leaning more to think that I am missing something in my configuration steps using VLANS.  My research has led me not to find the answer.  In my previous reply switching to IGMP works fine after a power cycle but I want to be able to use VLANS!

Hope you can continue to help!

Thanks.

Regards,

Jeff

Ok.  Thanks.  Power outage, eh?  Can I also ask for the output to the command "sh post"?

Leolaohoo,

"Show post" indicates passed on both a before and after a power cycle.  I am simply pulling the plug from the switch

to verify that the switch comes back to the working state that I configured it as.

Thanks.

Regards,

Jeff