[j-nsp] NAT Redundancy on Juniper routers
Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] NAT Redundancy on Juniper routers
Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] NAT Redundancy on Juniper routers
Hi Alex, Thanks for the response. So there is nothing i can do at this moment :( Regards, Gokhan On Mon, Jan 10, 2011 at 1:43 PM, Alex alex.arsen...@gmail.com wrote: Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] NAT Redundancy on Juniper routers
Actually on a second thought I reckon You might be able to achieve physical-box NAT redundancy using static NAT and IP-ALG but: 1/ it is not scalable (static NAT is 1:1) 2/ I never tried this myself :-) Where the port translation is involved the sequence of events is as I described below. Rgds Alex - Original Message - From: Gökhan Gümüs To: Alex Cc: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:46 PM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Hi Alex, Thanks for the response. So there is nothing i can do at this moment :( Regards, Gokhan On Mon, Jan 10, 2011 at 1:43 PM, Alex alex.arsen...@gmail.com wrote: Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] NAT Redundancy on Juniper routers
Actually i am doing Static-Nat 1:1 :( Rgds, Gokhan On Mon, Jan 10, 2011 at 1:55 PM, Alex alex.arsen...@gmail.com wrote: Actually on a second thought I reckon You might be able to achieve physical-box NAT redundancy using static NAT and IP-ALG but: 1/ it is not scalable (static NAT is 1:1) 2/ I never tried this myself :-) Where the port translation is involved the sequence of events is as I described below. Rgds Alex - Original Message - *From:* Gökhan Gümüş ggu...@gmail.com *To:* Alex alex.arsen...@gmail.com *Cc:* juniper-nsp@puck.nether.net *Sent:* Monday, January 10, 2011 12:46 PM *Subject:* Re: [j-nsp] NAT Redundancy on Juniper routers Hi Alex, Thanks for the response. So there is nothing i can do at this moment :( Regards, Gokhan On Mon, Jan 10, 2011 at 1:43 PM, Alex alex.arsen...@gmail.com wrote: Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] NAT Redundancy on Juniper routers
Then you are in a better position than I thought :-) Just change your NAT rule(s) to include match on junos-ip ALG which skips L4 checks like TCP 3WHS being complete, and test. Let us know the test results please. Rgds Alex - Original Message - From: Gökhan Gümüş To: Alex Cc: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 1:01 PM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Actually i am doing Static-Nat 1:1 :( Rgds, Gokhan On Mon, Jan 10, 2011 at 1:55 PM, Alex alex.arsen...@gmail.com wrote: Actually on a second thought I reckon You might be able to achieve physical-box NAT redundancy using static NAT and IP-ALG but: 1/ it is not scalable (static NAT is 1:1) 2/ I never tried this myself :-) Where the port translation is involved the sequence of events is as I described below. Rgds Alex - Original Message - From: Gökhan Gümüş To: Alex Cc: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:46 PM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Hi Alex, Thanks for the response. So there is nothing i can do at this moment :( Regards, Gokhan On Mon, Jan 10, 2011 at 1:43 PM, Alex alex.arsen...@gmail.com wrote: Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] NAT Redundancy on Juniper routers
Keep in mind that if you haven't already done so, you will need to have both an 'inside' and 'outside' rule for your NAT translation since the junos-ip ALG is unidirectional. From: Alex alex.arsen...@gmail.com To: Gökhan Gümüş ggu...@gmail.com Cc: juniper-nsp@puck.nether.net Sent: Mon, January 10, 2011 7:18:25 AM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Then you are in a better position than I thought :-) Just change your NAT rule(s) to include match on junos-ip ALG which skips L4 checks like TCP 3WHS being complete, and test. Let us know the test results please. Rgds Alex - Original Message - From: Gökhan Gümüş To: Alex Cc: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 1:01 PM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Actually i am doing Static-Nat 1:1 :( Rgds, Gokhan On Mon, Jan 10, 2011 at 1:55 PM, Alex alex.arsen...@gmail.com wrote: Actually on a second thought I reckon You might be able to achieve physical-box NAT redundancy using static NAT and IP-ALG but: 1/ it is not scalable (static NAT is 1:1) 2/ I never tried this myself :-) Where the port translation is involved the sequence of events is as I described below. Rgds Alex - Original Message - From: Gökhan Gümüş To: Alex Cc: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:46 PM Subject: Re: [j-nsp] NAT Redundancy on Juniper routers Hi Alex, Thanks for the response. So there is nothing i can do at this moment :( Regards, Gokhan On Mon, Jan 10, 2011 at 1:43 PM, Alex alex.arsen...@gmail.com wrote: Hello Gokhan Gumus, AFAIK this is not possible at the moment since flows are not shared between MSDPCs even inside same MX box let alone different physical boxes. So if R1 goes down the: 1/ TCP flows need to reestablish starting from 3-way handshake 2/ UDP flows with ALG need to reestablish starting from scratch (every ALG has different procedures) 3/ non-ALG UDP flows _can_ continue as if nothing happened depending on protocol, e.g. p2p UDP flows will resume from last xferred piece 4/ ICMP flows continue as if nothing happened If you need physical-box-redundant NAT I'd suggest to use SRX cluster. HTH Rgds Alex - Original Message - From: Gökhan Gümüs ggu...@gmail.com To: juniper-nsp@puck.nether.net Sent: Monday, January 10, 2011 12:15 PM Subject: [j-nsp] NAT Redundancy on Juniper routers Hi all, I am trying to achieve redundancy on Juniper routers while performing NAT. I have two Juniper MX960 router on the backbone with VRRP setup.I am configuring NAT on R1 successfull.Same NAT rules are existing on the other router but on R2,static route which is pointing sp interface is deactivated.Is there anyway to achieve automatic failover capability on NAT?In other words if something happened on R1, can R2 handle all NAT process without doing anything? Kind regards, Gokhan Gumus ___ 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] IPv6 for PPP customers on ERX310
Amos Rosenboim a...@oasis-tech.net writes: ipv6 nd prefix-advertisement 2a02:ed0:1002:1::/64 3600 3000 autoconfig You may want to add onlink here Bjørn ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] SNMP polling issue MX
It looks like there were possibly multiple mib2d process bugs. In our
case, restarting mib2d did not always resolve the issue.
The good news is that it does look like 10.2R3 fixes the mib2d issues we
were experiencing. We've been running 10.2R3 (or a derivative) for
several weeks and SNMP appears to be stable.
Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187
On Sunday, Richard said:
On Sun, Jan 09, 2011 at 04:14:04PM +0300, Tarique A. Nalkhande - BMC wrote:
All,
Even we faced a similar problem on our MX's running 10.2R3. Further
findings revealed memory leak bug for mib2d process.. restarting mib2d
fixed it.
Juniper is probably tracking it through some internal PR, the
committed release is 10.2R3 which doesn't look likely.
Hrmm supposedly the mib2d memory leak is fixed was 10.2R3, but we never
actually tested it, we just skipped straight ahead to 10.3R2 on new
deployments (as there were many other SNMP bugs still not fixed in 10.2
at the time). A quick and dirty workaround for the memory leak issue is
to periodically restart the mib2d process, which you can do with an
event script like so:
event-options {
generate-event {
/* Adjust ttimer as necessary based on memory consumption */
restart-mib2d time-interval 604800;
}
policy restart-mib2d {
events restart-mib2d;
/* Adjust this too, to something slightly less than above */
within 60 {
not events restart-mib2d;
}
then {
event-script restart-mib2d;
}
}
}
/var/db/scripts/op/restart-mib2d.slax:
version 1.0;
ns junos = http://xml.juniper.net/junos/*/junos;;
ns xnm = http://xml.juniper.net/xnm/1.1/xnm;;
ns jcs = http://xml.juniper.net/junos/commit-scripts/1.0;;
import ../import/junos.xsl;
match / {
op-script-results {
var $restart-mib2d = {
command restart mib-process gracefully;
}
var $result = jcs:invoke($restart-mib2d);
}
}
--
Richard A Steenbergen r...@e-gerbil.net http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] EX4200 Problem - Bad Switch?
Hey folks
Ran across a weird issue today on a new EX4200-48T switch. Switch boots up
and during so I see this (sorry for the length of the post):
Trying to mount root from ufs:/dev/da0s1a
Attaching /packages/jbase via /dev/mdctl...
Mounted jbase package on /dev/md0...
Verified manifest signed by PackageProduction_10_0_0
Verified jboot signed by PackageProduction_10_0_0
Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jcrypto-ex-10.0R4.7 not present.
/packages/jdocs-ex-10.0R4.7 not present.
Mounted jkernel-ex package on /dev/md1...
Verified manifest signed by PackageProduction_10_0_0
Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jpfe-ex42x package on /dev/md2...
Verified manifest signed by PackageProduction_10_0_0
Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jroute-ex package on /dev/md3...
Verified manifest signed by PackageProduction_10_0_0
Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jswitch-ex-10.0R4.7 not present.
Mounted jweb-ex package on /dev/md4...
Verified manifest signed by PackageProduction_10_0_0
Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0
Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post..
Automatic reboot in progress...
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
Creating initial configuration...mgd: error: Couldn't open lib
/usr/lib/dd//libjcrypto-dd.so: Cannot open /usr/lib/dd//libjcrypto-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so: Cannot
open /usr/lib/dd//libjcrypto_junos-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open
/usr/lib/dd//libjdocs-dd.so
/config/juniper.conf:294:(8) syntax error at 'rstp'
[edit protocols]
'rstp;'
syntax error
/config/juniper.conf:297:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:300:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:304:(1) error recovery ignores input until this point
at '}'
[edit]
'}'
error recovery ignores input until this point
[edit system services ssh]
'ssh'
warning: daemon binary /usr/sbin/sshd not found
mgd: commit complete
Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: OK: extracted home directories.
.
Doing initial network setup:
.
Initial interface configuration:
additional daemons:.
Additional routing options:kern.module_path: /boot//kernel;/bootLoading the
NETPFE ethernet module
/modules - /booLoading the EX-series platform NETPFE module
t//kernel;/boot/modules;/modules
grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 - 1
grat_arp_delay=${grat_arp_delay}: net.link.ether.inet.grat_arp_delay: 0 - 0
kld netpfe drv: ifpfed_ethkld platform: ex_ifpfe if_vcpkern.module_path:
/boot//kernel;/boot/modules;/modules -
/boot//kernel;/boot/modules;/modules;/modules/peertype
kld peertype: peertype_hcm peertype_pfem peertype_sfi peertype_slavere.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
ldconfig: warning: /opt/lib: No such file or directory
starting standard daemons: cron.
Local package initialization:.
kern.securelevel: -1 - 1
starting local daemons:.
Thu Oct 14 06:24:18 UTC 2010
Amnesiac (ttyu0)
So I thought that perhaps the JunOS install is corrupt and rebooted with my
USB drive connected. Ran through the installation and it wont complete:
loader install file:///jinstall-ex-4200-10.0R4.7-domestic-signed.tgz
Package /jinstall-ex-4200-10.0R4.7-domestic-signed.tgz is signed...
/kernel data=0x4efa0c+0x51a94 syms=[0x4+0x4e100+0x4+0x707d3]
Kernel entry at 0xa0e0 ...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
platform_early_bootinit: EX Series Early Boot Initialization
Copyright (c) 1996-2010, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
JUNOS 10.0R4.7 #0: 2010-08-22 02:45:23 UTC
buil...@ormonth.juniper.net:/volume/build/junos/10.0/release/10.0R4.7/obj-po
Timecounter decrementer frequency 5000 Hz quality 0
cpu0: Freescale e500v2 core revision 2.2
cpu0: HID0 80004080EMCP,TBEN,EN_MAS7_UPDATE
real memory = 1044381696 (996 MB)
Re: [j-nsp] EX4200 Problem - Bad Switch?
It looks like you're missing a few libraries (files) in your install.
Re-install JunOS.
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote:
Hey folks…
Ran across a weird issue today on a new EX4200-48T switch. Switch boots up
and during so I see this (sorry for the length of the post):
Trying to mount root from ufs:/dev/da0s1a
Attaching /packages/jbase via /dev/mdctl...
Mounted jbase package on /dev/md0...
Verified manifest signed by PackageProduction_10_0_0
Verified jboot signed by PackageProduction_10_0_0
Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jcrypto-ex-10.0R4.7 not present.
/packages/jdocs-ex-10.0R4.7 not present.
Mounted jkernel-ex package on /dev/md1...
Verified manifest signed by PackageProduction_10_0_0
Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jpfe-ex42x package on /dev/md2...
Verified manifest signed by PackageProduction_10_0_0
Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jroute-ex package on /dev/md3...
Verified manifest signed by PackageProduction_10_0_0
Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jswitch-ex-10.0R4.7 not present.
Mounted jweb-ex package on /dev/md4...
Verified manifest signed by PackageProduction_10_0_0
Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0
Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post..
Automatic reboot in progress...
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
Creating initial configuration...mgd: error: Couldn't open lib
/usr/lib/dd//libjcrypto-dd.so: Cannot open /usr/lib/dd//libjcrypto-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so: Cannot
open /usr/lib/dd//libjcrypto_junos-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open
/usr/lib/dd//libjdocs-dd.so
/config/juniper.conf:294:(8) syntax error at 'rstp'
[edit protocols]
'rstp;'
syntax error
/config/juniper.conf:297:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:300:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:304:(1) error recovery ignores input until this point
at '}'
[edit]
'}'
error recovery ignores input until this point
[edit system services ssh]
'ssh'
warning: daemon binary /usr/sbin/sshd not found
mgd: commit complete
Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: OK: extracted home directories.
.
Doing initial network setup:
.
Initial interface configuration:
additional daemons:.
Additional routing options:kern.module_path: /boot//kernel;/bootLoading the
NETPFE ethernet module
/modules - /booLoading the EX-series platform NETPFE module
t//kernel;/boot/modules;/modules
grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 - 1
grat_arp_delay=${grat_arp_delay}: net.link.ether.inet.grat_arp_delay: 0 - 0
kld netpfe drv: ifpfed_ethkld platform: ex_ifpfe if_vcpkern.module_path:
/boot//kernel;/boot/modules;/modules -
/boot//kernel;/boot/modules;/modules;/modules/peertype
kld peertype: peertype_hcm peertype_pfem peertype_sfi peertype_slavere.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
ldconfig: warning: /opt/lib: No such file or directory
starting standard daemons: cron.
Local package initialization:.
kern.securelevel: -1 - 1
starting local daemons:.
Thu Oct 14 06:24:18 UTC 2010
Amnesiac (ttyu0)
So I thought that perhaps the JunOS install is corrupt and rebooted with my
USB drive connected. Ran through the installation and it won’t complete:
loader install file:///jinstall-ex-4200-10.0R4.7-domestic-signed.tgz
Package /jinstall-ex-4200-10.0R4.7-domestic-signed.tgz is signed...
/kernel data=0x4efa0c+0x51a94 syms=[0x4+0x4e100+0x4+0x707d3]
Kernel entry at 0xa0e0 ...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
platform_early_bootinit: EX Series Early Boot Initialization
Copyright (c) 1996-2010, Juniper Networks, Inc.
All rights reserved.
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of
Re: [j-nsp] EX4200 Problem - Bad Switch?
Hi Paul, On Tue, Jan 11, 2011 at 7:53 AM, Paul Stewart p...@paulstewart.org wrote: Ran across a weird issue today on a new EX4200-48T switch. Switch boots up and during so I see this (sorry for the length of the post): [...] So I thought that perhaps the JunOS install is corrupt and rebooted with my USB drive connected. Ran through the installation and it won’t complete: [...] Is this a bad switch?? Probably no worse than every other EX4200 out there :-) They're a bit sensitive and emotional. Looks like the file system is corrupted. Re-installing JUNOS should fix it but you've tried that. In some cases when this has happened to us, we've needed to attempt the re-install a couple of times. If you haven't already, try re-installing from the loader prompt again. If/when you get it back online, open a JTAC case and ask for the 'automatic file system mirroring and recovery script'. Cheers, Dale ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 Problem - Bad Switch?
Thank you very much... Yes - tried installing 3 times now just to see if my luck was that bad ;) Paul -Original Message- From: dale.s...@gmail.com [mailto:dale.s...@gmail.com] On Behalf Of Dale Shaw Sent: January-10-11 4:14 PM To: Paul Stewart Cc: juniper-nsp Subject: Re: [j-nsp] EX4200 Problem - Bad Switch? Hi Paul, On Tue, Jan 11, 2011 at 7:53 AM, Paul Stewart p...@paulstewart.org wrote: Ran across a weird issue today on a new EX4200-48T switch. Switch boots up and during so I see this (sorry for the length of the post): [...] So I thought that perhaps the JunOS install is corrupt and rebooted with my USB drive connected. Ran through the installation and it wont complete: [...] Is this a bad switch?? Probably no worse than every other EX4200 out there :-) They're a bit sensitive and emotional. Looks like the file system is corrupted. Re-installing JUNOS should fix it but you've tried that. In some cases when this has happened to us, we've needed to attempt the re-install a couple of times. If you haven't already, try re-installing from the loader prompt again. If/when you get it back online, open a JTAC case and ask for the 'automatic file system mirroring and recovery script'. Cheers, Dale ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] EX4200 Problem - Bad Switch?
Thanks.. this was a brand new out of the box switch. It had been powered up
once successfully and worked fine at that point. Then it was powered down
and brought back up and now problems...
Tried 3 times now to reinstall JunOS and no luck ;(
-Original Message-
From: neth...@gmail.com [mailto:neth...@gmail.com] On Behalf Of Joe Hamelin
Sent: January-10-11 4:07 PM
To: Paul Stewart
Cc: juniper-nsp
Subject: Re: [j-nsp] EX4200 Problem - Bad Switch?
It looks like you're missing a few libraries (files) in your install.
Re-install JunOS.
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote:
Hey folks
Ran across a weird issue today on a new EX4200-48T switch. Switch boots
up
and during so I see this (sorry for the length of the post):
Trying to mount root from ufs:/dev/da0s1a
Attaching /packages/jbase via /dev/mdctl...
Mounted jbase package on /dev/md0...
Verified manifest signed by PackageProduction_10_0_0
Verified jboot signed by PackageProduction_10_0_0
Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jcrypto-ex-10.0R4.7 not present.
/packages/jdocs-ex-10.0R4.7 not present.
Mounted jkernel-ex package on /dev/md1...
Verified manifest signed by PackageProduction_10_0_0
Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jpfe-ex42x package on /dev/md2...
Verified manifest signed by PackageProduction_10_0_0
Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jroute-ex package on /dev/md3...
Verified manifest signed by PackageProduction_10_0_0
Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jswitch-ex-10.0R4.7 not present.
Mounted jweb-ex package on /dev/md4...
Verified manifest signed by PackageProduction_10_0_0
Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0
Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post..
Automatic reboot in progress...
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
Creating initial configuration...mgd: error: Couldn't open lib
/usr/lib/dd//libjcrypto-dd.so: Cannot open
/usr/lib/dd//libjcrypto-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so:
Cannot
open /usr/lib/dd//libjcrypto_junos-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open
/usr/lib/dd//libjdocs-dd.so
/config/juniper.conf:294:(8) syntax error at 'rstp'
[edit protocols]
'rstp;'
syntax error
/config/juniper.conf:297:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:300:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:304:(1) error recovery ignores input until this point
at '}'
[edit]
'}'
error recovery ignores input until this point
[edit system services ssh]
'ssh'
warning: daemon binary /usr/sbin/sshd not found
mgd: commit complete
Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: OK: extracted home directories.
.
Doing initial network setup:
.
Initial interface configuration:
additional daemons:.
Additional routing options:kern.module_path: /boot//kernel;/bootLoading
the
NETPFE ethernet module
/modules - /booLoading the EX-series platform NETPFE module
t//kernel;/boot/modules;/modules
grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 - 1
grat_arp_delay=${grat_arp_delay}: net.link.ether.inet.grat_arp_delay: 0 -
0
kld netpfe drv: ifpfed_ethkld platform: ex_ifpfe if_vcpkern.module_path:
/boot//kernel;/boot/modules;/modules -
/boot//kernel;/boot/modules;/modules;/modules/peertype
kld peertype: peertype_hcm peertype_pfem peertype_sfi peertype_slavere.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
ldconfig: warning: /opt/lib: No such file or directory
starting standard daemons: cron.
Local package initialization:.
kern.securelevel: -1 - 1
starting local daemons:.
Thu Oct 14 06:24:18 UTC 2010
Amnesiac (ttyu0)
So I thought that perhaps the JunOS install is corrupt and rebooted with
my
USB drive connected. Ran through the installation and it wont complete:
loader install file:///jinstall-ex-4200-10.0R4.7-domestic-signed.tgz
Package /jinstall-ex-4200-10.0R4.7-domestic-signed.tgz is signed...
/kernel
Re: [j-nsp] EX4200 Problem - Bad Switch?
Thanks.. going to try a few things and if not we'll RMA it via JTAC Paul -Original Message- From: Bill Blackford [mailto:bblackf...@nwresd.k12.or.us] Sent: January-10-11 5:52 PM To: Paul Stewart; 'Joe Hamelin' Cc: 'juniper-nsp' Subject: RE: [j-nsp] EX4200 Problem - Bad Switch? I was going to suggest looking at the caveats on Juniper's site regarding JUNOS levels and upgrading. IOW, if it shipped with certain 9.x versions you have to incrementally get to 10.x, however, reading further I see you had it successfully booted. I did have a EX3200-24T come back up in factory default once. I had JTAC replace the hardware. Unfortunately, I can't recall the details. After viewing the crash dump and logs, they claimed I issued a factory reset command (which I did not). I told I don't trust this piece of hardware, so they RMA'd it for me. I don't know if this helps, but it may be something to think about. -b -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Paul Stewart Sent: Monday, January 10, 2011 2:37 PM To: 'Joe Hamelin' Cc: 'juniper-nsp' Subject: Re: [j-nsp] EX4200 Problem - Bad Switch? Thanks.. this was a brand new out of the box switch. It had been powered up once successfully and worked fine at that point. Then it was powered down and brought back up and now problems... Tried 3 times now to reinstall JunOS and no luck ;( -Original Message- From: neth...@gmail.com [mailto:neth...@gmail.com] On Behalf Of Joe Hamelin Sent: January-10-11 4:07 PM To: Paul Stewart Cc: juniper-nsp Subject: Re: [j-nsp] EX4200 Problem - Bad Switch? It looks like you're missing a few libraries (files) in your install. Re-install JunOS. -- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote: Hey folks. Ran across a weird issue today on a new EX4200-48T switch. Switch boots up and during so I see this (sorry for the length of the post): Trying to mount root from ufs:/dev/da0s1a Attaching /packages/jbase via /dev/mdctl... Mounted jbase package on /dev/md0... Verified manifest signed by PackageProduction_10_0_0 Verified jboot signed by PackageProduction_10_0_0 Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0 /packages/jcrypto-ex-10.0R4.7 not present. /packages/jdocs-ex-10.0R4.7 not present. Mounted jkernel-ex package on /dev/md1... Verified manifest signed by PackageProduction_10_0_0 Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0 Mounted jpfe-ex42x package on /dev/md2... Verified manifest signed by PackageProduction_10_0_0 Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0 Mounted jroute-ex package on /dev/md3... Verified manifest signed by PackageProduction_10_0_0 Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0 /packages/jswitch-ex-10.0R4.7 not present. Mounted jweb-ex package on /dev/md4... Verified manifest signed by PackageProduction_10_0_0 Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0 Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post.. Automatic reboot in progress... FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation) Creating initial configuration...mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto-dd.so: Cannot open /usr/lib/dd//libjcrypto-dd.so mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so: Cannot open /usr/lib/dd//libjcrypto_junos-dd.so mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open /usr/lib/dd//libjdocs-dd.so /config/juniper.conf:294:(8) syntax error at 'rstp' [edit protocols] 'rstp;' syntax error /config/juniper.conf:297:(5) error recovery ignores input until this point at '}' [edit protocols] '}' error recovery ignores input until this point /config/juniper.conf:300:(5) error recovery ignores input until this point at '}' [edit protocols] '}' error recovery ignores input until this point /config/juniper.conf:304:(1) error recovery ignores input until this point at '}' [edit] '}' error recovery ignores input until this point [edit system services ssh] 'ssh' warning: daemon binary /usr/sbin/sshd not found mgd: commit complete Setting initial options: debugger_on_panic=NO debugger_on_break=NO. Starting optional daemons: OK: extracted home directories. . Doing initial network setup: . Initial interface configuration: additional daemons:. Additional routing
Re: [j-nsp] EX4200 Problem - Bad Switch?
No - never tried that... have to find a doc on how to do it ;)
Thanks for the suggestion
Paul
-Original Message-
From: Maarten van der Hoek [mailto:maar...@vanderhoek.nl]
Sent: January-10-11 5:45 PM
To: 'Paul Stewart'
Cc: 'juniper-nsp'
Subject: RE: [j-nsp] EX4200 Problem - Bad Switch?
Hi Paul,
We had similar issue's with 4200 switches...
The only installation way that helped us was using the TFTP server method!
Using f.e. USB made things even worse ... :(
Did you try TFTP ?
Maarten
-Oorspronkelijk bericht-
Van: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] Namens Paul Stewart
Verzonden: maandag 10 januari 2011 23:37
Aan: 'Joe Hamelin'
CC: 'juniper-nsp'
Onderwerp: Re: [j-nsp] EX4200 Problem - Bad Switch?
Thanks.. this was a brand new out of the box switch. It had been powered up
once successfully and worked fine at that point. Then it was powered down
and brought back up and now problems...
Tried 3 times now to reinstall JunOS and no luck ;(
-Original Message-
From: neth...@gmail.com [mailto:neth...@gmail.com] On Behalf Of Joe Hamelin
Sent: January-10-11 4:07 PM
To: Paul Stewart
Cc: juniper-nsp
Subject: Re: [j-nsp] EX4200 Problem - Bad Switch?
It looks like you're missing a few libraries (files) in your install.
Re-install JunOS.
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote:
Hey folks
Ran across a weird issue today on a new EX4200-48T switch. Switch
boots
up
and during so I see this (sorry for the length of the post):
Trying to mount root from ufs:/dev/da0s1a Attaching /packages/jbase
via /dev/mdctl...
Mounted jbase package on /dev/md0...
Verified manifest signed by PackageProduction_10_0_0 Verified jboot
signed by PackageProduction_10_0_0 Verified jbase-10.0R4.7 signed by
PackageProduction_10_0_0
/packages/jcrypto-ex-10.0R4.7 not present.
/packages/jdocs-ex-10.0R4.7 not present.
Mounted jkernel-ex package on /dev/md1...
Verified manifest signed by PackageProduction_10_0_0 Verified
jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0 Mounted
jpfe-ex42x package on /dev/md2...
Verified manifest signed by PackageProduction_10_0_0 Verified
jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0 Mounted
jroute-ex package on /dev/md3...
Verified manifest signed by PackageProduction_10_0_0 Verified
jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jswitch-ex-10.0R4.7 not present.
Mounted jweb-ex package on /dev/md4...
Verified manifest signed by PackageProduction_10_0_0 Verified
jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0 Executing
/packages/mnt/jweb-ex-10.0R4.7/mount.post..
Automatic reboot in progress...
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation) FILE
SYSTEM CLEAN; SKIPPING CHECKS clean, 28254 free (38 frags, 3527
blocks, 0.1% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean,
62228 free (244 frags, 7748 blocks, 0.4% fragmentation) FILE SYSTEM
CLEAN; SKIPPING CHECKS clean, 160996 free (28 frags, 20121 blocks,
0.0% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 160996
free (28 frags, 20121 blocks, 0.0% fragmentation) Creating initial
configuration...mgd: error: Couldn't open lib
/usr/lib/dd//libjcrypto-dd.so: Cannot open
/usr/lib/dd//libjcrypto-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so:
Cannot
open /usr/lib/dd//libjcrypto_junos-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot
open /usr/lib/dd//libjdocs-dd.so
/config/juniper.conf:294:(8) syntax error at 'rstp'
[edit protocols]
'rstp;'
syntax error
/config/juniper.conf:297:(5) error recovery ignores input until this
point at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:300:(5) error recovery ignores input until this
point at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:304:(1) error recovery ignores input until this
point at '}'
[edit]
'}'
error recovery ignores input until this point [edit system
services ssh]
'ssh'
warning: daemon binary /usr/sbin/sshd not found
mgd: commit complete
Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: OK: extracted home directories.
.
Doing initial network setup:
.
Initial interface configuration:
additional daemons:.
Additional routing options:kern.module_path:
/boot//kernel;/bootLoading
the
NETPFE ethernet module
/modules - /booLoading the EX-series platform NETPFE module
t//kernel;/boot/modules;/modules
grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 - 1
grat_arp_delay=${grat_arp_delay}: net.link.ether.inet.grat_arp_delay:
0 -
0
kld netpfe drv: ifpfed_ethkld platform: ex_ifpfe if_vcpkern.module_path:
Re: [j-nsp] EX4200 Problem - Bad Switch?
Hi Paul, Look at this KB: (explains It all.. :)) http://kb.juniper.net/InfoCenter/index?page=contentid=KB11752 Maarten -Oorspronkelijk bericht- Van: Paul Stewart [mailto:p...@paulstewart.org] Verzonden: dinsdag 11 januari 2011 0:14 Aan: 'Maarten van der Hoek' CC: 'juniper-nsp' Onderwerp: RE: [j-nsp] EX4200 Problem - Bad Switch? No - never tried that... have to find a doc on how to do it ;) Thanks for the suggestion Paul -Original Message- From: Maarten van der Hoek [mailto:maar...@vanderhoek.nl] Sent: January-10-11 5:45 PM To: 'Paul Stewart' Cc: 'juniper-nsp' Subject: RE: [j-nsp] EX4200 Problem - Bad Switch? Hi Paul, We had similar issue's with 4200 switches... The only installation way that helped us was using the TFTP server method! Using f.e. USB made things even worse ... :( Did you try TFTP ? Maarten -Oorspronkelijk bericht- Van: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] Namens Paul Stewart Verzonden: maandag 10 januari 2011 23:37 Aan: 'Joe Hamelin' CC: 'juniper-nsp' Onderwerp: Re: [j-nsp] EX4200 Problem - Bad Switch? Thanks.. this was a brand new out of the box switch. It had been powered up once successfully and worked fine at that point. Then it was powered down and brought back up and now problems... Tried 3 times now to reinstall JunOS and no luck ;( -Original Message- From: neth...@gmail.com [mailto:neth...@gmail.com] On Behalf Of Joe Hamelin Sent: January-10-11 4:07 PM To: Paul Stewart Cc: juniper-nsp Subject: Re: [j-nsp] EX4200 Problem - Bad Switch? It looks like you're missing a few libraries (files) in your install. Re-install JunOS. -- Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474 On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote: Hey folks Ran across a weird issue today on a new EX4200-48T switch. Switch boots up and during so I see this (sorry for the length of the post): Trying to mount root from ufs:/dev/da0s1a Attaching /packages/jbase via /dev/mdctl... Mounted jbase package on /dev/md0... Verified manifest signed by PackageProduction_10_0_0 Verified jboot signed by PackageProduction_10_0_0 Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0 /packages/jcrypto-ex-10.0R4.7 not present. /packages/jdocs-ex-10.0R4.7 not present. Mounted jkernel-ex package on /dev/md1... Verified manifest signed by PackageProduction_10_0_0 Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0 Mounted jpfe-ex42x package on /dev/md2... Verified manifest signed by PackageProduction_10_0_0 Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0 Mounted jroute-ex package on /dev/md3... Verified manifest signed by PackageProduction_10_0_0 Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0 /packages/jswitch-ex-10.0R4.7 not present. Mounted jweb-ex package on /dev/md4... Verified manifest signed by PackageProduction_10_0_0 Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0 Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post.. Automatic reboot in progress... FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation) FILE SYSTEM CLEAN; SKIPPING CHECKS clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation) Creating initial configuration...mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto-dd.so: Cannot open /usr/lib/dd//libjcrypto-dd.so mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so: Cannot open /usr/lib/dd//libjcrypto_junos-dd.so mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open /usr/lib/dd//libjdocs-dd.so /config/juniper.conf:294:(8) syntax error at 'rstp' [edit protocols] 'rstp;' syntax error /config/juniper.conf:297:(5) error recovery ignores input until this point at '}' [edit protocols] '}' error recovery ignores input until this point /config/juniper.conf:300:(5) error recovery ignores input until this point at '}' [edit protocols] '}' error recovery ignores input until this point /config/juniper.conf:304:(1) error recovery ignores input until this point at '}' [edit] '}' error recovery ignores input until this point [edit system services ssh] 'ssh' warning: daemon binary /usr/sbin/sshd not found mgd: commit complete Setting initial options: debugger_on_panic=NO debugger_on_break=NO. Starting optional daemons: OK: extracted home directories. . Doing initial network setup: . Initial interface configuration: additional daemons:. Additional routing options:kern.module_path: /boot//kernel;/bootLoading the NETPFE ethernet
Re: [j-nsp] EX4200 Problem - Bad Switch?
I was going to suggest looking at the caveats on Juniper's site regarding JUNOS
levels and upgrading. IOW, if it shipped with certain 9.x versions you have to
incrementally get to 10.x, however, reading further I see you had it
successfully booted.
I did have a EX3200-24T come back up in factory default once. I had JTAC
replace the hardware. Unfortunately, I can't recall the details. After viewing
the crash dump and logs, they claimed I issued a factory reset command (which I
did not). I told I don't trust this piece of hardware, so they RMA'd it for me.
I don't know if this helps, but it may be something to think about.
-b
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Paul Stewart
Sent: Monday, January 10, 2011 2:37 PM
To: 'Joe Hamelin'
Cc: 'juniper-nsp'
Subject: Re: [j-nsp] EX4200 Problem - Bad Switch?
Thanks.. this was a brand new out of the box switch. It had been powered up
once successfully and worked fine at that point. Then it was powered down
and brought back up and now problems...
Tried 3 times now to reinstall JunOS and no luck ;(
-Original Message-
From: neth...@gmail.com [mailto:neth...@gmail.com] On Behalf Of Joe Hamelin
Sent: January-10-11 4:07 PM
To: Paul Stewart
Cc: juniper-nsp
Subject: Re: [j-nsp] EX4200 Problem - Bad Switch?
It looks like you're missing a few libraries (files) in your install.
Re-install JunOS.
--
Joe Hamelin, W7COM, Tulalip, WA, 360-474-7474
On Mon, Jan 10, 2011 at 12:53 PM, Paul Stewart p...@paulstewart.org wrote:
Hey folks.
Ran across a weird issue today on a new EX4200-48T switch. Switch boots
up
and during so I see this (sorry for the length of the post):
Trying to mount root from ufs:/dev/da0s1a
Attaching /packages/jbase via /dev/mdctl...
Mounted jbase package on /dev/md0...
Verified manifest signed by PackageProduction_10_0_0
Verified jboot signed by PackageProduction_10_0_0
Verified jbase-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jcrypto-ex-10.0R4.7 not present.
/packages/jdocs-ex-10.0R4.7 not present.
Mounted jkernel-ex package on /dev/md1...
Verified manifest signed by PackageProduction_10_0_0
Verified jkernel-ex-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jpfe-ex42x package on /dev/md2...
Verified manifest signed by PackageProduction_10_0_0
Verified jpfe-ex42x-10.0R4.7 signed by PackageProduction_10_0_0
Mounted jroute-ex package on /dev/md3...
Verified manifest signed by PackageProduction_10_0_0
Verified jroute-ex-10.0R4.7 signed by PackageProduction_10_0_0
/packages/jswitch-ex-10.0R4.7 not present.
Mounted jweb-ex package on /dev/md4...
Verified manifest signed by PackageProduction_10_0_0
Verified jweb-ex-10.0R4.7 signed by PackageProduction_10_0_0
Executing /packages/mnt/jweb-ex-10.0R4.7/mount.post..
Automatic reboot in progress...
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 48430 free (46 frags, 6048 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 28254 free (38 frags, 3527 blocks, 0.1% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 62228 free (244 frags, 7748 blocks, 0.4% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 160996 free (28 frags, 20121 blocks, 0.0% fragmentation)
Creating initial configuration...mgd: error: Couldn't open lib
/usr/lib/dd//libjcrypto-dd.so: Cannot open
/usr/lib/dd//libjcrypto-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjcrypto_junos-dd.so:
Cannot
open /usr/lib/dd//libjcrypto_junos-dd.so
mgd: error: Couldn't open lib /usr/lib/dd//libjdocs-dd.so: Cannot open
/usr/lib/dd//libjdocs-dd.so
/config/juniper.conf:294:(8) syntax error at 'rstp'
[edit protocols]
'rstp;'
syntax error
/config/juniper.conf:297:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:300:(5) error recovery ignores input until this point
at '}'
[edit protocols]
'}'
error recovery ignores input until this point
/config/juniper.conf:304:(1) error recovery ignores input until this point
at '}'
[edit]
'}'
error recovery ignores input until this point
[edit system services ssh]
'ssh'
warning: daemon binary /usr/sbin/sshd not found
mgd: commit complete
Setting initial options: debugger_on_panic=NO debugger_on_break=NO.
Starting optional daemons: OK: extracted home directories.
.
Doing initial network setup:
.
Initial interface configuration:
additional daemons:.
Additional routing options:kern.module_path: /boot//kernel;/bootLoading
the
NETPFE ethernet module
/modules - /booLoading the EX-series platform NETPFE module
t//kernel;/boot/modules;/modules
grat_arp_on_ifup=YES: net.link.ether.inet.grat_arp_on_ifup: 1 - 1
grat_arp_delay=${grat_arp_delay}:
[j-nsp] Hard Disk Replacement - M5
Hello, I am trying to replace a hard drive on an old M5 running JunOS 6.2. The RE installs the drive which can be seen from the following output: r...@m5 show system boot-messages ad0: 91MB SanDisk SDCFB-96 [734/8/32] at ata0-master using PIO1 ad1: 11513MB IBM-DARA-212000 [23392/16/63] at ata0-slave using UDMA33 Mounting root from ufs:/dev/ad0s1a The problem is that the RE won't partition it: r...@m5 request system partition hard-disk mount: /dev/ad1s1e: Device not configured ERROR: Can't access hard disk, aborting partition. The hard drive had been erased with dd. Has anyone come across this problem? Am I missing something here? Thank you! Kind Regards, V. Vasilev ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
