Вы находитесь на странице: 1из 37

mcBSC

Monitoring
Professional training
• Antti Palojärvi
• 21-11-2016

1 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
Megamon usage

2 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• mcBSC supports megamon usage via main and extension switches.
• Megamon can not be used with mcTC

• Configuration changes are needed:


• Main and extension switch of the BCN node where megamon will be physically connected.
• Main switches of the other BCN nodes in the mcBSC
• To the IP Interfaces of the BJC-A/PCUM units in the mcBSC

MCBC-0 (BCN-A) MCBC-1 (BCN-A)

3 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• Megamon needs own VLAN_ID which needs to be configured to the BCN switches of each node in
mcBSC.
• In main switches VLAN has to be configured to CPU, HiGig and interface towards extension switch.

• Configuration example of the main switch of the interface


Enable
vlan database
// Enable prvilege mode node where megamon
0/19 // Interface will
towards MCMU
vlan participation include 3960
// Add meagmon vlan to the vlan database
0 be connected.
vlan 3960 vlan tagging 3960
vlan name 3960 "MEGAMON" exit
exit
// HiGig interfaces
Configure // Configure interfaces interface 0/1
vlan participation include 3960
interface 0/4 // Interface towards extension switch vlan tagging 3960
vlan participation include 3960 exit
vlan tagging 3960
exit interface 0/21
vlan participation include 3960
interface 0/5 // Interface towards OMU vlan tagging 3960
vlan participation include 3960 exit
vlan tagging 3960
exit interface 0/22
vlan participation include 3960
interface 0/15 // Interface towards BCXU 1 vlan tagging 3960
vlan participation include 3960 exit
vlan tagging 3960
exit interface 0/23
vlan participation include 3960
interface 0/17 // Interface towards BCXU 0 vlan tagging 3960
vlan participation include 3960 exit
vlan tagging 3960
exit interface 0/24
vlan participation include 3960
vlan tagging 3960
exit

exit

write memory
4 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
Megamon in mcBSC
• Only in the node where megamon is connected extension needs configuration changes.
• Megamon vlan has to be configured to the interface towards main switch and interface where meagmon
is connected.

• Configuration example
Enable
vlan database ofvlan
theto extension
// Enable prvilege mode
// Add meagmon the vlan databaseswitch of the node where megamon will be connected.
vlan 3960
vlan name 3960 "MEGAMON"
exit

Configure // Configure interfaces

interface 0/25 // Interface towards main switch


vlan participation include 3960
vlan tagging 3960
exit

interface 0/10 // Interace that is used as probe


no shutdown
vlan pvid 3960
vlan ingressfilter
vlan participation exclude 1
vlan participation include 3960
exit

exit

write memory

5 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• With BCN-B hardware it is recommended to use trace port as a external port for megamon.

MCBC-0 (BCN-B)

Enable // Enable prvilege mode


vlan database // Add meagmon vlan to the vlan database
vlan 3960
vlan name 3960 "MEGAMON"
exit

Configure // Configure interfaces

interface 0/28 // Inteface that is used as probe


no shutdown
description 'monitoring'
vlan pvid 3960
vlan participation include 3960
Exit

write memory

6 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• After the configuration changes in the switch are done the unit interfaces can be configured in MML.

OMU
ZQRA:OMU::VLAN3960,3960,EL0,;
ZQRN:OMU::VLAN3960:"10.40.40.3",28,P;

BCXU’s
ZQRA:BCXU,0::VLAN3960,3960,EL0,;
ZQRA:BCXU,1::VLAN3960,3960,EL0,;
ZQRA:BCXU,2::VLAN3960,3960,EL0,;
ZQRA:BCXU,3::VLAN3960,3960,EL0,;
ZQRN:BCXU,0::VLAN3960:"10.40.40.4",28,L;
ZQRN:BCXU,1::VLAN3960:"10.40.40.5",28,L;

