Before the benefits of 5G can be realized, the technology must overcome some obstacles.
Cisco shrinking overall ~2% per quarter (fifth straight down quarter). 10% down in routing, 5% down in switching, 4% down in DC. Increases dividend, investors happy.
Cisco reported $11.6 billion in revenue for Q2 2017 on February 15, 2017, a 2% YoY decrease, but in line with guidance of a 2-4% YoY decline.
Revenue breakout:
Product, $8.49B (down 5.5%); Service, $3.09B (up 4.9%).
By segment:
Switching, $3.31B (down 5%); NGN Routing, $1.82B (down 10%); Collaboration, $1.06B (up 4%); Data Center, $790M (down 4%); Wireless, $632M (up 3%); Security, $528M (up 14%); Service provider video, $241M (down 41%); other, $116M (up 53%
“Cash” of $71.8 billion at the end of Q2 2017, with only $9.6 billion in the US. The introduction of a Corporate Tax Holiday could have huge positive ramifications for Cisco.
The Q3 2017 outlook calls for revenue to decline by 2% or to remain flat YoY.
Data Center
Total product revenue was down 4% and let me walk through each of the product areas. Switching declined 5%, driven by weakness in Campus partially offset by strength in the ACI portfolio, which was up 28%
Cisco ACI is holding Continue reading
Angelos Vassiliou sent me an interesting lengthy email after I published my OSPF Forwarding Address series (part 1, part 2, part 3, part 4). I asked him whether it’s OK to publish his email together with my responses as a blog post and he gracefully agreed, so here it is.
Read more ... If the industry doesn't act, lawyers will.
No snowflake VNFs — just Lego blocks, please.
Routing was down 10% and switching 5%.
I’ve written a fair amount about Open vSwitch (OVS), including some articles on using it with KVM and Libvirt. One thing I haven’t discussed in such environments, though, is the potential challenge of mapping network interfaces in a guest domain to the corresponding OVS interface (for the purposes of troubleshooting, for example). There is no single command that will provide a guest-to-OVS interface map (as far as I know), but this information is easily gathered using a couple commands.
First, we’ll need to gather some information about the interface from the guest domain’s perspective. There are two ways we can do this: from within the guest OS itself, or by interrogating Libvirt.
Inside the guest domain (I’m assuming you’re using a relatively recent Linux distribution), you only need to use standard commands like ip link list
or ip addr list
. The goal is to obtain the MAC address assigned to the particular guest interface. So, for example, if you wanted to get the MAC address for the guest “eth0” interface, you’d run:
ip link list eth0
To isolate only the MAC address from the output of that Continue reading