3
Basically, you need to make up your mind which device your clients should use as default gateway: the OPNsense - then inter-VLAN routing goes that way, too - or the L3 switch, that in turn uses the OPNsense as default gateway.
If you use the OPNsense for inter-VLAN routing, you set up firewall rules for which connections are permitted. Note that the OPNsense ...
3
Now they have 230 devices and They are going to increase device count by 100.
Within the same subnet? Then you'd have to supernet that subnet to e.g. 192.168.24.0/23.
I cannot change subnet and increased usable IP addresses count because there are many dependencies.
Adding another subnet/VLAN is a better option anyway. As Jesse's already answered, that ...
3
Questions about protocols above layer 4 are off limits here, however, as a very basic explanation on a layer 2 and layer 3 level, you cannot have multiple VLANs using the same DHCP pool (same subnet). Each VLAN would need a separate DHCP pool (separate subnet) to assign addresses from.
For example:
VLAN 100: 192.168.1.0/24
VLAN 200: 192.168.2.0/24
Just to ...
2
you could add a second range to another vlan. If the switch is a layer 3 switch, it shouldn't be a problem to connect to eachother. If not, a downtime is necessary to adapt the existing one.
1
First- as many others PT is not IOS and many functions are either limited or do not work.
Second: Cisco defines two privilege levels by default (1 and 15) any non-default privilege level can be defined with privileges set.
You may be able to view the configuration by using the command “show run all” but I doubt the command works.
For more reading please ...
1
Short answer: Do NOT use hybrid mode. If you're after mixed tagged/untagged VLAN trunking, that's not what hybrid mode means.
Hybrid mode is used with protocol-based VLANs. Without proper configuration, frames all end up in the default VLAN. The only common use case for hybrid mode is a legacy end node that doesn't support tagging but where you still want to ...
1
Incidentally, I stumbled on a likely explanation for the described problem. Your suspicion is most probably correct: the switch does seem to verify the firmware version in the config with the actually running version.
When exported using the add-ignore-tag option, the first line is changed to e.g.
; J9850A IGNORE Configuration Editor; Created on release #KB....
Only top voted, non community-wiki answers of a minimum length are eligible
