My company ordered two t-1 to the Internet and I plan on multilinking them. When I received the confirmation each circuit had a different order number and public ip's. So my question is can I multilink these two circuits together even though they are two totally separate circuits?
The fact that they are two totally separate circuits does not necessarily tell us whether you can multilink them or not. The fact that each came with separate IP addresses indicates that the provider does not intend (at least at this point) to multilink them - and if the provider does not multilink them then you can not multilink them.
So what you really need to do is to talk to the provider. Tell them that you are interested in the possibility of multilink and ask if they can/will support multilink on these circuits. From your end multilink should be possible but you need to determine what happens at the provider end.
Just to add a line to your answer, infact, the ISP MUST allow before we can do any Multilinking, as the MPPP is done at both the ends, and if the ISP doesn't want Multilinking, then I guess we are out of options.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...