This post is more than 5 years old

79 Posts

27602

January 8th, 2014 07:00

Power Connect 5324 question on simple access

Good day All

I am trying to put a simple 5324 switch on a Sonicwall port I have Ip'ed.  The sonicwall port 172.16.10.2 and the only VLAN on the switch is IP 172.16.10.1

I have on box hanging off the switch with IP 172.16.10.10

From the switch I can ping the server 172.16.10.10 but cannot ping the sonicwall port of 172.16.10.2

from the sonicwall I can ping the VLAN ip of 172.16.10.1 but not anything behind it (172.16.10.10. I have had this before and I have even gotten the answer before I just keep forgetting. I have the port on the switch that is connected to the sonic wall set as a simple access port on the same single VLAN.

Can someone give me a littler push here

79 Posts

January 9th, 2014 12:00

Josh

When I connect the Websense server directly, I have a working system. Since I was only going to use it to pass WEB Traffic to the Websense to be filtered, I will just use this config

Moderator

 • 

9.6K Posts

 • 

116 Points

January 8th, 2014 08:00

Hi,

What model Sonicwall is it? Is there a default gateway on the switch and is it the same as the one on the Sonicwall? Is the switchport mode on the interface to the Sonicwall set in access mode, passing untagged traffic or in trunk mode passing tagged traffic?Are you using the default VLAN 1 or did you create a separate VLAN? If you create a static route from the 5324 to the Sonicwall does that work? 

79 Posts

January 8th, 2014 09:00

Hello Josh

It is an NSA 3500 and the switch does have a default gateway of 172.16.10.2 which is the interface on the Sonicwall. I have the port to the sonicwall set in access mode and I created a new VLAN 10 for this. I cannot create a static route I believe this is just a layer 2 switch

79 Posts

January 8th, 2014 11:00

Hi Josh

As you can see it is pretty basic

sh run


spanning-tree mode rstp
interface ethernet g24
switchport mode trunk
exit
vlan database
vlan 10
exit
interface range ethernet g(1-23)
switchport access vlan 10
exit
interface ethernet g24
switchport trunk allowed vlan add 10
exit
interface vlan 10
name ***WEBSENSE***
exit
interface vlan 10
ip address 172.16.10.1 255.255.255.0
exit
ip default-gateway 172.16.10.2
hostname BTCORPWEB001
username admin password d9fca3c0dab75d45ffbd6991fd4531d6 level 15 encrypted


username scummins password d41d8cd98f00b204e9800998ecf8427e level 15 encrypted
snmp-server host 172.16.100.15 M3rr1ll! 1
snmp-server community M3rr1ll! su 30.13.9.85
snmp-server community M3rr1ll! ro 172.16.100.15
snmp-server community B1llingTr33$ rw 172.16.125.44 view DefaultSuper
snmp-server host 172.16.125.44 B1llingTr33$ 2
clock timezone -7

Moderator

 • 

9.6K Posts

 • 

116 Points

January 8th, 2014 11:00

Are these new configurations or were there existing ones? Can you post the configuration of the interfaces? 

Moderator

 • 

9.6K Posts

 • 

116 Points

January 8th, 2014 13:00

That is a basic config, so it is odd that it isn't able to ping the firewall, as the other devices on the switch can ping each other, and like you said it is a layer 2 so it is using MAC addresses and not IP addresses. Do the computers that can't ping the firewall have their default gateway set to 172.16.10.2?

79 Posts

January 8th, 2014 14:00

No they are set to the IP of the VLAN on the switch, what is odd is I cannot Ping the Sonicwall interface from the switch and they are directly connected

Moderator

 • 

9.6K Posts

 • 

116 Points

January 8th, 2014 14:00

Try setting one to 172.16.10.2  and see if it is able to ping then. 

Moderator

 • 

9.6K Posts

 • 

116 Points

January 9th, 2014 09:00

The following is all true right?

172.16.10.1 can ping 172.16.10.10

172.16.10.1 can ping the corporate network on the other side of the Sonicwall

172.16.10.10 can ping 172.16.10

172.16.10.10 can't ping 172.16.10.2  or anything behind it

172.16.10.1 can't ping 172.16.10.2 

172.16.10.2 can't ping 172.16.10.10

 

I agree that there is not a nic or cable issue as some pings work. What happens if you bypass the switch and connect the server to the Sonicwall directly?

79 Posts

January 9th, 2014 09:00

Hello again Josh

I did so and same issue, However from the switch I can ping across the firewall to my corporate network, I just cannot get to the lone server sitting behind the switch it is so odd. I can actually ping from the switch to the server though so I assume it is not a cable or server NIC. From the Server I can ping the gateway but nothing more

79 Posts

January 9th, 2014 10:00

Josh

All that is correct EXCEPT

172.16.10.1 (switch) CAN ping 172.16.10.2 (sonicwall interface)

I don't know I have not tried that, Let me see

0 events found

No Events found!

Top