Wednesday, October 20, 2021

Juniper EX-3400 VC

Easiest way to stack two EX3400's is make sure they are on the same code level. Then connect them using the QSFP+ ports. Boot the master unit first. Then boot a blanked secondary unit. Give it a few minutes, but a stack will form. Then assign roles and build the config.

https://www.reddit.com/r/Juniper/comments/lccqui/juniper_virtual_chassis_ex3400/

If the two switches are physically co-located, then acquiring a pair of DAC cables would be best. But, you can certainly use SFP+ ports instead.

You will need to wipe the config on the second. Setup the virtual-chassis config on the primary as preprovisioned. List both serial numbers of both devices. Copy the config from the seconday, and add it as additional config to the primary, AFTER having edited all of the interfaces to be 1/x/x instead of 0/x/x.

Yes JunOS will let you configure interface config for interfaces that do not exist (yet.)

You'll also want to delete all of the system config and other non-interface config before you add it to the primary.

Get the secondary to the same software version as the primary, it's just easier. Wipe the config. Request the desired interfaces to be VC ports on the secondary. Power it down. Request the desired interfaces on the primary to be VC-ports. Connect the VC-port interfaces. Power-up the secondary.

Wednesday, November 8, 2017

IAP to CAP issue



Hey, are you having issues with the IAP305? This requires a minimum of ArubaOS 6.5.1.0 or 8.1.0.0 on the 7005 controller. Try upgrading the 7005 to 6.5.1.0 or above first.

http://www.arubanetworks.com/assets/ds/DS_AP300Series.pdf

The Instant firmware version has two parts, separated by a dash (-):
Release 6.5.1.0-4.3.1.3; means based on controller version 6.5.1.0, and the Instant version is 4.3.1.3. In your screenshot, you can see the -4.3, and scroll to the right to see the full version name (or just click on it).


http://community.arubanetworks.com/t5/Wireless-Access/Problems-when-converting-IAPs-to-CAPs/td-p/294459

I want to convert two IAPs to CAPs to be managed by a controller but I had a problem. One IAP is model 305 and the other is 325, both running firmware 6.5.1.0-4.3.1.3. The controller is model 7005 running firmware 6.4.4.12. The IAPs already have some configuration. When converting the IAPs I got this message
problem.png
Why do I get this error?
Is it because the IAPs firmware are higher than the controller firmware?

http://www.arubanetworks.com/techdocs/Instant_40_Mobile/Advanced/Content/UG_files/Basic_conf_tasks/Firmware_Image_Server_in.htm

Monday, November 6, 2017

IAP to Campus AP conversion problems

http://community.arubanetworks.com/t5/Controllerless-Networks/IAP-to-Campus-AP-conversion-problems/td-p/274331

AP rebooted Wed Aug 24 22:25:22 UTC 2016; Image Download Failed.
Your controller likely isn't running a version of code that supports your AP.
What release are you running on your controller?
As noted in the AP datasheet, the 325 requires a minimum of AOS 6.4.4.0.

Wednesday, November 1, 2017

voucher

https://community.ubnt.com/t5/UniFi-Wireless/Custom-UniFi-Voucher-Portal/td-p/251674/page/9
https://community.ubnt.com/t5/UniFi-Wireless/configure-vaucher-design/td-p/986261
C: \ Users \ PC \ Ubiquiti UniFi \ data \ sites \ default \ portal \ bundle
edit this file 'voucher.html "
the image size in the width and height We graduate
nome in url you put the extension and direction of your imagem
This is a personal design to use, I hope you serve as an example
v3.1.9
<div class="voucher">
<td> src="http://URL OF IMAGEM.png" <img style="width: 350px; height: 90px;" alt="NOME" /> </ td>
</ br>
  <br> <p class="note"> <unifi var="note" /> </ p>
<p class="code"> <unifi var="code" /> </ p>
Valid for InnoFiOS <p class="valid"> <unifi var="valid" /> </ p>
</ br> <p style="font-family: span Segoe UI Light; text-align: justify; font-size: 15px"> "Because the technology does not stop us"
</ div>

