Good Day All, I've situation here which the alarm appear to be like this :
run show chassis alarms 1 alarms currently active Alarm time Class Description 2007-12-23 20:13:00 MYT Minor Host 0 Boot from alternate media May I know how should I tackle this problem as it appear from M10? I'm new with Juniper Equipment Regards Irwan Time Dot Net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, December 21, 2007 1:00 AM To: [email protected] Subject: juniper-nsp Digest, Vol 61, Issue 30 Send juniper-nsp mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/juniper-nsp or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of juniper-nsp digest..." Today's Topics: 1. VRRP issue in 8.2R4.5 upwards (Mark Johnson) 2. Re: Upgrade without PCMCIA card? (Jared Mauch) 3. Re: 8.x Compatibility (was: Upgrade without PCMCIA card?) (Kevin Oberman) 4. delete configuration (sunnyday) 5. Re: Upgrade without PCMCIA card? (Shawn Morris) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Dec 2007 13:24:13 -0000 From: "Mark Johnson" <[EMAIL PROTECTED]> Subject: [j-nsp] VRRP issue in 8.2R4.5 upwards To: <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Hi, I came across this issue since upgrading from 8.2R2.4 to 8.2 R4.5. Essentially routers won't always take over as VRRP master. They think they've taken over but log this error: Dec 20 11:41:31 xxxxx-rtr dcd[3080]: DCD_CONFIG_WRITE_FAILED: configuration write failed for an RT ADD: Can't assign requested address The server is pingable from the local routers but not externally so it looks as though the error message means "can't add the VRRP address" and therefore the internal hosts lose connectivity. Jtac had access to the routers and found that by adding "accept-data" to the VRRP group it started working. Removing "accept-data" disabling the interfaces and changing priorities would *sometimes* enable the problem to surface again, but not always. Two VLAN's won't swap over even with "accept-data" added. So I want to ask if anyone else has seen this issue and/or what it might be while I wait for Imtech and Juniper to get back in touch. (sigh). Also, anyone that uses VRRP might want to force the mastership change on their VLAN's to make sure they aren't affected by this problem as you may not have the router redundancy you think you have :( Kind regards, Mark ------------------------------ Message: 2 Date: Thu, 20 Dec 2007 09:38:35 -0500 From: Jared Mauch <[EMAIL PROTECTED]> Subject: Re: [j-nsp] Upgrade without PCMCIA card? To: "Jonas Frey (Probe Networks)" <[EMAIL PROTECTED]> Cc: [email protected], Richard A Steenbergen <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii There should be no reason a 1G CF would not work. - Jared On Thu, Dec 20, 2007 at 11:50:09AM +0100, Jonas Frey (Probe Networks) wrote: > Hello, > > speaking of CF upgrades...anyone here did any yet? > Wondering how much cf memory the RE(2|3) can handle. -- Jared Mauch | pgp key available via finger from [EMAIL PROTECTED] clue++; | http://puck.nether.net/~jared/ My statements are only mine. ------------------------------ Message: 3 Date: Thu, 20 Dec 2007 07:29:51 -0800 From: "Kevin Oberman" <[EMAIL PROTECTED]> Subject: Re: [j-nsp] 8.x Compatibility (was: Upgrade without PCMCIA card?) To: "Eric Van Tol" <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" > Date: Thu, 20 Dec 2007 07:01:13 -0500 > From: "Eric Van Tol" <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > Downgrading to 7.6 worked for me, which is probably your best > > bet on the M5/10/20/40 unless you're willing to upgrade the > > RE's flash and the FEB/SSB SDRAM in a warranty-voiding kinda way. > > Can someone post some more info regarding this, perhaps with memory > requirements per platform? Will 8.5 cause problems on an M20 with an > RE-333-768 and SSB-E? What about an RE-600-2048 w/ SSB-E-16? This > seems pretty scary to me and is getting into Cisco territory now with > having to worry about what platform can run what JUNOS version. As of today an M20 with the 64MB of DRAM can still handle full routes. You can look at the utilization with 'show chassis [c]feb' or 'show chassis ssb', depending on the router model. Theat will tell you how much DRAM the system has and the heap utilization will tell you how close you are to falling off the end of the world. On most FEB and CFEB systems the move to new code ate about 6-12% more heap. If the system is sitting at 90% or higher, it is likely that you will have problems after the upgrade. Wee found that 64MB M10 and M5 systems could not work and rolled them back to V7. Our remaining M20s are still hanging in there, but we plan to replace it shortly. For reasons I don't understand, SSB utilization increased only slightly, if at all. Still, for a router carrying full routes, it will be getting close to the edge. > Also - what type of memory can you use on an old, outdated FEB? > Hypothetically, of course, because who would want to invalidate their > warranty? ;-) Huh? A 64MB FEB that is still in warranty? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : https://puck.nether.net/pipermail/juniper-nsp/attachments/20071220/0a21bb19/ attachment-0001.bin ------------------------------ Message: 4 Date: Thu, 20 Dec 2007 17:53:10 +0200 From: "sunnyday" <[EMAIL PROTECTED]> Subject: [j-nsp] delete configuration To: "Juniper-Nsp" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" how can i can use the command delete | except on m series from top of the configuration deleting everything except some element for example a certain interface Cheers ------------------------------ Message: 5 Date: Thu, 20 Dec 2007 08:53:04 -0800 From: "Shawn Morris" <[EMAIL PROTECTED]> Subject: Re: [j-nsp] Upgrade without PCMCIA card? To: "Jonas Frey (Probe Networks)" <[EMAIL PROTECTED]> Cc: [email protected], Richard A Steenbergen <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 We've done some upgrades of both RE3s and RE2s in our lab to 1g. On the RE3 it's extremely simple as it's designed to be a FRU. You just open a latch and replace the card. On the RE2 you have to remove the faceplate and about 5 screws on the bottom to remove the daugtherboard that the HD sits on and then the CF is on a daughterboard underneath that. We tried using some el-cheapo CF cards from Micro Center and those did not work. We had to use regular Sandisk 1g CF cards. On 12/20/07, Jonas Frey (Probe Networks) <[EMAIL PROTECTED]> wrote: > Hello, > > speaking of CF upgrades...anyone here did any yet? > Wondering how much cf memory the RE(2|3) can handle. > > Regards, > Jonas > > On Thu, December 20, 2007 00:53, Richard A Steenbergen wrote: > > On Wed, Dec 19, 2007 at 06:09:28PM -0400, chiel wrote: > > > >> Hi all, > >> > >> > >> I want to upgrade a M5 from 6.2R2.4 to 8.5R1.14. But I don't have a > >> PCMCIA card, see bellow: > >> > >> > >> root> request system software add non-validate reboot > >> /var/tmp/jinstall-8.5R1.14-export-signed.tgz > >> Installing package '/var/tmp/jinstall-8.5R1.14-export-signed.tgz' ... > >> Verified MD5 checksum of jinstall-8.5R1.14-export.tgz > >> Adding jinstall... > >> > >> > >> WARNING: This installation will not succeed. > >> WARNING: The boot device is less than 256M. > >> WARNING: A hardware upgrade is required. > >> > > > > JUNOS 8.5 and beyond will no longer fit on compact flash less than 256MB > > (some mysterous 40MB addition to the jpfe-common image which I haven't > > bothered to track down yet), which means no stock M5 RE will ever support > > it. > > > > You could upgrade your CF (unsupported but doable, not recommended for > > novices). but if you're like every other M5 user who upgraded to 8.x last > > week you'll probably end up blowing out with FEB DRAM as soon as you do > > anyways. You could of course also upgrade this (also unsupported :P), but > > if any of this is confusing the correct answer is to downgrade code or > > upgrade platform. :) > > > > -- > > Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras > > GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 > > 2CBC) > > _______________________________________________ > > juniper-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Shawn Morris IP Development - NTT America [EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] v: +1 214 915 1361 f: +1 815 327 3016 ------------------------------ _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp End of juniper-nsp Digest, Vol 61, Issue 30 ******************************************* - Powered by TIME dotNet Berhad - _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
