Re: [j-nsp] Debugging SONET (OC-3) errors
Hello Chris, If I remember correctly then B3 errors are associated with clocking alignment along the circuit. This also correlate to what you are saying about passing through 7 carriers. Regards Amos Rosenboim [EMAIL PROTECTED] On Aug 4, 2008, at 9:54 PM, Chris Adams wrote: I have an OC-3 (POS running PPP) between two POPs (an M10i at each end) getting errors, and this is the first time I've had to debug errors on a SONET link. I am seeing BIP-B3 and REI-P incrementing in spurts on the Z end (e.g. 99 BIP-B3 and 45 REI-P, both showing 2 seconds), as well as ES-P and ES-PFE matching the seconds (2 in since I cleared the counters). No other error counters are incrementing (no section or line errors at all). I have seen some errors at the A end as well, but not as many or as often. When I get a spurt of errors, both ends will show an interface flap (at least most of the time; I'm not sure this is 100% of the time or not). Reading various docs, this means there is a problem somewhere between telco devices with the transmission from the Z end to the A end. Is that correct? I opened a telco ticket, but they pretty much blew it off. I know little about SONET so I am having trouble telling them what to check. I'd like to avoid intrusive testing if possible (since this is a major circuit for us). Part of the problem is that this circuit goes through 7 (yes 7!) different carriers, and I am not sure that the telco that owns the whole thing is looking at anything other than the loop on the Z end (the only piece they actually own). Any suggestions? -- Chris Adams [EMAIL PROTECTED] Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. ___ 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] VPLS LM Status?
A typical usage of multiple local sites is multihoming. One site can be
multihomed another not.
I noticed you complain for this but it should work - just specify site
preferences in multihomed sites ( although I think bgp selection should fall
down skipping some steps like lowest IGP metric ..)
The mesh-groups is notion in regards to split-horizon rules in VPLS.
They are used (9.1) for interoperability between LDP and BGP signaling.
Also will be used is future releases for H-VPLS ( ldp sig) and inter-AS
VPLS.
In your setup the local mesh-groups (interfaces under site-IDs) should
forward flooded and learned traffic - working as designed.
Regards,
Krasi
_
From: Marlon Duksa [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 8:14 AM
To: Krasimir Avramski
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] VPLS LM Status?
It works. Thanks.
Can you please elaborate a bit more what do you mean by local mesh-groups?
I tried to forward learned traffic as well as flooded from interfaces
between local sites and interfaces within local sites...traffic was flowing
in any case.
Are those mesh groups supposed to supress some traffic? Not quite sure what
is the purpose of multiple local sites? If I have many interfaces in a
single site, wouldn't that work as well?
Thanks,
marlon
On Mon, Aug 4, 2008 at 1:30 AM, Krasimir Avramski [EMAIL PROTECTED] wrote:
Hello,
Only one pseudowire is setup between PEs of a VPLS domain.
There are already pseudowires 1-2 and 1-3, so site ID 1 is minimum
designated in PE for this VPLS domain. At the forwarding plain you should
not have any problems in communication between interfaces in site 4 to local
interfaces in site 1 and remote site IDs 2 and 3.
LM, RM states are not considered errors, that is more information for the
pseudowire selection.
Think of a site (VE) as a selection of PE-CE interfaces (local mesh-group)
for a vpls domain.
Also when configuring multihoming specify the site preferences in order PEs
to solve collisions and choose single forwarder.
Regards,
Krasi
-Original Message-
From: [EMAIL PROTECTED] [mailto:juniper-nsp-
[EMAIL PROTECTED] On Behalf Of Marlon Duksa
Sent: Monday, August 04, 2008 1:16 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] VPLS LM Status?
Does anyone know why would I get the LM status (local site ID not minimum
designated) on my VPLS connection.
I have two sites configured on a single PE in the same VPLS.
One site is coming up just fine, but the other is not.
The remote side for the 'not up' connection is complaining with the RM
status (remote site ID not minimum designated).
What does this 'ID not minimun designated' mean?
My sites ID are unique withing the VPLS and within the range that is
defined
for the site-range.
This is the config on my local router:
[EMAIL PROTECTED] show routing-instances
vpls {
instance-type vpls;
interface ge-0/1/1.0;
interface ge-8/2/0.0;
interface ge-5/3/4.0;
route-distinguisher 100:100;
vrf-target target:200:200;
protocols {
vpls {
site-range 10;
no-tunnel-services;
site green {
site-identifier 1;
interface ge-0/1/1.0;
interface ge-8/2/0.0;
}
site multi {
site-identifier 4;
interface ge-5/3/4.0;
}
}
}
}
And this is the status:
[EMAIL PROTECTED] run show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not
CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not
same
VC-Dn -- Virtual circuit downNP -- interface hardware not present
CM -- control-word mismatch - -- only outbound connection is up
CN -- circuit not provisioned- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum
designated
RN -- remote site not designated RM -- remote site ID not minimum
designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not availble
Legend for interface status
Up -- operational
Dn -- down
Instance: vpls
Local site: green (1)
connection-site Type St Time last up # Up
trans
2 rmt Up Aug 3 22:02:16 2008
1
Local interface: lsi.1048578, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls local site 1 remote site 2
Remote PE: 2.2.2.2, Negotiated control-word: No
Incoming label: 262154, Outgoing label: 800032
3
Re: [j-nsp] ex-series: counters for transit traffic ?
On Fri, Aug 01, 2008 at 06:39:22PM +0400, Alexandre Snarskii wrote: Hi! It looks like ex-series switches does not count nor packets nor bytes, nor ingress nor egress, for transit traffic. For example, on physical interfaces all I can get is Local statistics: Well, for physical interfaces it was my fault (detailed statistics is may be too detailed): counters are ok for the interface: Traffic statistics: Input bytes : 989129150 bps Output bytes : 235515820 bps Input packets:695950 pps Output packets: 2796090 pps and the only (cosmetic) bug is that they are not counted as 'Transit statistics' for unit 0. Thanks to everybody who pointed me to that. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Re : SSG XAUTH
Hi Sven,Yes it is possible. You need to select the configured authenctication server in Default XAUTH settings and the required IP pool.User will be authenticated from the remote authentication server and IP will be assigned from local IP pool..Regards//Amit SaxenaJNCIS- FWVOn Mon, 04 Aug 2008 09:24:52 +0200 Sven Juergensen (KielNET) wrote-BEGIN PGP SIGNED MESSAGE-Hash: SHA1Dear list,is it possible to seperate theauth and settings done throughXAUTH? I'm trying to authenticateagainst an LDAP-Server but wantto assign the IP-settings for theclient from local definitions.Thanks and regards,Mit freundlichen Gruesseni. A. Sven Juergensen- --FachbereichNetze/ProjekteKielNET GmbHGesellschaft fuer KommunikationPreusserstr. 1-9, 24105 KielTelefon : 0431 / 2219-053Telefax : 0431 / 2219-005E-Mail : [EMAIL PROTECTED]: http://www.kielnet.deGeschaeftsfuehrer Eberhard SchmidtHRB 4499 (Amtsgericht Kiel)-BEGIN PGP SIGNATURE-Version: GnuPG v2.0.9 (GNU/Linux)iE! YEARECAAYFAkiWrsQACgkQnEU7erAt4TKuTwCgv80KMZPjNrjE9Vdeee5rV//VDrEAoKrA+KJ5kvWEIFXcJziuApt6juE9=VtSw-END PGP SIGNATURE-___juniper-nsp mailing list [EMAIL PROTECTED]://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Rebuilding an M20 from a HD crash
Hello All, We had an M20 hard drive die on our routing engine. We ordered a used IBM hard drive and the Juniper seems to be detecting it. The problem we are having,however, is figuring out how to get JunOS back onto the hard drive. I was reading the JunOS Cookbook and there's a section for making and using an emergency boot disk. I tried that out, but it's not working. Has anyone else had this problem or has ideas about how to get the M20 back up and running from a crashed HD? Thanks for the help! -Lucas ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debugging SONET (OC-3) errors
Date: Mon, 4 Aug 2008 13:54:27 -0500 From: Chris Adams [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I have an OC-3 (POS running PPP) between two POPs (an M10i at each end) getting errors, and this is the first time I've had to debug errors on a SONET link. I am seeing BIP-B3 and REI-P incrementing in spurts on the Z end (e.g. 99 BIP-B3 and 45 REI-P, both showing 2 seconds), as well as ES-P and ES-PFE matching the seconds (2 in since I cleared the counters). No other error counters are incrementing (no section or line errors at all). I have seen some errors at the A end as well, but not as many or as often. When I get a spurt of errors, both ends will show an interface flap (at least most of the time; I'm not sure this is 100% of the time or not). Reading various docs, this means there is a problem somewhere between telco devices with the transmission from the Z end to the A end. Is that correct? I opened a telco ticket, but they pretty much blew it off. I know little about SONET so I am having trouble telling them what to check. I'd like to avoid intrusive testing if possible (since this is a major circuit for us). Part of the problem is that this circuit goes through 7 (yes 7!) different carriers, and I am not sure that the telco that owns the whole thing is looking at anything other than the loop on the Z end (the only piece they actually own). Any suggestions? I don't envy tracking something like this through 7 carriers! In any case, BIP-B3 errors are data errors and REI errors are Remote Error Indicators. Since you see PATH errors on both ends of the circuit, it is somewhere in the middle. The errors are in bursts which would indicate electrical noise at some OEO location (probably an ADM, though both amplifiers and regens can do this) or a clocking problem. Since REIs are reaching your equipment, some piece of gear at one of the carriers is reporting errors. It's just tracking it down that can be daunting. In may experience, the standard answer the first time you ask a carrier about line errors is that they have seen nothing. The error is probably at a hand-off from one carrier to another. Try to confirm which carrier(s) are seeing any non-path errors. This will at least help localize the issue. Good luck! -- 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 pgpvDoWeMaAuE.pgp Description: PGP signature ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debugging SONET (OC-3) errors
If the errors are occurring frequently enough (once an hour), you could ask for a hard loopback on one end and ask the service provider to run a bert test from the other side towards the hard loopback. The bert will see the path errors in the middle of the circuit which will prove the problem to the service provider. The downside being that your OC3c will be out of service for an extended period. I had to resort to this method once on a protected OC48c where the hard loopbacks were progressively moved towards the middle of the facility where the fault was found. Clinton. Chris Adams wrote: I have an OC-3 (POS running PPP) between two POPs (an M10i at each end) getting errors, and this is the first time I've had to debug errors on a SONET link. I am seeing BIP-B3 and REI-P incrementing in spurts on the Z end (e.g. 99 BIP-B3 and 45 REI-P, both showing 2 seconds), as well as ES-P and ES-PFE matching the seconds (2 in since I cleared the counters). No other error counters are incrementing (no section or line errors at all). I have seen some errors at the A end as well, but not as many or as often. -- = Clinton Work Airdrie, AB ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Rebuilding an M20 from a HD crash
Hello, its not that hard to do. In general you do the following: If the flash is still working the RE should boot up fine saying that it is creating an emergency /var partition in ram. You should be able to login. Issue the following command: request system snapshot partition This will partition the hdd and copy JunOS over to it. Basically this should be all you need to do. However it might be required to reinstall JunOS via a jinstall package. YMMV. Regards, Jonas Frey On Tue, 2008-08-05 at 17:22, Lucas T wrote: Hello All, We had an M20 hard drive die on our routing engine. We ordered a used IBM hard drive and the Juniper seems to be detecting it. The problem we are having,however, is figuring out how to get JunOS back onto the hard drive. I was reading the JunOS Cookbook and there's a section for making and using an emergency boot disk. I tried that out, but it's not working. Has anyone else had this problem or has ideas about how to get the M20 back up and running from a crashed HD? Thanks for the help! -Lucas ___ 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
[j-nsp] J-web installation-j6300 router
I have juniper j6300 router i want to install j web graphic interface on it previsly it was installed on it but i have disabled it from jweb now i want to do again\ can any bodey help me for giving the commands and process for jweb installation of jweb in J6300 router software version is 7.3R1.5 thanks arshad From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Routing options in J-Web
Hello, I'm studding for my JNCIA-ER exam and that includes some j-web configurations. But I noticed that on some M routers and on Olive you can't configure any routing protocols. Is this option in J-Web only available on J series routers? Or am I missing something. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] J-web installation-j6300 router
request system software delete jweb request system software add /var/tmp/blahblah system services web-management http On Tue, Aug 5, 2008 at 5:02 PM, Mohd Arshad [EMAIL PROTECTED] wrote: I have juniper j6300 router i want to install j web graphic interface on it previsly it was installed on it but i have disabled it from jweb now i want to do again\ can any bodey help me for giving the commands and process for jweb installation of jweb in J6300 router software version is 7.3R1.5 thanks arshad From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/ ___ 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
