One of the latest designs we have been working on at IP ArchiTechs is using eBGP and an OSPF transit fabric to provide traffic engineering and load balancing. If you missed this presentation at the 2017 MikroTik User Meeting in Denver, CO, here are the slides:
WISP-Design-Using-eBGP-and-OSPF-TF-traffic-engineering-MUM-2017_KevinMyers-4-by-3
One of the latest designs we have been working on at IP ArchiTechs is using eBGP and an OSPF transit fabric to provide traffic engineering and load balancing. If you missed this presentation at the 2017 MikroTik User Meeting in Denver, CO, here are the slides:
WISP-Design-Using-eBGP-and-OSPF-TF-traffic-engineering-MUM-2017_KevinMyers-4-by-3
Interference
Interference will exist if there are other transmitters on the same channel or adjacent channels. This will lead to loss of frames and the frames will then have to be retransmitted, using up air time. Interference can be caused by micro waves, DECT phones and other devices depending on the band used.
Co-Channel Interference
Co-Channel Interference occurs when two or more transmitters use the same channel. The signals completely overlap and the whole 20 or 22 MHz channel bandwidth is affected. This is only a problem if they transmit simultaneously though. However they will contend for the same airtime and a channel can become very congested. When two signals interfere, it causes data corruption, rentransmitting of frames and that in turn uses up even more airtime.
It is common practice to only place a transmitter on a specific channel where received signals are much weaker. A margin of 19 dB is recommended. The margin depends on the coding and modulation scheme. BPSK may need less than 10 db but 64-QAM will require 19 dB. More advanced modulation such as 256-QAM may require between 31 to 50 dB.
Neighboring Channel Interference
In the 2.4 GHz band neighboring Continue reading
The target was simple, we have an internal cloud datacenter at work that provides users and customers both virtual machines and physical machines. Each machine has to network interface cards (NICs), one is in control of the user/customer using SDN layer, the secondary NIC is for our support to monitor and help troubleshoot these machines when needed. This second NIC will be our target today. In the past we used per-user or per-customer firewall separations that was configuration intensive nightmare, but was reliable. However since we learned private VLANs are now supported by vmWares Distributed vSwitch (dvSwitch), we immediately tried to make it cooperate with private VLANs on physical switches. And since it worked like a charm, let me share with you a quick lab example. But theory first!
Fortunately Private VLANs arrived for most major vendors and promissed the ability to have one giant subnet and separate every host from each other on L2 using some basic principle of declaring ports as either promiscuous (can talk to any other port type), community (can talk to ports Continue reading
The post Worth Reading: A few secrets of successful learning appeared first on rule 11 reader.
The Packet Pushers 7th anniversary Weekly Show delves into the market impacts of SD-WAN, whats up with white box & thoughts on net neutrality. The post Show 341: The Packet Pushers’ 7th Anniversary appeared first on Packet Pushers.
Where do you get the most enjoyment from your conference attendance? Do you like going to sessions and learning about new things? Do you enjoy more of the social aspect of meeting friends and networking with your peers? Maybe it’s something else entirely?
When you look at shows like Cisco Live, VMworld, or Interop ITX, there’s a lot going on. There are diverse education tracks attended by thousands of people. You could go to Interop and bounce from a big data session into a security session, followed by a cloud panel. You could attend Cisco Live and never talk about networking. You could go to VMworld and only talk about networking. There are lots of opportunities to talk about a variety of things.
But these conferences are huge. Cisco and VMware both take up the entire Mandalay Bay Convention Center in Las Vegas. When in San Francisco, both of these events dwarf the Moscone Center and have to spread out into the surrounding hotels. That means it’s easy to get lost or be overlooked. I’ve been to Cisco Live before and never bumped into people I know from my area that said they Continue reading
Red Hat acquires cloud-native tool provider; Ericsson demonstrates 5G network slicing.
CEO Orion Hindawi says bullying reports are untrue.
Nexius will target telecom operators trying to tackle webscale plans.
While at Dell EMC World 2017 I had a very interesting chat with Jason Shepherd, Dell EMC’s Director of IoT Strategy & Partnerships. To be clear, I’m not an expert on the Internet of Things (IOT), and our discussion was a useful reminder how much difference perspective makes when evaluating a technology.
When I think about IOT the first thing that comes to mind — naturally enough — are the items most applicable to me, like a smart thermostat, smart door locks, smart light bulbs, and so forth. I work in an enterprise, so I also think about building management in the enterprise, to include things like smart lighting, HVAC, presence sensors, temperature monitoring and more. Both of these environments are ripe for IOT functionality, and are the ones that most of us are likely to encounter on a daily basis.
However, it’s probably obvious that there are many more use cases for IOT devices, including for example:
Security needs to be elastic enough to scale with the cloud infrastructure itself.