Cannot uplink to SG300-10 from another switch

[pdejan571]

I have two SG300-10 switches setup for my iSCSI network. I connected via the console and assigned static IP addresses from my service laptop. If I plug in directly to the SG300, I can connect to the web GUI and ping the switch. However, if I plug the SG300 into a port on anther switch, an SMC 8126L2, to uplink the switches together, I cannot connect to the SG300 from any computer connected to the SMC 81266L2 switch.

So far other than assigning an IP address, I have not modified any settings in the SG300.

Thanks for you help.

[pdejan571]

Additional info:

THe iSCSI traffic is working fine. The main reason for this is so I can manage the switch from my main network. I just need one port on the SG300 to communicate with the other switch for management purposes.

[David Hornstein]

Hi Philip

If iSCSI is working fine through the switch network. I gotta guess that traffic flow over the default vlan is working fine, even through the netgear switch.

Since my switch is still at the default configuration, all my ports should be in the default VLAN as untagged VLAN interfaces.

I am wondering if you didn't save the IP address of the switch to the startup configuration file,  and my switch grabbed an IP address via DHCP.

Console back into the switch and lets look at the IPv4 address table.

Here is a copy of mine, via the hyperterminal console screen.

I went to "MAIN MENU"   >  Option  1. System Configuration Menu > 6. IP Configuration > 1. IPv4 Address Configuration  then had a look at the IPv4 address table  >  2. IPv4 Address Table

                              IPv4 Address Table

                              ==================

  IPv4 Address       Interface  Type      Status        Delete/Keep

  ============       =========  ====      ======        ===========

192.168.10.17  /24  VLAN1      Static    Valid         Keep

192.168.75.1   /24  VLAN2      Static    Valid         Keep

What does your table look like, maybe copy and  paste your screen in reply ?

I just went through the process of adding a new address to my switch for the sake of this exercise.

                              IPv4 Address - Add

                              ==================

                      IPv4 Address:         192.168.10.100

                      Subnet Mask:          255.255.255.0

                      DHCP Client:          DISABLE

                      Interface Type:       VLAN

                      Interface Number:     1

Action->  Quit   Edit   Save

ArrowKey/TAB/BACK=Move  SPACE=Toggle  ENTER=Select  ESC=Back

I then made doubely sure i saved my configuration, by going back to the GUI on Internet Explorer and saving my running configuration to the startup file as per my screen capture below.

(note the change in management IPaddress :-)

You will see or maybe note, within the screen capture below,  that I am also using a Cisco Free utility called findit to find the switch.

But lets see what your switches IP address is at this stage and if it can survive a switch reboot..

seasons greetings

regards Dave

[pdejan571]

Thanks, Dave for your response.

I have checked that the IP address I assigned has been saved to the startup config.

I have rebooted it several times to make sure the save held.

I can navigate to the SG300 via a web browser and ping its IP address ONLY if my laptop is plugged directly into the SG300.

It doesn't matter which port I plug into BUT I MUST be plugged directly into the SG300 in order to connect to it.

If I plug a patch cable from any port on the SG300 into any port on my SMC8126L2 and plug my laptop into the SMC8126L2, I CANNOT access or ping the SG300.

The SMC8126L2 has a static assigned IP address on the same subnet as I have assigned to the SG300.

If I plug a patch cable from one SG300 into the other SG300, they can see each other via ping or web browser.

[David Hornstein]

Hi Philip,

Luckily the new 300 series has some pretty good diagnostics.

I think  port mirroring or vlan mirroring to capture the IP interaction would be most useful. Sure sounds like there is a problem with access to the management interface of the SG300 from the netgear. By default , i have no issue or restrictions on allowing a PC on VLAN1 to access the SG300.

It would be very interesting to see a wireshark capture showing;

1. a PC on the netgear switch trying to get to the SG300 management interface including
2. a PC on the SG300  switch trying to get to the SG300 management interface.

Maybe if you would be so kind as to use wireshark to capture vlan1 traffic. 

Just really want to see PC's on the netgear switch trying to get to the SG300 Web interface.  So need a large capture file, smaller the better.

Also be interesting to see the Layer 2 forwarding table, here is mine below ;

I am also wondering if there is a access restriction in place to stop access to the management interface, maybe save/backup and upload  a config file from the switch  and also show the following screen ;

regards Dave

[pdejan571]

Dave,

I am not sure what you're asking me to do. Please explain further.

I will be away until Tuesday so let's pick this up then.

Thanks.

Phil

[pdejan571]

A nice weekend works wonders. Came in this morning with

a clear head and figured out my problem.

The priority setting for the RSTP in the two Cisco SG300 switches was the same as the priority setting on the SMC 8126L2 switch.

I modified the priority setting on the Cisco SG300s to a lower priority. As soon the setting took affect, I could connect to the SG300s from anywhere on the network and connect from the SG300s to anywhere on the network.

Problem solved.

Thanks everyone for your help.

Philip