MCMU’s
ZQRA:MCMU,0::VLAN3960,3960,EL0,;
ZQRA:MCMU,1::VLAN3960,3960,EL0,;
ZQRN:MCMU,::VLAN3960:"10.40.40.6",28,L;

7 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• GSM16 supports also megamon for PCUM’s

PCUM’s
ZQRA:PCUM,0::VLAN3960,3960,EL0,;
ZQRA:PCUM,1::VLAN3960,3960,EL0,;
ZQRA:PCUM,2::VLAN3960,3960,EL0,;
ZQRA:PCUM,3::VLAN3960,3960,EL0,;
ZQRA:PCUM,4::VLAN3960,3960,EL0,;
ZQRN:PCUM,0::VLAN3960:"10.40.40.9",28,L;
ZQRN:PCUM,1::VLAN3960:"10.40.40.10",28,L;

8 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• GIVAXI application is the interface point in mcBSC for the megamon.
• GIVAXI need to have authentication key created and it is monitoring either port 8019 or 8021 depending
on SW version.
Authentication key creation: Check that TCP port usage is activated
TCP/IP STACK DATA HANDLING COMMAND <QR_> ZWOI:2,2093;
< ZQ4A:GIVAXIPSK,S:K:H;
IDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY
LOADING PROGRAM VERSION 7.1-0 02093 GIVAXI_PORT 00FF YES

ENTER KEY(MAX 64 HEXADECIMAL DIGITS):


11111111112222222222333333333344444444445555555555666 < QRS:MCMU,1;
66666667777
LOADING PROGRAM VERSION 27.3-0
COMMAND EXECUTED
mcBSC mcKOFF 2014-11-28 10:42:58
Note!: Length of the key has to be 64 digit and
exactly the same as defined in Megamon. UNIT: MCMU-1

Active Internet connections (including servers)


Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 *.8019 *.* LISTEN

!Note. Port 8021 in GSM16

9 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC
• For each BSC there has to be connection created in Megamon tool.
• MCMU IP, port and GIVAXI key have to match with the BSC.
• Also VLAN has to be noted in the Externa interface configuration.

10 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC PCUM support in GSM16
• In GSM16 only PDM and RCH applications are supported.
• This means no detailed Gb/Abis or DSP monitoring possibility with Megamon.
• PCU filters are set to own ini file via setup menu.
• Some filtering examples:
• TBF monitoring from all segments from PDM:
PDM(TBF)
• TBF monitoring from segments 1,2 &3 from PDM:
PDM(TBF:SEG=1&2&3)
• PDM log monitoring from segments 1,2&3 with log levels warning, error and critical:
PDM(LOG:SEG=1&2&3:LL=1&6&11)
• TBF monitoring from all applications where support exists
srv(TBF:SEG=1&2&3)
• TBF, Log and IPC message monitoring from all applications where support exists
srv(TBF:SEG=1&2&3,LOG:SEG=1&2&3:LL=1&6&11,IPC:SEG=1&2&3)

11 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon in mcBSC PCUM support in GSM16
• Actual setting of filters in tool and enabling the PCU monitoring.

12 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Megamon exrecises
• Exercise 1.
• Configure Megamon to mcBSC and verify that all the BJC-A units are reachable from Megamon.

• Exercise 2.
• Setup Megamon to monitor AIV and ABI.
• Make a MO call
• Check from the megamon logs that what is the Transport Layer IP assigned in Assignment Request.

• Exercise 3.
• Use Megamon for taking logs of TCSU recreation.
• MCMU: PUB & TFH
• BCXU: IMI

13 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
mirroring

14 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Monitoring external traffic

• Actual trace is taken with laptop / PC with wireshark from 1G probe port.
• Redundant connection to site equipment has to be disabled while trace is
taken.
MCBC-0 MCBC-1

Redundant interfaces in MCBC-1 has to be disabled while trace is


