In the Cisco's ISDN World, the bri 0 interface shows the state of the D channel (the communication between the customer's ISDN device and the service provider ISDN switch). I would acknowledge the Bri0:1 & 2 in the down state, get notified if your main circuit goes down. Your B channels should go "normal". After you fail back to the main circuit you would have to acknowledge the Bri's again. Is it pretty method? No, but the map is telling you the real state and you are getting notified like you are suppose to be. If you have a dirty circuit and it keeps going up and down, get it fixed (you will have a history at least). The difference in code is like comparing apples and oranges. Cisco will tell you that IOS is IOS, but that's not the case. There's a big difference between a 2611 running 12.1(5) and a 2611XM running 12.2(13), so don't expect them to act the same.Hello again,
Just my opinion
thanks for that tip but I’m not really sure how this will work. I try to explain what you want me to do.
I should “acknowledge” the device with the B Channels down (which should be the correct state for a bri interface defined for backup with floating static routes). So my first problem is, that I can only acknowledge the whole device not just an interface.
Will my “acknowledge” by reset by the main link going down ?? Sorry I don’t really know what happens exactly with acknowledged devices.
Thanks in advance for any word helping my mind understanding you previous mail.
J. Brändle
Juergen Braendle wrote:
am 06.06.2003 16:56 Uhr schrieb Mark Persiko unter
[EMAIL PROTECTED]:
For the unused switch ports issue, hide the network bubbles corresponding toHello,
each switch port. This will get the switch out of warning status. Select the
bubbles and press Command-H in Classic (or Shift-Command-H in OS X) to hide
them.
It's me again....
The "hiding" stuff may be a solution but not for me...
If you hide the "bubbles" you always have to "unhide" them all at once if
you want to add something to a switchport. To much work needed for a often
changing network.
Also I often have the problem that after closing a map an opening it again
some or all of the hidden bubbles reappear by themselves.
For the administratively down interfaces on Cisco routers, what IOS versions
are you running? On my maps, if a router interface is administratively down,
it shows up with a light blue "X" across the link, by default. This is true
with IOS versions 11.0(8) through 12.2(16.a). Do your backup links stay
administratively down until turned on manually, or are they dial-backup and
thereby down until activated?
Sorry I may wrote something wrong the last time.
The interfaces were not administratively down.
If so the things you described happen.
I have defined a flowting static route for backup purposes on the isdn
interfaces. Below you can find two examples of two routers behaving
different to the Intermapper Cisco SNMP probes.
The one called buhalahr_test will show the two B-chanels down an therefore
with a red cross. The other one (st_blasien ) shows the two B-channels a up.
By the way most of the router (90 %) behave like the one with the two
B-channels up.
Ok... ;-) normally I would expect the interfaces down ...
But why will the cisco probe gets different results?
And what can I do that Intermapper will alarm me if the backup is up and
shows all ok if the backup isn't established.
Thanks for any help
Greetings
J. Brändle
----
#####################
buhalahr_test#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IK9O3S-M), Version 12.2(13)T1, RELEASE
SOFTWARE (fc1)
Image text-base: 0x80008098, data-base: 0x81A08694
System image file is "flash:c2600-ik9o3s-mz.122-13.T1.bin"
cisco 2611XM (MPC860P) processor (revision 0x100) with 93184K/5120K bytes of
memory.
Processor board ID JAD07090LCP (3782151446)
M860 processor: part number 5, mask 2
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
2 FastEthernet/IEEE 802.3 interface(s)
1 ISDN Basic Rate interface(s)
1 Virtual Private Network (VPN) Module(s)
32K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)
#####################
buhalahr_test#sh int bri 0/0
BRI0/0 is up, line protocol is up (spoofing)
Hardware is PQUICC BRI
Encapsulation PPP, loopback not set
#####################
buhalahr_test#sh int bri 0/0:1
BRI0/0:1 is down, line protocol is down
Hardware is PQUICC BRI
Encapsulation PPP, LCP Closed
Closed: IPCP, loopback not set
#####################
buhalahr_test#sh int bri 0/0:2
BRI0/0:2 is down, line protocol is down
Hardware is PQUICC BRI
Encapsulation PPP, LCP Closed
Closed: IPCP, loopback not set
#####################
interface BRI0/0
ip address xxx.xxx.xxx.xxx 255.255.255.0
encapsulation ppp
dialer map ip xxx.xxx.xxx.xxx name xxxxx 123456789
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap
#####################
ip route 0.0.0.0 0.0.0.0 "IP OTHER END OF ISDN" 200
#########################################
#########################################
#####################
st_blasien#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IK2S-M), Version 12.1(5)T10, RELEASE
SOFTWARE (fc2)
Image text-base: 0x80008088, data-base: 0x8117C39C
System image file is "flash:c2600-ik2s-mz_121-5_T10.bin"
cisco 2611 (MPC860) processor (revision 0x203) with 61440K/4096K bytes of
memory.
Processor board ID JAD05361124 (527900373)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
Basic Rate ISDN software, Version 1.1.
2 Ethernet/IEEE 802.3 interface(s)
1 ISDN Basic Rate interface(s)
1 Virtual Private Network (VPN) Module(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
#####################
st_blasien#sh int bri 0/0
BRI0/0 is up (spoofing), line protocol is up (spoofing)
Hardware is PQUICC BRI
Encapsulation PPP, loopback not set
#####################
st_blasien#sh int bri 0/0:1
BRI0/0:1 is down, line protocol is down
Hardware is PQUICC BRI
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Closed
Closed: IPCP, CDPCP
#####################
st_blasien#sh int bri 0/0:2
BRI0/0:2 is down, line protocol is down
Hardware is PQUICC BRI
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Closed
Closed: IPCP, CDPCP
#####################
interface BRI0/0
ip address xxx.xxx.xxx.xxx 255.255.255.0
encapsulation ppp
dialer map ip xxx.xxx.xxx.xxx name xxxxx 123456789
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap
#####################
ip route 0.0.0.0 0.0.0.0 "IP OTHER END OF ISDN" 200
Thanks,
Mark
____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
