Force10 MXL - VLAN is not routing.

Similar Questions

• Force10 MXL and blades - mapping of Interfaces

  Hello

  I know it's a recurring topic but I am facing a strange problem in the last M1000e chassis that I was sent.

  According to: mapping is very clear. For example, the first interface of the first plank must be connected via the Midplane to te0/1 (first in the IOM1 interface), but when I set up the battery of the A2 Force10 MXL (just a pile between A1 and A2) became the master so I changed the priorities to ensure that A1 is the master. Once this is done, I realized that the first interface of the first blade was linked to the Te1/1, the first IOM2 interface. Is it possible to change this? I have several chassis and I want to set all the same way...

  Thank you!

  What servers are used? Just to be clear, while MXL in A2 was the master, the LOM 1 port connected to 0/1 and the LOM 2 port connected to 1/1? Then when you changed a switch to A1, now port 1 shows that 1/1 LOM and LOM 2 port connected to 0/1?

  The ports are all physically defined by the M1000e chassis.
  Have you tried:
  -unstacking switches
  -Can ensure that ports appear correctly so that not stacked.
  -Set the priority and then put.
  -Check the enumeration.

• Connect to Force10 MXL N4032 using cables QSFP + DA 40 G

  Hello

  I'm trying to connect a N4032 switch to a switch chassis Force10 MXL using QSFP + modules and a DA 40 G cable. Now, the problem I have is that when I plug the cable 40G QSFP DA I don't have a link, both switches show that the QSFP + optical has been inserted, and that the perspective is supported on two models of switches.

  The MXL is on the firmware 9.8.0.0 and the N4032 on 6.2.1.6.

  QSFP map show slot on the show N4032 command:

  Power admin card configured
  ID of the slot status State Pluggable model
  ----- ------ ------- ------- -------------------------------- ---------
  1/0 Enable full activate Dell N4032 number of networking
  1/1 full Activate activate card QSFP Dell Yes

  Optics QSFP + is connected to the port of1/1/1 on the N4032 and returns order status interface to see more:

  Physical admin link link LACP Flow physics
  INTF Type Mode Mode status trap Mode Mode
  --------- ------ ------- ---------- ---------- ------ ------- ------- -------
  TE1/0/1 Select Auto 10 G full turn off Active
  TE1/0/2 Select Auto 10 G full turn off Active
  TE1/0/3 select Auto 10 G full turn off Active
  TE1/0/4 turn down turn off idle
  TE1/0/5 turn down turn off idle
  TE1/0/6 turn down turn off idle
  TE1/0/7 activate Auto 10 G full activate deactivate Active
  TE1/0/8 enable Auto 10 G full activate deactivate Active
  TE1/0/9 turn down turn off idle
  TE1/0/10 turn down turn off idle
  TE1/0/11 select Auto 10 G full turn off Active
  TE1/0/12 enable Auto 10 G full activate deactivate Active
  TE1/0/13 turn down turn off idle
  TE1/0/14 turn down turn off idle
  TE1/0/15 turn on Auto 10 G full activate deactivate Active
  TE1/0/16 enable Auto 10 G full activate deactivate Active
  TE1/0/17 enable Auto 10 G full activate deactivate Active
  TE1/0/18 turn down turn off idle
  TE1/0/19 turn down turn off idle
  TE1/0/20 turn down turn off idle
  TE1/0/21 Enable Auto 1000 Full Up enable disable Active
  TE1/0/22 Enable Auto 1000 Full Up enable disable Active
  TE1/0/23 Enable Auto 1000 Full Up enable disable Active
  TE1/0/24 turn down turn off idle
  Of1/1/1 turn down turn off idle
  Of1/1/2 active 40 maximum G low turn off idle
  TE1/1/1 active 10G full detach turn off s/o
  TE1/1/2 Active 10 G full detach turn off s/o
  TE1/1/3 active 10G full detach turn off s/o

  As you can see that switch captures yet the speed of the optics. Now if I take the same cable and plug it between the 2 x N4032 switches - ports immediately show a link.

  Newspapers of the MXL show optics QSFP Fo0/33, it shows the status of the admin of the ports as upward, but the State of the interface is down. Now if I take the same cable of DA and plug it between the 2 MXL in the chassis, the interface state changes until almost immediately. The two MXL is configured in a VLT, but I tried to get the link to the top with the VLT and without the VLT, does anyway.

  This shows that cables of DA are fully functional, the ports I plug are functional - even when one end of the cable plugged into the N4032 and the other end in the MXL Force10, the link is not started.

  I have the show out of all 4 switches, if necessary technical support.

  Thank you

  Dave

  This problem has been resolved with the help of Technical Support.

  It was a mismatch of negotiation between switches.

  The fix has been add to the config of the port on the Force10 MXL:

  interface fortyGigE 0/33

  INTF-type cr4 autoneg

