Missing The Wave

Mornings are so different when my job is searching for new opportunities. Leaving SONIFI has been a bittersweet experience. I was a part of another success story: one which involved exponential growth and personal development. Moving forward I hope to find something which continues to push and inspire me in new and different ways.

As I look to the future, I find myself reflecting on all the amazing opportunities I have been close to.  I have almost three decades of telecommunications history allocated in my brain. New people are constantly entering the space. They are trained on cloud and virtual interfaces. Everything is about programming a server to do what professionals used to do through expertise and hands-on experience. Now, when the server breaks, the only recourse seems to be opening a ticket with a cloud provider and hope they will respond quickly. I find myself saying used to be… used to be simple, used to be quick, used to be efficient, used to work.

The other words I often think or say are, “I almost…” When people reach their twilight hours you will often hear these words or something similar. I almost… I wish I would have… If only I…

I almost built that tower. I almost bought that.

I was only in high school when one of those opportunities came to our family business. I remember spending my vacation and weekends interacting with the up-and-coming movers and shakers in telecommunications in Bellingham.

I remember attending the business meetings. It seemed like Olive Garden had just opened. We would meet there to discuss building a fiber optic network in Bellingham. It was an exciting time. We were so focused on building towers, microwave links and radio systems that we missed a great opportunity. We went in a different direction. I am grateful to have been a part of this. The opportunities we miss are bigger in our minds than reality. We need to focus on the opportunities we realized and be grateful.

I did that.

BH Sun, Mar 24, 1996 Page 39
Ready to be a ‘virtual village’?

Fiber-optics option brings information superhighway right past Whatcom County doors

Four Bellingham businessmen say now is the time for the information superhighway to come to Whatcom County. Spurred by the completion of a fiber-optic line between Seattle and Vancouver, B.C., the four want to string fiber-optic cables on power poles in Bellingham. That would allow them to offer businesses, governments and residents such high-technology Internet access options at speeds much faster than current telephone lines, video conferencing and cable television. Known as the Bellingham Data & Video Group, the partners have applied to the city for a franchise to allow them to use city rights of way. “In Bellingham and Whatcom County, businesses, the city and county, the university, can now be a virtual village,” said John Gar-gett, vice president of EIS International, a technology firm in Fairhaven. Quotable “This is not pie in the sky, this is literally here now.” John Gargett, EIS International

In addition to Gargett, the others involved are:

John Kehres, owner of Black Rock Cable, which operates a cable TV system in part of Whatcom County.

Gerald Noe, owner of Wiztronics, an electronics service and wireless communications firm on Ellis Street.

Dan Seafeldt, owner of Horizon Technologies, a Bellingham
Internet services provider.

