Options

log unknown

REDES_STI_UCHILEREDES_STI_UCHILE Member ✭
in System
Hello,
Today I have a problem with A10 Networks version 2.7.1-P1. when I saw the information about "#show log", I didn't understand the problem because I never had seen the following information:

Sep 21 2015 09:18:31 Notice [LOGGING]:A10LOGD received partition creation event from daemon.
Sep 21 2015 09:18:31 Notice [LOGGING]:A10LOGD received partition creation event from daemon.
Sep 21 2015 09:18:31 Notice [LOGGING]:A10LOGD received partition creation event from daemon.
Sep 21 2015 09:18:31 Notice [LOGGING]:A10LOGD received partition creation event from daemon.
Sep 21 2015 09:18:22 Notice [SYSTEM]:A cli session for user "admin" from 127.0.0.1 has been opened. Session ID assigned is 1.
Sep 21 2015 09:18:22 Info [COMPRESSION]:Hardware compression device not installed on AX
Sep 21 2015 09:18:17 Info [GSLB]:Initialization done
Sep 21 2015 09:18:17 Info [Fail Safe]:Fail Safe is initialized.
Sep 21 2015 09:18:15 Info [VCS]:aVCS daemon start running
Sep 21 2015 09:18:13 Error [L3]:Failed to establish connection to routing module (delete VR)
Sep 21 2015 09:18:13 Error [L3]:(19412) login virtual-router VR10 Failed [Connection closed]: login virtual-router VR10 Connection is closed!
Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
Sep 21 2015 09:18:11 Info [VCS]:aVCS daemon start running
Sep 21 2015 09:18:10 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
Sep 21 2015 09:18:09 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
Sep 21 2015 09:18:08 Error [L3]:Failed to establish connection to routing module (delete VR)
Sep 21 2015 09:18:08 Error [L3]:(19412) login virtual-router VR1 Failed [Connection closed]: login virtual-router VR1 Connection is closed!
Sep 21 2015 09:18:07 Error [ACOS]:Get all vserver failed.
Sep 21 2015 09:18:07 Error [ACOS]:Get all service group failed
Sep 21 2015 09:18:07 Error [CLI]:Error happens when building CLI configuration


Somebody have information about that?? o some pdf about log?
please.

bye.
Tagged:

