we have a block of IP's 10-15 of them, some being nated for internal services as usual, and it's all working good - so;
.132 webmail / autodiscover
all services are working, but... for some reason, more often then I'd like lately .132 goes into la la land and I cant ping from the outside, pinging is enable for the purpose of checking that this interface (ip) is up...when I cant ping i know users will call cause emails cant be sent from mobile devices, or received.
so i usually loggin with vpn, and i have to generate traffic internal out and eventually .132 comes up. Other then a tracker which i have setup to ping out to keep connection live, which is not working properly - any other ideas? When services are in use .132 has no issue, usually in the evening when less traffic.
Are you an experienced network professional?
If yes, we'd like to understand how we can better organize network management activities in a way that makes sense to you. Your response will help Cisco improve a product feature that could benefit you.&nb...
Hello I am getting this following error and get ACTV, XPS and S-PWR LEDs amber then suddenly all LEDs are off: Booting...(use DDR clock 667 MHz)*** Coprocessor Unusable Exception ***PC = 0x00000000 00000000SP = 0x00000000 00000000Cause Reg...
A fabric site is a portion of the fabric which has its own set of control plane nodes, border nodes, and edge nodes.
Key characteristics of a single fabric site are:
A given IP subnet is part of a single fabric site (except when VN anchoring...