[cisco-voip] CCM 4.2(3) - Disable RIP
Duy Nguyen
ccieid1ot at gmail.com
Tue Apr 7 13:58:29 EDT 2009
If your subscriber has a default gateway then there shouldn't be any
problems disabling the Routing and Remote Access service. You should also
check on the that service dependencies and determine what's needed.
On Tue, Apr 7, 2009 at 12:10 PM, Justin Kennedy <jkennedy at sofs.cc> wrote:
> Jason,
>
> I can only assume that Routing and Remote Access was enabled by my lead
> that’s a Windows guy so that we can use MS terminal services, but I’m not
> certain. I do have a VNC backdoor if this service is removed. I have to ask
> this question since it’s a production system.
>
>
>
> What other services are removed if Routing and Remote Access is deleted?
> Any other possible applications affected? Will IP routing still work, IE
> everything goes to the default GW.
>
>
>
> I apologize for the questions..they’re out of ignorance.
>
>
>
> [image: cid:image001.jpg at 01C95E92.243D8EE0]
>
>
>
> Justin Kennedy
>
> Stallion Oilfield Services
>
> StaRComm VSAT Administrator
>
> Cell: 432-638-6876
>
> Office: 432-687-9420
>
> email: jkennedy at sofs.cc
>
>
>
> *From:* Jason Aarons (US) [mailto:jason.aarons at us.didata.com]
> *Sent:* Tuesday, April 07, 2009 11:08 AM
> *To:* Justin Kennedy; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] CCM 4.2(3) - Disable RIP
>
>
>
> It’s not enabled by default, funny to hear someone turned it on. Guess
> they wanted an Intelligent end host….used to see this before the days of
> HSRP/VRRP/GLBP. Once saw a trading floor Unix server with 8 NICs running
> RIP, connected to each subnet for High Availability.
>
>
>
> You should remove Routing and Remote Access.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Justin Kennedy
> *Sent:* Tuesday, April 07, 2009 11:50 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] CCM 4.2(3) - Disable RIP
>
>
>
> Has anyone been able to disable RIP on a 4.2 call manager?
>
>
>
> I am by no means a Windows guy, more experience with Linux. Looking for the
> “RIP Listener” process has been futile, as it looks like Cisco has not used
> a canned MS RIP implementation.
>
>
>
> I have a 4.2(3) subscriber connected to a satellite network that uses RIPv2
> to advertise routes to an upstream router. We need to keep RIP enabled on
> both the satellite hub and the upstream router. The rip updates are causing
> the subscriber at the HUB to lose IP connectivity to the publisher when our
> WAN link bounces. If flush the route table at the subscriber the problem is
> resolved for a few months – until the WAN link bounces.
>
>
>
>
>
>
>
> [image: cid:image001.jpg at 01C95E92.243D8EE0]
>
>
>
> Justin Kennedy
>
> Stallion Oilfield Services
>
> StaRComm VSAT Administrator
>
> Cell: 432-638-6876
>
> Office: 432-687-9420
>
> email: jkennedy at sofs.cc
>
>
> ------------------------------
>
> *Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you. *
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090407/6402c27f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 5384 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090407/6402c27f/attachment.jpe>
More information about the cisco-voip
mailing list