CLI Cable Test
-
ste - Member
- Posts: 84
- Joined: Fri May 22, 2015 5:33 am
- Location: Regensburg Germany
- Has thanked: 2 times
- Been thanked: 13 times
CLI Cable Test
I cant reach a switch via http but with ssh. How to do a cable test?
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: CLI Cable Test
Moved your post from the pictures thread.
Why can you not get to the UI via http?
Why can you not get to the UI via http?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
ste - Member
- Posts: 84
- Joined: Fri May 22, 2015 5:33 am
- Location: Regensburg Germany
- Has thanked: 2 times
- Been thanked: 13 times
Re: CLI Cable Test
sirhc wrote:Moved your post from the pictures thread.
Why can you not get to the UI via http?
The switch seems to no longer power the main uplink (AF5x) where the default route goes This cable I want to test.
-
ste - Member
- Posts: 84
- Joined: Fri May 22, 2015 5:33 am
- Location: Regensburg Germany
- Has thanked: 2 times
- Been thanked: 13 times
Re: CLI Cable Test
Additional Info. I changed default gateway and disabled the route at the uplink router to route via the backupline.
But I did a port bounce before with cli to restart the AF5X. This seem to kill the webinterface. So I still can only ssh into the switch.
I cant find the command to remove the port bounce with cli.
But I did a port bounce before with cli to restart the AF5X. This seem to kill the webinterface. So I still can only ssh into the switch.
I cant find the command to remove the port bounce with cli.
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: CLI Cable Test
If this a version of firmware older than v1.4.3rc4 which has a fix where if you do a port bounce in the CLI it corrupts your config file.
Really sorry about that but this bug was just found a couple weeks ago.
I know, what are the odds right, sorry about this.
I am sure Eric would know how to better help you but I personally would factory default the unit and manually set it backup at this point.
I have pinged Eric to try and help you.
One other possible way to fix this would be to do a firmware upgrade to v1.4.3rc4 via the CLI but you would need a TFT server to do this as v1.4.3rc4 will fix the config file corruption.
To do a CLI upgrade press "?" and look for help
You see a list of commands and firmware is one of them
Then type "firmware upgrade <tftp URL>
EXAMPLE TFTP URL: tftp://server/path-and-filename
"
Really sorry about that but this bug was just found a couple weeks ago.
I know, what are the odds right, sorry about this.
I am sure Eric would know how to better help you but I personally would factory default the unit and manually set it backup at this point.
I have pinged Eric to try and help you.
One other possible way to fix this would be to do a firmware upgrade to v1.4.3rc4 via the CLI but you would need a TFT server to do this as v1.4.3rc4 will fix the config file corruption.
To do a CLI upgrade press "?" and look for help
You see a list of commands and firmware is one of them
Then type "firmware upgrade <tftp URL>
EXAMPLE TFTP URL: tftp://server/path-and-filename
"
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
Eric Stern - Employee
- Posts: 532
- Joined: Wed Apr 09, 2014 9:41 pm
- Location: Toronto, Ontario
- Has thanked: 0 time
- Been thanked: 130 times
Re: CLI Cable Test
ste wrote:Additional Info. I changed default gateway and disabled the route at the uplink router to route via the backupline.
But I did a port bounce before with cli to restart the AF5X. This seem to kill the webinterface. So I still can only ssh into the switch.
I cant find the command to remove the port bounce with cli.
Use the "show bounces" command to see the configured bounces.
- Code: Select all
Netonix Switch# show bounces
Number Port Enable Description Cut Power For Schedule Type Day Of The Month Hour Weekday
------ ---- ------ ----------- ------------- ------------- ---------------- ---- -------
1 5 true (null) 5 Daily 1 4 Sunday
This shows bounce #1 on port 5 with a null description (which is what is causing the problem).
To fix it you would do this in the CLI
- Code: Select all
config
int port 5
bounce 1
description foo
exit
exit
The web interface should now work again.
-
ste - Member
- Posts: 84
- Joined: Fri May 22, 2015 5:33 am
- Location: Regensburg Germany
- Has thanked: 2 times
- Been thanked: 13 times
Re: CLI Cable Test
Thanks. This did the job. Did a cable test and got the info that cable pair 1 is shorted with cable pair 2. So something happened to the cable.
It would be a good idea for the case that the primary uplink fails to have some backup ip mechanism on the switch. So a second IP/gateway on a second vlan which is enabled when ping to the uplink gateway fails. To reach the switch, routing has to be changed. So the other side of the uplink is not reachable then until routing is changed back.
It would be a good idea for the case that the primary uplink fails to have some backup ip mechanism on the switch. So a second IP/gateway on a second vlan which is enabled when ping to the uplink gateway fails. To reach the switch, routing has to be changed. So the other side of the uplink is not reachable then until routing is changed back.
7 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 53 guests