• Then a Force10 MXL blade handle no FCoE traffic?

  Hello.  I inherit a M1000e with few blades of the Force10 MXL switch installed.  The chassis has no other 10GBASE-T switches.  Since I have no plans on using FCoE, a Force10 MXL can be used for standard Ethernet (non-FCoE) traffic?  Or do I have to buy another switch?

  Thank you.

  Absolutely, to see the second page of the data sheet. It contains additional information about the available modules, how internal traffic is manipulated and external.

  http://Dell.to/1Q5fUo9

  The manuals are a great place to start. There is that a starter guide to help set up initial, and then a CLI and user guide to help configure additional features.

  http://Dell.to/1IIq8r2

  Let us know if you have any other questions.

• RV180W of WLAN traffic is not routed to WAN

  My WIFI traffic is not routed to WAN.

  I can access LAN and plug to NIR all on the local network. But internet access is not possible. WAN LAN access is allowed.

  I have reset the RV180w to factory settings and also reflashed the firmware to make sure.

  To configure a static route to wlan to wan?

  The routing of the generated RV180 table

  Destination	Entry door	Genmask	Metric	REF	Use	Interface	Type	Flags
  127.0.0.1	127.0.0.1	255.255.255.255	1	0	0	Lo	Static	Upward, gateway, host
  172.16.0.0	0.0.0.0	255.255.254.0	0	0	0	BDG1	Dynamics	UPWARD
  85.0.84.0	0.0.0.0	255.255.252.0	0	0	0	eth1	Dynamics	UPWARD
  127.0.0.0	0.0.0.0	255.0.0.0	0	0	0	Lo	Dynamics	UPWARD
  0.0.0.0	85.0.84.1	0.0.0.0	0	0	0	eth1	Dynamics	Upward, gateway

  Hi Pete,.

  I read your case, it seems that the problem is not related. What I am referring is an external AP connected to the RV180W when the wireless is enabled on the RV180W. Devices that connect to the AP will not be able to access the internet. If the radio on the RV180W is turned off, the devices that connect to the AP can connect to internet.

  -Marty

• I can mutually ping in router RVS4000 VLAN without another router

  One of our clients has RVS400 router with 4-port LAN VIRTUAL. We have recently added Crestron devices to our network and have some network problem. Search Google points to this page: Network slow question as discessed in this article: Troubleshooting network slow issues... There are two things happening with the Crestron system:... www.chicagotech.net/NetForums/viewtopic.php?f=1&t=7737 It recommends to create a local network VIRTUAL for Crestron. However, the Cisco RVS400 manual States: "function VLANS at layer 2.» VLANS isolate traffic within the VIRTUAL LAN, router layer 3 functioning router is needed to allow traffic between the VLANS. Layer 3 routers identify segments and coordinate with local networks virtual. "If we create two VLANS on the router without another router, can access us each other in these two VLAN?

  Hi chicagotech.

  I implemented a RVS4000 in our laboratory and created 2 VLAN, VLAN 1 and VLAN 2. I connected two PCs, 1 on each VLAN and they were able to ping each other with Inter-VLAN routing active. Here are the steps I followed:

  1. Go to L2 Switch-> create a VLAN. I have added VLAN ID: 2 and click Add VLAN
  2. Go to membership to a VLAN and select VLAN 2 from the drop-down. In the table for Port 2, select the Untagged radio button and click on save at the bottom.
  3. Go to settings-> Advanced Routing and ensure that the Inter-VLAN routing is enabled. (It is enabled by default)
  4. Connect a PC to port 2 and make sure he gets an IP to VLAN 2. (in this case 192.168.2.100) Ping this address in VLAN 1 PC-> success. From VLAN 2 PC, ping 192.168.1.101 (VLAN 1 PC)-> success.
  5. As a test I gave then the PCs in each VLAN to an IP address static and turned off the DHCP server on the router. 192.168.1.102 was able to ping 192.168.2.102 and vice versa.
  6. I then disabled Inter-VLAN routing and the PC could ping is no longer among them. They still had full access to the internet.

  It seems that the devices connected to the RVS4000 in different VLANS have no trouble to access each other with Inter-VLAN routing active.

