SD-WAN: A Disruptive Game-Changer
As with many emerging technologies, there are pros and cons to SD-WAN adoption.
As with many emerging technologies, there are pros and cons to SD-WAN adoption.
The Juniper documentation on log collector is a bit sparse to be honest, and once it is installed, SSHing to it doesn’t seem to produce a configuration menu any more. In order to change its config, there are some scripts, but I had to dig around for them:
[root@LOG-COLLECTOR bin]# ls adhoc.py disableExport.sh logcollectorWatchdog.py selfhealingES.py agentScript.sh elasticDiskAllocation.py logcollectorWatchdog.pyc selfhealingES.pyc agentUtilityScript.sh elasticDiskRollover.sh logcolmon.py startService.sh bashUtils.sh enableExport.sh logcolmon.pyc stopService.sh cleanZipLogs.sh generateReponse.pl lsStatisticsupdate.sh subsequentBootupdate.sh collectSystemLogs.sh getMountLocation.sh monitorPacketDrop.sh support-diagnostics.sh configureMailSetup.sh getRebootDetails.pl mountNfs.sh syslogForwardToggle.sh configureNameServer.sh getSystemInfo networkScript.sh updateEtcHosts.sh configureNode.sh getZipLogs.pl resizeFS.sh updateIndexerip.sh configureNtp.sh initConf.pl resourceMonitoring validateIpAddress.sh configureTimeZone.sh loadFirewal.sh rootWrapper whiteList.sh [root@LOG-COLLECTOR bin]#
They are in this directory:
[root@LOG-COLLECTOR bin]# pwd /opt/jnpr/bin [root@LOG-COLLECTOR bin]#
An important thing to be sure of is that log collector does not have two interfaces – it should have only eth0. If it gets an IP address on eth1, you might find that logging does not work. This is probably because it received a DHCP address on eth1, Continue reading
As discussed in prior Cross-VC NSX/multi-site blogs, Cross-VC NSX allows for NSX logical networking and security across multiple vCenter domains which may also be across multiple sites. The benefits of this capability are immediately clear in terms of workload mobility, resource pooling, central management and application of consistent security policies across vCenter domains/sites, and disaster recovery. More details on these use cases can be found in the prior Cross-VC NSX blogs listed below or in the recently published NSX-V: Multi-site Options and Cross-VC NSX Design Guide. This blog post, focuses on the ease and flexibility in terms of application of Cross-VC NSX for multi-site.
Prior Cross-VC NSX Blogs:
NSX-V: Multi-site Options and Cross-VC NSX Design Guide
Enhanced Disaster Recovery with Cross-VC NSX and SRM
Cross-VC NSX for Multi-site Solutions
In this example, vCenter, the primary NSX Manager, and the Universal Controller Cluster (UCC) is deployed at site 1. A secondary NSX Manager which is registered with the primary NSX Manager is deployed at site 2 along with its corresponding vCenter. For a quick overview on primary NSM Manager, secondary NSX Manager, and the UCC see this prior blog. For more detailed information, see the NSX-V: Multi-site Options and Cross-VC NSX Continue reading
A smart-bulb worm is possible, but Philips at least made it hard to do.
About 350 employees will be laid off.
We collect the top expert content in the infrastructure community and fire it along the priority queue.
Julien Lucek concluded his PCEP and BGP-LS webinar with a lengthy Q&A session addressing all sorts of questions from the audience (to access all videos in this webinar, register here).