Re: [j-nsp] SRX110H2-VA temperature sitting at 67c

2013-08-23 Thread Graham Brown
Hi Gavin, I have a box sat on my desk and it's running a similar temperature: admin@GB-DESK-TEST-UNIT> show chassis routing-engine Routing Engine status: Temperature 65 degrees C / 149 degrees F This is running 12.1X44-D20.3. HTH, Graham On 24 August 2013 09:46, Gavin Henr

Re: [j-nsp] SRX110H2-VA temperature sitting at 67c

2013-08-23 Thread Michael Dale
Hi Gavin, I have an SRX110H-VA sitting here doing nothing and is running at 57c. One of my customers has one sitting in a closed cupboard with no airflow and it is running at 72c, which is pretty high, but it has been running for a long time now without issue. Thanks, Michael. On 24/08/2013,

[j-nsp] SRX110H2-VA temperature sitting at 67c

2013-08-23 Thread Gavin Henry
Hi all, Just got one of these in for OoB management and noted it's sitting at around 67 Celsius on a lab test bench with lots of space around it in a not really hot room. On latest 12.1X too. Others seeing this? When it goes to the DC I'm sure it will be cooler due to Airton, but all its doing i

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Kevin R. Cullimore
On 8/23/2013 1:04 PM, Doug McIntyre wrote: On Fri, Aug 23, 2013 at 05:38:34PM +0100, Phil Mayers wrote: On 23/08/13 17:14, Michael Loftis wrote: Part of it probably has to do with SNMP. Pre-allocating the count keeps the SNMP index ID's from changing when devices are added/removed. ae0 is alw

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Morgan McLean
Also, if software is smart it updates its SNMP indexes it has on record...I know every custom script I've done checks to make sure its still looking at the right interface, and if not it updates for it or marks the interface as lost. Curious about the line as wellits annoying. Morgan On Fri

[j-nsp] EX-4200 two members virtual chassis problem

2013-08-23 Thread laith zuraiqi
Dears,   I have two ex-4200-24 f running 11.4r8.5 software, connected through two VCP ports, it was connected to mx router by trunk port and the uplink connected to member 0. The customers connected to member 0(master) working fine , but when I add a customer to member 1 ,I cannot access to the MX-

[j-nsp] EX-4200 two members virtual chassis problem

2013-08-23 Thread laith zuraiqi
Dears,   I have two ex-4200-24 f running 11.4r8.5 software, connected through two VCP ports, it was connected to mx router by trunk port and the uplink connected to member 0. The customers connected to member 0(master) working fine , but when I add a customer to member 0 I cannot access to the MX-R

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Michael Loftis
Heh, thats what I get for making an assumption! On Fri, Aug 23, 2013 at 9:38 AM, Phil Mayers wrote: > On 23/08/13 17:14, Michael Loftis wrote: >> >> Part of it probably has to do with SNMP. Pre-allocating the count >> keeps the SNMP index ID's from changing when devices are >> added/removed. ae

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Phil Mayers
On 23/08/13 18:04, Doug McIntyre wrote: But imagine the case, where you start with needing 4 LAGs, so that is what you set. Then you add in 10 SFPs for various things, and then you add in 4 more LAGs, then you remove 4 SFPs for some other project. What do your SNMP indexes look like now? And ho

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Doug McIntyre
On Fri, Aug 23, 2013 at 05:38:34PM +0100, Phil Mayers wrote: > On 23/08/13 17:14, Michael Loftis wrote: > > Part of it probably has to do with SNMP. Pre-allocating the count > > keeps the SNMP index ID's from changing when devices are > > added/removed. ae0 is always index blah. A lot of tools a

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Michael Loftis
Part of it probably has to do with SNMP. Pre-allocating the count keeps the SNMP index ID's from changing when devices are added/removed. ae0 is always index blah. A lot of tools are very dependent upon the SNMP index ID. On Fri, Aug 23, 2013 at 5:30 AM, Phil Mayers wrote: > Just for curiosi

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Phil Mayers
On 23/08/13 17:14, Michael Loftis wrote: Part of it probably has to do with SNMP. Pre-allocating the count keeps the SNMP index ID's from changing when devices are added/removed. ae0 is always index blah. A lot of tools are very dependent upon the SNMP index ID. I don't think so TBH. Having

Re: [j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Saku Ytti
On (2013-08-23 13:30 +0100), Phil Mayers wrote: > Just for curiosity - why is this a "thing" in JunOS? Why doesn't the > platform just let you configure the aeX interfaces and figure out > the "count" itself? I'd love to hear this. I also find it rather strange that we need to configure tunnel P

Re: [j-nsp] L2Circuit VLAN-CCC EX4550

2013-08-23 Thread chip
Try it like the below, terminating them on brocade gear and saw similar issues. You might need to check MTU operation too. set interfaces xe-0/0/1 description customer-3 set interfaces xe-0/0/1 vlan-tagging set interfaces xe-0/0/1 encapsulation vlan-ccc set interfaces xe-0/0/1 mtu 9216 set interf

[j-nsp] Rationale behind "set chassis aggregated-devices ethernet device-count"

2013-08-23 Thread Phil Mayers
Just for curiosity - why is this a "thing" in JunOS? Why doesn't the platform just let you configure the aeX interfaces and figure out the "count" itself? It's such a specific thing to have to do I feel sure there's a reason, but can't for the life of me guess what :o) ___

[j-nsp] L2Circuit VLAN-CCC EX4550

2013-08-23 Thread Giuliano Medalha
People, We have an issue when implementing vlan-CCC in JUNIPER EX4550 switches. When we put the port like the following mode: set interfaces xe-0/0/10 encapsulation vlan-ccc set interfaces xe-0/0/10 vlan-tagging set interfaces xe-0/0/10 unit 600 vlan-id 600 When we close L2Circuit with non-JUNI