- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- APA - LACP and LAN Monitor interface with a Cisco ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2012 05:39 PM
08-13-2012 05:39 PM
Hi - I have a bl860ci2 with 4 Cisco switches in the enclosure. Each pair of Cisco switches in configured in a "stack".
Our normal config on the servers is interfaces lanX and lanY on switch #1 configured as a LACP aggregate (e.g. lan900), and then interfaces lanA and lanB configured as another LACP aggregate (e.g. lan901) on switch #2.
We then create a failover group, lan902, made up of lan901 and lan902.
This has always worked and we've never had an issue...when these were set up as an "access" port so they could only be in one VLAN.
Now I have asked the network team to set these ports up as "trunk" ports so they support VLAN tagging...and its not working.
The LACP aggregates seem to create OK, but if I run lancheckconf I get this :-
ERROR: Ports 900 and 901 not connected
Some Fail-Over Group(s) in input file /etc/lanmon/lanconfig.ascii have verification errors.
I am using the standard lanconfig.ascii I always use which works everywhere else :-
LM_RAPID_ARP on
LM_RAPID_ARP_INTERVAL 1000000
LM_RAPID_ARP_COUNT 10
FAILOVER_GROUP lan902
PRIMARY lan900 5
STANDBY lan901 3
The network guys have checked and double checked and they say all is well from their side - so I am starting to wonder if this is something to do with supporting VLAN tagging/Cisco "trunk" ports via Lan Monitor or something like that.
Even more so as I also have a second set of NICS configured like this on the same server which are NOT VLAN tagged (just a standard Cisco "access" port) and that is working fine.
Any one get any insight? Thoughts?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2012 03:12 AM - edited 08-14-2012 03:28 AM
08-14-2012 03:12 AM - edited 08-14-2012 03:28 AM
Re: APA - LACP and LAN Monitor interface with a Cisco "trunk" port (for VLAN tagging).
Based on experience I would suggest to update LOM firmware, APA software and LAN drivers first.
LOM 50258
APA 11.31.60 (from software.hp.com):
HP-UX_11.31_for_IA_PA_J4240AA_B.11.31.60_HP-UX_B.11.31_IA_PA.depot
drivers:
HP-UX_11.31_10GigEthr-02_B.11.31.1205_HP-UX_B.11.31_IA.depot
Could you explain "not working"?
How does
# nwmgr
# nwmgr -S apa
# nwmgr -c lan900 [901/902] -v
# nwmgr -S apa -I 900 -v
... etc for 901/902
look like?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Tags:
- nwmgr
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2012 07:56 AM
08-14-2012 07:56 AM
Re: APA - LACP and LAN Monitor interface with a Cisco "trunk" port (for VLAN tagging).
...thanks Torsten.
Everything now updated, or was already at the latest levels (e.g. APA).
Output requested is below.
So, lan905 (which is a lan monitor of lan903 and lan904, which are LACP aggregates) is fine. On the Cisco side, it is an "access" port allowing only one VLAN - and the IP assigned to lan905 works.
On lan902 (which is a lan monitor of lan900 and lan901, which are LACP aggregates) I dont get any network connectivity when I assign the correct IP. This is a Cisco "trunk" port allowing multiple VLANs. (This will be an IVM host so I need multiple VLANs for various guests...)
When I start hplm, I do see this error though which I'm sure is relevant! -
WARNING: Failed link-level connectivity checks for ports in Fail-Over Group 902.
For more information, see nettl log messages for HP_APA.
Also, once hplm is started, a few moments after I see this on the console :-
----------------------Auto-Port Aggregation/9000 Networking-----------------@#%
Tue Aug 14 EDT 2012 10:43:49 AM.283594DISASTER Subsys:HP_APA Loc:00000
<1006> HP Auto-Port Aggregation product found that ports in failover
group lan902 are no longer connected to each other. Port 900 did
not receive any poll packets.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
----------------------Auto-Port Aggregation/9000 Networking-----------------@#%
Tue Aug 14 EDT 2012 10:43:49 AM.283608DISASTER Subsys:HP_APA Loc:00000
<1006> HP Auto-Port Aggregation product found that ports in failover
group lan902 are no longer connected to each other. Port 901 did
not receive any poll packets.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To eliminate the lan monitor piece, I have also tried to directly configure lan900 with an IP and even though the LACP aggregate looks OK in nwmgr, I still dont get any network connectivity...so its nothing to do with the lanmonitor piece.
I would love to say this was a network config issue, but I'm no expert at all and the network team tell me it OK.
I just dont know why a "trunk" vs. an "access" (Cisco speak) would make any difference.
_____________________________________________________
hpuxvsp1.biogenidec.com-> nwmgr
Name/ Interface Station Sub- Interface Related
ClassInstance State Address system Type Interface
============== ========= ============== ======== ============== =========
lan0 UP 0xD8D3856AC298 iexgbe 10GBASE-KR lan903
lan1 UP 0xD8D3856AC29C iexgbe 10GBASE-KR lan904
lan2 UP 0xD8D3856AC2A0 iexgbe 10GBASE-KR lan900
lan3 UP 0xD8D3856AC2A4 iexgbe 10GBASE-KR lan901
lan4 UP 0xD8D3856AC2A0 iether 1000Mb/s lan900
lan5 UP 0xD8D3856AC2A4 iether 1000Mb/s lan901
lan6 UP 0xD8D3856AC298 iether 1000Mb/s lan903
lan7 UP 0xD8D3856AC29C iether 1000Mb/s lan904
lan900 UP 0xD8D3856AC2A0 hp_apa hp_apa lan902
lan901 UP 0xD8D3856AC2A4 hp_apa hp_apa lan902
lan902 UP 0xD8D3856AC2A0 hp_apa hp_apa
lan903 UP 0xD8D3856AC298 hp_apa hp_apa lan905
lan904 UP 0xD8D3856AC29C hp_apa hp_apa lan905
lan905 UP 0xD8D3856AC298 hp_apa hp_apa
hpuxvsp1.biogenidec.com-> nwmgr -S apa
Class Mode Load Speed- Membership
Instance Balancing Duplex
======== =========== ========= ==================== ===========================
lan900 LACP_AUTO LB_MAC 2 Gbps Full Duplex 2,4
lan901 LACP_AUTO LB_MAC 2 Gbps Full Duplex 3,5
lan902 LAN_MONITOR LB_HS 2 Gbps Full Duplex 900,901
lan903 LACP_AUTO LB_MAC 2 Gbps Full Duplex 0,6
lan904 LACP_AUTO LB_MAC 2 Gbps Full Duplex 1,7
lan905 LAN_MONITOR LB_HS 2 Gbps Full Duplex 903,904
hpuxvsp1.biogenidec.com-> nwmgr -c lan900 -v
lan900 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a0
Network Management ID = 10
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 902
APA State = Active
Membership = 2,4
Active Port(s) = 2,4
Not Ready Port(s) = -
Key = 900
Operational Key = 900
Priority = 5
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -c lan901 -v
lan901 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a4
Network Management ID = 11
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 902
APA State = Standby
Membership = 3,5
Active Port(s) = 3,5
Not Ready Port(s) = -
Key = 901
Operational Key = 901
Priority = 3
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -c lan902 -v
lan902 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a0
Network Management ID = 12
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_HS
Mode = LAN_MONITOR
Parent PPA = -
APA State = Up
Membership = 900,901
Active Port(s) = 900
Ready Port(s) = 901
Not Ready Port(s) = -
Connected Port(s) = -
Polling Interval = 10000000
Dead Count = 3
Rapid ARP = on
Rapid ARP Interval = 1.0 second(s)
Rapid ARP Count = 10
Failover Policy = PRIORITY_BASED
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -c lan903 -v
lan903 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac298
Network Management ID = 13
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 905
APA State = Active
Membership = 0,6
Active Port(s) = 0,6
Not Ready Port(s) = -
Key = 903
Operational Key = 903
Priority = 5
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -c lan904 -v
lan904 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac29c
Network Management ID = 14
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 905
APA State = Standby
Membership = 1,7
Active Port(s) = 1,7
Not Ready Port(s) = -
Key = 904
Operational Key = 904
Priority = 3
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -c lan905 -v
lan905 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac298
Network Management ID = 15
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_HS
Mode = LAN_MONITOR
Parent PPA = -
APA State = Up
Membership = 903,904
Active Port(s) = 903
Ready Port(s) = 904
Not Ready Port(s) = -
Connected Port(s) = 904
Polling Interval = 10000000
Dead Count = 3
Rapid ARP = on
Rapid ARP Interval = 1.0 second(s)
Rapid ARP Count = 10
Failover Policy = PRIORITY_BASED
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 900 -v
lan900 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a0
Network Management ID = 10
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 902
APA State = Active
Membership = 2,4
Active Port(s) = 2,4
Not Ready Port(s) = -
Key = 900
Operational Key = 900
Priority = 5
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 901 -v
lan901 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a4
Network Management ID = 11
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 902
APA State = Standby
Membership = 3,5
Active Port(s) = 3,5
Not Ready Port(s) = -
Key = 901
Operational Key = 901
Priority = 3
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 902 -v
lan902 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac2a0
Network Management ID = 12
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_HS
Mode = LAN_MONITOR
Parent PPA = -
APA State = Up
Membership = 900,901
Active Port(s) = 900
Ready Port(s) = 901
Not Ready Port(s) = -
Connected Port(s) = -
Polling Interval = 10000000
Dead Count = 3
Rapid ARP = on
Rapid ARP Interval = 1.0 second(s)
Rapid ARP Count = 10
Failover Policy = PRIORITY_BASED
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 903 -v
lan903 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac298
Network Management ID = 13
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 905
APA State = Active
Membership = 0,6
Active Port(s) = 0,6
Not Ready Port(s) = -
Key = 903
Operational Key = 903
Priority = 5
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 904 -v
lan904 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac29c
Network Management ID = 14
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_MAC
Mode = LACP_AUTO
Parent PPA = 905
APA State = Standby
Membership = 1,7
Active Port(s) = 1,7
Not Ready Port(s) = -
Key = 904
Operational Key = 904
Priority = 3
Cost = 0
Normalized Port Cost = 0
Fixed Mac Address = off
hpuxvsp1.biogenidec.com-> nwmgr -S apa -I 905 -v
lan905 current values:
Speed = 2 Gbps Full Duplex
MTU = 1500
Virtual Maximum Transmission Unit = 0
MAC Address = 0xd8d3856ac298
Network Management ID = 15
Features = Linkagg Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Support
VLAN Tag Offload
64Bit MIB Support
Load Distribution Algorithm = LB_HS
Mode = LAN_MONITOR
Parent PPA = -
APA State = Up
Membership = 903,904
Active Port(s) = 903
Ready Port(s) = 904
Not Ready Port(s) = -
Connected Port(s) = 904
Polling Interval = 10000000
Dead Count = 3
Rapid ARP = on
Rapid ARP Interval = 1.0 second(s)
Rapid ARP Count = 10
Failover Policy = PRIORITY_BASED
Fixed Mac Address = off
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2012 01:18 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2012 10:53 PM - edited 08-14-2012 10:55 PM
08-14-2012 10:53 PM - edited 08-14-2012 10:55 PM
Re: APA - LACP and LAN Monitor interface with a Cisco "trunk" port (for VLAN tagging).
We had a similar setup and a strange behaviour after starting to update firmware, software, etc.
The lan900 trunk did not longer form, adding lan17 to aggregate lan904 failed:
# nwmgr -s -S apa -I 17 -A key=904 -A mode=LACP _AUTO
lan17 new values:
Key = 904
Mode = LACP_AUTO
# nwmgr -S apa
Class Mode Load Speed- Membership
Instance Balancing Duplex
======== =========== ========= ==================== ===========================
lan13 LACP_AUTO - 1 Gbps Full Duplex -
lan17 LACP_AUTO - 1 Gbps Full Duplex -
...
lan904 Not_Enabled LB_MAC 0 Mbps -
...
Finally it turns out the reason was a incorrect switch port setting, but the older combination of firmware+software did not check that. So it looks like working.
After correcting the switch setting it really worked.
So the reason for your problem was a switch setting too?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2013 06:52 PM
07-04-2013 06:52 PM
Re: APA - LACP and LAN Monitor interface with a Cisco "trunk" port (for VLAN tagging).
Hello,
Can you tell me what was the network configuration required to make LACP working ?
Thbaks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2014 10:58 PM
03-10-2014 10:58 PM
Re: APA - LACP and LAN Monitor interface with a Cisco "trunk" port (for VLAN tagging).
Hi Graham,
Greetings !!!
I am also facing the same issue as you mentioned. It shows the same error - lan900 and lan901 are not conencted.
ERROR: Ports 900 and 901 not connected
Some Fail-Over Group(s) in input file /etc/lanmon/lanconfig.ascii have verification errors.
Could you please let me know what was the solution. Is there something that we want to change in the switch side.
Also, is there any way that if any one of the network port in the active group (eg. lan2 of lan900) fails, it can fail over to the other group 901. Please let me know.
Thanks,
Umesh