So what about applications specifically do network engineers need to know.

I was at Network Worlds ONX (SDN) conference and I heard for the nth time that network engineers need to learn how to communicate with our application developer partners.

Learn WHAT, never seems to be answered. So I came to the conclusion I would need to figure this out myself.

Clearly we are going to have to speak some common language and develop a way to map the design of an application into network characteristic we can provision (QoS, load balancing, security, traffic engineering etc.).

I think the knowledge is there (and been there for a while) so looking at the ancient texts may give me some answers

My first stop is the classic 8 myths of distributed computing

1. The network is reliable.
2. Latency is zero.
3. Bandwidth is infinite.
4. The network is secure.
5. Topology doesn't change.
6. There is one administrator.
7. Transport cost is zero.
8. The network is homogeneous

See below for some links. We can now begin a discussion as to did the application developer make any of these assumptions and are any of these issues in your network.

http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing

http://java.sys-con.com/node/38665

http://www.rgoarchitects.com/Files/fallacies.pdf

 

I also remembered that there are a number of different interaction models for applications

RPC: Short message the application is waiting for a response so latency important

Message queuing: I send a message and check back later, latency not as important

File transfer: a 1 way transmission care about available bandwidth and is the application written to consume the bandwidth.

Email?

Streaming

Not sure if data base calls are the same as RPC or different.

The point is that the interaction model between application components is key to what demands the application will have upon the network. So understanding the interaction models and mapping them to the sorts of network services are required to make those applications work seems a good place to start.

 

I am not sure if I need to go into the types of SOA, SOAP, XML etc. I am hoping that people smarter than me can begin to describe what the right information we need to have as network engineers.

Ideas for cisco live

Many people publish advice for cisco live attendees, hopefully new information here. I have been a regular attendee since 2000.
1. If you take a techtorial (sic), bring an old 1 gig flash drive. Often the speakers do not have their current slides uploaded to the site on Sunday and so a flash drive is a passed around the room. We all have old 1-2 gig flash drives that are smaller than we normally use, bring one and you first get a copy of the slides early on, and also help the rest of the room.
2. See if the sessions you want to attend are already on cisco live 365 you can check out if the session is right for you and have the slides before you go.
3. bring and extension cord with extra outlets, power can be hard to come by but someone may share their outlet if you don't need them to unplug.
4. Don't schedule that really heavy technical presentation you need to see on Thursday afternoon, you will be tired.
5. Have software that lets you highlight or annotate the PDF slide decks (depends on your platform)
6. AC can be rough have a sweater or sweatshirt with you
7. Make use of any lounge  you can (netvet, certification, collaboration) its easier to get a seat and maybe a drink when you need it
8. Ask questions but project your voice (big room) and try not to tie up the speaker too long. Some of the best stuff is at the end of the talk and you don't want the speaker to rush through it.

what is this

I am doing this blog to record the vairous odd things that I encounter in my deployment and troubleshooting work. much of this is for myself but I hope some if it benefits others. this was recorded in ccie3555.blogspot.com but for some reason google lost its mind and cant make the links anymore