Comments

  • Options
    dshindshin Member ✭
    edited September 2015
    Hi Redes,

    I skimmed through the logs provided and I do not see any critical problems. These logs are informational systems logs that are automatically generated when the ACOS has a system change either through hardware failure, programming errors or changes.If you see "Emergency", "Alert" or "Critical" messages then those errors should NOT be ignored.

    Some explanations from your logs:

    *Sep 21 2015 09:18:31 Notice [LOGGING]:A10LOGD received partition creation event from daemon.

    *This error states that someone with administrator rights had created a new partition within the ACOS.

    **Sep 21 2015 09:18:15 Info [VCS]:aVCS daemon start running
    Sep 21 2015 09:18:13 Error [L3]:Failed to establish connection to routing module (delete VR)
    Sep 21 2015 09:18:13 Error [L3]:(19412) login virtual-router VR10 Failed [Connection closed]: login virtual-router VR10 Connection is closed!

    **aVCS/VRRP was not configured correctly.

    ***Sep 21 2015 09:18:22 Info [COMPRESSION]:Hardware compression device not installed on AX

    ***This error states that someone enabled a Compression as a feature but your existing box(ACOS) does not have a compression card.

    For your documentation inquiry, these errors are explained in the System Configuration and Administrator Guide. Else, talk to your regional SE/Sales so they could provide the proper documentations.


    Genard
  • Options
    REDES_STI_UCHILEREDES_STI_UCHILE Member ✭
    edited September 2015
    Sorry Garcia, I didn't explain well.
    We have two device with the same characteristics. In that moment when fail our device receives this logg. Both A10 show the same log and in device CISCO our link to A10 were down. I can't understand what happened because the A10 were always UP with energy.

    log A10

    Sep 21 2015 09:18:22 Info [COMPRESSION]:Hardware compression device not installed on AX
    Sep 21 2015 09:18:17 Info [GSLB]:Initialization done
    Sep 21 2015 09:18:17 Info [Fail Safe]:Fail Safe is initialized.
    Sep 21 2015 09:18:15 Info [VCS]:aVCS daemon start running
    Sep 21 2015 09:18:13 Error [L3]:Failed to establish connection to routing module (delete VR)
    Sep 21 2015 09:18:13 Error [L3]:(19412) login virtual-router VR10 Failed [Connection closed]: login virtual-router VR10 Connection is closed!
    Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
    Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
    Sep 21 2015 09:18:11 Info [VCS]:aVCS daemon start running
    Sep 21 2015 09:18:10 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
    Sep 21 2015 09:18:09 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
    Sep 21 2015 09:18:08 Error [L3]:Failed to establish connection to routing module (delete VR)
    Sep 21 2015 09:18:08 Error [L3]:(19412) login virtual-router VR1 Failed [Connection closed]: login virtual-router VR1 Connection is closed!
    Sep 21 2015 09:18:07 Error [ACOS]:Get all vserver failed.
    Sep 21 2015 09:18:07 Error [ACOS]:Get all service group failed


    log CISCO

    1747990: Sep 21 10:18:11: %EC-5-UNBUNDLE: Interface Gi2/42 left the port-channel Po10
    1747991: Sep 21 10:18:12: %DTP-5-NONTRUNKPORTON: Port Gi2/42 has become non-trunk
    1747992: Sep 21 10:18:12: %EC-5-UNBUNDLE: Interface Gi2/41 left the port-channel Po10
    1747993: Sep 21 10:18:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/42, changed state to down
    1747994: Sep 21 10:18:12: %DTP-5-NONTRUNKPORTON: Port Gi2/41 has become non-trunk
    1747995: Sep 21 10:18:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/41, changed state to down
    1747996: Sep 21 10:18:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel10, changed state to down
    1747997: Sep 21 10:18:13: %LINK-3-UPDOWN: Interface GigabitEthernet2/42, changed state to down
    1747998: Sep 21 10:18:14: %LINK-3-UPDOWN: Interface Port-channel10, changed state to down
    1747999: Sep 21 10:18:14: %LINK-3-UPDOWN: Interface GigabitEthernet2/41, changed state to down

    attached my example.
  • Options
    REDES_STI_UCHILEREDES_STI_UCHILE Member ✭
    edited September 2015
    Sorry Garcia, I didn't explain well.
    We have two device with the same characteristics. In that moment when fail our device receives this logg. Both A10 show the same log and in device CISCO our link to A10 were down. I can't understand what happened because the A10 were always UP with energy.

    log A10

    Sep 21 2015 09:18:22 Info [COMPRESSION]:Hardware compression device not installed on AX
    Sep 21 2015 09:18:17 Info [GSLB]:Initialization done
    Sep 21 2015 09:18:17 Info [Fail Safe]:Fail Safe is initialized.
    Sep 21 2015 09:18:15 Info [VCS]:aVCS daemon start running
    Sep 21 2015 09:18:13 Error [L3]:Failed to establish connection to routing module (delete VR)
    Sep 21 2015 09:18:13 Error [L3]:(19412) login virtual-router VR10 Failed [Connection closed]: login virtual-router VR10 Connection is closed!
    Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
    Sep 21 2015 09:18:11 Error [L3]:(19412) login virtual-router VR5 Failed [no such routing context]: login virtual-router VR5 No such VR Balanceador-T15#
    Sep 21 2015 09:18:11 Info [VCS]:aVCS daemon start running
    Sep 21 2015 09:18:10 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
    Sep 21 2015 09:18:09 Error [L3]:(19412) login virtual-router VR3 Failed [no such routing context]: login virtual-router VR3 No such VR Balanceador-T15#
    Sep 21 2015 09:18:08 Error [L3]:Failed to establish connection to routing module (delete VR)
    Sep 21 2015 09:18:08 Error [L3]:(19412) login virtual-router VR1 Failed [Connection closed]: login virtual-router VR1 Connection is closed!
    Sep 21 2015 09:18:07 Error [ACOS]:Get all vserver failed.
    Sep 21 2015 09:18:07 Error [ACOS]:Get all service group failed


    log CISCO

    1747990: Sep 21 10:18:11: %EC-5-UNBUNDLE: Interface Gi2/42 left the port-channel Po10
    1747991: Sep 21 10:18:12: %DTP-5-NONTRUNKPORTON: Port Gi2/42 has become non-trunk
    1747992: Sep 21 10:18:12: %EC-5-UNBUNDLE: Interface Gi2/41 left the port-channel Po10
    1747993: Sep 21 10:18:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/42, changed state to down
    1747994: Sep 21 10:18:12: %DTP-5-NONTRUNKPORTON: Port Gi2/41 has become non-trunk
    1747995: Sep 21 10:18:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/41, changed state to down
    1747996: Sep 21 10:18:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel10, changed state to down
    1747997: Sep 21 10:18:13: %LINK-3-UPDOWN: Interface GigabitEthernet2/42, changed state to down
    1747998: Sep 21 10:18:14: %LINK-3-UPDOWN: Interface Port-channel10, changed state to down
    1747999: Sep 21 10:18:14: %LINK-3-UPDOWN: Interface GigabitEthernet2/41, changed state to down

    attached my example.
  • Options
    dshindshin Member ✭
    edited September 2015
    To debug this problem, I would need a showtech from your A10 boxes. To keep the anonymity of your network and expedite the problem resolution, I suggest that you open a ticket with A10 support and they will require you to provide a showtech log. I think you have some configuration problems specific to VRRP-A causing the A10 boxes to not fail over properly.

    Genard
  • Options
    REDES_STI_UCHILEREDES_STI_UCHILE Member ✭
    edited September 2015
    Thank you for replying so quickly
Sign In or Register to comment.