Hi, just one question.. they have confirmed that it's broken for 8.3... or for
8.x ?? and for a particular Media-type ?
BR
Gaston.
Quoting "Judd, Michael \(Michael\)" <[EMAIL PROTECTED]>:
Hello, Juniper confirmed that this feature is broken in 8.x JUNOS.
Existing PR.
Specifically, the interface down timer does not work.
Regards
Mike
-----Original Message-----
From: Judd, Michael (Michael)
Sent: Tuesday, May 27, 2008 10:29 AM
To: 'Perry, Andrew'
Subject: RE: [j-nsp] Juniper M40e - Junos 8.3 - coc12
Hi Andy,
I have not tested 8.3 on any other chassis. I am awaiting a response
from Juniper to tell me if it is a defect with 8.3.
Regards
Mike
-----Original Message-----
From: Perry, Andrew [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2008 10:24 AM
To: Judd, Michael (Michael)
Subject: RE: [j-nsp] Juniper M40e - Junos 8.3 - coc12
Are you saying it only applies to the M40e or to any M-Series with 8.3
code?
Andy
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Judd, Michael
(Michael)
Sent: Tue 5/27/2008 8:19 AM
To: Erdem Sener
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Juniper M40e - Junos 8.3 - coc12
Erdem,
Thank you. I tested on another box, an M7i running 7.4. The hold-timer
worked as designed. I think there is a problem with the hold-timer in
JUNOS 8.3 for the M40e. I am addressing this with Juniper and asking
them to create a PR for this issue.
Thank you for the reply.
Regards
Mike
-----Original Message-----
From: Erdem Sener [mailto:[EMAIL PROTECTED]
Sent: Friday, May 23, 2008 6:06 PM
To: Judd, Michael (Michael)
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Juniper M40e - Junos 8.3 - coc12
Hi Mike,
hold-time does exactly what the documentation states; meaning that
instead of immediately bringing the interface down, it waits as much as
your hold time 'down' counter before making the interface down and as
much as your 'up'
counter before marking a down interface as up.
For example, the configuration below tells JUNOS to wait for 2 seconds
after an error (e.g. AIS) before bringing the interface down. If the AIS
took, say 5 seconds and the interface is down; JUNOS will wait for 2
seconds after the alarm is cleared before bringing the interface up.
e3-1/3/0 {
hold-time up 1000 down 2000;
unit 0 {
family mlppp {
bundle lsq-1/2/0.0;
}
}
}
Based on how your alarms are happening (e.g. sub-second, 1 second
etc.), you may use this feature safely I'd say.
HTH
Erdem
On Thu, May 22, 2008 at 8:31 PM, Judd, Michael (Michael)
<[EMAIL PROTECTED]> wrote:
BACKGROUND:
I am working with a customer who is using MLPPP. Whenever the directly
connected DACS experiences any sort of redunancy switchover, separate
from an APS switchover, a path AIS is generated which causes the M40's
ct3's to bounce. When this happens, all MLPPP re-negotiation/restart
occurs resulting in higher than desired recovery times for the network
that this service is serving. I found the following parameter in the
Juniper docs but have no easy way to test this in the lab.
Cisco has a similar feature called carrier-delay.
Question; does anyone have any experience or insight into the
following interfaces hold-time parameter?
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-netw
or k-interfaces/html/interfaces-physical-config31.html
Damping Interface Transitions
By default, when an interface changes from being up to being down, or
from down to up, this transition is advertised immediately to the
hardware and the JUNOS software. In some situations-for example, when
an interface is connected to an add-drop multiplexer (ADM) or
wavelength-division multiplexer (WDM), or to protect against SONET/SDH
framer holes-you might want to damp interface transitions. This means
not advertising the interface's transition until a certain period of
time has passed, called the hold-time. When you have damped interface
transitions and the interface goes from up to down, the interface is
not advertised to the rest of the system as being down until it has
remained down for the hold-time period. Similarly when an interface
goes from down to up, it is not advertised as being up until it has
remained up for the hold-time period.
To damp interface transitions, include the hold-time statement at the
[edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
hold-time
<http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-net
wo rk-interfaces/html/interfaces-summary143.html#1015655> up
milliseconds down milliseconds;
The time can be a value from 0 through 65,534 milliseconds. The
default value is 0, which means that interface transitions are not
damped. The JUNOS software advertises the transition within 100
milliseconds of the time value you specify.
Thank you !
~~~~~~~~~~~~~~~
Mike Judd
Member of Technical Staff
Alcatel-Lucent
4 Robbins Road
Westford, MA 01886
office: 978-392-6406
Alcatel-Lucent Global TSS Contact Center
** 24x7x365 Customer Technical Support ** In the United States;
1-866-Lucent8, option 1 / 1-866-582-3688, option 1 Outside of the
United States 1-630-224-4672 ~~~~~~~~~~~~~~~~~
_______________________________________________
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
This communication is the property of Qwest and may contain confidential
or privileged information. Unauthorized use of this communication is
strictly prohibited and may be unlawful. If you have received this
communication in error, please immediately notify the sender by reply
e-mail and destroy all copies of the communication and any attachments.
_______________________________________________
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
