No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Error Logs for the NX112 Are Found

Publication Date:  2015-06-25 Views:  69 Downloads:  0
Issue Description
Hardware configuration:
Two E6000 servers configured with NX112 switch modules

Networking:

Four NX112 switch modules are stacked for the A switching planes of two E6000 servers and connect to the S5352 switches at the peer end, as shown in Figure 1.

Figure 1 Networking diagram



Run the display logbuffer summary command on the NX112 to check log information in the log buffer. There are 80 errors and 146 warnings, which are highlighted in bold in the following command output.

[H1_E6000_1_A1]display logbuffer summary
      SLOT EMERG ALERT  CRIT ERROR  WARN NOTIF  INFO DEBUG
         0     0     0       0    80      146     0      0     0
         3     0     0       0     0        0     0      0     0
         0     0     0       0     0        0     0      0     0
         1     0     0       0     0        0     0      0     0
         2     0     0       0     0        0     0      0     0
Handling Process
1.  Run the display logbuffer command to display the NX112 logs. The command output is as follows:

Oct  1 2008 00:02:32-05:13 H1_E6000_1_A1 %%01SRM/3/INOUT(l)[0]:The optical module on interface GigabitEthernet3/0/20 is plugged IN.
Oct  1 2008 00:02:32-05:13 H1_E6000_1_A1 %%01SRM/3/INOUT(l)[1]:The optical module on interface GigabitEthernet3/0/19 is plugged IN.
¡­¡­
Oct  1 2008 00:02:30-05:13 H1_E6000_1_A1 %%01SRM/3/INOUT(l)[18]:The optical module on interface GigabitEthernet3/0/2 is plugged IN.
Oct  1 2008 00:02:30-05:13 H1_E6000_1_A1 %%01SRM/3/INOUT(l)[19]:The optical module on interface GigabitEthernet3/0/1 is plugged IN.The number highlighted in bold indicates that the


log level is error. These logs record plug-in information about ports 1 to 20. The information is normal.

Oct  1 2008 00:06:21-05:13 H1_E6000_1_A1 %%01IFNET/4/IF_STATE(l)[0]:Interface GigabitEthernet1/0/21 has turned into UP state.
Oct  1 2008 00:06:21-05:13 H1_E6000_1_A1 %%01IFNET/4/IF_STATE(l)[1]:Interface GigabitEthernet2/0/21 has turned into UP state.
¡­¡­
Oct  1 2008 00:02:18-05:13 H1_E6000_1_A1 %%01IFNET/4/IF_STATE(l)[29]:Interface GigabitEthernet0/0/3 has turned into UP state.
Oct  1 2008 00:02:18-05:13 H1_E6000_1_A1 %%01IFNET/4/IF_STATE(l)[30]:Interface GigabitEthernet0/0/2 has turned into UP state.The number highlighted in bold indicates that the log level is warning. These logs record the information of ports that are in the UP state. The information is normal.


Log analysis conclusion: These logs record port status information when the NX112 is powered on normally. No handling is required.

2.  Run the display logbuffer command to display the S5352 logs. The command output is as follows:

Mar 21 2012 14:16:37-05:13 H1_S5352_1 %%01SRM/3/RXPOWER_EXCEEDMINOR(l)[0]:Optical module in interface XGigabitEthernet0/1/1 exception, RX power too low.

The number highlighted in bold indicates that the log level is error. An exception occurs on the optical port, which may be caused by the removal and reinsertion of the optical fiber. The customer confirms that the optical fiber has been removed and reinserted.

Mar 23 2012 17:57:18-05:13 H1_S5352_1 %%01DEFD/4/CPCAR_DROP_MPU(l)[12]:Some packets are dropped by cpcar on the MPU. (Protocol=reserved-multicast, Drop-Count=080)
Mar 23 2012 17:37:18-05:13 H1_S5352_1 %%01DEFD/4/CPCAR_DROP_MPU(l)[13]:Some packets are dropped by cpcar on the MPU. (Protocol=reserved-multicast, Drop-Count=0212)
Mar 23 2012 17:27:18-05:13 H1_S5352_1 %%01DEFD/4/CPCAR_DROP_MPU(l)[14]:Some packets are dropped by cpcar on the MPU. (Protocol=reserved-multicast, Drop-Count=073)


The number highlighted in bold indicates that the log level is warning. Too many packets are sent to the CPU, and the CPU drop some packets. The customer confirms that the switch has been configured with loops, which causes this problem. Currently, the problem does not occur.

Log analysis conclusion: This problem is caused by abnormal configuration or misoperations, which has no impact on services.

3.  Command output of the dis logbuffer summary command first displays information about the master stacking switch module and then displays information about all other boards. When information about all other boards is displayed, information about the master stacking switch module is displayed again, and no log is displayed. This problem occurs in the the NX112 software version V100R005C01SPC100 and has been resolved in the V200R001C00 version.
Root Cause
Error and warning logs are generated because the customer has removed and reinserted the optical fiber and configured the switches with loops.

Suggestions
The error or warning logs of the NX112 do not mean that the device has faults. You can determine whether handling is required by viewing the log severity.

Note:

Logs are classified into eight levels by severity. A smaller value indicates a severer log, as described in Table 1. After a device is powered off, all log information in the log buffer is deleted.

Table 1 Log level definition 




The method for viewing a log level is as follows:

Run the display logbuffer command.

Oct  1 2008 05:11:33-05:13 NX112_LSW %%01SRM/3/INOUT(l)[3]:The optical module on interface GigabitEthernet0/0/20 is plugged IN.

The number highlighted in bold indicates the log level.

END