Mirroring
Actual traffic. taken by shutting down the ports in extension switch or in site
equipment.

15 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Monitoring external traffic

• Monitoring of external traffic can be done in BCN module with mirroring directly from
BCN’s extension
Configuration switch.
of mirroring in extension switch
(HusaBox1ExtSwitch) #configure
(HusaBox1ExtSwitch) (Config)# monitor session 1 destination interface 0/6
(HusaBox1ExtSwitch) (Config)# monitor session 1 source interface 0/25
(HusaBox1ExtSwitch) (Config)# monitor session 1 source interface 0/26
(HusaBox1ExtSwitch) (Config)# monitor session 1 mode
(HusaBox1ExtSwitch) #show monitor session 1

Session ID Admin Mode Probe Port Mirrored Port Type


---------- ---------- ---------- ------------- -----
1 Enable 0/6 0/25 Rx,Tx
0/26 Rx,Tx

This setting will mirror all the traffic between main & extension switch to port 6 which is SFP 12.

• With the described example all the traffic is mirrored to probe port 0/6 (SFP12).
• Port load can be decreased by mirroring only either one of the ports towards main switch
based on the fault under investigation.
• Note that in BCN-A the ext ports are 1G ports therefore in fully equipped mcBSC port
might not be able to handle full traffic between main and extension switch.
16 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID
Confidential
Monitoring external traffic exercises

• Configure mirroring so that Gb and Abis are mirrored into the same port.
• Take log from short GPRS transaction.

17 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
DPDUMP

18 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
DPDUMP 1/2
• DPDUMP service terminal extension in BJC-A plug in units can be used for interface monitoring within
the unit.
• With DPDUMP it is possible to monitor, DHCP, TCP and SNMP activity in mcBSC.
• Before DPDUMP logs can be read with wireshark it has to be converted with d2w software.
Example how to use DPDUMP for monitoring Vlan20 in OMU
ZDDS:OMU;
ZLE:2,DPDUMPGX
Z2T:-xx,-s,0,-n,-i,vlan20

Vlan 20 is used for management, control, dhcp and SW loading for BOC-A’s. Note, OMU is not loading source for BOC-A or BMPP2-B

More information and examples can be found from DPDUMP help:


0000-DPD> Z2?T
T:<options>

Most of the tcpdump options work. Check man pages:


http://www.tcpdump.org/tcpdump_man.html

Typical options:
-c Exit after receiving count packets.
-i Listen on interface. If unspecified, tcpdump searches the system interface list for the lowest numbered,
configured up
interface (excluding loopback). Ties are broken by choosing the earliest match.
-n Don't convert addresses (i.e., host addresses, port numbers, etc.) to names.

19 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
DPDUMP 2/2
• DPDUMP can be used also to take external trace directly from the unit for example Sigtran or Abis.
• It is highly recommended to use tcpdump filters to avoid loading the unit from where the trace is taken
from.how to use DPDUMP for monitoring Abis interface for one IUA association.
Example
ZDDS:OMU;

ZOYV:IUA::A; //Check association


SCTP ASSOCIATION ASSOC SCTP PARAMETER SET
NAME IND UNIT USER ROLE NAME STATE
---------------- ----- ------- ----- ------ ---------------- -------------
BTS1OM1 0 BCXU-3 IUA SERVER AFAST ASP-ACTIVE

SOURCE ADDRESS 1 . . . . . . . : 10.9.192.85

ZDDS:BCXU,3;
ZLE:2,DPDUMPGX
//In the actual DPDUMP the interface is the OMU/TRX-SIG VLAN and filtering is done by VLAN IP in BCXU
Z2T:-xx,-s,0,-n,-i,vlan3944,src,10.9.192.85,or,dst,10.9.192.85

20 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
DPDUMP exrecises
• Exercise 1.
• Take DPDUMP from BOC-A restart and analyze with wireshark the IP allocated to the unit.

• Exercise 2.
• Take DPDUMP log from external alarm SNMP trap

