In order to find out info of SFP installed in the Junos machine without taking out the SFP module, do the following commands:
- Log in to the shell of the relevant FPC. For this example I’ll use fpc4:
master@SW-QFX5100> start shell pfe network fpc4
(vty)# show sfp list
SFP Toolkit summary:
wakeup count: 47223201, debug: 0, periodic enabled: 1, diagnostics enabled: 1
thread: 0x03deaa78, itable: 0x03ddd868, itable iterator: 0, sem: 0x03e36fe8
polling interval delay: 1000 ms, polling max cpu: 100 ms
poll for diags every 3 wakeups , SFPs polled for diags last time: 2
last periodic CPU time: 1 ms, maximum periodic CPU time: 82 ms
SFP Toolkit syslog throttling parameters:
period: 120 samples , disable threshold: 10, enable threshold 0
Index Name Presence ID Eprom PNO SNO calibr
—– ————– ———- ——– ———- ———– ——-
1 Uplink SFP+ PIC(2) Present Complete 740-021333 AB33333 int
2 Uplink SFP+ PIC(3) Present Complete 740-021222 AB22222 int
I2C Acceleration table
Index Name Presence ID Eprom Reg ID I2C Master I2C Group
—– ————– ———- ——– ——– ———— ——-
(vty)# show sfp 1 ?
<carriage return> Completes command
alarms SFP diagnostics alarms
diagnostics display diagnostic measurements and thresholds
info SFP information
- You can use only “show sfp <index of installed sfp>” and you’ll get those kind of information for example:
First , in order to troubleshoot this issue , you need to be sure that ssh is enabled . How ?
- power off the machine from VMware workstation or vSphere , or suspend it.
- power it on
- after entering user/pass , you’ll be asked to select which mode to enter , check security (5)
- if appears disable ssh , then ssh is enabled . if not , then enable it .
- if then is not your problem , then enter the debugging mode (7) and do the following:
write down the command : $ ls -al /etc/ssh/ssh*key
if appears nothing , or zero as it shows in the picture , then you need to re-generate ssh key using the following command:
sudo ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
and then click Enter twice .
This should solve your problem .
If not , back to “secuirty (5)” section , and try disabling firewall .
Note: For more information regarding ssh keys , visit the following site.
Within the Junos Space you can find all the .conf files ‘Configuration Files > Config Files Management’ path . But you want to back it up via bach/script file that runs automatically instead of exporting it from the Space GUI , and you don’t know where those files are stored in the JS directories :
First, good luck with that 🙂
Second, here is the path :
# cd /usr/local/jboss/domain/tmp/servers/server1/.conf/RCS/
This is a description to solve this problem in KB : KB28018
But beside that , lets talk about another situation were this error message might appear.
This error message will also appear when you’re trying to configure both VPN Tunneling and WSAM in the same rule and trying to connect via NC
While you’re trying to backup your Junos Space VM machine via the VMware Tools, and you receive the following error:
FTL – vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
as part of my research in Junos space resources I can see that “Junos Space Network Management Platform is not certified to be used with VMware tools”
This should work From Junos Space Network Management Platform Release 16.1R1 onward.
The following MIB2D error is viewed in the log messages:
VC10 mib2d: MIB2D_KVM_FAILURE: tu_kread: kvm_read returns error: short read
Here is a description of the problem:
The error is generated because SNMP is trying to collect data on the TCP connections of the switch and this data might be incorrect.
What actually is happening is that mib2d is working on 32 bits whereas the kernel is using 64 bits.
When mib2d is requesting data from the kernel, it’s receiving an 8byte pointer, which is truncated by mib2d to 4 byte pointer.
Then the mib2d is requesting that data by providing the 4 byte pointer. If that pointer doesn’t exist, then this message is returned.
The work-around for this is the following steps:
These two commands will restart both the snmp and mib2d process. There will be no traffic impact doing this. Should this not work, you will want to reboot the switch.
This is not a permanent fix however and the messages may reappear in some time.
This bug has been reported and deal in this PR 1007305 [Confidential, Mistaken] – “DAEMON-3-MIB2D_KVM_FAILURE: tu_kread: kvm_read returns error: short read” messages seen in the logs
A more robust approach for mib2d to gather kernel information was implemented in Junos version R15.1
The fix for this situation is in Junos 15.1 version.
Please do an upgarde.
You can’t ping between two fxp interfaces in SRX cluster mode because the secondary node routing subsystem is not running… the backup-router configuration statement canbe used.
set system backup-router <gateway_ip> destination <your_source_network>
See page 15 of this PDF document