The group formed in the last four weeks. It plans to hook up to a fiber-optic cable system recently built by Canadian company Starcom International Optics Corp. The line goes through Bellingham and was responsible for several traffic snarls over the winter as Starcom contractors dug up parts of Holly Street and other roads to install the line. Starcom officials say they’re ready to provide the Bellingham Data & Video group access to the line. Fiber-optic cables are made of thin glass and are able to carry much more information that the copper cables in use in most phone and television cable systems. Lynden is the only county community wired with fiber-optic lines. TCI Cablevision of Washington Inc. has strung the high-tech wires there in preparation for eventually offering hundreds of cable channels, interactive television and possibly phone and Internet services. “There are other companies that have connections in Seattle and Vancouver,” said Edward Tucker, vice president of sales and marketing at Starcom. “We’ve taken an active interest in bringing these kinds of services to cities such as Bellingham.” Members of the Bellingham group say they haven’t formed their corporate structure yet, but have the financial backing to begin stringing cables to businesses and government offices within four to six weeks of approval of a city franchise. They don’t plan to string cable on every street and to every home in the city and county. Instead, they would run a line from Starcom to their headquarters and then to people who pay for the hookup. Group members say they expect businesses to be among their first customers. “I’m working on a project in an Asian country that requires me to travel three days there and three days back,” Gargett said. “What this system can do is allow me face-to-face, real-time meeting with officials of that country with out ever leaving the office. “It could allow me to watch and maybe even testify at a city meeting without ever leaving my home or office.”
The backers say the network could lure high-tech businesses to the county and create new jobs. City officials hold a key to the success of the plan: the franchise agreement. “Generally the city gets involved in franchises for public safety and taxation issues,” said Jack Garner, city public works director. “My guess is there will be a lot of discussion in the City Council about how to go about this.” The city now has several franchise agreements, such as those with Puget Sound Power & Light Co. and TCI Cable that allow the companies to string their lines and plant poles in city rights of way. If the city forces Data & Video Group to put their wires underground, it would cost too much and kill the project, Kehres said. But if the city approves above-ground hookups, the group would move ahead quickly, he said. “Black Rock Cable has the funding available now to build a lot of this line,” Kehres said. Part of the lure for Kehres is the ability to compete with TCI at businesses, hotels, apartment complexes in delivering cable TV. Black Rock now offers cable television to people in areas east of Bellingham, south of Everson and west of Nugents Corner. The new system wouldn’t be a standard cable system, but instead would allow apartment complexes and others to receive cable signals that they would manage themselves. Kehres said the timing is crucial. TCI Cable is planning to blanket the county with fiber-optic lines in the next few years. How long that will take depends on negotiations for franchise agreements between TCI and officials of Whatcom County and cities in the county. Negotiations between TCI, Whatcom County and the city of Bellingham are under way. “We have a window of opportunity to get a good portion of the market in data and wholesale video transmission,” he said.

It took me a while to find the article I had remembered reading almost thirty years ago. It is so fitting that I have worked so extensively with fiber optics despite it being closed off to me early on.

I look forward to capitalizing on new opportunities as I navigate the waves of possibility crossing over my proverbial bow. Let’s be honest, I will probably continue to telling tales of the old and new ones that got away.

1

2

Watchguard T55 Initial Setup

Pull everything out of the box.

Connect the power supply to AC power plug and the other end to DC plug on the back of the firewall.

Plug the 0/WAN port into your internet connection. Plug the 1/LAN port into your computer. You will configure your network adapter with a DHCP configuration.

Power up the firewall by turning the switch on. Located on the back.

When the firewall boots up, your computer should obtain a DHCP address.

IP:                        10.0.1.2
Subnet Mask:    255.255.255.0
Gateway:            10.0.1.1

Once this is complete, you will be able to manage the firebox by entering the following URL into your browser…

https://10.0.1.1:8080

Default credentials are…
admin
readwrite

Click Log In to access the web GUI.

Create a new configuration. Accept the License Agreement. Click Next.

The WAN interface might automatically connect with a DHCP address. If this is how your network will be configured, press Next. I will assign a static public IP in this case.

 Click the Static radio button. Click Next.

Enter the Static IP information. Click Next.

Enter the DNS information. Click Next.

Configure the trusted interface. Click Next.

Enter your status and admin credentials so that the device is not accessible with defaults. Click Next.

We will not worry about the remote management. Click Next.

Configure the Device Name, Device Location and Contact Person. Decide if you want to provide feedback and check the box accordingly. Click Next.

Select the Time Zone. Click Next.

Click Next.

Select some of the more advanced control features. Click Next.

Review your settings. Click Next.

The firewall will apply the new settings. You will be given a new IP address in the new subnet.

 

Ubiquiti EdgeSwitch 24 Lite Setup

Overview

Ubiquiti switching – I am deploying the non-POE lite version on a current project. This appears to be an enterprise-grade switch at a SOHO price point. Steel case, DC power option and standard console cable. Specs are comparable to long-established equipment providers.

Console Connection

To access console terminal, connect console rollover cable to console port on the rear of the switch.

