Junos OS

Have dual serial PIM and dual T1 PIM in J2350.

All four STATIS lights are solid red. Looked this up and says:

Red On steadily Active with a local alarm; device has detected a failure.

I have checked >show chassis alarms  ;; nothing

I have taken the dual serial PIM and put it into my other J2350 and after about a minute after reboot both statis lights go red again.

Within the global and edit modes all looks ok. I looked at all the chassis information (e.g. hardware, fpc, environment, routing-engine) and all looks ok.

Looked at boot-messages but couldn't really make out anything specific, the only failure i say was related to em0 which I think is the management interface and not related to the PIMs.

I WAS JUST WONDERING IF SOMEONE HAS DIRECT EXPERIENCE WITH THESE LIGHTS BEING RED AND MEANING THAT THE PIM IS BAD??  (i'm not yelling, I'm just wanting my question to stand out )

I am having a hard time imagining that both PIMs would be bad --the Serial and the T1--at the same time, but I can't imagine that both my J2350s are bad either, but I get the red statis lights in both routers when I put the serial PIM in?????

Am I missing something like licensing or some kind of installation initialization?

THANKS much,

robin hood

I think you are saying you did this but confirm when you do

show chassis hardware

the cards are correctly listed.

Also look at the output for

show system alarms

And do the interfaces show up under

show interfaces terse

Yes I did all that,

robmin@Junip2350-R6> show chassis alarms
No alarms currently active

show chassis hardware
Hardware inventory:
Item                     Version     Part number           Serial number            Description
Chassis                                                                 JN10F1AF0ADE      J2350
Midplane             REV 06   710-017556             PX7794
System IO           REV 06   710-017562              PY4691                    J23X0 System IO
Crypto Module                                                                                          Crypto Acceleration
Routing Engine   REV 10   710-017560             PX6996                     RE-J2350-2500
FPC 0                                                                                                        FPC
  PIC 0                                                                                                       4x GE Base PIC
FPC 1                  REV 08   750-010356             AG06510314           FPC
  PIC 0                                                                                                       2x Serial  <<--------------  Status lights RED Solid
FPC 2            REV 06   750-010355                   AI07100085            FPC
  PIC 0                                                                                                      2x T1         <<--------------  Status lights RED Solid
Power Supply 0

 show interfaces terse
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    down
ge-0/0/0.0              up    down inet     10.60.1.1/24
gr-0/0/0                up    up
ip-0/0/0                up    up
lsq-0/0/0               up    up
lt-0/0/0                up    up
mt-0/0/0                up    up
sp-0/0/0                up    up
sp-0/0/0.0              up    up   inet
sp-0/0/0.16383          up    up   inet     10.0.0.1            --> 10.0.0.16
                                            10.0.0.6            --> 0/0
                                            128.0.0.1           --> 128.0.1.16
                                            128.0.0.6           --> 0/0
ge-0/0/1                up    down
ge-0/0/2                up    down
ge-0/0/3                up    down
se-1/0/0                up    down                                         <------------ physical protocol won't come up even with configuration
se-1/0/0.0              up    down inet     10.61.1.1/24     <------------------- logical interface
se-1/0/1                up    down                                          <------------------physcial protocol down
se-1/0/1.0              up    down inet     10.11.11.2/24     <----------------- logical interface
t1-2/0/0                up    down
t1-2/0/1                up    down
dsc                     up    up
gre                     up    up
ipip                    up    up
lo0                     up    up
lo0.16384               up    up   inet     127.0.0.1           --> 0/0
lo0.16385               up    up   inet     10.0.0.1            --> 0/0
                                            10.0.0.16           --> 0/0
                                            128.0.0.1           --> 0/0
                                            128.0.0.4           --> 0/0
                                            128.0.1.16          --> 0/0
lo0.32768               up    up
lsi                     up    up
mtun                    up    up
pimd                    up    up
pime                    up    up
pp0                     up    up
ppd0                    up    up
ppe0                    up    up
st0                     up    up
tap                     up    up
vlan                    up    down

