This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Changing to 802.1q trunks

I currently have four physical ports on our ASG-320 (running V 8.3) that are connected to four ports on a Cisco switch configured for multiple VLAN's. Each of the ASG ports is for one of  four internal VLANS. 

I want to change the four physical connections to one 802.11q trunk between the ASG and the Cisco switch, keeping the same DG's, IP.s etc for each VLAN.

Is there a simple way to do that without destroying rules, etc. If I delete the port for VLAN #2 and then configure it on the 802.1q trunk for VLAN #2, will everything pick up, or will things have to be rebuilt?

Thanks,


This thread was automatically locked due to age.
Parents
  • You'll have to redo your rules.  The good news is that there is the handy "clone" option in most rulesets so recreating them shouldn't take too long.  You'd just create your new trunks with "fake" VLAN IDs, clone the rules from the existing ones... then delete the old interfaces, and change the VLAN IDs on the new trunks to "real" ones.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply
  • You'll have to redo your rules.  The good news is that there is the handy "clone" option in most rulesets so recreating them shouldn't take too long.  You'd just create your new trunks with "fake" VLAN IDs, clone the rules from the existing ones... then delete the old interfaces, and change the VLAN IDs on the new trunks to "real" ones.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Children
No Data