Skip to main content

Planet vlan

Planet Switch Configuration


Step 1: Log into the Planet Switch
Planet switch default IP address is 192.168.0.100. Default password is “admin”
Once you have logged into the switch you can change the default IP address to match the IP subnet for LAN1. Here we have used the IP address 192.168.10.100.


Step 2: Configure VLAN Membership
Go to VLAN Membership configuration menu and create VLAN ID’s and port association.
  • Enter new VLAN ID and click Add
  • On the next page that appears select the ports to be associated with the VLAN
  • Click Apply to save. (We have assigned 6 ports for each VLAN as shown in the screen shots below)
  • Repeat the steps for each VLAN (VLAN’s 1 to 4)
  • Ensure port 1 is associated with all VLANs as this will be the trunk port
Note: VLAN1 is enabled by default and all ports are associated with VLAN1

Note: Port 1 must be a member of all VLAN ID’s since this will be used as the 802.1Q VLAN Trunk (uplink) from the Vigor3200 router

Step 3: Configure VLAN Port Configuration
Go to VLAN Port configuration menu and assign VLAN ID’s for each port
  • For Port 1, set this to be a Tagged port as shown below. This is required to allow the 802.1Q trunk from the Vigor3200 to work.
  • For other ports configure them as Untagged
  • Set PVID for each port as the vlan id
  • Click Apply to save
 

Comments

Post a Comment

Popular posts from this blog

Cisco SG300 CLI Commands

Cisco SG300 CLI Commands Other parts were obtained using the CLI PDF provided by Cisco Remove a Trunk and switch to access config t int gi44 switchport trunk allowed vlan remove 2 switchport mode access switchport access vlan 2 or config t int gi44 switchport mode general switchport general allowed vlan remove 2 switchport mode access switchport access vlan 2 Change CDP Device ID Format to Hostname opposed to default MAC address s-sg300#sh cdp Global CDP information:         CDP is globally enabled         CDP log duplex mismatch is globally enabled         CDP log voice VLAN mismatch is globally enabled         CDP log native VLAN mismatch is globally enabled         Mandatory TLVs validation is disabled         Sending CDPv2 advertisements is enabled         Sending Appliance TLV is enabled       ...
Post a Comment
Read more

Policy Based Routing on a Cisco ASA

Cisco ASA 9.4 (and later) is now supporting Policy Based Routing. Yeah. Great news, since many customers are requesting something like “HTTP traffic to the left – VoIP traffic to the right”. Coming with a new Cisco ASA 5506-X I was happy to try the policy based routing feature. The configuration steps through the ASDM GUI are not easy and full of errors so I am trying to give some hints within this blog post. The main document from Cisco for policy based routing on a ASA is here . It describes the use-cases for PBR and gives examples. Configuration I am doing all of my configurations through the GUI ASDM. (I know, some people really love the CLI even for configurations, but I don’t. I am using it only for troubleshooting issues.) For this lab I am using a Cisco ASA 5506-X with ASA version 9.5(1), while ASDM is version 7.5(1) . In my lab, I have a default route to ISP 1 (gi1/1) and a different connection to ISP 2 (gi1/2). There is no route to ISP 2 in the ro...
Post a Comment
Read more

Patch Workflows

Thus far, all of the collaboration workflows we’ve seen rely heavily on branches. For example, in the last module, a contributor had to publish an entire branch for us to merge into our project. However, it’s also possible to communicate directly on the commit level using a patch . A patch file represents a single set of changes (i.e., a commit) that can be applied to any branch, in any order. In this sense, the patch workflow is akin to interactive rebasing, except you can easily share patches with other developers. This kind of communication lessens the importance of a project’s branch structure and gives complete control to the project maintainer (at least with regards to incorporating contributions). Integrating on the commit level will also give us a deeper understanding of how a Git repository records project history. Download the repositories for this module If you’ve been following along from the previous module, you already have everything you need. Otherwise, d...
Post a Comment
Read more