Re: [j-nsp] FEB/FPC Complexity
http://www.juniper.net/techpubs/software/junos/junos90/swconfig-high-availability/configuring-feb-redundancy-on-the-m120-router.html https://www.juniper.net/techpubs/software/junos/junos90/swconfig-system-basics/configuring-fpc-to-feb-connectivity-on-m120-routers.html --raymondh On Apr 7, 2009, at 12:41 AM, Andrew Jimmy wrote: Thanks for the email, the question is: Is it possible to use two FEBs for two FPC (type 1) while both FEBs are acting active/standby to each other so if one FEB goes offline the other can serve both FPCs. If yes, can some help in configuring this. -Original Message- From: raymondh (NSP) [mailto:raymondh@gmail.com] Sent: Monday, April 06, 2009 9:17 PM To: Andrew Jimmy Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] FEB/FPC Complexity A maximum of two Type 1 FPCs and one Type 2 or Type 3 compact FPC can be mapped per FEB. Do the math. Each FEB can hold up to 20G. To achieve to the N+1 concept, you'll need to do some basic math and FPC selection / PIC (Good to have or need to have / alternative solution). A general concept of the math (related to some other questions). https://puck.nether.net/pipermail/juniper-nsp/2009-February/ 012466.html --raymondh On Apr 6, 2009, at 10:53 PM, Andrew Jimmy wrote: I come to know that M120 can provide N:1 FEB redundancy. As per juniper DOCS, A FEB redundancy group is a named collection of two or more Forwarding Engine Boards (FEBs) that can improve interface availability. You can design your redundant FEB configuration to provide backup on a one-to-one basis, or you can provide one backup for multiple FEBs. Each FEB redundancy group can contain only one primary FEB. Can someone write some text about primary FEB and secondary FEBs, what is the difference? What if you have two FEBs type 1 along with two FPCs type 1, Is it possible to use both FEBs for each FPC 1+1 while both FEBs are acting active/standby to each other so if one FEB goes offline the other can serve both FPCs. If yes, can some help in configuring this. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] FEB/FPC Complexity
Thanks for the email, the question is: Is it possible to use two FEBs for two FPC (type 1) while both FEBs are acting active/standby to each other so if one FEB goes offline the other can serve both FPCs. If yes, can some help in configuring this. -Original Message- From: raymondh (NSP) [mailto:raymondh@gmail.com] Sent: Monday, April 06, 2009 9:17 PM To: Andrew Jimmy Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] FEB/FPC Complexity A maximum of two Type 1 FPCs and one Type 2 or Type 3 compact FPC can be mapped per FEB. Do the math. Each FEB can hold up to 20G. To achieve to the N+1 concept, you'll need to do some basic math and FPC selection / PIC (Good to have or need to have / alternative solution). A general concept of the math (related to some other questions). https://puck.nether.net/pipermail/juniper-nsp/2009-February/012466.html --raymondh On Apr 6, 2009, at 10:53 PM, Andrew Jimmy wrote: > I come to know that M120 can provide N:1 FEB redundancy. > > > > As per juniper DOCS, A FEB redundancy group is a named collection of > two or > more Forwarding Engine Boards (FEBs) that can improve interface > availability. You can design your redundant FEB configuration to > provide > backup on a one-to-one basis, or you can provide one backup for > multiple > FEBs. Each FEB redundancy group can contain only one primary FEB. > > > > Can someone write some text about primary FEB and secondary FEBs, > what is > the difference? What if you have two FEBs type 1 along with two > FPCs type > 1, Is it possible to use both FEBs for each FPC 1+1 while both FEBs > are > acting active/standby to each other so if one FEB goes offline the > other can > serve both FPCs. If yes, can some help in configuring this. > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] FEB/FPC Complexity
A maximum of two Type 1 FPCs and one Type 2 or Type 3 compact FPC can be mapped per FEB. Do the math. Each FEB can hold up to 20G. To achieve to the N+1 concept, you'll need to do some basic math and FPC selection / PIC (Good to have or need to have / alternative solution). A general concept of the math (related to some other questions). https://puck.nether.net/pipermail/juniper-nsp/2009-February/012466.html --raymondh On Apr 6, 2009, at 10:53 PM, Andrew Jimmy wrote: I come to know that M120 can provide N:1 FEB redundancy. As per juniper DOCS, A FEB redundancy group is a named collection of two or more Forwarding Engine Boards (FEBs) that can improve interface availability. You can design your redundant FEB configuration to provide backup on a one-to-one basis, or you can provide one backup for multiple FEBs. Each FEB redundancy group can contain only one primary FEB. Can someone write some text about primary FEB and secondary FEBs, what is the difference? What if you have two FEBs type 1 along with two FPCs type 1, Is it possible to use both FEBs for each FPC 1+1 while both FEBs are acting active/standby to each other so if one FEB goes offline the other can serve both FPCs. If yes, can some help in configuring this. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] FEB/FPC Complexity
I come to know that M120 can provide N:1 FEB redundancy. As per juniper DOCS, A FEB redundancy group is a named collection of two or more Forwarding Engine Boards (FEBs) that can improve interface availability. You can design your redundant FEB configuration to provide backup on a one-to-one basis, or you can provide one backup for multiple FEBs. Each FEB redundancy group can contain only one primary FEB. Can someone write some text about primary FEB and secondary FEBs, what is the difference? What if you have two FEBs type 1 along with two FPCs type 1, Is it possible to use both FEBs for each FPC 1+1 while both FEBs are acting active/standby to each other so if one FEB goes offline the other can serve both FPCs. If yes, can some help in configuring this. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