Settings
Speed                 115200
Data bits            8
Parity                 NONE
Stop Bits            1
Flow Control    NONE

You will need a USB to Serial adapter for most modern computers. Use Device Manager to determine COM port.

I received the following scrambled output while using an HL-340 USB to Serial Adapter…

CH▒▒
▒s[n▒▒H▒▒H▒7▒▒▒▒▒H▒▒H▒7▒▒▒▒▒

I used my Trendnet adapter and it worked.

User:ubnt
Password:ubnt
(UBNT EdgeSwitch) >en
Password:ubnt
(UBNT EdgeSwitch) #terminal length 0

(UBNT EdgeSwitch) #show run

default-config.txt

Show Interface Information

(UBNT EdgeSwitch) #show interfaces status all

Setup SSH

Generate the crypto key for SSH.

(UBNT EdgeSwitch) (Config)#crypto key generate rsa

(UBNT EdgeSwitch) (Config)#crypto key generate dsa

Make sure they are both present. Disable Version 1.

Here are some CLI commands for setting up SSH.

ip ssh server enable
ip ssh protocol 2

(UBNT EdgeSwitch) (Config)#show ip ssh

Administrative Mode: …………………….. Enabled
SSH Port: ………………………………. 22
Protocol Levels: ………………………… Version 2
SSH Sessions Currently Active: ……………. 1
Max SSH Sessions Allowed: ………………… 2
SSH Timeout: ……………………………. 5
Keys Present: …………………………… DSA RSA
Key Generation In Progress: ………………. None

CLI Write Memory To Save Config

(UBNT EdgeSwitch) #write memory confirm
Config file ‘startup-config’ created successfully .

Configuration Saved!

GUI Interface

The Edgeswitch comes with a default management IP address of  192.168.1.2

There is a cool tool for chrome that allows layer2 Ubiquiti device discovery. Ubiquiti Device Discovery Tool

Once installed you can access it from chrome by copying this into the URL… chrome://apps

You will need to set your network inteface IPV4 settings to 192.168.1.X (not 2) to reach the switch. (Or your can also use DHCP.) I like to know what switch I am working on by using the default IP directly connected.)

Make sure you can ping the switch.

Now you can access the management webpage from a browser by opening 192.168.1.2

Enter the username and password ubnt/ubnt and accept the terms if moved to do so.

GUI VLAN Setup

Add the new VLANs. I start by entering VLAN 3. Click Add.

Change the name once the VLAN is added. Click Submit. Repeat for the other VLANs.

Assign Untagged, Excluded or Tagged ports by toggling between U, E and T by clicking on the letter on the VLAN row. Make sure to leave your current management port untagged VLAN 1.

In this example, I am using port 23 and 24 for untagged VLAN 3 and tagged VLAN 4 backhaul traffic. Fiber ports 25 and 26 are tagged for potential future backhaul.

Setup Rapid Spanning Tree

I prefer to use Rapid Spanning Tree. The switch comes by default set to Multiple Spanning Tree. There is no need to run MST given our topology. Effectively MST will run like RSTP but what is the point? Just run RSTP to begin with.

Switching > Spanning Tree > Switch

Select IEEE 802.1w. Click submit.

GUI Management IP Setup

Finding the IP address in the legacy interface can be a challenge. The bread crumb to reach the interface configuration is…

System > Connectivity > IPv4

Enter the management IP address information. Select the Management VLAN ID. In this case we will use VLAN 3 for management.

WHEN YOU CLICK SUBMIT YOU WILL NEED TO CHANGE YOUR COMPUTER IP ADDRESS TO MATCH THE NEW SUBNET. YOU WILL ALSO NEED TO MOVE TO A PORT ON THE MANAGEMENT VLAN SETUP ABOVE.

Once you change your IP to the correct subnet. You will be able to log in on the new address.

Go back to the VLAN menu and program the original VLAN 1 management port to the VLAN it will used for.