• Exercise 3.
• Take DPDUMP from CS data call establishment signaling and point the transport layer IP in MGW.

21 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
OFL usage

22 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL 1/2
• OFL tool need to be occasionally used for taking logs from PCUM, ETMA & ETME.
• Improvement that the usage of OFL brings is that with OFL higher log levels can be used because log
writings are forwarded directly from unit to the PC in monitoring interface.
• Monitoring PC has to be in the same IP subnet as the PCUSIG.
• With BCN-B the trace port can be used for OFL meaning that only changes in configuration are needed
for trace port.
• With BCN-A instead the signaling vlan 20 has to be defined and configured in extension switch which is
not Nokia default.
• In the BCN-A example below the signaling vlan 20 goes from main to extension switch via interface pair 0/4
BCN-A and 0/25
example BCN-A example:
Needed configuration changes in main switch Needed configuration changes in extension switch
(MainSwitch1) #configure (Extensionswitch1)#vlan database
(MainSwitch1) (Config)#interface 0/4 (Extensionswitch1)(Vlan)#vlan 20
(MainSwitch1) (Interface 0/4)#vlan participation include 20 (Extensionswitch1)(Vlan)#vlan name 20 signaling
(MainSwitch1) (Interface 0/4)#vlan tagging 20 (Extensionswitch1)(Vlan)#exit
(MainSwitch1) (Interface 0/4)#exit (Extensionswitch1)#configure
(MainSwitch1) (Config)#exit (Extensionswitch1)(Config)#interface 0/25
(MainSwitch1) # (Extensionswitch1)(Interface 0/25)#vlan participation include 20
(Extensionswitch1)(Interface 0/25)#vlan tagging 20
(Extensionswitch1)(Interface 0/25)#exit
(Extensionswitch1)(Config)#interface 0/6
(Extensionswitch1)(Interface 0/6)#vlan participation include 20
(Extensionswitch1)(Interface 0/6)#vlan pvid 20
(Extensionswitch1)(Interface 0/6)#exit
(Extensionswitch1)(Config)#exit
(Extensionswitch1)#

23 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL 2/2
BCN-B example
Configuration of the OFL monitoring port
(KaskiMainSwitch2) >ena
Password:
(KaskiMainSwitch2) #configure
(KaskiMainSwitch2) (Config)#interface 0/28
(KaskiMainSwitch2) (Interface 0/28)#no shutdown
(KaskiMainSwitch2) (Interface 0/28)#description 'Monitoring‘
(KaskiMainSwitch2) (Interface 0/28)#mtu 1538
(KaskiMainSwitch2) (Interface 0/28)#vlan pvid 20
(KaskiMainSwitch2) (Interface 0/28)#vlan participation include 20
(KaskiMainSwitch2) (Interface 0/28)#exit
(KaskiMainSwitch2) (Config)#exit
(KaskiMainSwitch2) #

24 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL
• To define which IP address could be given to the monitoring PC check the current VLAN20 configuration.
< QRI:MCMU,1::VLAN20:;

LOADING PROGRAM VERSION 27.3-0

mcBSC DX220-LAB 2014-10-21 13:41:44

INTERROGATING NETWORK INTERFACE DATA

UNIT ADMIN ADDR


INTERFACE STATE MTU ATTR IP ADDRESS
------------ ----- ----- -------- ---------------------------------------------
MCMU-1
VLAN20 UP 1500 LIM 10.0.1.2/25
->EL0 20 0/0

COMMAND EXECUTED

• In the example above VLAN 20 is using /25 subnet as instructed in the guidelines therefore the client
IP’s can be 10.0.1.1 - 10.0.1.126.
• For the monitoring PC pick unused IP from the client IP’s and configure it to the PC.
• Connect the PC to the monitoring port in BCN and verify that PC is able to ping the unit which shall be
monitored.
• Note! Check that there is no firewall settings in monitoring PC that could prevent the vlan 20 traffic.

