Circuit ID Question.

[stonnet72]

How can I find out the Circuit ID of a T1 line without calling my ISP? Is this at all possible. I have a bunch of T1 circuits and I am trying to find out the CKT ID info without going to the individual sites. Any advice?

Thank you

[Jon Marshall · Accepted solution]

stonnet72 wrote:

How can I find out the Circuit ID of a T1 line without calling my ISP? Is this at all possible. I have a bunch of T1 circuits and I am trying to find out the CKT ID info without going to the individual sites. Any advice?
Thank you

Unless you have included it in the running-config under the interface description or have the paperwork you can't find this information out from the CLI.

Jon

[stonnet72]

You are right Jon. That is the only option.

[stonnet72]

You are right Jon. That is the only option.

[epdong04]

It's possible to find the Circuit ID with a simple show command.

Display interface information and filter for Description or connected.

Note: When using include or exclude multiple searches can be performed by separating the search strings with a pipe symbol ( | )

R1# show interface | include Desc|conn

Router responce:

R1#sh interfaces | include Desc|conn

GigabitEthernet0/0/0 is up, line protocol is up (connected)

Description: Connection to SW1

GigabitEthernet0/0/1 is up, line protocol is up (connected)

Description: Connection to SW2

Serial0/1/0 is up, line protocol is up (connected)

Description: Circuit ID BCB123450001

[Joseph W. Doherty]

"It's possible to find the Circuit ID with a simple show command."

@epdong04 provides a nice example using a config text search.

However, as noted by @Jon Marshall this would only be useful if someone had already configured this information in an interface description.

Oh, and although Jon mentions this information being in the running config, hopefully it also is identical in the start up config and could be found the same way there too.

BTW, having a circuit ID in an interface description it generally a good practice.  Actually, I've worked in companies that had defined information structures for interface descriptions, especially for infrastructure links, including information what's on the other side of the link (often including the information seen with CDP/LLDP, but handy when the link is down).