So, we're upgrading an application environment from its simple little single Unix box to a three-headed clustered servers (still Unix) which share the application's shared file system via a SAN.
At present, I have a variety of file events watching for periodic file drops which instantiate job insertions based on those files.
How best do I go about making sure I can still see files if one of the heads of the application server dies? File events & agent lists don't go together (I'm currently running 5.3.1, I should point out)... so, do I have to set up another two file events per file? (Yuck.) Or is there another, simpler answer?
(In the windows world), a cluster responds to the same machine name no matter which head is active. So \\cluster01\filename1 will reach the file, no matter which head is active. Is this not the behavior in the UNIX world?
cluster01 which was made up of server01 and server02. The Windows Cluster service would point the cluster01 name to the active node so the file events would just use the cluster01 name in the share.
Cisco launched their solution for hybrid cloud solution for the Microsoft Azure public cloud back in September of 2017. Since that time, Cisco has enjoyed great success with installations around the world from Poland to Australia and many points in ...
NoticeThis is not an official guide, just something I've been testing to help during those "difficult" situations. All works here are my own!GoalsThere are some situations where we need to load an image onto a Nexus switch (or other network devices ...
I was playing a little with some show commands on ACI and i found that on leaves there are VXLAN tunnels also towards the APIC (10.0.0.1 in the figure); i was wondering why there should be these tunnels? APIC is using VLAN 3967 as infrastructure VLAN, and...
Hello, We are a meetings and events company and we have decided to hold virtual meetings. The set up is that we usually invite 100 - 200 participants with 2 - 3 speakers. I would like to know how to extract WebEx analytics; ie participant...