...
- login to rddev111
- ping dtm with cmd: ping cob_dtm.
- if failed to ping the cob_dtm, could power cycle the COB
- open this switch , and the LED will turn to blue
- close this switch, and the LED will turn off in a few second, and waiting for ~1 mins, try to ping cob_dtm again
- open this switch , and the LED will turn to blue
- if failed to ping the cob_dtm, could power cycle the COB
- ping dpms with cmd: ping cob_dpmXY (as shown in the table below)
- for our setup, the cob_dpm7 is for the DPM0_rce0; cob_dpm8 is for the DPM0_rce2; the cob_dpm5 is for the DPM1_rce0; cob_dpm6 is for the DPM1_rce2; the cob_dpm3 is for the DPM3_rce0; cob_dpm4 is for the DPM3_rce2;
- if failed to ping the dpmX, need to restart it manually
- login to rddev111
ssh cob_dtm ethtool -s eth0 speed 1000 duplex full autoneg off
- setup RCE SDK with cmd: source /opt/rce/setup.sh
- manually restart rce with Cmd: cob_rce_reset [/slot[/bay[/rce]]]
- you can get help by: cob_rce_reset --help
- for our setup, the slot number is 4; if I want to restart the cob_dpm7dpm00, for example, it is the DPM0_rce0, the the bay number is 0, and rce number is 0. So, the full Cmd is "cob_rce_reset atlas-sm/4/0/0"
- waiting about 3 mins for RCE to reboot
you can also login dtm at first, them minicom to the dpm rce, with cmd: minicom bayX.Y (X is the bay number, Y is the rce number)
RCE RCE IP-name reboot cmd minicom name DPM3/RCE0 cob_dpm30 cob_rce_reset atlas-sm/4/3/0 minicom bay3.0 DPM3/RCE2 cob_dpm32 cob_rce_reset atlas-sm/4/3/2 minicom bay3.2 DPM1/RCE0 cob_dpm10 cob_rce_reset atlas-sm/4/1/0 minicom bay1.0 DPM1/RCE2 cob_dpm12 cob_rce_reset atlas-sm/4/1/2 minicom bay1.2 DPM0/RCE0 cob_dpm00 cob_rce_reset atlas-sm/4/0/0 minicom bay0.0 DPM0/RCE2 cob_dpm02 cob_rce_reset atlas-sm/4/0/2 minicom bay0.2