25 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL
• Run the ofl.exe in the monitoring PC.
Syntax:
ofl.exe < filename> <port> -s <size>
Where filename is the name of the pq2 log file
port is the port_number where this machine would listen to the BSC for the logs(any port not used by other utilities)
size is the size MB of each log file created. The utility will automatically create a new file after the logs file reach the defined limit.

• In the monitored unit define the needed log levels and forward the logs to the monitoring PC.
Example where pq2 logs from PCUM are redirected to PC with IP 10.0.1.125 port 4444
PCUM-A/2/10.0.1.22>rpq2l 10.0.1.125 4444
PQ2 logs will be redirected to 10.0.1.125:4444

Example where dsp logs from PCUM are redirected to PC with IP 10.0.1.125 port 4444
PCUM-A/2/10.0.1.22>rdspl 10.0.1.125 4444
PQ2 logs will be redirected to 10.0.1.125:4444

Example where pq2 logs in ETME are redirected to PC with IP 10.0.1.125 port 4444
ETME-A/0>rmcl 10.0.1.125 4444
PQ2 logs will be redirected to 10.0.1.125:4444

• Note that there are separate binaries for pcum/etm units as well for win32/win64 and linux.
Redirecting is disabled by useing redirecting command without parameters:
PCUM-A/2/10.0.1.22>rpq2l
Redirection of PQ2 logs disabled…

26 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL
• Example configuration for BCN-A where SFP+6 is used as a monitoring port
interface 0/2
no auto-negotiate
no shutdown
description 'monitoring'
spanning-tree bpdufilter
mtu 1538
vlan pvid 20
vlan participation include 20
exit

27 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
OFL Exercises
• Exercise 1:
• Configure the OFL to be used in unused SFP+ port of the BCN node
• Take PCUM, ETME and ETMA logs with OFL with following logs levels.
• PCUM: sll pq2 1:6:11 // Warning, Error, Critical for all the aplications
• PCUM: sll pq2:17 1:2:6:11  // Warning, Info1, Error and Critical for PDM   

28 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
System Event Log SEL &
Sensors

29 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
SystemEventLog SEL

• System Event Log contains information about changes in power feeding,


restarts, external alarms etc.
• SEL log can be printed out with ipmitool and mch_cli and filtered normally with
grep.
ipmitool
root@BCNMB-A:~# ipmitool sel list
1 | 05/23/2014 | 15:37:15 | Platform Alert #0xfe | Pair 0 alarm | Deasserted
2 | 05/23/2014 | 15:37:15 | Platform Alert #0xfe | Pair 1 alarm | Deasserted
3 | 05/23/2014 | 15:37:22 | Platform Alert #0xfe | Pair 1 alarm | Asserted
4 | 05/23/2014 | 15:37:23 | Platform Alert #0xfe | Pair 0 alarm | Asserted
5 | 05/27/2014 | 14:11:00 | Platform Alert #0xfe | Pair 0 alarm | Deasserted

mch_cli
root@BCNMB-A:~# mch_cli SEL list
1 | 05/23/2014 | 15:37:15 | BCNMB-A | Main Board | Platform Alert #0xfe "External alarm" | Pair 0 alarm | Deasserted
2 | 05/23/2014 | 15:37:15 | BCNMB-A | Main Board | Platform Alert #0xfe "External alarm" | Pair 1 alarm | Deasserted
3 | 05/23/2014 | 15:37:22 | BCNMB-A | Main Board | Platform Alert #0xfe "External alarm" | Pair 1 alarm | Asserted
4 | 05/23/2014 | 15:37:23 | BCNMB-A | Main Board | Platform Alert #0xfe "External alarm" | Pair 0 alarm | Asserted
5 | 05/27/2014 | 14:11:00 | BCNMB-A | Main Board | Platform Alert #0xfe "External alarm" | Pair 0 alarm | Deasserted