Sunday, October 29, 2017

USG - How to configure in existing multiple VLAN network


The trick was to have the management network untagged and the other network(s) tagged.

The error I made was to have de management network tagged as well.

I've changed the port on the switch to untagged VLAN 10 and tagged VLAN 2.
I removed all the networks from the USG, changed the primary IP to the correct one in VLAN 10. After a few second I could reach it on the correct network and added the other network.

https://www.blogger.com/blogger.g?blogID=8575246386029674811#editor

Thursday, October 12, 2017

Juno: Configuring VLANS and Trunking on the EX-series Switch

1. From configuration mode create the VLAN and add access interface to it:  

root> configure
Entering configuration mode

[edit]
root# set vlans <vlan-name> vlan-id <vlan-id (1..4095)>
root# set interfaces ge-0/0/<port#>.0 family ethernet-switching port-mode access vlan members <vlan-name>
root# commit 


2. Verify the VLAN and interface:
root# run show vlans
-------------------------------------------------------
Name           Tag     Adress            Ports
                                       Active/Total
-------------------------------------------------------
bar           67      ---------           0/0
default       None    ---------           3/5
foo           66      ---------           1/1

 
root# run show ethernet-switching table | except :

  VLAN              MAC address       Type         Age Interfaces
  foo               *                 Flood          - ge-0/0/5.0
  bar               *                 Flood          - ge-0/0/16.0, ge-0/0/15.0
  default           *                 Flood          - ge-0/0/0.0, ge-0/0/1.0, ge-0/0/2.0

 
root# run show ethernet-switching interfaces
Interface   Index    State     VLAN members
ge-0/0/0.0  69       UP        default
ge-0/0/1.0  70       UP        default
ge-0/0/5.0  71       UP        foo

 
root# show ethernet-switching interfaces detail
Interface: ge-0/0/0.0 Index: 69
  State: UP
  Vlans: default(untagged)

Interface: ge-0/0/1.0 Index: 70
  State: UP
  Vlans: default(untagged)

Interface: ge-0/0/5.0 Index: 71
  State: UP
  Vlans: foo(untagged)
  3. Configure the TRUNK and add VLAN that was created in previous steps:
root# set interfaces ge-0/0/<port#>.0 family ethernet-switching port-mode trunk [native-vlan-id <id>] vlan members [ whitespace separated list of vlan names or IDs ]

root# commit

4, Verify the TRUNK and the VLAN members for this trunk:
root# run show interfaces ge-0/0/<port#>.0
Flags: Trunk-Mode <---

root# run show ethernet-switching interfaces
Interface   Index    State     VLAN members
ge-0/0/2.0  71       UP        my-vlan, mydefault, pfetest

Tuesday, October 10, 2017

Guest VLAN cannot access Guest Portal

Telnet into those ports which seems to connect on both. I ran nmap to verify the ports were open from the guest client to the controller.  The following ports were open that should be associated with the UniFi controller:
8080
8443
8843
8880

I **think** that I am doing what you want. I run my own controller on my LAN at 192.168.16.14. I have a VLAN-capable firewall, but no VLAN switch. I created a VLAN with three ports of my firewall (one is the uplink to non-VLAN switch; two are for UAP connections). I set up a matching VLAN for the guest SSID on my two UAPs, and I have my inform address as a public FQDN. My firewall is set to allow loopback processing, so when a guest tries to reach the portal, traffic goes "out" the firewall and back "in" to the WAN IP via the FQDN lookup in my public DNS. That way, there is no LAN traffic needed to reach the controller for the guest portal, and it works with the guest in its own VLAN.

Yeah that's pretty close, the difference is that we do some tagging on the switch as well, but we've confirmed that traffic is flowing already so I'm less concerned now about the VLAN tagging now than I am the firewall itself and it being an ASA not allowing loopback.  The strange thing is that everything still seems to be getting through though port wise.

Unfortunately support hasn't been able to help yet.

Juniper EX-3400 VC

Easiest way to stack two EX3400's is make sure they are on the same code level. Then connect them using the QSFP+ ports. Boot the master...