Should the cisco remote-alarm command be permanently on all my routers?
I have one site that is having issues and Sprint's MPLS group asked that I put the command
(config)#service-module t1 fdl both
on my router for troubleshooting. Apparently this sends alarm info back along the line and lets them look at both the XMT and REC side instead of just the XMT.
I also have another router that has this command on it, new router 1811 from Sprint that I manage, but their default config included this statement:
service-module t1 remote-alarm-enable
My questions to the experts is that are one or both of these commands OK to leave on all the time?
if so Why?
Should they only be put on during times of trouble on the WIC?
Do they consume a significant amount of unnecessary resources?
(config)#service-module t1 fdl both
on my router for troubleshooting. Apparently this sends alarm info back along the line and lets them look at both the XMT and REC side instead of just the XMT.
I also have another router that has this command on it, new router 1811 from Sprint that I manage, but their default config included this statement:
service-module t1 remote-alarm-enable
My questions to the experts is that are one or both of these commands OK to leave on all the time?
if so Why?
Should they only be put on during times of trouble on the WIC?
Do they consume a significant amount of unnecessary resources?
luc_roy
first what type of framing are you using? You should only use this option with ESF framing because it conflicts with SF framing. If you are using ESF the you should leave it on always to validate your connection. It will not reduce performance.
ASKER
Definitely using ESF.
Should both commands be on?
Can you elaborate on the command purpose
Should both commands be on?
Can you elaborate on the command purpose
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
should both commands be on?
(config)#service-module t1 fdl both
service-module t1 remote-alarm-enable
(config)#service-module t1 fdl both
service-module t1 remote-alarm-enable
one is simply for troubleshooting the other (service-module) is the connection type. You can chose from ansi, att or both. One command has nothing to do with the other. So yes you can run both.
ASKER
Here is a clearer explanation
This command
(config-if)#service-module
(config-if)#service-module
FDL stands for Facility Data Link. It is part of the overhead bit of a T1 ESF circuit. The FDL reports line and alarm conditions accross the link to the other CSU/DSU. This information can be retrieved from either CSU/DSU and used for trouble shooting. There are two common type of FDLs, ANSI and ATT. It doesn't matter which one you use. In fact you don't need to use either. If neither one is enabled the only downside is that the information is not available. If you choose to make use of the FDL feature You must configure it the same at both ends. They are very similar, but not compatable. By setting the FDL to ATT you matched the setting that was used at the other end, thus allowing the tech to see the line condition. Therefore it would only be necessary to invoke this command if you and your LEC or carrier are in agreement and will be looking at this info,
This command
(config-if)#service-module
(config-if)#service-module
FDL stands for Facility Data Link. It is part of the overhead bit of a T1 ESF circuit. The FDL reports line and alarm conditions accross the link to the other CSU/DSU. This information can be retrieved from either CSU/DSU and used for trouble shooting. There are two common type of FDLs, ANSI and ATT. It doesn't matter which one you use. In fact you don't need to use either. If neither one is enabled the only downside is that the information is not available. If you choose to make use of the FDL feature You must configure it the same at both ends. They are very similar, but not compatable. By setting the FDL to ATT you matched the setting that was used at the other end, thus allowing the tech to see the line condition. Therefore it would only be necessary to invoke this command if you and your LEC or carrier are in agreement and will be looking at this info,