• 515E - host on VLAN may not leave

  Hi all

  I have a restricted license, the PIX 515E 6.3 (4) running. 2 physical and logical interfaces 1 (Vlan20). The movement of the inside to the outside and inside to Vlan20 works very well. Set up a domestic test Web on Vlan20 and can host server access without any problem. HOWEVER! Hosts on Vlan20 cannot send or receive through the outside interface! I'm dying here...

  It's my current config. Thanks in advance.

  P.S. I'm not using non routable IP. Two subnets are public.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  Result of the firewall command: "sh run".

  : Saved

  :

  6.3 (4) version PIX

  interface ethernet0 100full

  interface ethernet1 100full

  logical interface ethernet1 vlan20

  ethernet0 nameif outside security0

  nameif ethernet1 inside the security100

  nameif vlan20 security20 1st2ndfloor

  activate the password * blah * encrypted

  passwd * blah *.

  hostname PIX

  domain uberblah.net

  fixup protocol dns-length maximum 512

  fixup protocol ftp 21

  fixup protocol h323 h225 1720

  fixup protocol h323 ras 1718-1719

  fixup protocol http 80

  fixup protocol rsh 514

  fixup protocol rtsp 554

  fixup protocol sip 5060

  fixup protocol sip udp 5060

  fixup protocol 2000 skinny

  fixup protocol smtp 25

  fixup protocol sqlnet 1521

  fixup protocol tftp 69

  names of

  1st2ndfloor_access_in ip access list allow a whole

  pager lines 24

  opening of session

  Outside 1500 MTU

  Within 1500 MTU

  IP address outside aaa.eee.127.66 255.255.255.252

  IP address inside aaa.eee.45.1 255.255.255.128

  IP address 1st2ndfloor aaa.eee.51.1 255.255.255.128

  alarm action IP verification of information

  alarm action attack IP audit

  PDM location aaa.eee.45.95 255.255.255.255 inside

  PDM location aaa.eee.45.100 255.255.255.255 inside

  PDM 200 debug logging

  history of PDM activate

  ARP timeout 14400

  NAT (inside) 0 0.0.0.0 0.0.0.0 0 0

  NAT (1st2ndfloor) 0 0.0.0.0 0.0.0.0 0 0

  Access-group 1st2ndfloor_access_in in the 1st2ndfloor interface

  Route outside 0.0.0.0 0.0.0.0 aaa.eee.127.65 1

  Timeout xlate 03:00

  Timeout conn 01:00 half-closed 0:10:00 udp 0: CPP 02:00 0:10:00 01:00 h225

  H323 timeout 0:05:00 mgcp 0: sip from 05:00 0:30:00 sip_media 0:02:00

  Timeout, uauth 0:05:00 absolute

  GANYMEDE + Protocol Ganymede + AAA-server

  AAA-server GANYMEDE + 3 max-failed-attempts

  AAA-server GANYMEDE + deadtime 10

  RADIUS Protocol RADIUS AAA server

  AAA-server RADIUS 3 max-failed-attempts

  AAA-RADIUS deadtime 10 Server

  AAA-server local LOCAL Protocol

  Enable http server

  http aaa.eee.45.95 255.255.255.255 inside

  http aaa.eee.45.100 255.255.255.255 inside

  No snmp server location

  No snmp Server contact

  SNMP-Server Community public

  No trap to activate snmp Server

  enable floodguard

  Telnet timeout 5

  SSH timeout 5

  Console timeout 0

  dhcpd address aaa.eee.45.40 - aaa.eee.45.50 inside

  dhcpd dns aaa.bbb.101.10 aaa.ddd.201.10

  dhcpd lease 345600

  dhcpd ping_timeout 750

  dhcpd field uberblah.net

  dhcpd allow inside

  Terminal width 80

  Cryptochecksum: * blah *.

  : end

  The only other thing I can think is the possiblilty that, since you are not using a NAT at the address which is routed through your router upstream to is you have a routing problem there. If your upstream neighbor does not route these addresses to your pix that COULD be your problem. You could try the pat to see if it solves your problem and which would indicate that there is a routing problem.