Firmware Upgrade

Determine what the latest firmware revision is available on the site.

Ubiquiti Firmware

We will use ES-eswh.v1.8.2-lite.5192445.stk

Navigate to Basic>Firmware Upgrade

Select the Backup image upload by clicking the up arrow to load the firmware to the backup flash.

Navigate to the folder containing the firmware file and click Open.

Click Begin Transfer button.

Once the Transfer is complete, click close.

The new firmware should be in the backup location. Click the radio button to have the new firmware as Next Active. Click Submit.

Click on the Restart Switch tab. Basic > Restart Switch
Make sure that you have saved the configuration before reloading the switch.

Click Restart Without Core Dump

Once the device reloads, check to see if the firmware upgraded properly.

Through CLI you can issue the following…

(UBNT EdgeSwitch) #show version

Switch: 1

System Description……………………….. EdgeSwitch 24-Port Lite, 1.8.2-lite, Linux 3.6.5-1b505fb7, 1.0.0.4857129
Machine Type…………………………….. EdgeSwitch 24-Port Lite
Machine Model……………………………. ES-24-Lite
Serial Number……………………………. 18E8294A815A
Burned In MAC Address…………………….. 18:E8:29:4A:81:5A
Software Version…………………………. 1.8.2-lite

Make sure all your switches are running the same firmware.

Setting Up Time Servers

I tried using the default time servers. They did not work for me. I have always had trouble with name servers on switches. DNS resolution can be problematic even on the old school brands. I ended up loading resolved IP addresses for the servers and was able to get it working right away.

time-a-g.nist.gov…………..129.6.15.28
time-b-g.nist.gov…………..129.6.15.29
time-c-g.nist.gov……………129.6.15.30
time-d-g.nist.gov……………129.6.15.27

GUI Way
System > Advanced Configuration > SNTP > Global Configuration

System > Advanced Configuration > SNTP > Server Configuration

CLI Way

sntp unicast client poll-retry 10
sntp client port 123
no sntp server “1.ubnt.pool.ntp.org”
no sntp server “2.ubnt.pool.ntp.org”
sntp server “129.6.15.28”
sntp server “129.6.15.29”
sntp server “129.6.15.30”
sntp server “129.6.15.27”
clock summer-time recurring USA offset 60
clock timezone -8 minutes 0 zone “PDT”

Base Configuration

Base-Config

LLDP Configuration

LLDP is configured by the port on Ubiquiti switches.

To send all traffic…

interface 0/x
lldp transmit-tlv port-desc
lldp transmit-tlv sys-name
lldp transmit-tlv sys-desc
lldp transmit-tlv sys-cap
lldp transmit-mgmt

To prune LLDP traffic on port both directions…

interface 0/x
no lldp transmit
no lldp receive

To listen for LLDP packets and not transmit…

interface 0/x
no lldp transmit

Some helpful LLDP commands…

(UBNT EdgeSwitch) #show lldp remote-device all

LLDP Remote Device Summary

Local
Interface RemID Chassis ID Port ID System Name
——— ——- ——————– —————— ——————
0/23
0/24 3 18:E8:29:4A:81:5A 24 OtherSW
0/25
0/26

(UBNT EdgeSwitch) #show lldp remote-device detail 0/24

LLDP Remote Device Detail

Local Interface: 0/24

Remote Identifier: 3
Chassis ID Subtype: MAC Address
Chassis ID: 18:E8:29:4A:81:5A
Port ID Subtype: Local
Port ID: 24
System Name: OtherSW
System Description: EdgeSwitch 24-Port Lite, 1.8.2-lite, Linux 3.6.5-1b505fb7, 1.0.0.4857129
Port Description: Uplink
System Capabilities Supported: bridge, router
System Capabilities Enabled: bridge
Management Address:
Type: IPv4
Address: 192.168.0.21
Time to Live: 114 seconds