Scribd
Upload
50 views

Line Protocol: Cacti Logs Types of Logs

The document contains logs from various network devices with information about different types of issues: - Interface status changes, fiber/module issues, VLAN flapping due to access topology loops, temperature alarms and power supply failures. - The logs would need to be reviewed and the relevant teams engaged to address issues like port channel misconfigurations, ASIC card errors and prolonged interface outages. - Recurring errors may require engaging the packet team to further investigate and resolve network problems.

Uploaded by

Wateen DataNoc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
50 views

Line Protocol: Cacti Logs Types of Logs

The document contains logs from various network devices with information about different types of issues: - Interface status changes, fiber/module issues, VLAN flapping due to access topology loops, temperature alarms and power supply failures. - The logs would need to be reviewed and the relevant teams engaged to address issues like port channel misconfigurations, ASIC card errors and prolonged interface outages. - Recurring errors may require engaging the packet team to further investigate and resolve network problems.

Uploaded by

Wateen DataNoc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Cacti Logs

Types of Logs

Mar 1 10:05:01 Lah-Khalid-Plaza-H11-P76R2[58.27.191.216]


040402: Mar 1 10:04:36.067 GMT: %LINEPROTO-5-UPDOWN: Line
protocol on Interface TenGigabitEthernet3/1, changed state to down

Mar 1 14:57:31 Kar-12816-p1[58.27.191.31] 030827: Mar 1


14:57:04.334 GMT: %OSPF-5-ADJCHG: Process 1, Nbr Isb-12816-
p1[58.27.191.57] on GigabitEthernet5/0/4 from FULL to DOWN,
Neighbor Down: BFD node down

Feb 28 08:54:42 Sheikhupura-ME3400B[58.27.180.54] :


%SW_MATM-4-MACFLAP_NOTIF: Host 001e.13e5.7e40 in vlan 2134
is flapping between port Gi0/16 and port Gi0/3

Feb 28 20:21:34 Lah-hdc-7609-intgw02[58.27.190.190] 133089: Feb


28 20:21:06.676 GMT: %OIR-SP-3-PWRCYCLE: Card in module 5, is
being power-cycled (Module reset)

Feb 26 07:18:31 Lah-Near-UET-H09-P76R2[58.27.191.215] 022457:


Feb 26 07:18:05.326 GMT: %C6KENV-SP-4-MINORTEMPALARM:
module 1 inlet temperature crossed threshold #1(=45C). It has
exceeded normal operating temperature range.

Feb 28 02:24:20 Kar-GGC-3850-SW1[58.27.182.70] GMT: %LINK-3-


UPDOWN: Interface TenGigabitEthernet1/0/1, changed state to
down

Feb 27 17:00:42 Guj-me3750-01[172.22.32.60] 006275: Feb 27


17:00:16.392 GMT: %POWER_SUPPLIES-5-PWR_OK: Power supply B
is functioning

Feb 27 15:31:56 Kar-7609-intgw2[58.27.190.242] 100996: Feb 27


15:31:30.895: %C7600_PWR-SP-2-PSFAIL: power supply 1 output
failed.

Feb 27 15:31:56 Kar-7609-intgw2[58.27.190.242] 100997: Feb 27


15:31:30.895: %C7600_PWR-SP-4-PSREDUNDANTONESUPPLY: in
power-redundancy mode, system is operating on one power supply.

Feb 27 12:19:11 Skt-7609-PE1[58.27.191.9] 029507: Feb 27


12:19:28.193 GMT: %PM-SP-4-ERR_DISABLE: pagp-flap error
detected on Gi9/8, putting Gi9/8 in err-disable state

Feb 27 12:19:12 Skt-7609-PE1[58.27.191.9] 029508: Feb 27


12:19:28.312 GMT: %PM-SP-STDBY-4-ERR_DISABLE: pagp-flap error
detected on Gi9/8, putting Gi9/8 in err-disable state
Feb 26 13:40:35 Lah-hdc-6513-dc2[58.27.190.192] 163410: Feb 26
13:40:09.628 GMT: %SIBYTE-DFC3-3-CORRECTABLE_ECC_ERR: A
correctable ECC error has occurred, A_BUS_L2_ERRORS: 0x0,
A_BUS_MEMIO_ERRORS: 0xFF, A_SCD_BUS_ERR_STATUS:
0xC0DC3000
Cacti Logs
Description

Fiber/Sfp issue/module issue

Fiber/module issue

Vlan flapping due to access topology issue (Loop in access end topology)

Physical Hardware failure Issue

Temperature issue

Not in packet control, but port shouldn’t be down for long.

Power supply / power issue

Power supply issue

Port channel configuration issue


ASIC card errors
Action Taken

Engage relevant team. OFC/Packet

Engage relevant team. OFC/Packet

Not relevant

Engage packet (Critical)

Engage Infra team asap

Engage packet if port is down from 3 4 hours

Engage packet/infra accordingly.

Engage packet (Critical)

If core then engage packet accordingly.


If multiple logs observed engage packet accordingly

You might also like