10-03-2017 01:34 PM - edited 03-21-2019 11:16 AM
Background: I am moving away from pfSense hosted on ESX to a physial L2/L3 environment. pfSense provided my routing previously so I am off LAN with this switch and it has been factory reset and configured only with the default network of 192.168.1.0, a DHCP default route which the Cisco created and is attached to VLAN1.
I've been working to setup a single SG300-10PP. My deployment objectives are:
- Change the default route
- Change the default VLAN
- Cisco provides DHCP to all VLAN clients
- Cisco provides routing between VLANs
I lose connecticvity to the WebGUI any time I:
- Change the default route
- Remove the existing default route (VLAN1, DHCP 0.0.0.0/255.255.255.255) even though (VLAN1, Default, 192.168.1.254/255.255.255.0) exists.
- Remove/Change the existing default route to a different VLAN
In order to enable and configure DHCP I have to remove this route. If I can only bring up 1 VLAN, it would be 99 since I use this for mgmt.
I have followed the configuration direction from "Cisco 300 Series Managed Switches Administration Guide" for each and the only progress I've made is uncovering additional caveats of "do this before you do that." While I do lack Cisco ios knowledge I am quite handy (even at the shell) on an F5. I do have SSH access to the switch but am opting to program it from the Web GUI. I am not at all averse to using the shell, but I seem to be missing some "process." I hope you can help!
Here is what I have configured at present (most is default):
sg300#show running-config
config-file-header
sg300
v1.4.8.6 / R800_NIK_1_4_202_008
CLI v1.0
set system mode router
file SSD indicator encrypted
@
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
!
vlan database
vlan 10,20,30,40,50,99
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
bonjour interface range vlan 1
hostname sg300
line ssh
exec-timeout 0
exit
no passwords complexity enable
username cisco password encrypted 7a6a917cc20e6da0c1317a2ea42d72c3d7c25649 privilege 15
ip ssh server
snmp-server location "Main Office"
snmp-server contact "ADC Team"
ip http timeout-policy 1800 https-only
no ip http server
clock timezone CT -5
clock summer-time web recurring usa
clock source browser
!
interface vlan 10
name 10
!
interface vlan 20
name 20
!
interface vlan 30
name 30
!
interface vlan 40
name 40
!
interface vlan 50
name 50
!
interface vlan 99
name 99
!
interface gigabitethernet1
channel-group 1 mode auto
!
interface gigabitethernet2
channel-group 1 mode auto
!
interface gigabitethernet3
channel-group 2 mode auto
!
interface gigabitethernet4
channel-group 2 mode auto
!
interface gigabitethernet7
switchport trunk native vlan 30
!
interface gigabitethernet9
switchport trunk native vlan 99
!
interface Port-channel1
description ESX1LAG
!
interface Port-channel2
description ESX2LAG
!
exit
sg300#
sg300#show ip route
Maximum Parallel Paths: 1 (1 after reset)
IP Forwarding: enabled
Codes: > - best, C - connected, S - static
C 192.168.1.0/24 is directly connected, vlan 1
sg300#
Solved! Go to Solution.
10-05-2017 02:09 PM
OK so it turns out this was about as easy to resolve as it can get. The switch needed to be connected to the other network (VLAN20) and a client needed to be ACTIVE on that VLAN. This keeps the GUI from removing the default route and subsequesnt connectiveity loss
10-03-2017 05:03 PM
Hi,
Are you connecting to the Switch from a remote network? If does, this make sense you loose connection when you remove default route, after all, switch does not know how to reply to you.
Also, you are configuring port as trunk but you put the vlan as native, which means no tag. So, Why to you need trunk is the only one vlan you have will not be tagged?
!
interface gigabitethernet7
switchport trunk native vlan 30
!
interface gigabitethernet9
switchport trunk native vlan 99
!
10-05-2017 02:09 PM
OK so it turns out this was about as easy to resolve as it can get. The switch needed to be connected to the other network (VLAN20) and a client needed to be ACTIVE on that VLAN. This keeps the GUI from removing the default route and subsequesnt connectiveity loss
10-05-2017 02:16 PM
Very good, glad to hear!
-If I helped you somehow, please, rate it as useful.-
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide