I've asked a fair number of questions here, which would only be a
starting point if I were building a solution to this problem -- even
though I don't fully understand the problem yet. The key message I'm
trying to convey is that the first task in developing a solution is
to translate customer wants/perceptions into specific technical
requirements (e.g., SLAs, routing policies, and the like). Selecting
the specific technology is the second task, and selecting platforms
and configuring them follows.
>See my dear this solution to done for a customer and not for the ISP. One
>of the Software development firm (MY friend works there and i want to help
>him out) they have two internet link from different internet service
>provider. earlier they were using 2 router for differnet link but now they
>want to go for only one router (3640).
Why? If they had two, clearly that is more reliable. Is it that the
3640 will have more power than the previous two, which might be a
perfectly good reason.
>What can be done for this. In normal
>condition they use one internet link always to upload their software to
>some web server and another link is used internet browsing. Now when any
>one link goes down how everything will function normally ?
As you have stated the problem., things will NOT function normally if
one link goes down. I might guess that in the event of one failure,
you want all the traffic to move to the other link, but you don't
explicitly say that and assumptions are dangerous.
If both types of traffic are going over the same link, is some sort
of traffic conditioning -- rate limiting, queueing, etc.,
appropriate? What sort of availability and performance do they need
for each services.
What about other services? Is the uploading FTP, HTTP, RPC, or what?
Do telnet, FTP downloads, etc., qualify as web browsing, or is web
browsing limited to HTTP?
> why i am asking
>this is there arevalid ip address which belongs to both the ISP's.
>And any
>one ISP goes down what about routing of that perticular ip address stream.
If the address spaces are much smaller than /24, there may not be a
routing based solution. Any routing solution will require
coordination among the customer and the two ISPs.
It may be appropriate to look at various NAT, tunneling, and DNS
techniques as well. There's just not enough information to know.
> Hope this helps you to give some more clear cut solution.
>
>Regards
>Atul
\
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
