- J-Net
- :
- Forums
- :
- Ethernet Switching
- :
- Re: pem_tvp_periodic
- Application Acceleration 
- BLOG: Community Talk 
- BLOG: Information Experience (iX) 
- Community Feedback 
- Contrail Platform Developers 
- Ethernet Switching 
- Identity & Policy Control - SBR Carrier & SRC 
- Intrusion Prevention 
- Junos 
- Junos Automation (Scripting) 
- Junos Space Developer 
- Junosphere 
- Management 
- Routing 
- ScreenOS Firewalls (NOT SRX) 
- SRX Services Gateway 
- Training, Certification, and Career Topics 
- vMX 
- vSRX 
- Wireless LAN 
- Juniper Open Learning 
- Day One Books Archive 
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
pem_tvp_periodic
[ Edited ]Hi,
in my chassis Logfile I've tons of those messages:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
There are two possibilities
One is communication error between the daemon who is managing LEDs and physical LEDs. The other is power supply flapping.
Are you seeing any alarm at the time of errors?
Two narrow down
1. Restart “craftd” via shell command “root% kill -9 <process ID of craftd>”
2. Reseat physically all power supplies on both FPCs
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
Ok, it must be the deamon for managing the LEDs because all LEDs are off but Ports working fine so far. I'm new in QFX and already wondering why all LEDs are off.
Maybe a hardware problem on both switches because reboot does not help to enable LEDs?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
Restart of craftd did not help:
Jan 11 14:31:51 pem_tvp_periodic cbd=9518940 slot=1, state=1
Jan 11 14:31:53 chassis_handle_peer_receive: closing connection: errno = 0
Jan 11 14:31:53 closing connection on fd 42
Jan 11 14:31:53 craftd connection completed
Jan 11 14:31:56 pem_tvp_periodic cbd=9518940 slot=1, state=1
Jan 11 14:31:56 pem_tvp_periodic cbd=9518940 slot=1, state=1
Jan 11 14:32:01 pem_tvp_periodic cbd=9518940 slot=1, state=1
Jan 11 14:32:01 pem_tvp_periodic cbd=9518940 slot=1, state=1
Jan 11 14:32:06 pem_tvp_periodic cbd=9518940 slot=1, state=1
There are no alarms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
Since the reboot of the switch and restart of process do not help this is very likely a hardware failure.
You will need to open an official support ticket with JTAC to have them verify and arrange for an RMA replacement.
https://my.juniper.net/#dashboard/servicerequests
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
This is not a hardware failure. These logs are informational and are displayed after the periodic check that confirms that that the power supply is ok. No need for a RMA or further action.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
If there is no hardware issue why are all the craft LEDs not working?
And why would an "all is good" event be logged at such a frequency?
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
Oh I missed the part about the LEDs. My response was based solely on the meaning of the messages in the initial post. The messages don't indicate a problem as I previously stated.
It would be interesting to see the output of "show chassis led" to understand what might be going on with the LEDs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
manuel@qfx5100-01> show chassis led
LED status for: FPC 0
-----------------------------------
LEDs status:
Alarm LED : Off
Beacon LED: Off
System LED: Green
Master LED: Green
Interface STATUS LED LINK/ACTIVITY LED
---------------------------------------------------------
xe-0/0/0 N/A Green
xe-0/0/1 N/A Green
xe-0/0/2 N/A Green
xe-0/0/3 N/A Green
xe-0/0/4 N/A Green
xe-0/0/5 N/A Green
xe-0/0/6 N/A Green
xe-0/0/7 N/A Green
xe-0/0/8 N/A Green
xe-0/0/9 N/A Green
xe-0/0/10 N/A Green
xe-0/0/11 N/A Green
xe-0/0/12 N/A Green
xe-0/0/13 N/A Green
xe-0/0/14 N/A Green
xe-0/0/15 N/A Green
xe-0/0/16 N/A Green
xe-0/0/17 N/A Green
xe-0/0/18 N/A Green
xe-0/0/19 N/A Green
xe-0/0/20 N/A Green
xe-0/0/21 N/A Green
xe-0/0/22 N/A Green
xe-0/0/23 N/A Green
xe-0/0/24 N/A Green
xe-0/0/25 N/A Green
xe-0/0/26 N/A Green
xe-0/0/27 N/A Green
xe-0/0/28 N/A Green
xe-0/0/29 N/A Green
xe-0/0/30 N/A Green
xe-0/0/31 N/A Green
xe-0/0/32 N/A Green
xe-0/0/33 N/A Green
xe-0/0/34 N/A Green
xe-0/0/35 N/A Green
xe-0/0/36 N/A Green
xe-0/0/37 N/A Green
xe-0/0/38 N/A Green
xe-0/0/39 N/A Green
xe-0/0/40 N/A Green
xe-0/0/41 N/A Green
xe-0/0/42 N/A Green
xe-0/0/43 N/A Green
xe-0/0/44 N/A Green
xe-0/0/45 N/A Green
xe-0/0/46 N/A Green
xe-0/0/47 N/A Green
LED status for: FPC 1
-----------------------------------
LEDs status:
Alarm LED : Off
Beacon LED: Beacon ON
System LED: Green
Master LED: Green Blinking
Phone Home LED: Green
Interface STATUS LED LINK/ACTIVITY LED
---------------------------------------------------------
xe-1/0/0 N/A Green
xe-1/0/1 N/A Green
xe-1/0/2 N/A Green
xe-1/0/3 N/A Green
xe-1/0/4 N/A Green
xe-1/0/5 N/A Green
xe-1/0/6 N/A Green
xe-1/0/7 N/A Green
xe-1/0/8 N/A Green
xe-1/0/9 N/A Green
xe-1/0/10 N/A Green
xe-1/0/11 N/A Green
xe-1/0/12 N/A Green
xe-1/0/13 N/A Green
xe-1/0/14 N/A Green
xe-1/0/15 N/A Green
xe-1/0/16 N/A Green
xe-1/0/17 N/A Green
xe-1/0/18 N/A Green
xe-1/0/19 N/A Green
xe-1/0/20 N/A Green
xe-1/0/21 N/A Green
xe-1/0/22 N/A Green
xe-1/0/23 N/A Green
xe-1/0/24 N/A Green
xe-1/0/25 N/A Green
xe-1/0/26 N/A Green
xe-1/0/27 N/A Green
xe-1/0/28 N/A Green
xe-1/0/29 N/A Green
xe-1/0/30 N/A Green
xe-1/0/31 N/A Green
xe-1/0/32 N/A Green
xe-1/0/33 N/A Green
xe-1/0/34 N/A Green
xe-1/0/35 N/A Green
xe-1/0/36 N/A Green
xe-1/0/37 N/A Green
xe-1/0/38 N/A Green
xe-1/0/39 N/A Green
xe-1/0/40 N/A Green
xe-1/0/41 N/A Green
xe-1/0/42 N/A Green
xe-1/0/43 N/A Green
xe-1/0/44 N/A Green
xe-1/0/45 N/A Green
xe-1/0/46 N/A Green
xe-1/0/47 N/A Green
{master:0}
manuel@qfx5100-01>
I'm wondering that all Ports should be "Green" because not all Ports have an aktive link.
For exmaple:
Physical interface: xe-0/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, Media type: Fiber
Device flags : Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags : None
Logical interface xe-0/0/0.0
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
eth-switch
Physical interface: xe-0/0/1, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, Media type: Fiber
Device flags : Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags : None
Logical interface xe-0/0/1.0
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
eth-switch
Physical interface: xe-0/0/2, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 9216, LAN-PHY mode, Speed: Auto, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, Media type: Fiber
Device flags : Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags : None
Logical interface xe-0/0/2.0
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
aenet
Physical interface: xe-0/0/3, Enabled, Physical link is Down
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Disabled, Remote fault: Offline, Media type: Fiber
Device flags : Present Running Down
Interface flags: Hardware-Down SNMP-Traps Internal: 0x4000
Link flags : None
Logical interface xe-0/0/3.16386
Flags: Device-Down 0x4004000 Encapsulation: ENET2
You see, "xe-0/0/3" is down. Should the LED also be Green in such state?
The repeat it: All physikal LEDs are OFF at the Front!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Re: pem_tvp_periodic
The cli view should match the led view and the actual status of the ports. So clearly there is a problem here.
It might be possible this is software and not hardware but that seems unlikely to me.
I would open an official ticket for review and request an RMA.
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home