Update - One recomendation I can make at the end of this process was to use the CLI command to update both RCPs at the same time.  The software rev. was so different the two RCPs were not playing well together.

There is so little publically available information I thought i would run down the steps for upgrading the Shade Tree software on an ST200.  Do this from the console port just to be sure.

1)  login into the ST200 as one would normally.  From the user@hotname> prompt, type “start shell”

2)  now, ftp the new image “ftp X.X.X.X” and from the ftp prompt get st.200-3.2R4.24-XXXXXX-restricted.tar

I now logged out of the st200 and logged back in as root.  I then copied the file to /var/staging/bundle

3) log out and back in as a regular superuser and type “request system software add st.200-3.2R4.24-XXXXXX-restricted.tar older”

It will now do its thing.

Restart when finsihed.  Any problems feel free to contact me.

—  Day 1, Monday June 8th 2009

It was our decision to deploy one ST200s in our POP (Point of Presence) in Florida.  I am going to post portions of the configuration to guide others who might be deploying hardware using Shadetree software.

From the top down, the config has been set as follows:

set system domain-name mia01.digiport.net - easy enough, we set the domain name for the system

set system host-name core01 - again, very straight forward

set system login user NOCUSER class super-user - Iw ill change the premissions for this user later

set system login user NOCUSER authentication encrypted-passsword - hitting enter then prompts for a password

set system management-network interfaces eth0 unit 0 family inet address X.X.X.X/24 - setting ip

set system management-network static-route X.X.X.1/24 - still fairly straigh forward stuff

set system name-server 4.2.2.2 - have to love AT&T’s name server

commit

I am going to run a cable to the management network and test IP connectivity.

Step 2

Now that I have a list of suitable hardware prospects the next step was to submit a network design to each of the vendors. Now, I did not want to steer each manufacturer towards what I had in my head, I only wanted to seed their imagination. I provided a rough concept of what we were trying to accomplish and asked for network designs back from each hardware vendor reflecting how they would accomplish our goals using their technology. Interestingly enough, each hardware vendor returned with an almost identical design.

Stage 1

Obviously before even a vendor selection process can begin you must have a properly defined business networking objective. In my case, I can not say this was true. I was presented with a very clear and concise business objective - Connect a Number of Offices together while keeping our costs to a minimum yet allow for growth. Simple enough objective, right ? Not really, as you will discover as I bring you through this process.

So, that said. Here are the vendors I Evaluated

ECI Telecom which included their monster machine Laurel ST200 as well as the ECI 9705 Switch/Router.
Cisco Systems 6500, 7609 and the smaller ME switches. I mean, they are Cisco so I will devote more time to discussing the options they presented. Think “Chinese food menu” with larger numbers on the right.
Juniper - If I said, “they are Juniper, enough said”, I would be lying. You might be surprised by my findings.
Foundry - This is another really interesting company, actually they all are, however Foundry was a little perplexing to me. Their product set included the Net Iron, Big Iron and so forth.
Alcatel / Lucent - Now, as this story is still playing out I won’t comment much other then to say life is full of surprises. Their products are the Alcatel 5630 and Alcatel 7750
Extreme Networks - Models’ Alpine. Good for skiing or networking. Stay tuned to find out

As some of the vendors asked I sign NDA’s the information at time might seem a little vague. In the interest of fairness I will only disclose the same “type” of information for all of them vendors as if they are all covered under the same NDA.

If you wish specific information or can’t wait until until I finish all the postings please email me at rob@robthorell.com

Nearing Christmas, I find myself engrossed in my most challenging network project to date.  While I have moved, changed, built and torn down networks with live operating services for years I have never been presented with the unique challenge of building a national IP service delivery network from the ground up.  This is mainly a result of trying to predict and account for all possible services and network growth that could be encountered over the next 5 or more years all the while trying to keep hardware costs such as switches and routers as a minimum.

I will attempt to post as many details as possible to my network design page in order to hopefully provide guidance and assistance to others facing the same challenges as myself.  Let’s start with the scope.