Forum Discussion

Bidu_9756's avatar
Bidu_9756
Icon for Nimbostratus rankNimbostratus
Oct 11, 2013

BigIP AOM issue

Hi all I have an issue with the setup of AOM on a LoadBalancer. With "ssh aom" I don't get access to the subsystem. This ssh shows the following error:

 

[...@BIPB:Standby] ~ ssh -v aom OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /config/ssh/ssh_config debug1: Applying options for aom debug1: Applying options for * debug1: Connecting to aom [127.2.0.1] port 22. debug1: connect to address 127.2.0.1 port 22: No route to host ssh: connect to host aom port 22: No route to host

 

For troubleshooting I did those steps:

 

  • checking iptables: [...@BIPB:Standby] ~ iptables -nvL Chain INPUT (policy ACCEPT 4007K packets, 381M bytes) pkts bytes target prot opt in out source destination

     

    0 0 ACCEPT all -- eth0.1 * 127.2.0.1 127.2.0.2

     

    344K 21M ACCEPT all -- lo+ * 127.2.0.2 127.2.0.2

     

    0 0 DROP all -- * * 0.0.0.0/0 127.2.0.2

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 4909K packets, 437M bytes) pkts bytes target prot opt in out source destination

 

  • Relevant entries in /etc/hosts: [...@BIPB:Standby] ~ cat /etc/hosts
THIS IS AN AUTO-GENERATED FILE -- DO NOT EDIT!!! Use the bigpipe shell utility to make changes to the system configuration. For more information, see bigpipe system help.

127.0.0.1 localhost.localdomain localhost sysname.domain.com 127.2.0.1 sccp aom AOM 127.2.0.2 sysname.domain.ch 127.1.1.2 tmm 127.1.1.3 tmm1 127.1.1.4 tmm2 127.1.1.5 tmm3

 

  • ping aom [...@BIPB:Standby] ~ ping aom PING sccp (127.2.0.1) 56(84) bytes of data. From sysname.domain.ch (127.2.0.2) icmp_seq=2 Destination Host Unreachable From sysname.domain.ch (127.2.0.2) icmp_seq=5 Destination Host Unreachable

     

  • routing [...@BIPB:Standby] ~ netstat -rnv | sort . . 127.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tmm0 127.2.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0.1 . .

     

  • installed AOM packages [...@BIPB:Standby] ~ rpm -qa | grep aom aom-software-1.0.F5-10.1.10.100.6.0 f5config-aom-10.2.4-577.0 aom-firmware-1.4-10.1.10.100.6.0

     

  • installed version is: BIG-IP 10.2.4 Build 817.0 Hotfix HF7

     

Without this general AOM access using ssh, I am not able to configure baud rate an the IP address. Does anyone know how to get around this issue?

 

Regards

 

3 Replies

  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus

    What sort of hardware? Some systems (e.g. Viprion) don't have AOM.

     

    H

     

  • Hello Hamish

     

    We have this problem with 3900 appliances. Actually there are two appliances (active and standby), but this AOM problem we have only on one box. With the 2nd appliance there are no problems with AOM.

     

    Regards Bidu