Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Within my organization, we have a TWTC fiber ring that has roughly 7 nodes comprising the ring. We have been experiencing EIGRP syslog traps on various nodes that comprise the ring sporatically. We have also reached out to TWTC, for we thought that...
I have found that in our GRE DSL environment, client workstations cannot perform a ping or a traceroute from their dos prompts to internal Domain controller servers going over a GRE tunnel. The resources are availabe to them, however they cannot run...
We have found that when a client running the Cisco VPN client makes a connection to the VPN Concentrator they connect up fine. When they connect up to the new ASA device, the connection runs slow. We are thinking that this could be realted to MTU. ...
We have run into a strange problem that we are trying to get answers on. We have a WAE box setup in one of our locations, and when we try to ping hosts in the same private subnet from the WAE box, certain IP's will ping but not others. All the host...
We have a L2 interface that sits in the respective VLANID of 250, and then we also have a L3 SVI assigned the IP range of choice.The capacity of SONET serivce is Gigabit Ethernet on each of the nodes entering into the ring.
These neighbor changes have been going on for quite some time on the ring, but they have become much more frequent since we brought on (3) additional nodes to the ring roughly a few weeks ago. Primarily we get holding time has expired messages most...
Hi In answer to you questions:1. We are using a SONET fiber ring 2. Routing through the ring internally is by the use of EIGRP. All EIGRP members that comprise the ring are on the same AS#. The local IP subnet is the same for each of the nodes co...
Rick,I have confirmed that other end stations in the same Service Center where the GRE tunnel is implemented all have the same problem. On the traceroute the path goes to the peer address of the other end of the tunnel, that being the host VPN router...
