Go CCIE Go!! - A Cisco Certified Internetwork Expert

hello experts, i was working on some labs with fram realy taks and i came across a task that asks for setting the DE bit. the solution was through MQC but i […]

One of the better resources I used was the knowledgenet video. It was quite good.
On Sun, Nov 30, 2008 at 5:41 AM, dara tomar wrote:
> Yes Indeed, > > 1>Jeff Doyle vol 2 multicasting sections > 2>Developing IP Multicast Networks by Beau Williamson > 3>The Doc-CD multicasting documentation > > In the sequence above […]

Hi Frog,
The normal advice is, if you don’t see it, ask your SE for it. You never know, they may have development releases with the feature. If they receive enough requests it can also affect how they allocate resources to its development. They are after all in the business of keeping their […]

p.s. I should have said we need to set maximum hops to 255 and generate a packet as if it has passed over >224 hops. IPv6 hop limit, like TTL, count down not up.
On Sun, Nov 30, 2008 at 9:15 PM, paul cosgrove wrote:
> Hi Timothy, > > Thanks for the link. […]

Hi Timothy,
Thanks for the link. The paragraph which explains the 224 limit is incorrect in that the Transport Control Field does not exist in IP or IPv6 headers. The IPX TC header field functions like a hop count, and IPX packets with a TC of 16 are dropped, hence the need for a […]

Thanks pradeep… very nice elaboration.
On Mon, Dec 1, 2008 at 1:14 AM, Pradeep wrote:
> Keepalive messages check the health of a link. The keepalive* *timer is > the number of seconds a router waits between sending keepalive messages to a > peer. If no response from the peer is received, the local router retransmits […]

Yes! i have this situation of back-to-back frame-relay configuration …..where i was trying to implement simple point to point frame-relay. and i found this concept of “no keepalives”. Anyways thanks for guiding.
On Mon, Dec 1, 2008 at 1:13 AM, Modular wrote:
> I don’t really understand your problem…. but generally “no keepalives” in > Frame […]

Keepalive messages check the health of a link. The keepalive* *timer is the number of seconds a router waits between sending keepalive messages to a peer. If no response from the peer is received, the local router retransmits the keepalive message up to five times. If no response is received from the peer, the local […]

That’s impressive… i didnt know this… i have found a helpful article on this which i want to share
http://www.cisco.com/en/US/tech/tk713/tk237/technologies_configuration_example09186a0080094a3b.shtml On Mon, Dec 1, 2008 at 1:04 AM, Bogdan Sass wrote:
> khurram noor wrote: > >> Can anyone explains the logic behind inserting “no keepalives” in a frame >> relay interface configuration mode. […]

Can anyone explains the logic behind inserting “no keepalives” in a frame relay interface configuration mode. i have a scenerio in which i have a frame-relay point-point connectivity… but the link does not come up until i assign “no keepalives” under physical interface of both routers along with clock rate on one of the routers.
[…]