Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionUsing N2048 vLANs in shared circuit
I recently inherited an old network with a failing 3com switch. I am trying to replace the 3com switch in the simplest manner possible with a N2048.
Currently, our ISP connection comes in on port 24 (via ethernet handoff from a Level3 router in our basement) on the 3com switch and our firewall plugs in port 48 of the 3com switch. I have attempted to configure the N2048 exactly the same as the existing 3com switch. When I do this and patch the connection in, I have connectivity in our local subnet as well as internet. However, I cannot communicate to a subnet that connects to a remote office.
Local subnet: 192.168.6.0/24
Local internet gateway: 192.168.6.38
Local gateway for remote subnet: 192.168.6.9
Remote subnet: 192.168.5.0/24
The remote subnet is accessed through the same connection as the internet via vLAN and static route that the ISP set up. I have the original document that the ISP provided for the configuration as follows:
Customer CPE WAN Interface Configuration Requirements: 100M Full Duplex
Customer WAN Netblock(s) CIDR - Subnet Mask:
Vlan 100 207.67.73.184/29 - 255.255.255.248
Vlan 1 192.168.255.0/30 - 255.255.255.252
Customer CPE Default GW / Remote Neighbor IP:
207.67.73.185
192.168.255.1
Static Route:
192.168.6.0/24 - 255.255.255.0 destination 192.168.255.2
On the N2048 ports 1-48 are members of VLAN 1 and ports 24,48 are members of VLAN 100.
VLAN 1 are untagged and VLAN 100 are tagged.
Comparing the 3COM and N2048 switch everything seems to configured the same. It seems this should be a simple setup but I cannot figure out why the N2048 will not communicate with the remote subnet.
Any thoughts or advice would be greatly appreciated.
Thanks for the suggestion. I removed the vlan association.
I ended up working with our ISP and found out the information was not correct. There was no 192.168.255.0/30 or route. Not sure why that was on the original document as they provided no explanation (prob due to ISP buys ISP who busy ISP). Other than removing the vlan association nothing else was changed, and of course after finally getting someone on the phone that could assist it started working. I was sure I tested without the vlan association before, and only added it after not getting anywhere.
Anyways all is working now. Thanks.
kwood12
3 Posts
1664
0
Posted September 27th, 2018 12:00
Thanks so much for the reply. Here is the running config.
!Current Configuration:
!System Description "Dell Networking N2048P, 6.3.2.3, Linux 3.6.5-e788596a"
!System Software Version 6.3.2.3
!
configure
vlan 100
exit
vlan 100
name "VLAN100"
vlan association subnet 192.168.5.0 255.255.255.0
exit
slot 1/0 9 ! Dell Networking N2048P
stack
member 1 9 ! N2048P
exit
logging buffered debugging
interface vlan 1
ip address 192.168.6.3 255.255.255.0
bandwidth 10000
exit
interface vlan 100
exit
monitor session 1 destination interface Gi1/0/17
monitor session 1 source interface Gi1/0/24
ip ssh server
application install SupportAssist auto-restart start-on-boot
application install hiveagent start-on-boot
!
interface Gi1/0/21
switchport general ingress-filtering disable
exit
!
interface Gi1/0/23
switchport general ingress-filtering disable
exit
!
interface Gi1/0/24
speed 100
flowcontrol receive off
description "Level3"
switchport mode general
switchport general allowed vlan add 100 tagged
exit
!
interface Gi1/0/48
flowcontrol receive off
switchport mode general
switchport general allowed vlan add 100 tagged
exit
snmp-server engineid local 800002a203e4f004d9cb22
exit