IPv6 prefix assignment BCOP published as RIPE-690
We’re pleased to announce that after a year of intensive work by IPv6 experts around the world, supported by the Deploy360 team, the RIPE community has reached consensus on the Best Current Operational Practices (BCOP) for IPv6 prefix assignment for end-users – persistent vs non persistent and what size to choose. These were officially published as RIPE-690 this week.
RIPE-690 outlines best current operational practices for the assignment of IPv6 prefixes (i.e. a block of IPv6 addresses) for end-users, as making wrong choices when designing an IPv6 network will eventually have negative implications for deployment and require further effort such as renumbering when the network is already in operation. In particular, assigning IPv6 prefixes longer than /56 to residential customers is strong discouraged, with /48 recommended for business customers. This will allow plenty of space for future expansion and sub-netting without the need for renumbering, whilst persistent prefixes (i.e. static) should be highly preferred for simplicity, stability and cost reasons.
The target audience of RIPE-690 is technical staff working in ISPs and other network operators who currently provide or intend to provide IPv6 services to residential or business end-users. Up until now, there have been no clear Continue reading
Object Storage: 8 Things to Know
Learn about the fast-growing technology that's reshaping enterprise storage.
Object Storage: 8 Things to Know
Learn about the fast-growing technology that's reshaping enterprise storage.
Must Read: Network Engineer Persona
David Gee (whom I finally met in person during recent ipSpace.net Summit) published a fantastic series of articles on what someone bringing together networking, development and automation should know and do.
Read more ...ForeScout Plans for $101 Million IPO
The company will sell 4.8 million shares priced between $20 and $22 per share later this month.
Cheap Stuff is not Cheap
I have often fallen for the temptation of buying cheap instead of buying quality. This might be a saw, a drill, a lawnmower or just about anything imaginable. When I look at what professionals use I see them buying well-known and commercial grade products. For example, I wouldn’t expect to see my lawn care team buying a consumer lawnmower at Evil Big Box Store. They actually buy expensive commercial grade zero turn models that are roughly eight to ten times the cost of any mower I would consider.
My lawn care professionals mow lawns to make money, so what gives? Some might assume that these commercial grade products simply allow them to do their jobs faster. In nearly all cases, that is only half of the story. These products last much longer and hold up under the extremes of daily use. Their decks are heavy duty and the blades are less susceptible to being bent. The bottom line that these units mow faster AND they last longer. They spend less time in the shop and do the job they were purchased to do.
I find these quality issues with many consumer grade products. They’re basically cheap and disposable. The end result is Continue reading
Security Companies’ Growth Outpaces NASDAQ, S&P 500
SecureWorks, a Dell Technologies brand, saw the most growth at 33 percent.
HCI Provider Virtuozzo Adopts Kubernetes SDS Support
The Kubernetes product joins the company's current support for Docker containers.
Barefoot’s Tofino Chip and P4 Could Replace Load Balancers
The programmable chip costs the same as fixed-function chips.
Arista EOS CloudVision
Fabric Visibility on Arista EOS Central describes how to use industry standard sFlow instrumentation in Arista switches to deliver real-time flow analytics. This article describes the steps needed to integrate flow analytics into CloudVision.
Log into the CloudVision node and run the following cvp_install_fabricview.sh script as root:
#!/bin/shEdit the cvp-api-topology.py script to Continue reading
# Install Fabric View on CloudVision Portal (CVP)
VER=`wget -qO - http://inmon.com/products/sFlow-RT/latest.txt`
wget http://www.inmon.com/products/sFlow-RT/sflow-rt-$VER.noarch.rpm
rpm --nodeps -ivh sflow-rt-$VER.noarch.rpm
/usr/local/sflow-rt/get-app.sh sflow-rt fabric-view
ln -s /cvpi/jdk/bin/java /usr/bin/java
sed -i '/^# http.hostname=/s/^# //' /usr/local/sflow-rt/conf.d/sflow-rt.conf
echo "http.html.redirect=./app/fabric-view/html/" >> /usr/local/sflow-rt/conf.d/sflow-rt.conf
cat <<EOT > /etc/nginx/conf.d/locations/sflow-rt.https.conf
location /sflow-rt/ {
auth_request /aeris/auth;
proxy_buffering off;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Prefix /sflow-rt/;
proxy_set_header Host \$host;
proxy_pass http://localhost:8008/;
proxy_redirect ~^http://[^/]+(/.+)\$ /sflow-rt\$1;
}
EOT
systemctl restart nginx.service
firewall-cmd --zone public --add-port=6343/udp --permanent
firewall-cmd --reload
systemctl enable sflow-rt.service
systemctl start sflow-rt.service
wget http://www.inmon.com/products/sFlow-RT/cvp-eapi-topology.py
chmod +x cvp-eapi-topology.py
echo "configure and run cvp-eapi-topology.py"
Docker Capitulates to Customer Demand, Adds Kubernetes Support
Docker support follows on the heels of Mesosphere adoption of Kubernetes.
Real world use cases for NSX and Pivotal Cloud Foundry
Pivotal Cloud Foundry (PCF) is the leading PaaS solution for enterprise customers today, providing a fast way to convert their ideas from conception to production. This is achieved by providing a platform to run their code in any cloud and any language taking care of all the infrastructure “stuff” for them.
From building the container image, compiling it with the required runtime , deploying it in a highly available mode and connecting it to the required services, PCF allows dev shops to concentrate on developing their code.
While the platform is providing developers with the most simplified experience conceivable, under the hood there are many moving parts that make that happen and plumbing all these parts can be complex. That’s where customers are really enjoying the power of VMware’s SDDC, and the glue between the PaaS and SDDC layers is NSX, it is the enabler that makes it all work.
In this blog post I detail some of the main uses cases customers have already deployed NSX for PCF on top of vSphere and how PCF and NSX are much better together in the real world.
The use cases customers are deploying with NSX for PCF are varied and ill Continue reading