Extremely long time to establish network link with Nexus N9K-C9372-PX-E
This switch is completely default, no configuration has been done other than resetting it to default configuration, and going through the normal naming of the switch and time etc.
The problem I'm seeing is that it takes 30-45 seconds for clients to get fully linked/connected. So for example, if we restart one of our Ubuntu clients, the Ubuntu machine will get to the login screen and then it takes another good 30-40 seconds before we will get the notification saying "Connection established".
Comparing this to our other switches that generally have the connection ready within 3-5 seconds after hitting the login screen. Is there something specific to the switch that I can change to reduce the time it takes to establish a connection?
cisco 10gbase
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This switch is completely default, no configuration has been done other than resetting it to default configuration, and going through the normal naming of the switch and time etc.
The problem I'm seeing is that it takes 30-45 seconds for clients to get fully linked/connected. So for example, if we restart one of our Ubuntu clients, the Ubuntu machine will get to the login screen and then it takes another good 30-40 seconds before we will get the notification saying "Connection established".
Comparing this to our other switches that generally have the connection ready within 3-5 seconds after hitting the login screen. Is there something specific to the switch that I can change to reduce the time it takes to establish a connection?
cisco 10gbase
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12
add a comment |
This switch is completely default, no configuration has been done other than resetting it to default configuration, and going through the normal naming of the switch and time etc.
The problem I'm seeing is that it takes 30-45 seconds for clients to get fully linked/connected. So for example, if we restart one of our Ubuntu clients, the Ubuntu machine will get to the login screen and then it takes another good 30-40 seconds before we will get the notification saying "Connection established".
Comparing this to our other switches that generally have the connection ready within 3-5 seconds after hitting the login screen. Is there something specific to the switch that I can change to reduce the time it takes to establish a connection?
cisco 10gbase
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This switch is completely default, no configuration has been done other than resetting it to default configuration, and going through the normal naming of the switch and time etc.
The problem I'm seeing is that it takes 30-45 seconds for clients to get fully linked/connected. So for example, if we restart one of our Ubuntu clients, the Ubuntu machine will get to the login screen and then it takes another good 30-40 seconds before we will get the notification saying "Connection established".
Comparing this to our other switches that generally have the connection ready within 3-5 seconds after hitting the login screen. Is there something specific to the switch that I can change to reduce the time it takes to establish a connection?
cisco 10gbase
cisco 10gbase
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
edited Jan 14 at 17:38
Ron Trunk
35.3k33372
35.3k33372
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
asked Jan 14 at 17:32
Kevin VaskoKevin Vasko
1061
1061
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Kevin Vasko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12
add a comment |
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12
add a comment |
1 Answer
1
active
oldest
votes
If you have a switch with a default configuration, spanning tree will block ports when they come up until the forwarding timer expires.
You can configure portfast on ports that have end hosts on them to allow spanning-tree to put the ports immediately into forwarding mode.
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Kevin Vasko is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f56108%2fextremely-long-time-to-establish-network-link-with-nexus-n9k-c9372-px-e%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you have a switch with a default configuration, spanning tree will block ports when they come up until the forwarding timer expires.
You can configure portfast on ports that have end hosts on them to allow spanning-tree to put the ports immediately into forwarding mode.
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
add a comment |
If you have a switch with a default configuration, spanning tree will block ports when they come up until the forwarding timer expires.
You can configure portfast on ports that have end hosts on them to allow spanning-tree to put the ports immediately into forwarding mode.
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
add a comment |
If you have a switch with a default configuration, spanning tree will block ports when they come up until the forwarding timer expires.
You can configure portfast on ports that have end hosts on them to allow spanning-tree to put the ports immediately into forwarding mode.
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
If you have a switch with a default configuration, spanning tree will block ports when they come up until the forwarding timer expires.
You can configure portfast on ports that have end hosts on them to allow spanning-tree to put the ports immediately into forwarding mode.
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
answered Jan 14 at 17:59
Ron TrunkRon Trunk
35.3k33372
35.3k33372
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
add a comment |
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
1
1
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
A true evergreen in networking: portfast trouble. Here probably in its NX-OS guise as "spanning tree port type edge" if the port is in access mode (single VLAN untagged), respevtively as "spanning tree port type edge trunk" if the port is 802.1q with tagging towards the host. You wouldn't believe how many networks run without it, esepecially the without the latter variety...
– Marc 'netztier' Luethi
Jan 14 at 20:48
add a comment |
Kevin Vasko is a new contributor. Be nice, and check out our Code of Conduct.
Kevin Vasko is a new contributor. Be nice, and check out our Code of Conduct.
Kevin Vasko is a new contributor. Be nice, and check out our Code of Conduct.
Kevin Vasko is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f56108%2fextremely-long-time-to-establish-network-link-with-nexus-n9k-c9372-px-e%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Not enough information. Could it be spanning tree that causing your issue?
– Ron Trunk
Jan 14 at 17:38
Logging in is host-specific which is off-topic here. You need to add details on when the link LED comes on (physical layer) and when data transfer starts (data link layer, check switch port status).
– Zac67
Jan 14 at 17:50
@RonTrunk As in configuring the switch for spanning tree? Or are you asking if I have loops in the network? If it is the latter, it does not have loops in the network. This is a diagram of the network. imgur.com/HpBrAnU
– Kevin Vasko
Jan 14 at 17:51
@Zac67 I'm not talking about logging in. I'm talking about how long it takes between when the connection is marked active and usable, I was using the login scenario as an example. In Ubuntu I can unplug the cable going to the 10Gb switch, plug it back in, and it takes 30-45 seconds before the connection is up and functioning (e.g. the little network connection wheel keeps spinning). If I plug the system up to one of our 1Gb switches it takes about 10 seconds.
– Kevin Vasko
Jan 14 at 17:54
The "little network connection wheel" is a host feature. Check out the switch LED/status instead.
– Zac67
Jan 14 at 18:12