Re: [j-nsp] gNMI on MX960

there plans to distribute the open config proto files that juniper > uses, or do these need to be loaded to work correctly? > > - Jared > > Sent via RFC1925 compliant device > > > On Mar 7, 2024, at 1:54 PM, Ebben Aries via juniper-nsp > > wrote: > > > >

Re: [j-nsp] gNMI on MX960

> "UNKNOWN:Error received from peer ipv4:10.4.0.78:30030 > {grpc_message:"Qos not supported", grpc_status:12, > created_time:"2024-03-07T16:20:41.756921+01:00"}" This would imply that the `qos` field is likely being populated in your request message: https://github.com/openconfig/gnmi/blob/master

Re: [j-nsp] Simple Script Running

That is because you are most likely attempting to your rpc-reply directly causing the cli formatting to only display the raw xml leaf nodes. If you are looking to just output commands as normal cli rendered output, you will want to copy your rpc-reply directly to the result-tree using "copy-

Re: [j-nsp] 'phantom' link aggregation interface

> around for years and that nobody seems to care about either. For example > "show interface diagnostics optics" allows you to hit enter afterwards > without specifying an interface, but if you don't specify an interface > it won't return any optical data at all. This not only doesn't follow > all

Re: [j-nsp] P-4DS3 cables?

posilock SMB http://www.juniper.net/products/modules/100049.html#specifications On 9/10/07, TCIS List Acct <[EMAIL PROTECTED]> wrote: > We have a clear-channel DS-3 we need to turn up in a M-series. The P-4DS3 > looks > like what we need, but the coax connectors look "smaller" than normal. I

Re: [j-nsp] BGP Origin Issue

___ > > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > NOTICE: This electronic mail transmission may contain confidential > information and is intended on

Re: [j-nsp] BGP Origin Issue

this transmission in error, please notify the sender via e-mail. > > > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp -- Ebben Aries Lead Network Engineer United Communications, Inc. 389 SW Scalehouse Ct.

Re: [j-nsp] BGP Origin Issue

When you redistribute into BGP, the routes will show as imcomplete. I believe that is cisco default behavior on redistribution. To circumvent the issue, you can create a route-map w/ a 'set origin' on outbound announcements. On Thursday 19 April 2007 11:22 am, Borchers, Mark M. wrote: > We hav

Re: [j-nsp] PE-4FE-TX not transmitting anything...faulty?

traffic sent at all? Also, are you seeing any RE bound traffic attempting to be sent when you issue 'monitor traffic interface fe-x/x/x' ? Anyone else out there ran into this? I am also anxiously awaiting any insight. Thanks, Ebben ---- From: Ebben Aries <[EMAIL PROTECT

[j-nsp] P-4FE-TX Output Drops

Hello all, This is a weird one.. I have a P-4FE-TX that has one interface that is displaying the following. Output errors: Carrier transitions: 0, Errors: 0, Drops: 29052, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0 Egres

Re: [j-nsp] MLPPP link drop brings bundle down

I am running the same scenario terminating on a P-AS in L2 mode and have not had any problems regarding the bundle going down if only 1 member T1 goes down. By default, only 1 link needs to be up for the bundle to be labeled as up. The amount of minimum links however is a configurable option.

Re: [j-nsp] J4350/6350 experiences?

with a > J4350 or J6350, but I have about 15-20 T1/fracT1 customers and I can't > get that many into a single Jx350. -- Ebben Aries Lead Network Engineer United Communications, Inc. 389 SW Scalehouse Ct. Suite 100 Bend, OR  97702 Office: 541.322.1407 Fax: 541.322.1417 [EMAIL PROTECTED]

[j-nsp] P-ChDS3/P-ChDS3-QPP

Hello all I believe I already know the answer to this but worth giving it a shot. I have multiple P-ChDS3 PICs in E-FPCs where we aggregate T1 Customers. I already know that these PICs cannot do queuing down to the logical interface level but can anyone confirm how queuing works on these ?