Building an IoT company is a great opportunity to work on things you have never done before. Here is a list of my conclusions with brief anecdotes about the difficulties of building az IoT company.
Choose the size of your funding need wisely
When we started, our pre-seed angel investor suggested to close an angel round by involving other investors. The more money you attract at the beginning, the longer runway you have to develop the product that you believe in without having to take away your focus from value creation. It turned out without having the credibility of using small investments wisely and build traction with it you won’t be given the opportunity to get funded with hundreds/millions of Dollars. Build up your credibility together with your venture. One step at a time. Read More »
Tags: #ciscochampion, internet of things, IoT
Nowadays, there are billions of devices connected to the Internet, and this has led to some advances in the Electronics and Telecommunication technology developments in recent years which resulted in various kinds of very powerful devices with communication and networking capabilities that have attracted the industries to adopt this technology into their daily business to increase their efficiency. Other than the industrial sector, there are other sectors like assisted living services, public services, etc., which have a big demand for Information and Communication Technology developments. Therefore, there is the need for a new paradigm in M2M communication which enables “Things” connectivity to the Global Internet Network. This paradigm is known by the term IoT.
IoT is the network of physical objects or “Things” embedded with electronics, SW, Sensors and connectivity to enable it to achieve value and service by exchanging data with the manufacturer, operator and/or other connected devices through advanced communication protocols without human operation. The technology of IoT has been evolved according to the environment based on information communication technology and social infrastructure, and we need to know the technological evolution of IoT in the future. Read More »
Tags: #ciscochampion, Cloud Computing, Fog computing, grids, internet of things, IoT, smart, smart grids
With the adoption of overlay networks as the standard deployment for multi-tenant network, Layer2 over Layer3 protocols have been the favorite among network engineers. One of the Layer2 over Layer3 (or Layer2 over UDP) protocols adopted by the industry is VXLAN. Now, as with any other overlay network protocol, its scalability is tied into how well it can handle the Broadcast, Unknown unicast and Multicast (BUM). That is where the evolution of VXLAN control plane comes into play.
The standard does not define a “standard” control plane for VXLAN. There are several drafts describing the use of different control planes. The most commonly use VXLAN control plane is multicast. It is implemented and supported by multiple vendors and it is even natively supported in server OS like the Linux Kernel.
This post tries to summarize the three (3) control planes currently supported by some of the Cisco NX-OS/IOS-XR. My focus is more towards the Nexus 7k, Nexus 9k, Nexus 1k and CSR1000v.
Each control plane may have a series of caveats in their own, but those are not covered by this blog entry. Let’s start with some VXLAN definitions:
(1) VXLAN Tunnel Endpoint (VTEP): Map tenants’ end devices to VXLAN segments. Used to perform VXLAN encapsulation/de-encapsulation.
(2) Virtual Network Identifier (VNI): identify a VXLAN segment. It hast up to 224 IDs theoretically giving us 16,777,216 segments. (Valid VNI values are from 4096 to 16777215). Each segment can transport 802.1q-encapsulated packets, theoretically giving us 212 or 4096 VLANs over a single VNI.
(3) Network Virtualization Endpoint or Network Virtualization Edge (NVE): overlay interface configured in Cisco devices to define a VTEP
VXLAN with Multicast Control Plane
Read More »
Tags: #ciscochampion, Cisco Nexus 9000, CSR1000v, Nexus 1000, Nexus 7000, Nexus 9000, VXLAN
#CiscoChampion Radio is a podcast series by Cisco Champions as technologists. Today we’ll be talking about Collaboration and Cisco Unity Connection with Cisco Technical Marketing Engineers Chris Ward and Chris Barlow.
Listen to the Podcast.
Learn about the Cisco Champions Program HERE.
See a list of all #CiscoChampion Radio podcasts HERE.
Chris Ward, Cisco Technical Marketing Engineer
Chris Barlow, Cisco Technical Marketing Engineer
Cisco Champion Guest Hosts
Michael Aossey, @aossey, Solutions Architect
Erick Berquist, @erickbe, Senior Engineer
Kim Austin (@ciscokima)
What is Cisco Unity Collaboration?
Unity Collaboration and Secure Messaging
Unity Connection and compatibility with existing solutions
Video greeting feature and media capabilities on Unity Connection
Benefits of Unity Connection over other solutions
Cisco native SRSV and Unity Connection
Cisco Unity Collaboration Overview
Data Sheets and Literature
White Paper: MWI Normilization with Centralized CUC
Tags: #CiscoChampionRadio, Cisco collaboration, unity connection
In youth-oriented Silicon Valley, it’s risky to mention this, but I’ve been around for a long time. In fact, in theory I could retire! I already moved to a small town in the Pacific Northwest where the cost of living is low, and I could spend my days hiking in the mountains.
But actually I can’t retire. Why? The networking field is too interesting! In addition, modern networking, with its emphasis on design, applications, policies, and users, focuses on the same concepts that have interested me from the beginning. Not only that, but I firmly believe that with today’s network design tools, we are positioned to build networks that are faster, larger, and even more user-friendly than ever. How could I retire when that’s the case?
In the Beginning
I started my career as a software developer. This was long before agile software development became popular, but nonetheless there was a focus on agility and flexibility. The goal was to develop software that could be used in multiple ways to support a broad range of users. The focus was on user behavior, application modeling, systems analysis, and structured design. Read More »
Tags: #ciscochampion, Cisco APIC, Cisco Application Centric Infrastructure, Cisco SDN, Declarative, Network design