• vLAN is not projection in ESXi COP out

  I have a vLAN that I use in my environment and that works very well between the ESXi host and the physical network.  However, when I run the command to display the information of the COP of the ESXi host, I don't see.  I see other virtual local networks which are also used without problem.  Why if this vLAN is not displayed in the output of the CDP, but is other VLAN?

  Thank you!

  Vim - cmd hostsvc/net/query_networkhint

  [(vim.host.PhysicalNic.NetworkHint)

  {(vim.host.PhysicalNic.NetworkHint)

  dynamicType = < unset >

  Device = "vmnic0".

  subnet = [(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  {(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  dynamicType = < unset >

  vlanId = 401,

  : ipSubnet = "10.40.11.32 - 10.40.11.63"

  },

  {(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  dynamicType = < unset >

  vlanId = 1163,

  : ipSubnet = "10.40.163.23 - 10.40.163.23"

  },

  {(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  dynamicType = < unset >

  vlanId = 210,

  : ipSubnet = "10.40.210.1 - 10.40.210.63"

  },

  {(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  dynamicType = < unset >

  vlanId = 208,

  : ipSubnet = "10.40.208.1 - 10.40.208.31"

  },

  {(vim.host.PhysicalNic.NetworkHint.IpNetwork)

  dynamicType = < unset >

  vlanId = 213,

  : ipSubnet = "0.0.0.1 - 255.255.255.254."

  }

  ],

  That doesn't seem to work for the collection of information VLAN is to allow the development of statistics on the level of vmnic... This seems to show all tags VLAN on the trunk connected. As a test, I installed an ESXi 5.1U1 host, configured with a single NETWORK adapter connected to a trunk port where only one VLAN native could as well as a labeled (VLAN5). No other VLAN is allowed on the port of pSwitch...

  Then I activated the stats on the vmnic function... (statistics of vlan network nic put true-e - n vmnic0 esxcli)

  Then, I pulled her stats to check that only the VLAN with 5 native VLAN are seen...

  ~ # esxcli network nic vlan stats get vmnic0 - n

  VLAN 0

  Packets received: 140

  Packets sent: 5

  VLAN 5

  Packets received: 727

  Packets sent: 366

  ~ #

  Everything is good...

  Then I configured the port of pSwitch to be member of an extra VIRTUAL local network... VLAN 6. Did nothing on the host side.

  Fired again stats...

  ~ # esxcli network nic vlan stats get vmnic0 - n

  VLAN 0

  Packets received: 243

  Packets sent: 8

  VLAN 5

  Packets received: 979

  Packets sent: 431

  VLAN 6

  Packets received: 14

  Packets sent: 0

  ~ #

  Looks like the stat info is updated very quickly in my quick test...  Perhaps this will help you check VLAN available...

  / Rubeck

• VLAN does not work on my ESXi 4.1

  Hello world

  I thank I could achieve this configuration fairly quickly, but it looks like I forgot something.

  I want to connect to a real machine, I'll call her server to one of my virtual machine, using a 802. 1 q VLan. To do this:

  -on my physical netgear switch, I created a new VLAN 802. 1 q, which has the id: 100. My server is connected to a port without a label to this VLAN '100 '.

  My ESXi is connected to a port marked to this VLAN '100 '.

  - then I created a new group of ports in the vswitch linked to my ethernet interface physical ESXi (the one that is connected to the netgear switch). I implemented the VLAN 100 id in this port group.

  -J' I set up my VM so that it uses this interface ethernet port group.

  The problem is when my ping on my server VM, it gets no answer: I see the appeal by the virtual machine on my server with tcpdump, then the response from the server with arp ARP response, but this arp reply never saw my VM.

  So it seems that communication is correct VM to the server but no server VM. I use an ESXi DELL server with some ethernet interfaces and the one I use (broadcom interface) for the VLAN is not the management interface.

  Thanks much for any help!

  Alex

  Alex

  If your ESXi is connected only to physical port 1 and port is shared resources on the physical switch, then you should have a unique vSwitch in your ESXi. On this vSwitch, create two ports: one for one for VM3 and VM2. Give each group of port id VLAN different (2 for "port_group_2") and 3 for "port_group_3" and attach each VM to its corresponding port group.

  Franck

• DCB - Force10 MXL and Equallogic PS6210 - worth it or not?

  Hello all

  I have a new 3-blade M620 virtualization environment, 2 x MXL Force10 switches and 2 x Equallogic PS6210 - there is the possibility of using DCB - is it useful to configure DCB, will I get the gains and better stability, or for a small environment should I just use the configuration standard iscsi?

  Ideas or alternative options gratefully received.

  Thank you

  Hello

  If the switches are dedicated for iSCSI use, then there is no advantage to the use of DCB.  DCB in itself does not have iSCSI faster.  I just made sure non-iSCSI traffic doesn't interfere by providing iSCSI with a higher priority.  All other traffic is going in a "lossy" class of service.

  Also, you will need DCB converged network adapters to use BCD on the hosts.  Most of the iSCSI software adapters do not support DCB.

  Kind regards

• Force10 MXL - stack or do not stack

  Hi guys,.

  If the availability is the most important thing, trunk or battery MXL rocking?

  I like simplified management, ability to balance the load on several links but I am concerned about uptime during the upgrade firmware (5-10 minutes?) and the possibility of a total interruption of the battery breaks.

  On the other hand Force10 perhaps more capable stacking that for example. 6224 switches, I had a lot of problems of overlap with.

  Forgive me if this is the wrong place to ask, but I couldn't find a Force10 forum? :-)

  Thank you

  Respect of
  Kristoffer

  The MXL switches support Virtual Link Trunking (VLT) later this year, which will solve this problem.

• Force10 MXL config question

  My MXL blades have been set up by Dell Technology Services and work fine, but I would like to make a few changes now and not being Setup is not a network engineer, I have a problem with the docs I could find on the config of Force 10.  Specifically, I want to do 3 things:

  (1) change the SSH root password

  (2) remove a port to a LAG (port channel) group

  (3) add a new VLAN to some ports in the switch, including the one I just removed the lag, but abandon the SHIFT since the new VLAN

  Can someone point me to a doc that explains how to do this kind of things?

  Also, is it possible to access the console somehow by SSH in the CMC?  I swear I've seen Dell Tech Services people who do somehow, but I don't know how they did it.  Maybe I misunderstood what they were doing.  It would be nice to not have the addresses of IP config exposed and control access through the permissions of CMC.

  Thank you.

  Hi amunter,

  You can SSH to the CMC racadm commands and use to set it up. You just need to use PuTTY or other terminal program and go to the CMC host name or IP address.

  You should be able to change the password in this way

  (Force10) > activate

  (Force10) #config

  (Force10) (Config) #username admin passwd un_mot_de_passe

  _Config_07_29_2014.PDF https://www.force10networks.com/CSPortal20/Knowledgebase/documentation/CLIConfig/FTOS/MXL_9.5 (0.1)

  You can remove a port of a port channel in the channel of the port and using the command config no channel-member interface

  Page 395

  You can assign a VLAN to a port with the command interface vlan id - vlan

  Page 910

• VLAN will not work on Interswitch link SLM2008 SRW2008MP

  I have a SLM2008 (SW01) and a SRW2008MP (SW02), these are inter connected both on port g1. G8 SW01 port is connected to the HDSL modem my ISP (off-grid). Connected G2is inside an ASA5505, offering my inside of network port. G7 and g8 SW02 port is connected outside 2 servers. I created a VLAN 2 on both switches. SW01 has 2 PVID on port 8, Acceptable frame types = All and enabled the capture filter. All other ports has same config except PVID on these are 1.
  On SW02 I tried several setting of VLAN on ports 1, 7 and 8. NO CHANCE!
  In general, I tried g1 as trunk, joined the untagged VLAN1, VLAN2 tagged, Acceptable frame types = All, PVID = 1, penetration fltering on. Ports g7 and g8, I tried with the access mode both in general mode, with several combinations of tag/untagged etc etc.
  I am not able to pass all traffic to the outside.

  Anyone? Help.

  Thanks in advance

  HKL

  Basically, what I want to achieve is; using a vlan between the 2 switches create a topology as if I had 4 physical switches, connected 2 and 2. No traffic should pass between the 2 pairs. No servers or other resources should be informed (or care) if they are on the physical pair 1 (VLAN1) or physical to pair 2 (VLAN2).

  As I see, or understand, the only difference between 4 physical switches and 2 physical (using the VIRTUAL local area network), it is that we need two trunk VLAN through, instead of having 2 physical connections intercommutation

  All outside routing is handled by the ASA (from vlan1) to VLAN2, the server will be directly using public IP address.

  In a concern for information inside subnet is 192.168.1.x, NAT by ASA at the public address 62.89.36.34/24 outside VLAN2 will be directly connected and use the servers 62.89.36.45 and 62.89.36.46

  GW = 62.89.36.33

  Hope this will make sence?

  BR

  JK.

• Reference Dell Force10 S4810 VLAN in mirror

  Ladies and gentlemen,

  I was wondering if you have some experience with the mirroring of the ports on the VLT in Dell Force10 switches and if it is possible.
  I searched for more information last week and could not find valuable comments.
  I have a setup two switches to the VLT VLT.
  I have a couple of servers connected with port LACP channels and dozens of VLANs which they are responsible.
  Is it possible in the VLT to have mirrored a VLAN configuration to other VIRTUAL LAN?
  Best regards
  Kaloyan S.

  A full installation of VLT will require more ports that supports mirroring, and there is not a way to layer 3 mirroring.

• 6248 VLAN do not receive the DHCP scope

  I created two new DHCP scopes in my windows server 2003:

  192.168.2.0 - public, and
  192.168.3.0 - VOIP.

  This DHCP server is connected to a Dell powerconnect 2708, which is connected to our new powerconnect 6248P via fiber point-to-point.

  In the new computers on network on the default 1 VLAN are correctly attributed IPs as they connect.

  I issued the following commands to the 6248 CLI:

  Enable
  Configure
  database of VLAN
  VLAN 20
  VLAN 30
  output

  Configure
  range of interface ethernet 1/1-g1/g2
  switchport mode general
  VLAN allowed switchport General add 20
  switchport General pvid 20
  l2relay DHCP
  output

  Configure
  range of interface ethernet 1/1-g3/g6
  switchport mode general
  VLAN allowed switchport General add 30
  switchport General pvid 30
  l2relay DHCP
  output

  interface ethernet 1/g11
  switchport mode general
  VLAN allowed switchport General add 20
  VLAN allowed switchport General add 30
  l2relay DHCP
  output

  Configure
  interface vlan 20
  name 'PUBLIC '.
  Routing
  IP 192.168.2.1 255.255.255.0
  IP helper 192.168.1.150
  output

  Configure
  interface vlan 30
  name "VOIP."
  Routing
  address 192.168.3.1 255.255.255
  IP helper 192.168.1.150
  output

  IP routing

  I also added all traffic on VLAN 20 and 30 of VLAN on ports 1/g11 (6248) and port 2 (2708). VLAN 1 access was removed from ports 1/1/g1-g6 (6248)

  Everything seems to have been set correctly, but I can't get a response from the DHCP server on all ports attached to VLAN 20. The powerconnect 2708 switch is unable to pass the baton to the server? Is it possible that something falls in the point to point?

  I would greatly appreciate any comments or suggestions, thanks!

  The 6248 has no default gateway. It wont let me put 192.168.1.1 because he does not reside in the same subnet as the 6248 (192.168.99.1)

  The 2708 has listed 192.168.1.1 as its default gateway.

  At this point, the network has too many complexities for me to unravel. I am very happy that at least I solved for DHCP when we finally migrate our server to the new location.

  Once the server is up, and the gateway/firewall are directly connected to the 6248; I will review the correct configuration of this network.

  Some advice to those who might have a similar problem: check your management VLAN. It may not be the same VLAN 1 if you plan to routing to work from VLAN 1 to nowhere else because the VLAN management cannot be routed. Also check static routing of your access point, make sure the front door has a return of the ips of your VLAN, IE: 192.168.2.0 255.255.255.0 gateway_ip

  That's all for now. Thank you to all who have contributed