Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
Hi all, these codes are basically the same, both are MX80 based devices with a MIC 1x20GE (all mics are commercially called 3D, no difference here) already installed in one of the two available slots. On MX5 (and in the commercial bundle MX80-5) the 20x1G MIC is the only card available to connect the MX to the network, as the on board 10GE ports are software restricted and not configurable. So, the two differences are: 1) the MX5 is a chassis which is phisically grey and you can read MX5 on the front panel, whereas MX80-5-DC-B is a commercial bundle based on a MX80 chassis; the commercial bundle was needed to have a faster go to market time schedule, that's it; of course, MX5 chassis (and MX10 MX40) are exactly an MX80, just the color and the label on the front panel change; 2) the T versions (all the T versions, MX5, 10,40 and also MX80-T) supports Sync-E according with G.8261 / G.8262 standards; 1) is just commercial, whereas 2) is a technical difference. Both models are field upgradable to MX10, MX40 and MX80 using the same licensing scheme. If you need MX5 now, my advice is to go with the bundle as the real MX5 will ship end of this year (11.2R4/11.4R1 time frame). Hope this helps! Magno. On Fri, Nov 18, 2011 at 10:12 PM, Paul Stewart p...@paulstewart.org wrote: There are bundles and then there are base units. The bundles typically include the MIC-3D-20GE-SFP - there were no MIC's that I'm aware of that weren't 3D ... definitely not on the MX80 platform. Yes, MX5 is modular it's physically the same as an MX80 box, just with software based restrictions in place (which unless it's changed are honor system based still) as noted by 4x10G fixed ports and 1x front empty MIC slot restricted .. restricted = not usable without software upgrade. Paul -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Kevin Wormington Sent: Friday, November 18, 2011 3:22 PM To: sth...@nethelp.no Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B I agree the specs look to be the same, the only difference I can see is the MX5 says it includes a MIC-3D-20GE-SFP and the MX80 a 20x1G MIC. Did they make a MIC that wasn't 3D? I'm pretty sure the MX5 is modular as well since it has the open MIC slot that you can get an upgrade license to be able to use. On 11/18/2011 01:37 PM, sth...@nethelp.no wrote: The T version is copper only. The DC version is modular. Certain about this? In my price list (from August), these bundles are listed with exactly the same price. MX80-5G-DC-B: MX80 Promotional 5G Bundle, Includes MX80 Modular DC, spare DC Power supply, 20x1G MIC including L3-ADV license, Queuing, Inline Jflow, Junos WW. (4x10G fixed ports and 1x front empty MIC slot restricted) MX5-T-DC: MX5 DC chassis with timing support - includes dual power supplies, MIC-3D-20GE-SFP, Junos, S-MX80-ADV-R, S-MX80-Q S-ACCT-JFLOW-IN-5G licenses. Power-supply cable to be ordered separately Sure looks to me like the specifications are the same too. Steinar Haug, Nethelp consulting, sth...@nethelp.no On Nov 18, 2011, at 11:06 AM, Kevin Wormington wrote: I'm looking at the above two MX bundles and other than timing support on the MX5 they seem to have the same specs. Is there something that I'm missing? Does anyone on the list know why one might want the MX80-5G-DC-B vs the MX5-T-DC? Thanks Kevin ___ 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 ___ 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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
On 19 November 2011 10:21, magno massimo.magn...@gmail.com wrote: 2) the T versions (all the T versions, MX5, 10,40 and also MX80-T) supports Sync-E according with G.8261 / G.8262 standards; All modular MX80 boxes should do SyncE. But IEEE 1588-2008 (PPT) needs better oscillator and -T denotes this. I think the non-modular models don't support even SyncE without -T model. It really looks like design fault that they needed better oscillator for the modular boxes, I'm pretty sure they planned to support PPT in all modular boxes. Possibly original oscillator was of poorer specs than they expected it to be? Since they're not exactly expensive components, makes no sense to have model for SyncE and model for SyncE+PPT. MPCx and MPCxE difference also should be same, better oscillator for PPT. (and supposedly 256M-512M FIB, i.e. 2M - 4M routes or so). -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
Hello, Hi all, these codes are basically the same, both are MX80 based devices with a MIC 1x20GE (all mics are commercially called 3D, no difference here) already installed in one of the two available slots. On MX5 (and in the commercial bundle MX80-5) the 20x1G MIC is the only card available to connect the MX to the network, as the on board 10GE ports are software restricted and not configurable. That is not true. The ports are configurable and usable. But you need a license to be allowed to use them. The license is just paperwork and you dont need to activate it somewhere. However this policy will change in the future, all MX5/10/40 bundles and line cards are EEPROM coded and a later JunOS will activate these limitations (ask your channel partner about this...). So, the two differences are: 1) the MX5 is a chassis which is phisically grey and you can read MX5 on the front panel, whereas MX80-5-DC-B is a commercial bundle based on a MX80 chassis; the commercial bundle was needed to have a faster go to market time schedule, that's it; of course, MX5 chassis (and MX10 MX40) are exactly an MX80, just the color and the label on the front panel change; 2) the T versions (all the T versions, MX5, 10,40 and also MX80-T) supports Sync-E according with G.8261 / G.8262 standards; No, we have multiple MX5/MX10 boxes and none of them have any visual difference to a real MX80. If they changed this in the last 2 months, then this must be new. 1) is just commercial, whereas 2) is a technical difference. Both models are field upgradable to MX10, MX40 and MX80 using the same licensing scheme. If you need MX5 now, my advice is to go with the bundle as the real MX5 will ship end of this year (11.2R4/11.4R1 time frame). Hope this helps! Magno. On Fri, Nov 18, 2011 at 10:12 PM, Paul Stewart p...@paulstewart.org wrote: There are bundles and then there are base units. The bundles typically include the MIC-3D-20GE-SFP - there were no MIC's that I'm aware of that weren't 3D ... definitely not on the MX80 platform. Yes, MX5 is modular it's physically the same as an MX80 box, just with software based restrictions in place (which unless it's changed are honor system based still) as noted by 4x10G fixed ports and 1x front empty MIC slot restricted .. restricted = not usable without software upgrade. Paul -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Kevin Wormington Sent: Friday, November 18, 2011 3:22 PM To: sth...@nethelp.no Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B I agree the specs look to be the same, the only difference I can see is the MX5 says it includes a MIC-3D-20GE-SFP and the MX80 a 20x1G MIC. Did they make a MIC that wasn't 3D? I'm pretty sure the MX5 is modular as well since it has the open MIC slot that you can get an upgrade license to be able to use. On 11/18/2011 01:37 PM, sth...@nethelp.no wrote: The T version is copper only. The DC version is modular. Certain about this? In my price list (from August), these bundles are listed with exactly the same price. MX80-5G-DC-B: MX80 Promotional 5G Bundle, Includes MX80 Modular DC, spare DC Power supply, 20x1G MIC including L3-ADV license, Queuing, Inline Jflow, Junos WW. (4x10G fixed ports and 1x front empty MIC slot restricted) MX5-T-DC: MX5 DC chassis with timing support - includes dual power supplies, MIC-3D-20GE-SFP, Junos, S-MX80-ADV-R, S-MX80-Q S-ACCT-JFLOW-IN-5G licenses. Power-supply cable to be ordered separately Sure looks to me like the specifications are the same too. Steinar Haug, Nethelp consulting, sth...@nethelp.no On Nov 18, 2011, at 11:06 AM, Kevin Wormington wrote: I'm looking at the above two MX bundles and other than timing support on the MX5 they seem to have the same specs. Is there something that I'm missing? Does anyone on the list know why one might want the MX80-5G-DC-B vs the MX5-T-DC? Thanks Kevin ___ 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 ___ 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 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp signature.asc Description:
Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
Hi Nico, which JunOS are you running? 10.4R7.5 here. Maybe they changed it on later MX5/10/40 bundles or its now beeing enforced on newer JunOS versions (just as i said)... Best regards, Jonas Am Samstag, den 19.11.2011, 18:46 +0100 schrieb Nicolaj Kamensek: Am 19.11.2011 17:52, schrieb Jonas Frey (Probe Networks): Hello, That is not true. The ports are configurable and usable. But you need a license to be allowed to use them. The license is just paperwork and you dont need to activate it somewhere. However this policy will change in the future, all MX5/10/40 bundles and line cards are EEPROM coded and a later JunOS will activate these limitations (ask your channel partner about this...). I beg to differ: I currently have a MX80-5G bundle in the lab which does show the interfaces in the 'show chassis hardware' statement but does not allow the link to come up. Furthermore, the MIC-3D-20GE-SFP will not come online in the 2nd MIC slot as well. The system is about 8 weeks old. Regards, Nico signature.asc Description: This is a digitally signed message part ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
That is not true. The ports are configurable and usable. But you need a license to be allowed to use them. The license is just paperwork and you dont need to activate it somewhere. However this policy will change in the future, all MX5/10/40 bundles and line cards are EEPROM coded and a later JunOS will activate these limitations (ask your channel partner about this...). Looks like this is the difference between the bundles and the gray boxes like MX80-5G vs MX5 and so on. For bundles (which are about to leave the price-list till the end of the year) the port restrictions are honor-based, and it looks like (of course, there is no official approval) this is going to be kept on. For MX5/10/40 Juniper is promising to enforce it in 11.4/12.1 or something, I forgot. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B
Quote: That is not true. The ports are configurable and usable. But you need a license to be allowed to use them. The license is just paperwork and you dont need to activate it somewhere. However this policy will change in the future, all MX5/10/40 bundles and line cards are EEPROM coded and a later JunOS will activate these limitations (ask your channel partner about this...). Magno: True for today Junos, but as Juniper has the rights to lock these ports it is not safe to use them for production. Of course, today all the licenses (but the Subscriber management) are honor based but this will change in the future for sure, so my advice is not to rely too much on this approach because as soon as you upgrade the box to a future release you may lose these ports. The license enforcer software is already in Junos, just not used today. Quote: 'No, we have multiple MX5/MX10 boxes and none of them have any visual difference to a real MX80. If they changed this in the last 2 months, then this must be new. Magno: Yes, correct just because you have vanilla MX80s which were sold just using a commercial bundle (basically the ones sold using the part number MX80-5*/MX80-10*/MX80-40*) . MX5/10/40 chassis will ship starting with JUNOS 11.4R1, so end of 2011/beginning of 2012. Of course, as I stated before, there are no practical differences between the current chassis and the new ones. Quote: MPCx and MPCxE difference also should be same, better oscillator for PPT. (and supposedly 256M-512M FIB, i.e. 2M - 4M routes or so). Magno: This is not 100% correct. It's correct about the oscillator, but not about the memory. The only actual benefit coming from the memory upgrade (256 mbytes to 512 mbytes) is about mobile users for the MobileNext platform. Prefixes/nexthops are stored elsewhere; nevertheless the current 2.4M FIB IPv4 prefixes supported today will be increased by new features such as FIB localization, to name just one. Hope this helps. Magno. On Sat, Nov 19, 2011 at 5:52 PM, Jonas Frey (Probe Networks) j...@probe-networks.de wrote: Hello, Hi all, these codes are basically the same, both are MX80 based devices with a MIC 1x20GE (all mics are commercially called 3D, no difference here) already installed in one of the two available slots. On MX5 (and in the commercial bundle MX80-5) the 20x1G MIC is the only card available to connect the MX to the network, as the on board 10GE ports are software restricted and not configurable. That is not true. The ports are configurable and usable. But you need a license to be allowed to use them. The license is just paperwork and you dont need to activate it somewhere. However this policy will change in the future, all MX5/10/40 bundles and line cards are EEPROM coded and a later JunOS will activate these limitations (ask your channel partner about this...). So, the two differences are: 1) the MX5 is a chassis which is phisically grey and you can read MX5 on the front panel, whereas MX80-5-DC-B is a commercial bundle based on a MX80 chassis; the commercial bundle was needed to have a faster go to market time schedule, that's it; of course, MX5 chassis (and MX10 MX40) are exactly an MX80, just the color and the label on the front panel change; 2) the T versions (all the T versions, MX5, 10,40 and also MX80-T) supports Sync-E according with G.8261 / G.8262 standards; No, we have multiple MX5/MX10 boxes and none of them have any visual difference to a real MX80. If they changed this in the last 2 months, then this must be new. 1) is just commercial, whereas 2) is a technical difference. Both models are field upgradable to MX10, MX40 and MX80 using the same licensing scheme. If you need MX5 now, my advice is to go with the bundle as the real MX5 will ship end of this year (11.2R4/11.4R1 time frame). Hope this helps! Magno. On Fri, Nov 18, 2011 at 10:12 PM, Paul Stewart p...@paulstewart.org wrote: There are bundles and then there are base units. The bundles typically include the MIC-3D-20GE-SFP - there were no MIC's that I'm aware of that weren't 3D ... definitely not on the MX80 platform. Yes, MX5 is modular it's physically the same as an MX80 box, just with software based restrictions in place (which unless it's changed are honor system based still) as noted by 4x10G fixed ports and 1x front empty MIC slot restricted .. restricted = not usable without software upgrade. Paul -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Kevin Wormington Sent: Friday, November 18, 2011 3:22 PM To: sth...@nethelp.no Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] MX5-T-DC vs MX80-5G-DC-B I agree the specs look to be the same, the only difference I can see is the MX5 says it includes a MIC-3D-20GE-SFP and the MX80 a 20x1G MIC. Did they make a MIC that
[j-nsp] SRX650 Dual SRE6
People, Does anyone knows if SRX650 box supports dual SRE6 (Services and Routing Engine 6) ? It is possible with JUNOS 11.4 (last version available) to use both routing engines ? Any special configuration to do ... for this both SRE6 to work ? We have tried dual SRE6 ... but what happen is that system do not recognizes second routing engine. The second SRE stays in shutdown mode ... or inactive mode. Can you please give to me some feedback ? Anyone experience sometinh similar ? Thanks a lot, Giuliano ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] SRX650 Dual SRE6
It's been well known that the dual RE design while there is space in the chassis it's not supported in software as of today. I just looked at the release notes and I can't find any reference to dual RE's being supported. Did you expect it to be a feature there? I'm honestly not aware of it being on the roadmap to be supported, then again I haven't seen much of the 12.x roadmap as of late. I would talk to your SE about this if it's something you need to have to find out if/when it will be supported and under what circumstances. Good luck, -Tim Eberhard On Sat, Nov 19, 2011 at 8:26 PM, GIULIANO (WZTECH) giuli...@wztech.com.br wrote: People, Does anyone knows if SRX650 box supports dual SRE6 (Services and Routing Engine 6) ? It is possible with JUNOS 11.4 (last version available) to use both routing engines ? Any special configuration to do ... for this both SRE6 to work ? We have tried dual SRE6 ... but what happen is that system do not recognizes second routing engine. The second SRE stays in shutdown mode ... or inactive mode. Can you please give to me some feedback ? Anyone experience sometinh similar ? Thanks a lot, Giuliano ___ 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