show interfaces se-1/0/0
Physical interface: se-1/0/0, Enabled, Physical link is Down
  Interface index: 143, SNMP ifIndex: 507
  Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 8mbps
  Device flags   : Present Running Down
  Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
  Link flags     : Keepalives
  Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
  Keepalive: Input: 0 (never), Output: 0 (never)
  LCP state: Down
  NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured, mpls:
  Not-configured
  CHAP state: Closed
  PAP state: Closed
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : 2015-05-24 03:04:55 UTC (00:09:39 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface se-1/0/0.0 (Index 72) (SNMP ifIndex 534)
    Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps 0x4000
    Encapsulation: PPP
    Security: Zone: Null
    Protocol inet, MTU: 1500
      Flags: Sendbcast-pkt-to-re, Protocol-Down
      Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
        Destination: 10.61.1/24, Local: 10.61.1.1, Broadcast: 10.61.1.255

show interfaces se-1/0/1
Physical interface: se-1/0/1, Enabled, Physical link is Down
  Interface index: 144, SNMP ifIndex: 533
  Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 8mbps
  Device flags   : Present Running Down
  Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
  Link flags     : Keepalives
  Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
  Keepalive: Input: 0 (never), Output: 0 (never)
  LCP state: Down
  NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured, mpls:
  Not-configured
  CHAP state: Closed
  PAP state: Closed
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : 2015-05-24 03:04:55 UTC (00:08:37 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface se-1/0/1.0 (Index 73) (SNMP ifIndex 535)
    Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps 0x4000
    Encapsulation: PPP
    Security: Zone: Null
    Protocol inet, MTU: 1500
      Flags: Sendbcast-pkt-to-re, Protocol-Down
      Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
        Destination: 10.11.11/24, Local: 10.11.11.2, Broadcast: 10.11.11.255

 show interfaces t1-2/0/0
Physical interface: t1-2/0/0, Enabled, Physical link is Down
  Interface index: 145, SNMP ifIndex: 527
  Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
  Loopback: None, FCS: 16, Framing: ESF
  Device flags   : Present Running Down
  Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x4000
  Link flags     : Keepalives
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : 2015-05-24 03:04:55 UTC (00:11:27 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  DS1   alarms   : LOF, LOS
  DS1   defects  : LOF, LOS

 show interfaces t1-2/0/1
Physical interface: t1-2/0/1, Enabled, Physical link is Down
  Interface index: 146, SNMP ifIndex: 528
  Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
  Loopback: None, FCS: 16, Framing: ESF
  Device flags   : Present Running Down
  Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x4000
  Link flags     : Keepalives
  CoS queues     : 8 supported, 8 maximum usable queues
  Last flapped   : 2015-05-24 03:04:55 UTC (00:11:52 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  DS1   alarms   : LOF, LOS
  DS1   defects  : LOF, LOS

I even configured serial connections on them, tried both ppp and cisco-hdlc to cisco routers, had cable connected with DCE on clocking side, and DTE on the other, etc.

But no matter how many variations and types of encapsulation the physical side is down on all four ports.

Can't help repeating: I am having a hard time imagining that both PIMs would be bad --the Serial and the T1--at the same time, but I can't imagine that both my J2350s are bad either;  smiley: confused

THANKS

robin hood

Based on the output it looks like the light is just indicating that the link is down.  For the T1 serial these are link lights indicating a good connection to the other end point not just that the port is configured.

Once you have both sides configured and the link comes up these will go away.

You can verfiy the T1 ports by plugging in a loopback connector if the other side is not availalbe or the link is not coming up and you want to do the testing one side at a time.

http://community.spiceworks.com/how_to/2514-how-to-make-a-t1-loopback-plug-for-testing-both-line-and-csu-dsu

I've not used the serial port cards so I'm not sure what the loopback pins are there for testing.

Thanks very much, I will try to make this connector ASAP. UPDATE: Made the T1 Loopback adapter and it worked. It turns the status light green in any T1 port I plug it into. A also made a T1 cable and it turns the lights green as well. I am working on getting the ping to return successfully but one side's logical protocol will not come up.

UPDATE: I just got another dual T1 PIM come in. I can't believe they delivered not only on a Sunday, but on Memorial Day weekend as well. I put it into my J2320 and both lights also went red after about a minute after booting. So this has to be what you said Spuluka. I am so relieved.  I will be trying to connect the two routers together over their t1-0/0/0 ports. Could you throw me a quick t1 config to test this for each end? Also do I just use a normal Cat5 patch cable?

Just to let you guys know, I have been working and studying every single minute of every single day for over three months since I got my first call at a large campus client who is using primarily Juniper equipment. I had never touched a Juniper device and felt that it was a huge undertaking as they have been having some seeminly deep issues. I jumped in from moment one and never looked back. I have literally been studying 13 to 15 hours a day on getting my first Juniper certification and everytime I am able to make a milestone progress like this it is SO HELPFUL and ENCOURAGING!

I could not have done what I have done so far without the help so far on this forum! ENJOY OUR VICTORY VIDEO.

UPDATE UPDATE: made the cable per this link: http://sh-run.com/2009/06/04/how-to-make-a-t1-crossover-cable/

And BOTH LIGHTS WENT GREEN GREEN GREEN GREEN GREEN GREEN GREEN GREEN! Yaaaaahhhhhhh!

:: dogvery-happy.   WE are all very happy here. Thank you Spuluka!

Also sometime this next week i have another SERIAL PIM coming in that I can put into my other J2350 and then try to link these.

I wonder if the DTE-DCE serial cable will be the right one?  I know you said you have not done Serial. Would anyone else know?  What would be a quick config to slap on there once I get this other PIM just to see if the lights go out?  THANKS to anyone.

Thank you again spuluka!

P.S. Could I plug in a regular cat5 cable from one t1 port to the other t1 port (on the same PIM) and configure these ports to connect to each other?  Like t1-0/0/0 to t1-0/0/1?

UPDATE ON T1 CONFIG:

JunipJ2350-R6 (DCE side)

interfaces {
....
	t1-3/0/0 {
		no-keepalives;
                dce;
		mtu 256;
		encapsulation frame-relay;
		t1-options {
			time-slots 1-24;
			buildout 0-132;
		}
		unit 0 {
			dlci 200;
			family inet {
				address 10.60.31.1/24
			}
		}
	}
}

 JunipJ2320-R8

interfaces {
....
	t1-1/0/0 {
		no-keepalives;
		mtu 256;
		encapsulation frame-relay;
		t1-options {
			time-slots 1-24;
			buildout 0-132;
		}
		unit 0 {
			dlci 200;
			family inet {
				address 10.60.31.2/24
			}
		}
	}
}

 Now to make the cable.

I found someone said: For T1, you need to cross pins 1&2 with pins 4&5, respectively.

Is this right?  And does it matter which end of the cable you plug into the DCE side?

Thanks

Glad to hear you are well on your way.

Configuring T1 services has lots of options depending on the provisioning.  You'll find them outlined in this documentation.

http://www.juniper.net/techpubs/en_US/junos14.1/topics/usage-guidelines/interfaces-configuring-t1-physical-interface-properties.html

This says on the right side that it is for the carrier class devices but the commands are the same on your J series router.

As with any of these types of physical connections, you saw in making your T1 cable that you connect the transmit pins of device A to the receive pins of device B and the transmit pins of device B to the receive pins of device A.  The same will be true for your serial cables.

this documentation shows the pin out connections needed for the various standard equipment on the serial side.

http://www.juniper.net/techpubs/hardware/junos-jseries/junos-jseries96/junos-jseries-hardware-guide/index.html?hw-hardware-features-j2320-j2350.html

Thanks for the link Spuluka. Also, thanks for taking the time to answer my questions. I really appreciate it.

In my fourth UPDATE under my 

License not valid-T1 up down??

post

UPDATE 4 - got the T1 link to ping both ways (!!!!!) even using the 'license error' router on one side of the link. This 'licensing error' message pops up everytime I change the configuration and seems to be a permanent part of my configuration under the T1-2/0/0 interface configuration.

Could I use the 'load replace monitor relative' command and just take out that messsage under the interface configuration?

I have been finding that it seems the licensing error message does not make any difference in the functionality of my learning configurations.  I came across a Juniper document concerning SRX issue that said just delete the license and the error message will stop popping up when configuration changes are made. 

1.) Does this apply to the J-series as well, and

2.) how would I delete the license?

I tried making a backup directory under /config called /license2 and moving the license file that was in /config/license to this backup directory. Rebooting made it so the t1 PIM was not even seen at all.  I put the file back and the PIM appeared again.

 Obviously this is not the way to delete the license.

Obviously, I do not want to learn how to circumvent licensing in a production environment. This is only in my own lab. The SRX technical document did add to contact Juniper and get the correct license. But this is not an option as I could not afford to buy a license for only my own studying.  As I have said in other posts, I have already spent all my money and stretched my credit past the precarious level just getting the hardware so that I could study. And I still have to come up with the money for the test!

3.) I went through the link, thanks again, and I could not find anything on clocking. I 'startpage'd' it and could only find specifc instructions on one side of the link.  What I would like to find is a Juniper document that discusses the clocking relationship on both sides of the link; i.e. when you set one side this way, you must set the other side that way.  The reason I am drilling down into this is that the documents that I read on clocking said to set one side to DCE. I tried this and my logicial llink did not come up. It was only through trying every possible combination with clocking and dce settings that I got the link to come up on both sides.

I did further reading and did find that when you have UP and DOWN it is many times related to a clocking issue: http://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/14149-chapter15.html.  But even in that document it did not explain the relationship. I found a Juniper document that said what the internal clock is, and even how to sync it externally with another clock, but still nothing on the relationship over a single link and what the options are in a configuration http://www.juniper.net/documentation/en_US/junos14.1/topics/task/configuration/interfaces-clock-source-configuring.html

4.) Also, I did a whole bunch of research last night on 'no-keepalives'. I could not find anywhere that explained why on a T1 connection you want to turn off keepalives.  It seems that in most other situations keepalives are a good thing and usually added. Does anyone know the reason behind this T1 configuration norm?

THANKS

robin hood