root@BCNMB-A:~# mch_cli SEL list | grep "Cold reset"


58 | 06/12/2014 | 14:24:29 | BJC-A | CPU Slot 2 | System Event #0x81 "Cold reset" |
59 | 06/12/2014 | 14:24:29 | BJC-A | CPU Slot 3 | System Event #0xa1 "Cold reset" |
5a | 06/12/2014 | 14:24:29 | BJC-A | CPU Slot 1 | System Event #0x61 "Cold reset" |
5d | 06/12/2014 | 14:24:29 | BJC-A | CPU Slot 8 | System Event #0x51 "Cold reset" |

30 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
SystemEventLog SEL

• External alarm in SEL


In the example below external alarm switch has been opened for 6sec
root@BCNMB-A:~# mch_cli SEL list
1 | 11/28/2013 | 16:11:50 | Platform Alert #0xfe | Pair 0 alarm | Deasserted
2 | 11/28/2013 | 16:11:56 | Platform Alert #0xfe | Pair 0 alarm | Asserted

root@BCNMB-A:~#

• Voltage issues in SEL


root@BCNMB-A:~# mch_cli SEL list | grep "Voltage"
9d2 | 11/28/2013 | 10:23:24 | Voltage #0x17 | Lower Non-recoverable going low | Reading 1.27 < Threshold 1.00 volts
9d3 | 11/28/2013 | 10:23:24 | Voltage #0x18 | Lower Non-recoverable going low | Reading 1.01 < Threshold 0.70 volts
9d4 | 11/28/2013 | 10:23:26 | Voltage #0x1a | Lower Non-recoverable going low | Reading 144 < Threshold 44 volts
9d5 | 11/28/2013 | 10:23:26 | Voltage #0x1e | Lower Non-recoverable going low | Reading 3.19 < Threshold 3.00 volts

31 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
SystemEventLog SEL

• Add-in card restarts and FRU state changes are also visible in SEL
root@BCNMB-A:~# mch_cli SEL list | grep "CPU Slot 8"
1 | 06/17/2014 | 13:02:18 | BCNOC-A | CPU Slot 8 | System Boot Initiated #0x4d "RESET_TYPE" | Initiated by hard reset | Asserted
2 | 06/17/2014 | 13:02:33 | BCNOC-A | CPU Slot 8 | OS Boot #0x4c "BOOT" | U-boot ready | Asserted
3 | 06/17/2014 | 13:03:34 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M5 from M4 cause 3 | Asserted
4 | 06/17/2014 | 13:03:35 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M6 from M5 cause 1 | Asserted
5 | 06/17/2014 | 13:03:37 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M1 from M6 cause 0 | Asserted
6 | 06/17/2014 | 13:03:49 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M2 from M1 cause 2 | Asserted
7 | 06/17/2014 | 13:03:51 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M3 from M2 cause 1 | Asserted
8 | 06/17/2014 | 13:03:52 | BCNOC-A | CPU Slot 8 | System Boot Initiated #0x4d "RESET_TYPE" | Initiated by hard reset | Asserted
9 | 06/17/2014 | 13:03:53 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M4 from M3 cause 0 | Asserted
a | 06/17/2014 | 13:04:05 | BCNOC-A | CPU Slot 8 | OS Boot #0x4c "BOOT" | U-boot ready | Asserted
root@BCNMB-A:~#

SEL records1 & 2 above are written in case in unit is restarted with ZUSU
SEL records 3 to A are related to case where BOC-A add-in card was deactivated and activated from LMP and add-in card FRU state changes.

FRU states:
M0 = FRU not installed (Add-in card status LED Off)
M1 = FRU installed but inactive (Color of status LED: Blue)
M2 = Waiting for activation request (Color of status LED: Blue)
M3 = Activation in progress
M4 = Active (Color of status LED: Red, Green for application usage)
M5 = Waiting for deactivation request (Color of status LED: Red)
M6 = Deactivation in progress (Color of status LED: Red)

