- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: LACP randomly fail between hpe5700 and cisco 6...
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
Forums
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
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
01-19-2017 07:19 AM
01-19-2017 07:19 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
Here the logs of the Cisco CBS :
<189>150915: Jan 19 02:31:18.826 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/14, changed state to down <191>150916: Jan 19 02:31:18.868 CET: STP: PVST vlan 1010 port Gi0/14 created, ext id 4492944 <191>150917: Jan 19 02:31:18.868 CET: RSTP(1010): initializing port Gi0/14 <191>150918: Jan 19 02:31:18.868 CET: RSTP(1010): Gi0/14 is now designated <191>150919: Jan 19 02:31:18.876 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150920: Jan 19 02:31:20.210 CET: RSTP(1010): transmitting a proposal on Gi0/14 <189>150921: Jan 19 02:31:20.839 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/14, changed state to up <191>150922: Jan 19 02:31:22.224 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150923: Jan 19 02:31:24.237 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150924: Jan 19 02:31:26.250 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150925: Jan 19 02:31:28.263 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150926: Jan 19 02:31:30.277 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150927: Jan 19 02:31:32.290 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150928: Jan 19 02:31:33.876 CET: RSTP(1010): Gi0/14 fdwhile Expired <191>150929: Jan 19 02:31:34.312 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150930: Jan 19 02:31:36.325 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150931: Jan 19 02:31:38.338 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150932: Jan 19 02:31:40.352 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150933: Jan 19 02:31:42.365 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150934: Jan 19 02:31:44.378 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150935: Jan 19 02:31:46.392 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150936: Jan 19 02:31:48.405 CET: RSTP(1010): transmitting a proposal on Gi0/14 <191>150937: Jan 19 02:31:48.883 CET: RSTP(1010): Gi0/14 fdwhile Expired <191>150938: Jan 19 02:31:52.633 CET: RSTP(1): updt roles, received superior bpdu on Po1 <191>150939: Jan 19 02:31:52.633 CET: RSTP(1): synced Po1 <191>150940: Jan 19 02:31:52.641 CET: RSTP(1): transmitting an agreement on Po1 as a response to a proposal <191>150941: Jan 19 02:31:52.834 CET: RSTP(1): updt roles, received superior bpdu on Po1 <191>150942: Jan 19 02:31:52.834 CET: RSTP(1): synced Po1 <191>150943: Jan 19 02:31:52.843 CET: RSTP(1): transmitting an agreement on Po1 as a response to a proposal <191>150944: Jan 19 02:31:56.752 CET: RSTP(1011): Po1 rcvd info expired <191>150945: Jan 19 02:31:56.752 CET: RSTP(1011): updt roles, information on root port Po1 expired <191>150946: Jan 19 02:31:56.752 CET: RSTP(1011): we become the root bridge <191>150947: Jan 19 02:31:56.752 CET: RSTP(1011): Po1 is now designated <191>150948: Jan 19 02:31:56.760 CET: RSTP(1011): updt roles, received superior bpdu on Po1 <191>150949: Jan 19 02:31:56.760 CET: RSTP(1011): Po1 is now root port <191>150950: Jan 19 02:31:57.633 CET: RSTP(31): Po1 rcvd info expired <191>150951: Jan 19 02:31:57.633 CET: RSTP(31): updt roles, information on root port Po1 expired <191>150952: Jan 19 02:31:57.633 CET: RSTP(31): we become the root bridge <191>150953: Jan 19 02:31:57.633 CET: RSTP(31): Po1 is now designated <191>150954: Jan 19 02:31:57.641 CET: RSTP(1010): Po1 rcvd info expired <191>150955: Jan 19 02:31:57.641 CET: RSTP(1010): updt roles, information on root port Po1 expired <191>150956: Jan 19 02:31:57.641 CET: RSTP(1010): we become the root bridge <191>150957: Jan 19 02:31:57.641 CET: RSTP(1010): Po1 is now designated <191>150958: Jan 19 02:31:57.641 CET: RSTP(1020): Po1 rcvd info expired <191>150959: Jan 19 02:31:57.641 CET: RSTP(1020): updt roles, information on root port Po1 expired <191>150960: Jan 19 02:31:57.641 CET: RSTP(1020): we become the root bridge <191>150961: Jan 19 02:31:57.641 CET: RSTP(1020): Po1 is now designated <191>150962: Jan 19 02:31:57.641 CET: RSTP(1030): Po1 rcvd info expired <191>150963: Jan 19 02:31:57.641 CET: RSTP(1030): updt roles, information on root port Po1 expired <191>150964: Jan 19 02:31:57.641 CET: RSTP(1030): we become the root bridge <191>150965: Jan 19 02:31:57.641 CET: RSTP(1030): Po1 is now designated <191>150966: Jan 19 02:31:57.641 CET: RSTP(31): updt roles, received superior bpdu on Po1 <191>150967: Jan 19 02:31:57.641 CET: RSTP(31): Po1 is now root port <191>150968: Jan 19 02:31:57.658 CET: RSTP(1010): updt roles, received superior bpdu on Po1 <191>150969: Jan 19 02:31:57.658 CET: RSTP(1010): Po1 is now root port <191>150970: Jan 19 02:31:57.658 CET: RSTP(1020): updt roles, received superior bpdu on Po1 <191>150971: Jan 19 02:31:57.658 CET: RSTP(1020): Po1 is now root port <191>150972: Jan 19 02:31:57.658 CET: RSTP(1010): updt roles, received superior bpdu on Po1 <191>150973: Jan 19 02:31:57.658 CET: RSTP(1030): updt roles, received superior bpdu on Po1 <191>150974: Jan 19 02:31:57.658 CET: RSTP(1030): Po1 is now root port <191>150975: Jan 19 02:31:57.675 CET: RSTP(1040): Po1 rcvd info expired <191>150976: Jan 19 02:31:57.675 CET: RSTP(1040): updt roles, information on root port Po1 expired <191>150977: Jan 19 02:31:57.675 CET: RSTP(1040): we become the root bridge
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 07:20 AM
01-19-2017 07:20 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
I don't really understand what is downstream channels....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 08:20 AM
01-19-2017 08:20 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
ethernet port of server side inside HPE Chassis
what is the verion of CBS ?
JY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 08:28 AM
01-19-2017 08:28 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
It's a :12.2(50) version as shown below :
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 24 WS-CBS3032-DEL-F 12.2(50)SE3 CBS31X0-UNIVERSAL-M
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 08:46 AM
01-19-2017 08:46 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
could you update to at least most recent version please ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 09:18 AM - edited 01-19-2017 09:19 AM
01-19-2017 09:18 AM - edited 01-19-2017 09:19 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
We can attempt to find the last version.
I must plan this update because it's production.
I don't really understand what can cause this behavior. Do you have any idea STP/LACP....
In your firsts posts you talked about set the link between 6500 an HP5700 in etherchannel static mode.
As these 2 switchs are connected directly is there any issue to do nonLACP bonding ?
We always setup LACP as a standard bonding mode but we have ne experience in static bonding mode.
It seems we must be very carreful on static etherchannel to avoid loop.
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2017 09:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2017 04:15 AM
02-14-2017 04:15 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
Hi,
We have made the Cisco update last week.
No more problems since this update.
Thanks for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2017 04:43 AM
02-14-2017 04:43 AM
Re: LACP randomly fail between hpe5700 and cisco 6509
great !!
thanks for the feedback
JY
- « Previous
-
- 1
- 2
- Next »