32 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
SystemEventLog SEL

• More details can be printed with SEL get


root@BCNMB-A:~# mch_cli SEL list | grep "cause 3"
3 | 06/17/2014 | 13:03:34 | BCNOC-A | CPU Slot 8 | FRU Hot Swap #0x38 "Hot Swap AMC 8" | Transition to M5 from M4 cause 3 | Asserted

root@BCNMB-A:~# mch_cli SEL get 0x3


SEL Record ID : 0003
Record Type : 02
Timestamp : 06/17/2014 13:03:34
Generator ID : 0020
EvM Revision : 04
Sensor Type : ATCA Hotswap
Sensor Number : 38
Event Type : Sensor-specific Discrete
Event Direction : Assertion Event
Event Data (RAW) : 05340C
Event Interpretation Missing
Description : Transition to M5

Sensor ID : Hot Swap AMC 8(0x38)


Entity ID : 193.104
Sensor Type (Analog) : ATCA Hotswap
Sensor Reading :
States:

• Note that the grep’s in previous pages are just examples how to read the SEL.

33 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Sensors

• BCN and add-in cards have various sensors for Voltage, Temperature watchdog
etc.
• Status of these can be investigated via ipmitool and mch_cli
Ipmitool
root@BCNMB-A:~# ipmitool sensor
Sensor Name | Reading | Measuring | State | LNR | LCR | LNC | UNC | UCR | UNR
-----------------|------------|------------|-------|-----------|-----------|-----------|-----------|-----------|--------
PEX Temp | 48.000 | degrees C | ok | na | na | na | 105.000 | 110.000 | 115.000
LMP Temp | 45.000 | degrees C | ok | na | na | na | 86.000 | 91.000 | 96.000
BCM56512 Temp | 50.000 | degrees C | ok | na | na | na | 110.000 | 115.000 | 120.000
BCM56820 Temp | 71.000 | degrees C | ok | na | na | na | 105.000 | 110.000 | 115.000

3.3SB | 3.325 | Volts | ok | 3.012 | 3.084 | 3.156 | 3.470 | 3.542 | 3.614
1.1V | 1.092 | Volts | ok | 0.900 | na | na | na | na | 1.500
1.8V | 1.828 | Volts | ok | 1.500 | na | na | na | na | 2.004
0.9V | 0.924 | Volts | ok | 0.700 | na | na | na | na | 1.100
12V | 12.033 | Volts | ok | 11.225 | na | na | na | na | 12.841

34 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
Sensors

• Ipmitool gives quick list of sensors and their status.


• mch_cli instead can be used for more detailed troubleshooting
mch_cli
ShowSensor gives the list of available sensors, Logical Unit Number and sensor number
root@BCNMB-A:~# mch_cli ShowSensor
Entity: CPU 8
...
VCC CPU0 0x01 0x4b
1.05V 0x01 0x50
12V 0x01 0x4a
1.5V 0x01 0x49
1.8V 0x01 0x4d
5V 0x01 0x44
...

ReadSensor command give details for the particular sensor


root@BCNMB-A:~# mch_cli ReadSensor 1 0x4a
Sensor: 12V
Lun: 0x01
Number: 0x4a
Value: 11.940000

Syntax: mch_cli ReadSensor <lun> <sensor number>

35 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
mcBSC
tcpdump

36 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential
tcpdump
• TCPDUMP is used to record trace from BCN unit ifeth or vlan interfaces.

In the example above Vlan800 SNMP port is monitored with tcpdump in LMP
tcpdump -i eth0.800 -s 0 port 162 -w capture.pcap
Interface = vlan800, port = 162, file = capture.pcap

NOTE! It is good idea to log into the file in /tmp folder.

37 8/18/19 © Nokia 2014 - File Name - Version - Creator - DocID


Confidential

Оценить